Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
See `content/06-decision-tree.xml`. The tree maps observable signals (input shape, scope, evidence presence, owner presence, cadence status) to a concrete action, each leaf referencing a rule from `01
Imported from faionfaion/faion-network (skills/faion/knowledge/infra/capacity-safety-floor-policy/AGENTS.md). Install upstream with npx skills add faionfaion/faion-network --skill capacity-safety-floor-policy. Copyright stays with the author.
Capacity Safety-Floor Policy
Summary
One-sentence: Published policy file (YAML) that pins per-service safety-floor headroom thresholds, audit cadence, breach response, and the named owner — replaces tribal-knowledge thresholds.
One-paragraph: Published policy file (YAML) that pins per-service safety-floor headroom thresholds, audit cadence, breach response, and the named owner — replaces tribal-knowledge thresholds. The methodology pins the discipline that turns folklore into a reviewable, owned, version-controlled operating artefact: rule-bound output contract, evidence anchors, named owner, published review cadence. Outputs of the wrong shape are rejected at review; outputs without evidence are demoted to hypotheses; outputs without owners are tagged stale.
Applies If (ALL must hold)
Production service uses an autoscaler.
Capacity utilisation metrics are scraped + queryable.
There is a named SRE owner who can sign the policy.
Skip If (ANY kills it)
Service has no autoscaler — write one first or fix capacity at a static value.
Solo project with no measurable headroom requirement.
Capacity is bounded by a hardware limit not by policy (single appliance).
Ефективно для:
Production fleets з HPA / VMSS / ASG.
Команди де headroom thresholds живуть у головах SRE.
Validate artefact against the JSON Schema in content/02-output-contract.xml. Stdlib-only.
CI on artefact change; pre-commit.
Related
[[templates]]
Decision tree
See content/06-decision-tree.xml. The tree maps observable signals (input shape, scope, evidence presence, owner presence, cadence status) to a concrete action, each leaf referencing a rule from 01-core-rules.xml. Use it when in doubt about which variant of the methodology to apply.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
yaml
targets:
- https://api.opensmartroute.ai/api/v1/registry/faionfaion-faion-network-capacity-safety-floor-policy/manifest # or paste the manifest below
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
{
"ocm": "1",
"id": "faionfaion-faion-network-capacity-safety-floor-policy",
"kind": "skill",
"name": "capacity-safety-floor-policy",
"description": "See `content/06-decision-tree.xml`. The tree maps observable signals (input shape, scope, evidence presence, owner presence, cadence status) to a concrete action, each leaf referencing a rule from `01-core-rules.xml`. Use it when in doubt about which variant of the methodology to apply.",
"publisher": "faionfaion",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"github-agents"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"See `content/06-decision-tree.xml`. The tree maps observable signals (input shape, scope, evidence presence, owner presence, cadence status) to a concrete action, each leaf referencing a rule from `01-core-rules.xml`. Use it when in doubt about which variant of the methodology to apply."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-agents",
"repository": "https://github.com/faionfaion/faion-network",
"path": "skills/faion/knowledge/infra/capacity-safety-floor-policy/AGENTS.md",
"ref": "8e31684537e64d45c75264b1e0a2384f9b024a34",
"url": "https://github.com/faionfaion/faion-network/blob/8e31684537e64d45c75264b1e0a2384f9b024a34/skills/faion/knowledge/infra/capacity-safety-floor-policy/AGENTS.md",
"key": "faionfaion/faion-network/skills/faion/knowledge/infra/capacity-safety-floor-policy/AGENTS.md"
}
},
"instructions": "# Capacity Safety-Floor Policy\n\n## Summary\n\n**One-sentence:** Published policy file (YAML) that pins per-service safety-floor headroom thresholds, audit cadence, breach response, and the named owner — replaces tribal-knowledge thresholds.\n\n**One-paragraph:** Published policy file (YAML) that pins per-service safety-floor headroom thresholds, audit cadence, breach response, and the named owner — replaces tribal-knowledge thresholds. The methodology pins the discipline that turns folklore into a reviewable, owned, version-controlled operating artefact: rule-bound output contract, evidence anchor",
"cost": {
"context_tokens": 981
}
}
Fetch it by URL: GET /api/v1/registry/faionfaion-faion-network-capacity-safety-floor-policy/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.
