aoa-decision-correct

Intent

Use this skill to repair an existing decision record, its index metadata, supersession links, source-surface list, or generated decision indexes without letting the workspace graph become the authority.

Trigger boundary

Use this skill when:

• a decision record is stale, incomplete, misindexed, wrongly sourced, or needs supersession
• generated decision indexes are out of date with source metadata
• graph lookup shows a mismatch that must be verified against the source note
• a correction must preserve local decision-lane law and validation

Do not use this skill when:

• the task is only to find relevant rationale; use aoa-decision-find
• a new durable decision is required instead; use aoa-decision-create
• the source surface itself is wrong and no decision-lane change is needed
• a generated graph or index can be refreshed without source-note drift
• the correction would rewrite history instead of adding an explicit supersession or status change

Inputs

• target decision ID, path, source surface, stale index, or graph mismatch
• aoa_decisions status, issues, decision, changed-path, source-surface,

owner-surface, or repo packet for the target record when available

• repo-local decision route card, template, source note, and generated indexes
• source files changed by the correction when relevant
• validation commands for decision indexes and affected surfaces

Outputs

• corrected source decision note or explicit no-change finding
• regenerated repo-local decision indexes when metadata changed
• refreshed or checked workspace graph
• clear report of old mismatch, correction, validation, and any remaining risk

Procedure

1. use aoa_decisions status and issues first, then fetch the target decision,

changed-path, source-surface, owner-surface, or repo packet when available

1. if graph issues exist for the target repo, classify whether the fix belongs

to the source note, local index contract, workspace graph registry, or cache refresh

1. read the source decision note before editing anything
2. read the repo-local decision route card and generated index contract
3. classify the correction as metadata, source-surface list, status,

supersession, typo-only, or generated-index drift

1. edit the source note first; use explicit supersession or status language for

semantic changes instead of silent history rewrite

1. regenerate repo-local decision indexes when metadata or source-record shape changed
2. run the repo-local decision validator/check and any affected surface validator
3. refresh or check the workspace graph, run the decision-graph lane when available,

and compare the corrected graph packet

1. report whether the graph, source note, and local indexes are now aligned

Contracts

• source notes are edited before generated indexes or graph cache
• generated graph/cache refresh cannot be used to hide source drift
• semantic corrections must preserve reviewable history through status or supersession
• typo-only fixes should not inflate into new rationale
• validation must cover the owner repo, not only the workspace graph
• graph issue packets are triage inputs; they do not replace source-note or

local-contract inspection

Risks and anti-patterns

• fixing only generated indexes while leaving source metadata wrong
• changing meaning silently without status or supersession
• broad rewriting because a small metadata fix was requested
• trusting a stale graph packet after editing source files
• applying another repo's metadata vocabulary where it does not fit
• clearing cache freshness while leaving an unknown decision-lane surface unmodeled

Verification

• confirm the source note was inspected and, if needed, edited
• confirm generated indexes were regenerated only from source metadata
• confirm repo-local decision checks passed or failures are explicit
• confirm workspace graph refresh/check and decision-graph lane see the corrected state
• confirm semantic rewrites are avoided or made explicit through supersession/status

Technique traceability

Manifest-backed techniques:

• AOA-T-0001 from 8Dionysus/aoa-techniques at cd276f040d55d490bd015b8698c7a5d594b9f875 using path techniques/execution/agent-workflows-core/plan-diff-apply-verify-report/TECHNIQUE.md and sections: Intent, When to use, Inputs, Outputs, Core procedure, Contracts, Risks, Validation
• AOA-T-0033 from 8Dionysus/aoa-techniques at 3b1d5d623569aa4920b87280d0db0e911d2e29d5 using path techniques/instruction/docs-boundary/decision-rationale-recording/TECHNIQUE.md and sections: Intent, When to use, When not to use, Inputs, Outputs, Core procedure, Contracts, Risks, Validation
• AOA-T-0002 from 8Dionysus/aoa-techniques at cd276f040d55d490bd015b8698c7a5d594b9f875 using path techniques/instruction/docs-boundary/source-of-truth-layout/TECHNIQUE.md and sections: Intent, When to use, Inputs, Outputs, Core procedure, Contracts, Risks, Validation

Adaptation points

• repo-specific supersession/status vocabulary
• repo-local generated index commands
• decision validator and affected surface validator
• MCP refresh command or graph fallback