Use cases
Each use case below states only what the released tools do today, links the guide and the tagged release that show it, and says what is not built or not part of SteerSpec. The guides cover the tagged strspc release and strspc-sync release.
SteerSpec does not store or recall what an agent did in a session. Today it holds rules, checks changes against them in CI, and distributes and monitors config files.
// Engineer running several agents
“I run several coding agents across a few repos. Each one follows whichever rules file it reads, and nothing tells me which version that was.”
What SteerSpec does today. Holds your rules as plain JSON files in a realm, versioned in git. Once a rule is Published, strspc diff rejects an edit to its body with RD002, so you supersede the rule instead. strspc ci init writes the GitHub Actions workflow that lints the rules on pull requests.
Evidence. SteerSpec 101, step 6 (a Published rule resists change) · strspc release
Not yet, or not part of SteerSpec. SteerSpec does not store or recall what an agent did in a session. It holds rules, checks them with strspc and distributes config files; it does not make an agent follow a rule on its own.
// Platform lead
“Dozens of our repos each carry their own CLAUDE.md, agents and settings. A fix in one repo never reaches the rest, and I find out about edits late.”
What SteerSpec does today. strspc-sync renders the shared part of CLAUDE.md from a template in one central repo and proposes it to each target repo as a pull request that the repo’s owners review; it never force-pushes and never merges. The monitor opens one GitHub issue for each repo and template whose copy differs, on a schedule. The quickstart configuration also distributes agents, skills and settings. Both guides are written from the strspc-sync documentation and source, not from a live run.
Evidence. Keep CLAUDE.md consistent across repos · Detect drift in AI agent config files · strspc-sync release
Not yet, or not part of SteerSpec. In the strspc-sync sources of the release linked here, the rule MNRACT-006 says the drift issues open in the central repo and the quickstart workflow comment says the target repos. Its rules are Draft.
// Engineering manager or CTO
“I need to know which rules our teams' agents are held to, and that a change to them goes through review like any other change.”
What SteerSpec does today. Rules are plain JSON files in git, so a change to a rule is a pull request. strspc ci init writes a GitHub Actions workflow that runs on pushes to the default branch (main unless --branch says otherwise) and on pull requests that target it; its --dry-run prints the workflow without writing it. Shared config files reach each repo by pull request through strspc-sync.
Evidence. SteerSpec 101, step 7 (CI and sync) · Keep CLAUDE.md consistent across repos · strspc release
Not yet, or not part of SteerSpec. The 101 prints the workflow with --dry-run and does not show a CI run. The sync guide is written from the strspc-sync documentation, not a live run. The cloud API is planned, not available.
// Standards body or compliance lead
“I need to record which external standard our rules cite, and which rule maps which clause.”
What SteerSpec does today. Declare a standard on a realm or an entity, with the relation implements or derived_from. Map a rule to a clause with a standard note, <id>:<clause>. strspc lint and strspc realm validate check the form of both, and strspc standards coverage lists each mapped clause as covered, mapped, lapsed or cited. A mapping is a reference you declare: SteerSpec does not read the standard or assess rules against it, and covered means a mapped rule is Implemented, not that the clause is met. strspc standards coverage can also fail a CI build when coverage weakens.
Evidence. Map rules to a standard · Standards as realms · strspc release
Not yet, or not part of SteerSpec. No Standard Realm is published yet, so SteerSpec holds no clause lists. The crosswalk between editions of a standard is not built. The rules behind the mapping (STDREF, STDRLM) are Draft.
// Solo developer growing into a team
“It is me and one CLAUDE.md today. Soon there will be more of us, and what I remember will not be enough.”
What SteerSpec does today. You can start with one realm in your own repo: a rule starts as Draft, Published fixes its text, and strspc diff rejects an edit to a Published body. Add the CI check when a second person joins. strspc-sync works without the rest of SteerSpec, so sharing config across repos is a separate, later step.
Evidence. SteerSpec 101 · strspc release
Not yet, or not part of SteerSpec. The 101 covers one realm in one repo, from a real run. Sharing config across repos is the strspc-sync guide, which is written from documentation, not a live run.