Diagnostic and repair reference

Every stable diagnostic code and its policy-preserving repair actions.

Structured failures

201 diagnostics · catalog identity ac29b5e4a8f71bf9dbc88819d4baaad58e41b37b296693f8ab67e258c39ae2a7

Repairs are conditional plans, not permission to bypass policy or obligations. Re-check identity and preconditions before automation.

canonicalization

Code	Severity	Safe action
canon/coreform	error	canonicalize-input
fmt/not-canonical	error	canonicalize-input

canon/coreform

Severity: error · ID: genesis/diagnostic/v1/canon/coreform

Likely causes

• Input is not valid canonical CoreForm.
• Formatting would change the checked artifact.

Safe repairs

• canonicalize-input (not automatic; review required): Run the formatter on the reported source, review the deterministic diff, and retry the same check.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

fmt/not-canonical

Severity: error · ID: genesis/diagnostic/v1/fmt/not-canonical

Likely causes

• Input is not valid canonical CoreForm.
• Formatting would change the checked artifact.

Safe repairs

• canonicalize-input (not automatic; review required): Run the formatter on the reported source, review the deterministic diff, and retry the same check.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

debugging

Code	Severity	Safe action
debug/bisect	error	regenerate-debug-artifact
debug/break	error	regenerate-debug-artifact
debug/continue	error	regenerate-debug-artifact
debug/frames	error	regenerate-debug-artifact
debug/inspect	error	regenerate-debug-artifact
debug/match	error	regenerate-debug-artifact
debug/step	error	regenerate-debug-artifact
debug/timeline	error	regenerate-debug-artifact
debug/trace	error	regenerate-debug-artifact

debug/bisect

Severity: error · ID: genesis/diagnostic/v1/debug/bisect

Likely causes

• A trace, timeline, cursor, frame, breakpoint, or matcher does not satisfy the debugger contract.
• The inspected artifact is stale, malformed, or outside its valid bounds.

Safe repairs

• regenerate-debug-artifact (automatic eligible; review not required by catalog): Regenerate the bounded trace or timeline from the current program, then retry the exact debugger operation.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

debug/break

Severity: error · ID: genesis/diagnostic/v1/debug/break

Likely causes

• A trace, timeline, cursor, frame, breakpoint, or matcher does not satisfy the debugger contract.
• The inspected artifact is stale, malformed, or outside its valid bounds.

Safe repairs

• regenerate-debug-artifact (automatic eligible; review not required by catalog): Regenerate the bounded trace or timeline from the current program, then retry the exact debugger operation.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

debug/continue

Severity: error · ID: genesis/diagnostic/v1/debug/continue

Likely causes

• A trace, timeline, cursor, frame, breakpoint, or matcher does not satisfy the debugger contract.
• The inspected artifact is stale, malformed, or outside its valid bounds.

Safe repairs

• regenerate-debug-artifact (automatic eligible; review not required by catalog): Regenerate the bounded trace or timeline from the current program, then retry the exact debugger operation.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

debug/frames

Severity: error · ID: genesis/diagnostic/v1/debug/frames

Likely causes

• A trace, timeline, cursor, frame, breakpoint, or matcher does not satisfy the debugger contract.
• The inspected artifact is stale, malformed, or outside its valid bounds.

Safe repairs

• regenerate-debug-artifact (automatic eligible; review not required by catalog): Regenerate the bounded trace or timeline from the current program, then retry the exact debugger operation.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

debug/inspect

Severity: error · ID: genesis/diagnostic/v1/debug/inspect

Likely causes

• A trace, timeline, cursor, frame, breakpoint, or matcher does not satisfy the debugger contract.
• The inspected artifact is stale, malformed, or outside its valid bounds.

Safe repairs

• regenerate-debug-artifact (automatic eligible; review not required by catalog): Regenerate the bounded trace or timeline from the current program, then retry the exact debugger operation.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

debug/match

Severity: error · ID: genesis/diagnostic/v1/debug/match

Likely causes

• A trace, timeline, cursor, frame, breakpoint, or matcher does not satisfy the debugger contract.
• The inspected artifact is stale, malformed, or outside its valid bounds.

Safe repairs

• regenerate-debug-artifact (automatic eligible; review not required by catalog): Regenerate the bounded trace or timeline from the current program, then retry the exact debugger operation.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

debug/step

Severity: error · ID: genesis/diagnostic/v1/debug/step

Likely causes

• A trace, timeline, cursor, frame, breakpoint, or matcher does not satisfy the debugger contract.
• The inspected artifact is stale, malformed, or outside its valid bounds.

Safe repairs

• regenerate-debug-artifact (automatic eligible; review not required by catalog): Regenerate the bounded trace or timeline from the current program, then retry the exact debugger operation.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

debug/timeline

Severity: error · ID: genesis/diagnostic/v1/debug/timeline

Likely causes

• A trace, timeline, cursor, frame, breakpoint, or matcher does not satisfy the debugger contract.
• The inspected artifact is stale, malformed, or outside its valid bounds.

Safe repairs

• regenerate-debug-artifact (automatic eligible; review not required by catalog): Regenerate the bounded trace or timeline from the current program, then retry the exact debugger operation.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

debug/trace

Severity: error · ID: genesis/diagnostic/v1/debug/trace

Likely causes

• A trace, timeline, cursor, frame, breakpoint, or matcher does not satisfy the debugger contract.
• The inspected artifact is stale, malformed, or outside its valid bounds.

Safe repairs

• regenerate-debug-artifact (automatic eligible; review not required by catalog): Regenerate the bounded trace or timeline from the current program, then retry the exact debugger operation.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

effects

Code	Severity	Safe action
bridge/dispatch	error	inspect-effect-boundary
effects/run	error	inspect-effect-boundary
net/cleanup	error	inspect-effect-boundary

bridge/dispatch

Severity: error · ID: genesis/diagnostic/v1/bridge/dispatch

Likely causes

• An effect program or host bridge failed at the deny-by-default runner boundary.
• The effect payload, host response, or resource cleanup violated its contract.

Safe repairs

• inspect-effect-boundary (not automatic; review required): Inspect the operation, capability decision, sealed error, and cleanup context; preserve the policy unless a separate review authorizes change.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

effects/run

Severity: error · ID: genesis/diagnostic/v1/effects/run

Likely causes

• An effect program or host bridge failed at the deny-by-default runner boundary.
• The effect payload, host response, or resource cleanup violated its contract.

Safe repairs

• inspect-effect-boundary (not automatic; review required): Inspect the operation, capability decision, sealed error, and cleanup context; preserve the policy unless a separate review authorizes change.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

net/cleanup

Severity: error · ID: genesis/diagnostic/v1/net/cleanup

Likely causes

• An effect program or host bridge failed at the deny-by-default runner boundary.
• The effect payload, host response, or resource cleanup violated its contract.

Safe repairs

• inspect-effect-boundary (not automatic; review required): Inspect the operation, capability decision, sealed error, and cleanup context; preserve the policy unless a separate review authorizes change.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

evaluation

Code	Severity	Safe action
eval/error	error	inspect-evaluation-trace

eval/error

Severity: error · ID: genesis/diagnostic/v1/eval/error

Likely causes

• Evaluation reached an invalid form, value, call, or resource boundary.
• A runtime precondition was not established by the program.

Safe repairs

• inspect-evaluation-trace (automatic eligible; review not required by catalog): Inspect structured context and a bounded debug trace, repair the smallest failing expression, and rerun.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

internal

Code	Severity	Safe action
diagnostic/catalog-miss	error	report-catalog-violation
error/unknown	error	report-catalog-violation

diagnostic/catalog-miss

Severity: error · ID: genesis/diagnostic/v1/diagnostic/catalog-miss

Likely causes

• Production emitted an uncataloged diagnostic or could not identify a structured failure.
• An internal invariant failed before a more specific diagnostic was available.

Safe repairs

• report-catalog-violation (automatic eligible; review not required by catalog): Preserve the original code and context, run the diagnostic catalog gate, and report this as an implementation defect.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

error/unknown

Severity: error · ID: genesis/diagnostic/v1/error/unknown

Likely causes

• Production emitted an uncataloged diagnostic or could not identify a structured failure.
• An internal invariant failed before a more specific diagnostic was available.

Safe repairs

• report-catalog-violation (automatic eligible; review not required by catalog): Preserve the original code and context, run the diagnostic catalog gate, and report this as an implementation defect.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

invocation

Code	Severity	Safe action
agent-index/card-invalid	error	inspect-invocation-contract
agent-index/diagnostic-catalog-invalid	error	inspect-invocation-contract
agent-index/diagnostic-invalid	error	inspect-invocation-contract
agent-index/diagnostic-not-found	error	inspect-invocation-contract
agent-index/search-invalid	error	inspect-invocation-contract
agent-index/symbol-index-invalid	error	inspect-invocation-contract
agent-index/symbol-invalid	error	inspect-invocation-contract
agent-index/symbol-not-found	error	inspect-invocation-contract
agent-plan/task-cards	error	inspect-invocation-contract
bench/authority-root-missing	error	inspect-invocation-contract
bench/crypto-dispatch	error	inspect-invocation-contract
bench/current-directory	error	inspect-invocation-contract
bench/driver-invalid	error	inspect-invocation-contract
bench/driver-spawn	error	inspect-invocation-contract
bench/executable-unavailable	error	inspect-invocation-contract
bench/front-door-failed	error	inspect-invocation-contract
bench/open-agent-dispatch	error	inspect-invocation-contract
bench/output-invalid	error	inspect-invocation-contract
bench/output-limit	error	inspect-invocation-contract
bench/selfhost-artifact-required	error	inspect-invocation-contract
compat/rust-engine-disabled	error	inspect-invocation-contract
engine/rust-disabled	error	inspect-invocation-contract
mcp/input	error	inspect-invocation-contract
mcp/interface-invalid	error	inspect-invocation-contract
mcp/limit-invalid	error	inspect-invocation-contract
mcp/output	error	inspect-invocation-contract
mcp/resource-limit	error	inspect-invocation-contract
mcp/workspace-root	error	inspect-invocation-contract
prelude/missing	error	inspect-invocation-contract
warm/argv-parse	error	inspect-invocation-contract
warm/max-frame-bytes	error	inspect-invocation-contract
warm/max-queue	error	inspect-invocation-contract
warm/max-workspaces	error	inspect-invocation-contract
warm/nested	error	inspect-invocation-contract
warm/reader-launch	error	inspect-invocation-contract
warm/resource-limit	error	inspect-invocation-contract
warm/resource-override	error	inspect-invocation-contract
warm/workspace-escape	error	inspect-invocation-contract
warm/workspace-limit	error	inspect-invocation-contract
warm/workspace-path	error	inspect-invocation-contract
warm/workspace-path-escape	error	inspect-invocation-contract
warm/workspace-rebind	error	inspect-invocation-contract
warm/workspace-root	error	inspect-invocation-contract
warm/workspace-unavailable	error	inspect-invocation-contract

agent-index/card-invalid

Severity: error · ID: genesis/diagnostic/v1/agent-index/card-invalid

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

agent-index/diagnostic-catalog-invalid

Severity: error · ID: genesis/diagnostic/v1/agent-index/diagnostic-catalog-invalid

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

agent-index/diagnostic-invalid

Severity: error · ID: genesis/diagnostic/v1/agent-index/diagnostic-invalid

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

agent-index/diagnostic-not-found

Severity: error · ID: genesis/diagnostic/v1/agent-index/diagnostic-not-found

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

agent-index/search-invalid

Severity: error · ID: genesis/diagnostic/v1/agent-index/search-invalid

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

agent-index/symbol-index-invalid

Severity: error · ID: genesis/diagnostic/v1/agent-index/symbol-index-invalid

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

agent-index/symbol-invalid

Severity: error · ID: genesis/diagnostic/v1/agent-index/symbol-invalid

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

agent-index/symbol-not-found

Severity: error · ID: genesis/diagnostic/v1/agent-index/symbol-not-found

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

agent-plan/task-cards

Severity: error · ID: genesis/diagnostic/v1/agent-plan/task-cards

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

bench/authority-root-missing

Severity: error · ID: genesis/diagnostic/v1/bench/authority-root-missing

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

bench/crypto-dispatch

Severity: error · ID: genesis/diagnostic/v1/bench/crypto-dispatch

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

bench/current-directory

Severity: error · ID: genesis/diagnostic/v1/bench/current-directory

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

bench/driver-invalid

Severity: error · ID: genesis/diagnostic/v1/bench/driver-invalid

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

bench/driver-spawn

Severity: error · ID: genesis/diagnostic/v1/bench/driver-spawn

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

bench/executable-unavailable

Severity: error · ID: genesis/diagnostic/v1/bench/executable-unavailable

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

bench/front-door-failed

Severity: error · ID: genesis/diagnostic/v1/bench/front-door-failed

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

bench/open-agent-dispatch

Severity: error · ID: genesis/diagnostic/v1/bench/open-agent-dispatch

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

bench/output-invalid

Severity: error · ID: genesis/diagnostic/v1/bench/output-invalid

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

bench/output-limit

Severity: error · ID: genesis/diagnostic/v1/bench/output-limit

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

bench/selfhost-artifact-required

Severity: error · ID: genesis/diagnostic/v1/bench/selfhost-artifact-required

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

compat/rust-engine-disabled

Severity: error · ID: genesis/diagnostic/v1/compat/rust-engine-disabled

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

engine/rust-disabled

Severity: error · ID: genesis/diagnostic/v1/engine/rust-disabled

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

mcp/input

Severity: error · ID: genesis/diagnostic/v1/mcp/input

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

mcp/interface-invalid

Severity: error · ID: genesis/diagnostic/v1/mcp/interface-invalid

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

mcp/limit-invalid

Severity: error · ID: genesis/diagnostic/v1/mcp/limit-invalid

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

mcp/output

Severity: error · ID: genesis/diagnostic/v1/mcp/output

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

mcp/resource-limit

Severity: error · ID: genesis/diagnostic/v1/mcp/resource-limit

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

mcp/workspace-root

Severity: error · ID: genesis/diagnostic/v1/mcp/workspace-root

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

prelude/missing

Severity: error · ID: genesis/diagnostic/v1/prelude/missing

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

warm/argv-parse

Severity: error · ID: genesis/diagnostic/v1/warm/argv-parse

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

warm/max-frame-bytes

Severity: error · ID: genesis/diagnostic/v1/warm/max-frame-bytes

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

warm/max-queue

Severity: error · ID: genesis/diagnostic/v1/warm/max-queue

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

warm/max-workspaces

Severity: error · ID: genesis/diagnostic/v1/warm/max-workspaces

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

warm/nested

Severity: error · ID: genesis/diagnostic/v1/warm/nested

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

warm/reader-launch

Severity: error · ID: genesis/diagnostic/v1/warm/reader-launch

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

warm/resource-limit

Severity: error · ID: genesis/diagnostic/v1/warm/resource-limit

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

warm/resource-override

Severity: error · ID: genesis/diagnostic/v1/warm/resource-override

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

warm/workspace-escape

Severity: error · ID: genesis/diagnostic/v1/warm/workspace-escape

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

warm/workspace-limit

Severity: error · ID: genesis/diagnostic/v1/warm/workspace-limit

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

warm/workspace-path

Severity: error · ID: genesis/diagnostic/v1/warm/workspace-path

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

warm/workspace-path-escape

Severity: error · ID: genesis/diagnostic/v1/warm/workspace-path-escape

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

warm/workspace-rebind

Severity: error · ID: genesis/diagnostic/v1/warm/workspace-rebind

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

warm/workspace-root

Severity: error · ID: genesis/diagnostic/v1/warm/workspace-root

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

warm/workspace-unavailable

Severity: error · ID: genesis/diagnostic/v1/warm/workspace-unavailable

Likely causes

• The requested command, profile, or embedded agent authority is unavailable or inconsistent.
• An exact lookup or invocation precondition was not satisfied.

Safe repairs

• inspect-invocation-contract (automatic eligible; review not required by catalog): Inspect the exact command schema or agent index record, correct only the rejected input, and retry.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

io

Code	Severity	Safe action
io/cwd	error	verify-io-preconditions
io/error	error	verify-io-preconditions
io/mkdir	error	verify-io-preconditions
io/read	error	verify-io-preconditions
io/store	error	verify-io-preconditions
io/write	error	verify-io-preconditions

io/cwd

Severity: error · ID: genesis/diagnostic/v1/io/cwd

Likely causes

• A base-relative path is missing, inaccessible, or outside the active sandbox.
• A deterministic filesystem operation failed.

Safe repairs

• verify-io-preconditions (automatic eligible; review not required by catalog): Verify the reported base-relative path, permissions, and sandbox boundary, then retry without widening access.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

io/error

Severity: error · ID: genesis/diagnostic/v1/io/error

Likely causes

• A base-relative path is missing, inaccessible, or outside the active sandbox.
• A deterministic filesystem operation failed.

Safe repairs

• verify-io-preconditions (automatic eligible; review not required by catalog): Verify the reported base-relative path, permissions, and sandbox boundary, then retry without widening access.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

io/mkdir

Severity: error · ID: genesis/diagnostic/v1/io/mkdir

Likely causes

• A base-relative path is missing, inaccessible, or outside the active sandbox.
• A deterministic filesystem operation failed.

Safe repairs

• verify-io-preconditions (automatic eligible; review not required by catalog): Verify the reported base-relative path, permissions, and sandbox boundary, then retry without widening access.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

io/read

Severity: error · ID: genesis/diagnostic/v1/io/read

Likely causes

• A base-relative path is missing, inaccessible, or outside the active sandbox.
• A deterministic filesystem operation failed.

Safe repairs

• verify-io-preconditions (automatic eligible; review not required by catalog): Verify the reported base-relative path, permissions, and sandbox boundary, then retry without widening access.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

io/store

Severity: error · ID: genesis/diagnostic/v1/io/store

Likely causes

• A base-relative path is missing, inaccessible, or outside the active sandbox.
• A deterministic filesystem operation failed.

Safe repairs

• verify-io-preconditions (automatic eligible; review not required by catalog): Verify the reported base-relative path, permissions, and sandbox boundary, then retry without widening access.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

io/write

Severity: error · ID: genesis/diagnostic/v1/io/write

Likely causes

• A base-relative path is missing, inaccessible, or outside the active sandbox.
• A deterministic filesystem operation failed.

Safe repairs

• verify-io-preconditions (automatic eligible; review not required by catalog): Verify the reported base-relative path, permissions, and sandbox boundary, then retry without widening access.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

obligation

Code	Severity	Safe action
obligation/stage1-validation	error	resolve-obligation
obligation/translation-validation	error	resolve-obligation
opt/error	error	resolve-obligation
test/error	error	resolve-obligation
typecheck/error	error	resolve-obligation

obligation/stage1-validation

Severity: error · ID: genesis/diagnostic/v1/obligation/stage1-validation

Likely causes

• A type, proof, test, optimization, or translation obligation did not hold.
• Required evidence is missing, stale, or mismatched.

Safe repairs

• resolve-obligation (automatic eligible; review not required by catalog): Inspect the named obligation artifact, repair the source or proof, and rerun the exact verification command.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

obligation/translation-validation

Severity: error · ID: genesis/diagnostic/v1/obligation/translation-validation

Likely causes

• A type, proof, test, optimization, or translation obligation did not hold.
• Required evidence is missing, stale, or mismatched.

Safe repairs

• resolve-obligation (automatic eligible; review not required by catalog): Inspect the named obligation artifact, repair the source or proof, and rerun the exact verification command.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

opt/error

Severity: error · ID: genesis/diagnostic/v1/opt/error

Likely causes

• A type, proof, test, optimization, or translation obligation did not hold.
• Required evidence is missing, stale, or mismatched.

Safe repairs

• resolve-obligation (automatic eligible; review not required by catalog): Inspect the named obligation artifact, repair the source or proof, and rerun the exact verification command.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

test/error

Severity: error · ID: genesis/diagnostic/v1/test/error

Likely causes

• A type, proof, test, optimization, or translation obligation did not hold.
• Required evidence is missing, stale, or mismatched.

Safe repairs

• resolve-obligation (automatic eligible; review not required by catalog): Inspect the named obligation artifact, repair the source or proof, and rerun the exact verification command.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

typecheck/error

Severity: error · ID: genesis/diagnostic/v1/typecheck/error

Likely causes

• A type, proof, test, optimization, or translation obligation did not hold.
• Required evidence is missing, stale, or mismatched.

Safe repairs

• resolve-obligation (automatic eligible; review not required by catalog): Inspect the named obligation artifact, repair the source or proof, and rerun the exact verification command.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

package

Code	Severity	Safe action
pkg/abi	error	verify-package-state
pkg/assurance-pack	error	verify-package-state
pkg/build	error	verify-package-state
pkg/dispatch-drift	error	verify-package-state
pkg/env	error	verify-package-state
pkg/env-hydrate	error	verify-package-state
pkg/error	error	verify-package-state
pkg/import	error	verify-package-state
pkg/migrate	error	verify-package-state
pkg/new	error	verify-package-state
pkg/profile-runtime	error	verify-package-state
pkg/qualify	error	verify-package-state
pkg/remove	error	verify-package-state
pkg/run	error	verify-package-state
pkg/run-contract	error	verify-package-state
pkg/scaffold	error	verify-package-state
pkg/self-optimize	error	verify-package-state
pkg/spec	error	verify-package-state
pkg/trace	error	verify-package-state

pkg/abi

Severity: error · ID: genesis/diagnostic/v1/pkg/abi

Likely causes

• Package metadata, lock state, dependency evidence, or frontend dispatch is invalid.
• The requested package lifecycle transition cannot be verified.

Safe repairs

• verify-package-state (automatic eligible; review not required by catalog): Inspect package and lock diagnostics, repair the declared input, and regenerate only derived package artifacts.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

pkg/assurance-pack

Severity: error · ID: genesis/diagnostic/v1/pkg/assurance-pack

Likely causes

• Package metadata, lock state, dependency evidence, or frontend dispatch is invalid.
• The requested package lifecycle transition cannot be verified.

Safe repairs

• verify-package-state (automatic eligible; review not required by catalog): Inspect package and lock diagnostics, repair the declared input, and regenerate only derived package artifacts.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

pkg/build

Severity: error · ID: genesis/diagnostic/v1/pkg/build

Likely causes

• Package metadata, lock state, dependency evidence, or frontend dispatch is invalid.
• The requested package lifecycle transition cannot be verified.

Safe repairs

• verify-package-state (automatic eligible; review not required by catalog): Inspect package and lock diagnostics, repair the declared input, and regenerate only derived package artifacts.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

pkg/dispatch-drift

Severity: error · ID: genesis/diagnostic/v1/pkg/dispatch-drift

Likely causes

• Package metadata, lock state, dependency evidence, or frontend dispatch is invalid.
• The requested package lifecycle transition cannot be verified.

Safe repairs

• verify-package-state (automatic eligible; review not required by catalog): Inspect package and lock diagnostics, repair the declared input, and regenerate only derived package artifacts.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

pkg/env

Severity: error · ID: genesis/diagnostic/v1/pkg/env

Likely causes

• Package metadata, lock state, dependency evidence, or frontend dispatch is invalid.
• The requested package lifecycle transition cannot be verified.

Safe repairs

• verify-package-state (automatic eligible; review not required by catalog): Inspect package and lock diagnostics, repair the declared input, and regenerate only derived package artifacts.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

pkg/env-hydrate

Severity: error · ID: genesis/diagnostic/v1/pkg/env-hydrate

Likely causes

• Package metadata, lock state, dependency evidence, or frontend dispatch is invalid.
• The requested package lifecycle transition cannot be verified.

Safe repairs

• verify-package-state (automatic eligible; review not required by catalog): Inspect package and lock diagnostics, repair the declared input, and regenerate only derived package artifacts.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

pkg/error

Severity: error · ID: genesis/diagnostic/v1/pkg/error

Likely causes

• Package metadata, lock state, dependency evidence, or frontend dispatch is invalid.
• The requested package lifecycle transition cannot be verified.

Safe repairs

• verify-package-state (automatic eligible; review not required by catalog): Inspect package and lock diagnostics, repair the declared input, and regenerate only derived package artifacts.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

pkg/import

Severity: error · ID: genesis/diagnostic/v1/pkg/import

Likely causes

• Package metadata, lock state, dependency evidence, or frontend dispatch is invalid.
• The requested package lifecycle transition cannot be verified.

Safe repairs

• verify-package-state (automatic eligible; review not required by catalog): Inspect package and lock diagnostics, repair the declared input, and regenerate only derived package artifacts.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

pkg/migrate

Severity: error · ID: genesis/diagnostic/v1/pkg/migrate

Likely causes

• Package metadata, lock state, dependency evidence, or frontend dispatch is invalid.
• The requested package lifecycle transition cannot be verified.

Safe repairs

• verify-package-state (automatic eligible; review not required by catalog): Inspect package and lock diagnostics, repair the declared input, and regenerate only derived package artifacts.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

pkg/new

Severity: error · ID: genesis/diagnostic/v1/pkg/new

Likely causes

• Package metadata, lock state, dependency evidence, or frontend dispatch is invalid.
• The requested package lifecycle transition cannot be verified.

Safe repairs

• verify-package-state (automatic eligible; review not required by catalog): Inspect package and lock diagnostics, repair the declared input, and regenerate only derived package artifacts.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

pkg/profile-runtime

Severity: error · ID: genesis/diagnostic/v1/pkg/profile-runtime

Likely causes

• Package metadata, lock state, dependency evidence, or frontend dispatch is invalid.
• The requested package lifecycle transition cannot be verified.

Safe repairs

• verify-package-state (automatic eligible; review not required by catalog): Inspect package and lock diagnostics, repair the declared input, and regenerate only derived package artifacts.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

pkg/qualify

Severity: error · ID: genesis/diagnostic/v1/pkg/qualify

Likely causes

• Package metadata, lock state, dependency evidence, or frontend dispatch is invalid.
• The requested package lifecycle transition cannot be verified.

Safe repairs

• verify-package-state (automatic eligible; review not required by catalog): Inspect package and lock diagnostics, repair the declared input, and regenerate only derived package artifacts.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

pkg/remove

Severity: error · ID: genesis/diagnostic/v1/pkg/remove

Likely causes

• Package metadata, lock state, dependency evidence, or frontend dispatch is invalid.
• The requested package lifecycle transition cannot be verified.

Safe repairs

• verify-package-state (automatic eligible; review not required by catalog): Inspect package and lock diagnostics, repair the declared input, and regenerate only derived package artifacts.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

pkg/run

Severity: error · ID: genesis/diagnostic/v1/pkg/run

Likely causes

• Package metadata, lock state, dependency evidence, or frontend dispatch is invalid.
• The requested package lifecycle transition cannot be verified.

Safe repairs

• verify-package-state (automatic eligible; review not required by catalog): Inspect package and lock diagnostics, repair the declared input, and regenerate only derived package artifacts.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

pkg/run-contract

Severity: error · ID: genesis/diagnostic/v1/pkg/run-contract

Likely causes

• Package metadata, lock state, dependency evidence, or frontend dispatch is invalid.
• The requested package lifecycle transition cannot be verified.

Safe repairs

• verify-package-state (automatic eligible; review not required by catalog): Inspect package and lock diagnostics, repair the declared input, and regenerate only derived package artifacts.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

pkg/scaffold

Severity: error · ID: genesis/diagnostic/v1/pkg/scaffold

Likely causes

• Package metadata, lock state, dependency evidence, or frontend dispatch is invalid.
• The requested package lifecycle transition cannot be verified.

Safe repairs

• verify-package-state (automatic eligible; review not required by catalog): Inspect package and lock diagnostics, repair the declared input, and regenerate only derived package artifacts.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

pkg/self-optimize

Severity: error · ID: genesis/diagnostic/v1/pkg/self-optimize

Likely causes

• Package metadata, lock state, dependency evidence, or frontend dispatch is invalid.
• The requested package lifecycle transition cannot be verified.

Safe repairs

• verify-package-state (automatic eligible; review not required by catalog): Inspect package and lock diagnostics, repair the declared input, and regenerate only derived package artifacts.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

pkg/spec

Severity: error · ID: genesis/diagnostic/v1/pkg/spec

Likely causes

• Package metadata, lock state, dependency evidence, or frontend dispatch is invalid.
• The requested package lifecycle transition cannot be verified.

Safe repairs

• verify-package-state (automatic eligible; review not required by catalog): Inspect package and lock diagnostics, repair the declared input, and regenerate only derived package artifacts.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

pkg/trace

Severity: error · ID: genesis/diagnostic/v1/pkg/trace

Likely causes

• Package metadata, lock state, dependency evidence, or frontend dispatch is invalid.
• The requested package lifecycle transition cannot be verified.

Safe repairs

• verify-package-state (automatic eligible; review not required by catalog): Inspect package and lock diagnostics, repair the declared input, and regenerate only derived package artifacts.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

parse

Code	Severity	Safe action
manifest/error	error	repair-parse-input
manifest/parse	error	repair-parse-input
module/error	error	repair-parse-input
package/invalid	error	repair-parse-input
parse/coreform	error	repair-parse-input
parse/log	error	repair-parse-input
parse/term	error	repair-parse-input

manifest/error

Severity: error · ID: genesis/diagnostic/v1/manifest/error

Likely causes

• Source or metadata does not satisfy its declared grammar or schema.
• A required field or canonical representation is missing.

Safe repairs

• repair-parse-input (automatic eligible; review not required by catalog): Repair the localized syntax or schema violation without changing capability policy, then parse or format again.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

manifest/parse

Severity: error · ID: genesis/diagnostic/v1/manifest/parse

Likely causes

• Source or metadata does not satisfy its declared grammar or schema.
• A required field or canonical representation is missing.

Safe repairs

• repair-parse-input (automatic eligible; review not required by catalog): Repair the localized syntax or schema violation without changing capability policy, then parse or format again.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

module/error

Severity: error · ID: genesis/diagnostic/v1/module/error

Likely causes

• Source or metadata does not satisfy its declared grammar or schema.
• A required field or canonical representation is missing.

Safe repairs

• repair-parse-input (automatic eligible; review not required by catalog): Repair the localized syntax or schema violation without changing capability policy, then parse or format again.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

package/invalid

Severity: error · ID: genesis/diagnostic/v1/package/invalid

Likely causes

• Source or metadata does not satisfy its declared grammar or schema.
• A required field or canonical representation is missing.

Safe repairs

• repair-parse-input (automatic eligible; review not required by catalog): Repair the localized syntax or schema violation without changing capability policy, then parse or format again.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

parse/coreform

Severity: error · ID: genesis/diagnostic/v1/parse/coreform

Likely causes

• Source or metadata does not satisfy its declared grammar or schema.
• A required field or canonical representation is missing.

Safe repairs

• repair-parse-input (automatic eligible; review not required by catalog): Repair the localized syntax or schema violation without changing capability policy, then parse or format again.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

parse/log

Severity: error · ID: genesis/diagnostic/v1/parse/log

Likely causes

• Source or metadata does not satisfy its declared grammar or schema.
• A required field or canonical representation is missing.

Safe repairs

• repair-parse-input (automatic eligible; review not required by catalog): Repair the localized syntax or schema violation without changing capability policy, then parse or format again.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

parse/term

Severity: error · ID: genesis/diagnostic/v1/parse/term

Likely causes

• Source or metadata does not satisfy its declared grammar or schema.
• A required field or canonical representation is missing.

Safe repairs

• repair-parse-input (automatic eligible; review not required by catalog): Repair the localized syntax or schema violation without changing capability policy, then parse or format again.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

policy

Code	Severity	Safe action
caps/denied	error	review-policy-denial
caps/missing	error	review-policy-denial
caps/parse	error	review-policy-denial
policy/authority	error	review-policy-denial
policy/parse	error	review-policy-denial
policy/resolve	error	review-policy-denial
policy/schema	error	review-policy-denial
policy/set-default	error	review-policy-denial

caps/denied

Severity: error · ID: genesis/diagnostic/v1/caps/denied

Likely causes

• The requested operation is absent from the active deny-by-default policy.
• Policy syntax, schema, or selected profile is invalid.

Safe repairs

• review-policy-denial (not automatic; review required): Inspect the required capability and policy decision; do not broaden policy unless a separate reviewed policy change is intended.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

caps/missing

Severity: error · ID: genesis/diagnostic/v1/caps/missing

Likely causes

• The requested operation is absent from the active deny-by-default policy.
• Policy syntax, schema, or selected profile is invalid.

Safe repairs

• review-policy-denial (not automatic; review required): Inspect the required capability and policy decision; do not broaden policy unless a separate reviewed policy change is intended.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

caps/parse

Severity: error · ID: genesis/diagnostic/v1/caps/parse

Likely causes

• The requested operation is absent from the active deny-by-default policy.
• Policy syntax, schema, or selected profile is invalid.

Safe repairs

• review-policy-denial (not automatic; review required): Inspect the required capability and policy decision; do not broaden policy unless a separate reviewed policy change is intended.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

policy/authority

Severity: error · ID: genesis/diagnostic/v1/policy/authority

Likely causes

• The requested operation is absent from the active deny-by-default policy.
• Policy syntax, schema, or selected profile is invalid.

Safe repairs

• review-policy-denial (not automatic; review required): Inspect the required capability and policy decision; do not broaden policy unless a separate reviewed policy change is intended.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

policy/parse

Severity: error · ID: genesis/diagnostic/v1/policy/parse

Likely causes

• The requested operation is absent from the active deny-by-default policy.
• Policy syntax, schema, or selected profile is invalid.

Safe repairs

• review-policy-denial (not automatic; review required): Inspect the required capability and policy decision; do not broaden policy unless a separate reviewed policy change is intended.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

policy/resolve

Severity: error · ID: genesis/diagnostic/v1/policy/resolve

Likely causes

• The requested operation is absent from the active deny-by-default policy.
• Policy syntax, schema, or selected profile is invalid.

Safe repairs

• review-policy-denial (not automatic; review required): Inspect the required capability and policy decision; do not broaden policy unless a separate reviewed policy change is intended.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

policy/schema

Severity: error · ID: genesis/diagnostic/v1/policy/schema

Likely causes

• The requested operation is absent from the active deny-by-default policy.
• Policy syntax, schema, or selected profile is invalid.

Safe repairs

• review-policy-denial (not automatic; review required): Inspect the required capability and policy decision; do not broaden policy unless a separate reviewed policy change is intended.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

policy/set-default

Severity: error · ID: genesis/diagnostic/v1/policy/set-default

Likely causes

• The requested operation is absent from the active deny-by-default policy.
• Policy syntax, schema, or selected profile is invalid.

Safe repairs

• review-policy-denial (not automatic; review required): Inspect the required capability and policy decision; do not broaden policy unless a separate reviewed policy change is intended.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

registry

Code	Severity	Safe action
registry/config	error	verify-registry-input
registry/io	error	verify-registry-input
registry/serve	error	verify-registry-input

registry/config

Severity: error · ID: genesis/diagnostic/v1/registry/config

Likely causes

• Registry configuration, storage, or serving preconditions are invalid.
• A registry artifact could not be read or verified.

Safe repairs

• verify-registry-input (automatic eligible; review not required by catalog): Validate registry configuration and artifact identities before retrying the same operation.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

registry/io

Severity: error · ID: genesis/diagnostic/v1/registry/io

Likely causes

• Registry configuration, storage, or serving preconditions are invalid.
• A registry artifact could not be read or verified.

Safe repairs

• verify-registry-input (automatic eligible; review not required by catalog): Validate registry configuration and artifact identities before retrying the same operation.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

registry/serve

Severity: error · ID: genesis/diagnostic/v1/registry/serve

Likely causes

• Registry configuration, storage, or serving preconditions are invalid.
• A registry artifact could not be read or verified.

Safe repairs

• verify-registry-input (automatic eligible; review not required by catalog): Validate registry configuration and artifact identities before retrying the same operation.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

replay

Code	Severity	Safe action
replay/error	error	regenerate-replay-log
replay/mismatch	error	regenerate-replay-log
replay/program-hash-mismatch	error	regenerate-replay-log

replay/error

Severity: error · ID: genesis/diagnostic/v1/replay/error

Likely causes

• Program, request, response, policy, or scheduler facts differ from the recorded log.
• The log belongs to another execution identity or is corrupted.

Safe repairs

• regenerate-replay-log (not automatic; review required): Preserve the mismatched log for investigation, then generate a new log from the exact current program and policy.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

replay/mismatch

Severity: error · ID: genesis/diagnostic/v1/replay/mismatch

Likely causes

• Program, request, response, policy, or scheduler facts differ from the recorded log.
• The log belongs to another execution identity or is corrupted.

Safe repairs

• regenerate-replay-log (not automatic; review required): Preserve the mismatched log for investigation, then generate a new log from the exact current program and policy.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

replay/program-hash-mismatch

Severity: error · ID: genesis/diagnostic/v1/replay/program-hash-mismatch

Likely causes

• Program, request, response, policy, or scheduler facts differ from the recorded log.
• The log belongs to another execution identity or is corrupted.

Safe repairs

• regenerate-replay-log (not automatic; review required): Preserve the mismatched log for investigation, then generate a new log from the exact current program and policy.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

runtime-stage

Code	Severity	Safe action
stage1/error	error	inspect-stage-evidence
stage2/error	error	inspect-stage-evidence
stage2/unsupported	error	inspect-stage-evidence

stage1/error

Severity: error · ID: genesis/diagnostic/v1/stage1/error

Likely causes

• A staged translation or execution boundary returned an error or unsupported result.
• Cross-stage validation rejected the produced artifact.

Safe repairs

• inspect-stage-evidence (automatic eligible; review not required by catalog): Inspect the stage result and translation-validation evidence; repair the producer rather than suppressing validation.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

stage2/error

Severity: error · ID: genesis/diagnostic/v1/stage2/error

Likely causes

• A staged translation or execution boundary returned an error or unsupported result.
• Cross-stage validation rejected the produced artifact.

Safe repairs

• inspect-stage-evidence (automatic eligible; review not required by catalog): Inspect the stage result and translation-validation evidence; repair the producer rather than suppressing validation.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

stage2/unsupported

Severity: error · ID: genesis/diagnostic/v1/stage2/unsupported

Likely causes

• A staged translation or execution boundary returned an error or unsupported result.
• Cross-stage validation rejected the produced artifact.

Safe repairs

• inspect-stage-evidence (automatic eligible; review not required by catalog): Inspect the stage result and translation-validation evidence; repair the producer rather than suppressing validation.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

security

Code	Severity	Safe action
keygen/authority	error	verify-security-evidence
keygen/mechanism	error	verify-security-evidence
sign/acceptance	error	verify-security-evidence
sign/authority	error	verify-security-evidence
sign/key	error	verify-security-evidence
sign/signature-set	error	verify-security-evidence
sign/transparency-head	error	verify-security-evidence
transparency/error	error	verify-security-evidence

keygen/authority

Severity: error · ID: genesis/diagnostic/v1/keygen/authority

Likely causes

• Signature, acceptance, key, or transparency evidence failed verification.
• The artifact identity does not match the signed statement.

Safe repairs

• verify-security-evidence (automatic eligible; review not required by catalog): Do not bypass verification; inspect identities and regenerate evidence only from trusted source artifacts.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

keygen/mechanism

Severity: error · ID: genesis/diagnostic/v1/keygen/mechanism

Likely causes

• Signature, acceptance, key, or transparency evidence failed verification.
• The artifact identity does not match the signed statement.

Safe repairs

• verify-security-evidence (automatic eligible; review not required by catalog): Do not bypass verification; inspect identities and regenerate evidence only from trusted source artifacts.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

sign/acceptance

Severity: error · ID: genesis/diagnostic/v1/sign/acceptance

Likely causes

• Signature, acceptance, key, or transparency evidence failed verification.
• The artifact identity does not match the signed statement.

Safe repairs

• verify-security-evidence (automatic eligible; review not required by catalog): Do not bypass verification; inspect identities and regenerate evidence only from trusted source artifacts.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

sign/authority

Severity: error · ID: genesis/diagnostic/v1/sign/authority

Likely causes

• Signature, acceptance, key, or transparency evidence failed verification.
• The artifact identity does not match the signed statement.

Safe repairs

• verify-security-evidence (automatic eligible; review not required by catalog): Do not bypass verification; inspect identities and regenerate evidence only from trusted source artifacts.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

sign/key

Severity: error · ID: genesis/diagnostic/v1/sign/key

Likely causes

• Signature, acceptance, key, or transparency evidence failed verification.
• The artifact identity does not match the signed statement.

Safe repairs

• verify-security-evidence (automatic eligible; review not required by catalog): Do not bypass verification; inspect identities and regenerate evidence only from trusted source artifacts.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

sign/signature-set

Severity: error · ID: genesis/diagnostic/v1/sign/signature-set

Likely causes

• Signature, acceptance, key, or transparency evidence failed verification.
• The artifact identity does not match the signed statement.

Safe repairs

• verify-security-evidence (automatic eligible; review not required by catalog): Do not bypass verification; inspect identities and regenerate evidence only from trusted source artifacts.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

sign/transparency-head

Severity: error · ID: genesis/diagnostic/v1/sign/transparency-head

Likely causes

• Signature, acceptance, key, or transparency evidence failed verification.
• The artifact identity does not match the signed statement.

Safe repairs

• verify-security-evidence (automatic eligible; review not required by catalog): Do not bypass verification; inspect identities and regenerate evidence only from trusted source artifacts.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

transparency/error

Severity: error · ID: genesis/diagnostic/v1/transparency/error

Likely causes

• Signature, acceptance, key, or transparency evidence failed verification.
• The artifact identity does not match the signed statement.

Safe repairs

• verify-security-evidence (automatic eligible; review not required by catalog): Do not bypass verification; inspect identities and regenerate evidence only from trusted source artifacts.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

selfhost

Code	Severity	Safe action
selfhost-only/bootstrap	error	verify-selfhost-artifact
selfhost-only/engine	error	verify-selfhost-artifact
selfhost-only/frontend	error	verify-selfhost-artifact
selfhost-only/legacy-semantic-fallback	error	verify-selfhost-artifact
selfhost/artifact-missing	error	verify-selfhost-artifact
selfhost/artifact-required	error	verify-selfhost-artifact
selfhost/bad-return	error	verify-selfhost-artifact
selfhost/bootstrap	error	verify-selfhost-artifact
selfhost/bootstrap-mode	error	verify-selfhost-artifact
selfhost/canon	error	verify-selfhost-artifact
selfhost/dashboard	error	verify-selfhost-artifact
selfhost/error	error	verify-selfhost-artifact
selfhost/freshness	error	verify-selfhost-artifact
selfhost/hash	error	verify-selfhost-artifact
selfhost/init	error	verify-selfhost-artifact
selfhost/missing	error	verify-selfhost-artifact
selfhost/parse	error	verify-selfhost-artifact
selfhost/plan	error	verify-selfhost-artifact
selfhost/recovery	error	verify-selfhost-artifact
selfhost/seed	error	verify-selfhost-artifact
selfhost/sources	error	verify-selfhost-artifact
selfhost/stage1	error	verify-selfhost-artifact

selfhost-only/bootstrap

Severity: error · ID: genesis/diagnostic/v1/selfhost-only/bootstrap

Likely causes

• A self-hosted artifact, bootstrap stage, source identity, or frontend result is missing or stale.
• The selected execution profile forbids a Rust fallback.

Safe repairs

• verify-selfhost-artifact (automatic eligible; review not required by catalog): Verify bootstrap inputs and artifact identity, rebuild through the declared self-host path, and rerun parity checks.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

selfhost-only/engine

Severity: error · ID: genesis/diagnostic/v1/selfhost-only/engine

Likely causes

• A self-hosted artifact, bootstrap stage, source identity, or frontend result is missing or stale.
• The selected execution profile forbids a Rust fallback.

Safe repairs

• verify-selfhost-artifact (automatic eligible; review not required by catalog): Verify bootstrap inputs and artifact identity, rebuild through the declared self-host path, and rerun parity checks.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

selfhost-only/frontend

Severity: error · ID: genesis/diagnostic/v1/selfhost-only/frontend

Likely causes

• A self-hosted artifact, bootstrap stage, source identity, or frontend result is missing or stale.
• The selected execution profile forbids a Rust fallback.

Safe repairs

• verify-selfhost-artifact (automatic eligible; review not required by catalog): Verify bootstrap inputs and artifact identity, rebuild through the declared self-host path, and rerun parity checks.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

selfhost-only/legacy-semantic-fallback

Severity: error · ID: genesis/diagnostic/v1/selfhost-only/legacy-semantic-fallback

Likely causes

• A self-hosted artifact, bootstrap stage, source identity, or frontend result is missing or stale.
• The selected execution profile forbids a Rust fallback.

Safe repairs

• verify-selfhost-artifact (automatic eligible; review not required by catalog): Verify bootstrap inputs and artifact identity, rebuild through the declared self-host path, and rerun parity checks.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

selfhost/artifact-missing

Severity: error · ID: genesis/diagnostic/v1/selfhost/artifact-missing

Likely causes

• A self-hosted artifact, bootstrap stage, source identity, or frontend result is missing or stale.
• The selected execution profile forbids a Rust fallback.

Safe repairs

• verify-selfhost-artifact (automatic eligible; review not required by catalog): Verify bootstrap inputs and artifact identity, rebuild through the declared self-host path, and rerun parity checks.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

selfhost/artifact-required

Severity: error · ID: genesis/diagnostic/v1/selfhost/artifact-required

Likely causes

• A self-hosted artifact, bootstrap stage, source identity, or frontend result is missing or stale.
• The selected execution profile forbids a Rust fallback.

Safe repairs

• verify-selfhost-artifact (automatic eligible; review not required by catalog): Verify bootstrap inputs and artifact identity, rebuild through the declared self-host path, and rerun parity checks.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

selfhost/bad-return

Severity: error · ID: genesis/diagnostic/v1/selfhost/bad-return

Likely causes

• A self-hosted artifact, bootstrap stage, source identity, or frontend result is missing or stale.
• The selected execution profile forbids a Rust fallback.

Safe repairs

• verify-selfhost-artifact (automatic eligible; review not required by catalog): Verify bootstrap inputs and artifact identity, rebuild through the declared self-host path, and rerun parity checks.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

selfhost/bootstrap

Severity: error · ID: genesis/diagnostic/v1/selfhost/bootstrap

Likely causes

• A self-hosted artifact, bootstrap stage, source identity, or frontend result is missing or stale.
• The selected execution profile forbids a Rust fallback.

Safe repairs

• verify-selfhost-artifact (automatic eligible; review not required by catalog): Verify bootstrap inputs and artifact identity, rebuild through the declared self-host path, and rerun parity checks.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

selfhost/bootstrap-mode

Severity: error · ID: genesis/diagnostic/v1/selfhost/bootstrap-mode

Likely causes

• A self-hosted artifact, bootstrap stage, source identity, or frontend result is missing or stale.
• The selected execution profile forbids a Rust fallback.

Safe repairs

• verify-selfhost-artifact (automatic eligible; review not required by catalog): Verify bootstrap inputs and artifact identity, rebuild through the declared self-host path, and rerun parity checks.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

selfhost/canon

Severity: error · ID: genesis/diagnostic/v1/selfhost/canon

Likely causes

• A self-hosted artifact, bootstrap stage, source identity, or frontend result is missing or stale.
• The selected execution profile forbids a Rust fallback.

Safe repairs

• verify-selfhost-artifact (automatic eligible; review not required by catalog): Verify bootstrap inputs and artifact identity, rebuild through the declared self-host path, and rerun parity checks.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

selfhost/dashboard

Severity: error · ID: genesis/diagnostic/v1/selfhost/dashboard

Likely causes

• A self-hosted artifact, bootstrap stage, source identity, or frontend result is missing or stale.
• The selected execution profile forbids a Rust fallback.

Safe repairs

• verify-selfhost-artifact (automatic eligible; review not required by catalog): Verify bootstrap inputs and artifact identity, rebuild through the declared self-host path, and rerun parity checks.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

selfhost/error

Severity: error · ID: genesis/diagnostic/v1/selfhost/error

Likely causes

• A self-hosted artifact, bootstrap stage, source identity, or frontend result is missing or stale.
• The selected execution profile forbids a Rust fallback.

Safe repairs

• verify-selfhost-artifact (automatic eligible; review not required by catalog): Verify bootstrap inputs and artifact identity, rebuild through the declared self-host path, and rerun parity checks.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

selfhost/freshness

Severity: error · ID: genesis/diagnostic/v1/selfhost/freshness

Likely causes

• A self-hosted artifact, bootstrap stage, source identity, or frontend result is missing or stale.
• The selected execution profile forbids a Rust fallback.

Safe repairs

• verify-selfhost-artifact (automatic eligible; review not required by catalog): Verify bootstrap inputs and artifact identity, rebuild through the declared self-host path, and rerun parity checks.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

selfhost/hash

Severity: error · ID: genesis/diagnostic/v1/selfhost/hash

Likely causes

• A self-hosted artifact, bootstrap stage, source identity, or frontend result is missing or stale.
• The selected execution profile forbids a Rust fallback.

Safe repairs

• verify-selfhost-artifact (automatic eligible; review not required by catalog): Verify bootstrap inputs and artifact identity, rebuild through the declared self-host path, and rerun parity checks.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

selfhost/init

Severity: error · ID: genesis/diagnostic/v1/selfhost/init

Likely causes

• A self-hosted artifact, bootstrap stage, source identity, or frontend result is missing or stale.
• The selected execution profile forbids a Rust fallback.

Safe repairs

• verify-selfhost-artifact (automatic eligible; review not required by catalog): Verify bootstrap inputs and artifact identity, rebuild through the declared self-host path, and rerun parity checks.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

selfhost/missing

Severity: error · ID: genesis/diagnostic/v1/selfhost/missing

Likely causes

• A self-hosted artifact, bootstrap stage, source identity, or frontend result is missing or stale.
• The selected execution profile forbids a Rust fallback.

Safe repairs

• verify-selfhost-artifact (automatic eligible; review not required by catalog): Verify bootstrap inputs and artifact identity, rebuild through the declared self-host path, and rerun parity checks.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

selfhost/parse

Severity: error · ID: genesis/diagnostic/v1/selfhost/parse

Likely causes

• A self-hosted artifact, bootstrap stage, source identity, or frontend result is missing or stale.
• The selected execution profile forbids a Rust fallback.

Safe repairs

• verify-selfhost-artifact (automatic eligible; review not required by catalog): Verify bootstrap inputs and artifact identity, rebuild through the declared self-host path, and rerun parity checks.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

selfhost/plan

Severity: error · ID: genesis/diagnostic/v1/selfhost/plan

Likely causes

• A self-hosted artifact, bootstrap stage, source identity, or frontend result is missing or stale.
• The selected execution profile forbids a Rust fallback.

Safe repairs

• verify-selfhost-artifact (automatic eligible; review not required by catalog): Verify bootstrap inputs and artifact identity, rebuild through the declared self-host path, and rerun parity checks.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

selfhost/recovery

Severity: error · ID: genesis/diagnostic/v1/selfhost/recovery

Likely causes

• A self-hosted artifact, bootstrap stage, source identity, or frontend result is missing or stale.
• The selected execution profile forbids a Rust fallback.

Safe repairs

• verify-selfhost-artifact (automatic eligible; review not required by catalog): Verify bootstrap inputs and artifact identity, rebuild through the declared self-host path, and rerun parity checks.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

selfhost/seed

Severity: error · ID: genesis/diagnostic/v1/selfhost/seed

Likely causes

• A self-hosted artifact, bootstrap stage, source identity, or frontend result is missing or stale.
• The selected execution profile forbids a Rust fallback.

Safe repairs

• verify-selfhost-artifact (automatic eligible; review not required by catalog): Verify bootstrap inputs and artifact identity, rebuild through the declared self-host path, and rerun parity checks.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

selfhost/sources

Severity: error · ID: genesis/diagnostic/v1/selfhost/sources

Likely causes

• A self-hosted artifact, bootstrap stage, source identity, or frontend result is missing or stale.
• The selected execution profile forbids a Rust fallback.

Safe repairs

• verify-selfhost-artifact (automatic eligible; review not required by catalog): Verify bootstrap inputs and artifact identity, rebuild through the declared self-host path, and rerun parity checks.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

selfhost/stage1

Severity: error · ID: genesis/diagnostic/v1/selfhost/stage1

Likely causes

• A self-hosted artifact, bootstrap stage, source identity, or frontend result is missing or stale.
• The selected execution profile forbids a Rust fallback.

Safe repairs

• verify-selfhost-artifact (automatic eligible; review not required by catalog): Verify bootstrap inputs and artifact identity, rebuild through the declared self-host path, and rerun parity checks.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

semantic-edit

Code	Severity	Safe action
patch/invalid	error	replan-semantic-edit
patch/obligation	error	replan-semantic-edit
semantic-edit/invalid	error	replan-semantic-edit
semantic-edit/path	error	replan-semantic-edit
semantic-edit/workspace-graph	error	replan-semantic-edit
session/already-exists	error	replan-semantic-edit
session/apply-busy	error	replan-semantic-edit
session/apply-failed	error	replan-semantic-edit
session/apply-mismatch	error	replan-semantic-edit
session/caps-outside-snapshot	error	replan-semantic-edit
session/caps-unavailable	error	replan-semantic-edit
session/invalid-id	error	replan-semantic-edit
session/lock-failed	error	replan-semantic-edit
session/not-found	error	replan-semantic-edit
session/not-open	error	replan-semantic-edit
session/obligation-error	error	replan-semantic-edit
session/obligations-failed	error	replan-semantic-edit
session/package-invalid	error	replan-semantic-edit
session/package-path	error	replan-semantic-edit
session/package-unavailable	error	replan-semantic-edit
session/patch-invalid	error	replan-semantic-edit
session/patch-io	error	replan-semantic-edit
session/patch-obligation	error	replan-semantic-edit
session/patch-store	error	replan-semantic-edit
session/patch-unavailable	error	replan-semantic-edit
session/rollback-failed	error	replan-semantic-edit
session/snapshot-escape	error	replan-semantic-edit
session/snapshot-file	error	replan-semantic-edit
session/snapshot-limit	error	replan-semantic-edit
session/snapshot-mismatch	error	replan-semantic-edit
session/snapshot-missing	error	replan-semantic-edit
session/snapshot-path	error	replan-semantic-edit
session/snapshot-read	error	replan-semantic-edit
session/stale-base	error	replan-semantic-edit
session/state-invalid	error	replan-semantic-edit
session/state-write	error	replan-semantic-edit
session/store-write	error	replan-semantic-edit
session/unverified	error	replan-semantic-edit
session/worker-output	error	replan-semantic-edit
session/worker-wait	error	replan-semantic-edit
session/workspace-tampered	error	replan-semantic-edit
session/workspace-write	error	replan-semantic-edit

patch/invalid

Severity: error · ID: genesis/diagnostic/v1/patch/invalid

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

patch/obligation

Severity: error · ID: genesis/diagnostic/v1/patch/obligation

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

semantic-edit/invalid

Severity: error · ID: genesis/diagnostic/v1/semantic-edit/invalid

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

semantic-edit/path

Severity: error · ID: genesis/diagnostic/v1/semantic-edit/path

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

semantic-edit/workspace-graph

Severity: error · ID: genesis/diagnostic/v1/semantic-edit/workspace-graph

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/already-exists

Severity: error · ID: genesis/diagnostic/v1/session/already-exists

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/apply-busy

Severity: error · ID: genesis/diagnostic/v1/session/apply-busy

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/apply-failed

Severity: error · ID: genesis/diagnostic/v1/session/apply-failed

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/apply-mismatch

Severity: error · ID: genesis/diagnostic/v1/session/apply-mismatch

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/caps-outside-snapshot

Severity: error · ID: genesis/diagnostic/v1/session/caps-outside-snapshot

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/caps-unavailable

Severity: error · ID: genesis/diagnostic/v1/session/caps-unavailable

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/invalid-id

Severity: error · ID: genesis/diagnostic/v1/session/invalid-id

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/lock-failed

Severity: error · ID: genesis/diagnostic/v1/session/lock-failed

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/not-found

Severity: error · ID: genesis/diagnostic/v1/session/not-found

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/not-open

Severity: error · ID: genesis/diagnostic/v1/session/not-open

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/obligation-error

Severity: error · ID: genesis/diagnostic/v1/session/obligation-error

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/obligations-failed

Severity: error · ID: genesis/diagnostic/v1/session/obligations-failed

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/package-invalid

Severity: error · ID: genesis/diagnostic/v1/session/package-invalid

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/package-path

Severity: error · ID: genesis/diagnostic/v1/session/package-path

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/package-unavailable

Severity: error · ID: genesis/diagnostic/v1/session/package-unavailable

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/patch-invalid

Severity: error · ID: genesis/diagnostic/v1/session/patch-invalid

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/patch-io

Severity: error · ID: genesis/diagnostic/v1/session/patch-io

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/patch-obligation

Severity: error · ID: genesis/diagnostic/v1/session/patch-obligation

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/patch-store

Severity: error · ID: genesis/diagnostic/v1/session/patch-store

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/patch-unavailable

Severity: error · ID: genesis/diagnostic/v1/session/patch-unavailable

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/rollback-failed

Severity: error · ID: genesis/diagnostic/v1/session/rollback-failed

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/snapshot-escape

Severity: error · ID: genesis/diagnostic/v1/session/snapshot-escape

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/snapshot-file

Severity: error · ID: genesis/diagnostic/v1/session/snapshot-file

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/snapshot-limit

Severity: error · ID: genesis/diagnostic/v1/session/snapshot-limit

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/snapshot-mismatch

Severity: error · ID: genesis/diagnostic/v1/session/snapshot-mismatch

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/snapshot-missing

Severity: error · ID: genesis/diagnostic/v1/session/snapshot-missing

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/snapshot-path

Severity: error · ID: genesis/diagnostic/v1/session/snapshot-path

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/snapshot-read

Severity: error · ID: genesis/diagnostic/v1/session/snapshot-read

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/stale-base

Severity: error · ID: genesis/diagnostic/v1/session/stale-base

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/state-invalid

Severity: error · ID: genesis/diagnostic/v1/session/state-invalid

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/state-write

Severity: error · ID: genesis/diagnostic/v1/session/state-write

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/store-write

Severity: error · ID: genesis/diagnostic/v1/session/store-write

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/unverified

Severity: error · ID: genesis/diagnostic/v1/session/unverified

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/worker-output

Severity: error · ID: genesis/diagnostic/v1/session/worker-output

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/worker-wait

Severity: error · ID: genesis/diagnostic/v1/session/worker-wait

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/workspace-tampered

Severity: error · ID: genesis/diagnostic/v1/session/workspace-tampered

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

session/workspace-write

Severity: error · ID: genesis/diagnostic/v1/session/workspace-write

Likely causes

• A patch or semantic edit is stale, ambiguous, invalid, or escapes its workspace boundary.
• The source graph no longer matches the plan preconditions.

Safe repairs

• replan-semantic-edit (automatic eligible; review not required by catalog): Regenerate the semantic plan against the current content hash, review the diff, and apply transactionally.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

serialization

Code	Severity	Safe action
json/serialize	error	report-serialization-contract

json/serialize

Severity: error · ID: genesis/diagnostic/v1/json/serialize

Likely causes

• A command result could not be represented by the versioned JSON envelope.
• An internal value violated the serializer contract.

Safe repairs

• report-serialization-contract (automatic eligible; review not required by catalog): Preserve the failing structured context and report the catalog ID as an implementation defect.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

storage

Code	Severity	Safe action
commit/new	error	verify-storage-identity
commit/show	error	verify-storage-identity
gc/error	error	verify-storage-identity
refs/error	error	verify-storage-identity
store/dispatch-drift	error	verify-storage-identity
store/error	error	verify-storage-identity
sync/error	error	verify-storage-identity
sync/set-ref	error	verify-storage-identity

commit/new

Severity: error · ID: genesis/diagnostic/v1/commit/new

Likely causes

• Content-addressed storage, references, commits, synchronization, or garbage-collection state is invalid.
• A requested identity is missing or does not verify.

Safe repairs

• verify-storage-identity (automatic eligible; review not required by catalog): Verify content identities and references before retrying; never delete or rewrite reachable data as an automatic repair.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

commit/show

Severity: error · ID: genesis/diagnostic/v1/commit/show

Likely causes

• Content-addressed storage, references, commits, synchronization, or garbage-collection state is invalid.
• A requested identity is missing or does not verify.

Safe repairs

• verify-storage-identity (automatic eligible; review not required by catalog): Verify content identities and references before retrying; never delete or rewrite reachable data as an automatic repair.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

gc/error

Severity: error · ID: genesis/diagnostic/v1/gc/error

Likely causes

• Content-addressed storage, references, commits, synchronization, or garbage-collection state is invalid.
• A requested identity is missing or does not verify.

Safe repairs

• verify-storage-identity (automatic eligible; review not required by catalog): Verify content identities and references before retrying; never delete or rewrite reachable data as an automatic repair.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

refs/error

Severity: error · ID: genesis/diagnostic/v1/refs/error

Likely causes

• Content-addressed storage, references, commits, synchronization, or garbage-collection state is invalid.
• A requested identity is missing or does not verify.

Safe repairs

• verify-storage-identity (automatic eligible; review not required by catalog): Verify content identities and references before retrying; never delete or rewrite reachable data as an automatic repair.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

store/dispatch-drift

Severity: error · ID: genesis/diagnostic/v1/store/dispatch-drift

Likely causes

• Content-addressed storage, references, commits, synchronization, or garbage-collection state is invalid.
• A requested identity is missing or does not verify.

Safe repairs

• verify-storage-identity (automatic eligible; review not required by catalog): Verify content identities and references before retrying; never delete or rewrite reachable data as an automatic repair.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

store/error

Severity: error · ID: genesis/diagnostic/v1/store/error

Likely causes

• Content-addressed storage, references, commits, synchronization, or garbage-collection state is invalid.
• A requested identity is missing or does not verify.

Safe repairs

• verify-storage-identity (automatic eligible; review not required by catalog): Verify content identities and references before retrying; never delete or rewrite reachable data as an automatic repair.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

sync/error

Severity: error · ID: genesis/diagnostic/v1/sync/error

Likely causes

• Content-addressed storage, references, commits, synchronization, or garbage-collection state is invalid.
• A requested identity is missing or does not verify.

Safe repairs

• verify-storage-identity (automatic eligible; review not required by catalog): Verify content identities and references before retrying; never delete or rewrite reachable data as an automatic repair.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

sync/set-ref

Severity: error · ID: genesis/diagnostic/v1/sync/set-ref

Likely causes

• Content-addressed storage, references, commits, synchronization, or garbage-collection state is invalid.
• A requested identity is missing or does not verify.

Safe repairs

• verify-storage-identity (automatic eligible; review not required by catalog): Verify content identities and references before retrying; never delete or rewrite reachable data as an automatic repair.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

vcs

Code	Severity	Safe action
vcs/blame	error	inspect-vcs-precondition
vcs/dispatch-drift	error	inspect-vcs-precondition
vcs/error	error	inspect-vcs-precondition
vcs/resolve-conflict	error	inspect-vcs-precondition
vcs/why	error	inspect-vcs-precondition

vcs/blame

Severity: error · ID: genesis/diagnostic/v1/vcs/blame

Likely causes

• A version-control artifact, conflict resolution, or self-host dispatch result is invalid.
• The requested snapshot or symbol does not exist in the selected history.

Safe repairs

• inspect-vcs-precondition (automatic eligible; review not required by catalog): Verify snapshot identities and conflict preconditions, regenerate the plan if stale, and preserve unresolved data.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

vcs/dispatch-drift

Severity: error · ID: genesis/diagnostic/v1/vcs/dispatch-drift

Likely causes

• A version-control artifact, conflict resolution, or self-host dispatch result is invalid.
• The requested snapshot or symbol does not exist in the selected history.

Safe repairs

• inspect-vcs-precondition (automatic eligible; review not required by catalog): Verify snapshot identities and conflict preconditions, regenerate the plan if stale, and preserve unresolved data.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

vcs/error

Severity: error · ID: genesis/diagnostic/v1/vcs/error

Likely causes

• A version-control artifact, conflict resolution, or self-host dispatch result is invalid.
• The requested snapshot or symbol does not exist in the selected history.

Safe repairs

• inspect-vcs-precondition (automatic eligible; review not required by catalog): Verify snapshot identities and conflict preconditions, regenerate the plan if stale, and preserve unresolved data.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

vcs/resolve-conflict

Severity: error · ID: genesis/diagnostic/v1/vcs/resolve-conflict

Likely causes

• A version-control artifact, conflict resolution, or self-host dispatch result is invalid.
• The requested snapshot or symbol does not exist in the selected history.

Safe repairs

• inspect-vcs-precondition (automatic eligible; review not required by catalog): Verify snapshot identities and conflict preconditions, regenerate the plan if stale, and preserve unresolved data.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md

vcs/why

Severity: error · ID: genesis/diagnostic/v1/vcs/why

Likely causes

• A version-control artifact, conflict resolution, or self-host dispatch result is invalid.
• The requested snapshot or symbol does not exist in the selected history.

Safe repairs

• inspect-vcs-precondition (automatic eligible; review not required by catalog): Verify snapshot identities and conflict preconditions, regenerate the plan if stale, and preserve unresolved data.

Documentation: docs/spec/CLI_JSON_SCHEMAS_v0.1.md