domains / families / agent-tooling / atlas-contract
atlas-contract
separate
Goal-integrity skill. Use for backend/API/persistence, preserve/do-not-change, tests/validation, mocks, rework, multi-part requests. Emits Goal Contracts, Deviation Notices, Phase Checks, Final Audits. Skip for Q&A or trivial edits.
When to use
- backend/API/persistence
- preserve/do-not-change
- tests/validation
- mocks
- rework
- multi-part requests
When not to use
- This is a prompt-level governance layer, not an external enforcement mechanism; the same model that drifts may still misapply the audit.
- Heavy footprint can add significant interaction overhead and should not be imposed on simple factual answers or trivial edits.
- It cannot prove tool effects mechanically; high-stakes work still needs independent tests, review, or code-level gates.
- The companion ledger only works when the user confirms durable clauses and the project keeps `Atlas.md` available.
Skill page
Source