Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

spec-harness

by spec-familyversion 0.26.0i★ 0iRuns on your computerRepository ↗
Registry nameio.github.spec-family/spec-harness

How to install

What it does

Rounds of agent work under a brief: context to start, a check on each path, an audit at the end.

  • Connects Runs on your computer
  • Account or key No key needed
  • Category Other

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity22/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score34/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install spec-harness. Follow https://mcp.popnx.com/i/spec-family-spec-harness.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server spec-harness for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "spec-harness": { "command": "npx", "args": [ "-y", "@spec-family/spec-harness", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the spec-harness tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  3. Paste these settings and save the file

    {
      "mcpServers": {
        "spec-harness": {
          "command": "npx",
          "args": [
            "-y",
            "@spec-family/spec-harness",
            "mcp"
          ]
        }
      }
    }
  4. Quit Claude and open it again

  5. Try it

    Use spec-harness and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using spec-harness or shows a spec-harness tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect spec-harness yet

spec-harness runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect spec-harness

  • Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)

B · Others in Other that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server spec-harness for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user spec-harness -- npx -y @spec-family/spec-harness mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the spec-harness tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

    claude mcp add --scope user spec-harness -- npx -y @spec-family/spec-harness mcp
  4. Type /mcp in Claude Code

    You should see spec-harness listed as connected

  5. Try it

    Use spec-harness and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using spec-harness or shows a spec-harness tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server spec-harness for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "spec-harness": { "command": "npx", "args": [ "-y", "@spec-family/spec-harness", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the spec-harness tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  3. Open the AI chat in Cursor in Agent mode

  4. Try it

    Use spec-harness and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using spec-harness or shows a spec-harness tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server spec-harness for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "spec-harness": { "type": "stdio", "command": "npx", "args": [ "-y", "@spec-family/spec-harness", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the spec-harness tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  3. Open the AI chat in VS Code in Agent mode

  4. Try it

    Use spec-harness and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using spec-harness or shows a spec-harness tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use spec-harness💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user spec-harness -- npx -y @spec-family/spec-harness mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "spec-harness": {
      "command": "npx",
      "args": [
        "-y",
        "@spec-family/spec-harness",
        "mcp"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "spec-harness": {
      "command": "npx",
      "args": [
        "-y",
        "@spec-family/spec-harness",
        "mcp"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "spec-harness": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@spec-family/spec-harness",
        "mcp"
      ]
    }
  }
}

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
1,003/wk
Connection
Runs on your computer
Latest versioni
0.26.0
Categoryi
Other
Published to registryi
Nov 14, 2026
Code last changedi
Nov 14, 2026
Maker
spec-family
Packages
npm: @spec-family/spec-harness
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account spec-family, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 5 days ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for @spec-family/spec-harness@0.26.0

Checks only this package version, not every dependency · checked Nov 15, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/spec-family-spec-harness.svg)](https://mcp.popnx.com/en/servers/spec-family-spec-harness)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Otheri

  • More stars than 0% of the other 20613 servers in this category
  • Published to the registry more recently than 90% of the other 20613 servers in this category
  • Basic checks equal to or better than 99% of the other 20613 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is spec-harness safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 5 days ago, and the latest version (0.26.0) reached the registry 5 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

by koala73Widely used★ 90.9KUpdated 3 days ago

Runs in the cloud✓ service owner · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

by openstatusHQWidely used★ 9.3KUpdated 2 months ago

Runs in the cloud✓ service owner · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

by JanDeDobbeleerWidely used★ 23.8K Stars for the whole repoUpdated 30 days ago

Runs in the cloud✓ service owner · ohmyposh.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

by Klavis-AIGrowing★ 5.8KUpdated 14 months ago

Runs in the cloudRepo archived✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

by jitsucomWidely used★ 5.1KUpdated 4 months ago

Runs in the cloud✓ service owner · jitsu.com
Compared with similar ones
This one
spec-harness
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/34/44/44/41/44/4
LicenseMITAGPL-3.0AGPL-3.0MITApache-2.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

spec-harness

Rounds of agent work under a brief a person approved: what the agent needs to start, a guard on the agent's writes, an escalation a person signs when the brief is not enough, and an audit when it ends.

spec-harness is the agent-facing member of the spec-\* tools. It calls no model and writes no content - the agent is the model. It gives the agent the contract and the facts, and answers, the same way every time, whether the agent stayed inside the lines. No runtime dependencies, no account, no network.

The family's words - brief, round, wave, ruling, premise, the two kinds of plugin - are defined in concepts, and the tutorial takes one round from the brief to the archive in ten steps. This README is the front page; the reference has every command, flag, hook, MCP tool, configuration key and doctor check.

Quick start

npm install --save-dev @spec-family/spec-harness @spec-family/spec-brief

npx --no-install @spec-family/spec-harness init # the plan: what it would configure, and why npx --no-install @spec-family/spec-harness init --write # apply it

In a repository made with git init on main, with no remote yet, the plan reads:

run     .spec-brief.json

spec-brief init: the brief and archive directories, every default spelled out update .spec-brief.json load spec-harness's plugin, "@spec-family/spec-harness/spec-brief-plugin": spec-brief's archive asks it whether a signed ruling allows a protected file, and refuses the file without it; measure the archive from main, as spec-harness does: without a base, spec-brief's archive warns that the scope went unmeasured and checks no protected file create .spec-harness.json rounds are measured from main, the branch init runs on: no remote records a default branch (refs/remotes/origin/HEAD); change "base" if rounds merge into another create .claude/settings.json the guard hooks, run with node from the project's install: a PreToolUse hook refuses writes to protected files; a PostToolUse hook warns about writes outside the scope; a SessionStart hook says, as a session starts, what would hold every write of it create .mcp.json the spec-harness MCP server, run with node from the project's install: start_round, check_path, request_escalation, audit_round, list_rounds advise .git/hooks/pre-commit no pre-commit hook runs spec-harness: one refuses a commit that changes what the active brief protects, for any agent or none, a shell's writes included; run spec-harness init --git-hook --write to add it advise .github/allowed_signers rulings count only when signed by a key listed here on the base branch: one line per person, namespaces="git" . Where an agent runs as the person, make it a FIDO2 key, ssh-keygen -t ed25519-sk, whose signature needs a touch no process can supply. Have the forge protect this file, the ADRs, the tool configurations and the CI configuration, so no change to them reaches the base branch without a person, and check each change in CI against the base branch's rules: on GitHub, CODEOWNERS and a protected branch; on GitLab Premium, Code Owners; on GitLab Free, a protected branch no one pushes to, merged by Maintainers, agents as Developers, and pipelines that must succeed. spec-core's docs/adopting.md has the settings

Nothing was changed. Run again with --write to apply the plan.

Then a brief: npx --no-install @spec-family/spec-brief new "Rotate tokens" scaffolds briefs/001_rotate-tokens.md, and a person fills it in and makes it active, here with affectedFiles: ["src/auth/**"] and protectedFiles: ["src/db/schema.ts"]. On its branch the guard answers for any path:

git switch -c brief/001-rotate-tokens

npx --no-install @spec-family/spec-harness guard src/db/schema.ts src/auth/token.ts README.md

refused  brief 001 does not empower this round to change src/db/schema.ts (protectedFiles: src/db/schema.ts)

if the round cannot be done without it, stop and ask for a ruling: spec-harness escalate --path --reason , or the request_escalation tool ok src/auth/token.ts is in brief 001's scope (src/auth/) warning README.md is outside brief 001's scope, which covers src/auth/ if the round needs it, say so in briefs/001_rotate-tokens.md and add it to affectedFiles; the archive reports every file outside the scope that the round commits

That exits 1. Claude Code asks the same before every Edit and Write, through the hook init wrote, and the refused write never happens; Claude reads why, and the next step:

{"hookSpecificOutput":{"hookEventName":"PreToolUse","permissionDecision":"deny","permissionDecisionReason":"spec-harness: brief 001 does not empower this round to change src/db/schema.ts (protectedFiles: src/db/schema.ts). Next: if the round cannot be done without it, stop and ask for a ruling: spec-harness escalate --path <file> --reason <why>, or the request_escalation tool."}}

A repository that is not Node installs the tools the same way, from a package.json that holds { "private": true } (Installing).

Names

The package is @spec-family/spec-harness, and the command it installs is spec-harness. The name without the scope is not this project: on npm, spec-harness is another publisher's package, and it installs a command of the same name. So give npx the full name:

  • npx --no-install @spec-family/spec-harness in a project that installed it runs that install, the version the lockfile pins, and where there is none it stops with an error that names this package. Every command in this README, in the reference and in the skills is written so.
  • npx @spec-family/spec-harness, without --no-install, fetches this package where nothing is installed: for a look at --help, and little else.

Never npx spec-harness, and not npx --no-install spec-harness either: npm still runs a copy of the other package that an earlier fetch left in its cache. Names has how to clear that cache, and the same for the siblings' names.

Requirements

  • spec-brief 0.12.0 or later, required: the brief is the contract, and spec-brief is its reader.
  • spec-guard 0.30.0 and spec-graph 0.21.0 or later, used when they are installed. Their absence is reported, never assumed clean.
  • Claude Code 2.1.139 or later runs the guard hooks and the Claude Code plugin's server; an older one runs every write unguarded, so doctor checks the one on PATH.
  • git 2.31 or later, and Node 22 or later.

A sibling installed below its minimum is never run: doctor and every command that needed it name the minimum. Installing has why each release is the floor.

A round

person approves brief 012 ─▶ agent on branch brief/012-rotate-tokens

│ spec-harness context ◀─┘ the brief, its scope, signed rulings, │ the rules in force, the documents it cites ▼ agent edits ── hook: protected? refused, with the next step │ outside the scope? a warning after the write │ ├── needs a protected file ─▶ escalate ─▶ person rules, signs ▼ spec-harness audit ─▶ spec-brief archive --dry-run ─▶ person archives

The round's brief is named, never guessed: --brief , then SPEC_BRIEF, then the branch, brief/{id}, brief-{id}, */brief/{id} or */brief-{id}, so claude/brief-042-rotate-tokens is brief 042. A name that names no brief is not passed over for the next. A round has the order in full, the branch a forge's CI names on a detached HEAD, worktrees and the branches an app makes, and what each layer catches of a session that writes through a shell.

Commands

In the order a round meets them; init and doctor set a repository up and check it. Each heading's page in the reference has the whole of it.

context [brief]

The packet an agent starts a round with: the brief in full - it is the contract - then the files it may write and must not change, the rulings already signed, the briefs it depends on, the architecture rules spec-guard holds over its scope, and the documents it cites, whole, up to a budget. What could not be read is named, never left out (context).

guard and the hooks

May the round write this?

The pathThe answer
one the brief protectsRefused, unless a signed ruling allows it.
one in affectedFilesAllowed.
anything elseOutside the scope: a warning by default, or a question to the person, or a refusal (outOfScope: warn, ask, deny).

The hooks ask it of every write:

WhenThe hookWhat it does
Before an Edit, Write, MultiEdit or NotebookEdithook claude, Claude Code's PreToolUseRefuses a write to a protected file, with the reason and the next step. It never answers allow, which would skip the person's own permission prompt.
After such a writehook claude, PostToolUseWarns Claude of a write outside the scope.
As a session startshook claude, SessionStartSays in one line what would hold every write of the session. It holds nothing.
As a turn ends, with "turnReport": truehook claude, StopReports every changed path the brief protects or that is outside its scope, a shell's writes among them.
Before Codex's apply_patch, or a shell command that hands it a patchhook codex, Codex's PreToolUse, from .codex/hooks.jsonRefuses a write to a protected file, with the reason and the next step.
Before Copilot creates or edits a filehook copilot, Copilot's preToolUse, from .github/hooks/spec-harness.jsonThe same, as Copilot reads it.
Before a commithook git, git's pre-commit, from init --git-hookRefuses a commit that changes a protected file, for any agent or none.

A guard is a guardrail - an agent that writes through a shell passes it - so the audit and spec-brief's archive are the gates (guard and the hooks).

The write guard covers Claude Code, and Codex and Copilot by their documentation. hook codex and hook copilot answer each agent in its own language, as its hooks reference describes it (read 2026-11-12), and are tested against the shapes it documents; neither agent was run against them. Other agents have hooks that can hold a write, each in a language of its own. By their documentation, GitHub Copilot and Cursor also read .claude/settings.json and run the line init wrote there, and neither reads its answer: Copilot would hold every edit, whatever hook copilot answers, and Cursor let every one through. hook claude says so in one line where the question carries another agent's fields, and checks nothing for it. For any agent, git's pre-commit hook from init --git-hook, the audit and spec-brief's archive hold.

escalate, rule, rulings

When the round cannot be done without a protected file, the agent writes a memo and stops; a person rules, and signs:

# the agent

npx --no-install @spec-family/spec-harness escalate --path src/db/schema.ts \ --reason "Rotation needs a rotated_at column." \ --option "Allow: one additive column" --option "Refuse: rotation keeps no timestamp" \

Only the beginning is shown; read the rest in the repo