agentic-praxis-grimoire

Exit Records

Exit records preserve the truthful terminal disposition of a bounded APG phase. They summarize scope, outcome, validation, deferrals, and the next authorization. They are project history, not substitutes for Git or operational report artifacts.

Path and sequence

Use:

docs/status/YYYY/MM/DD/NNNNN-<phase>-<slug>-exit.md

• YYYY/MM/DD is normally the local calendar date encoded in the committer timestamp of the commit that first introduced the logical exit record. When an explicit phase assignment instead authorizes a document-stated status date, the path matches that stated date without later timestamp archaeology.
• Preserve the date in that timestamp’s numeric offset. Do not convert the timestamp to UTC or to the reviewing machine’s timezone.
• Later moves or corrections do not change the assigned introduction date.
• NNNNN is a five-digit sequence that advances across the complete exit-record tree. The first value is 00001.
• Select the next value by finding the greatest assigned exit number and adding one.
• An assigned exit number and date are stable and are never reused or changed, including when a phase is partial, blocked, rejected, stopped, or its record later moves explicitly.
• Each exit number must be unique within the exit-record namespace.
• Exit numbering is independent of the ADR namespace under docs/adr/.
• Compute the next exit only from this namespace; do not compare it with an ADR number.

Record contract

• The filename ends in -exit.md.
• The document title contains Exit.
• The disposition is truthful; an incomplete phase may still close with a partial, blocked, rejected, or stopped exit.
• The record states phase identity, scope, outcome, validation actually run, deferred work, and the next authorized decision or action.
• From exit 00029 onward, the path’s lowercase phase token, index label, H1, and exactly one Phase ID field agree. Canonical phase spelling is uppercase and globally unique case-insensitively.
• Publishable exit records do not expose unpublished repository identities, private source topology, private commit identities, local paths, or private report destinations.

The phase and record identity guide owns phase forms, never-reuse, durable references, precommit finalization, and the mechanical checker.

Index

• 00001 — APG0 Foundation Exit
• 00002 — APG1 Public Projection and Documentation Hygiene Exit
• 00003 — APG2 Roadmap Reconciliation Proposal Exit
• 00004 — APG2A First Implementation Sequence Acceptance Exit
• 00005 — APG3 Bounded Worker-Assignment Skill Evaluation Exit
• 00006 — APG4 Bootstrap v0.1 Exit
• 00007 — APG4A Codex Repository Skill Discovery Exit
• 00008 — APG5 First Codex Dogfooding and Commit-Message Hygiene Exit
• 00009 — APG6 RepoMap Cross-Repository Dogfooding Exit
• 00010 — APG7 Project-Local Skill Projection and Rollback Tooling Exit
• 00011 — APG7A Idempotent Projection Compliance Correction Exit
• 00012 — APG8 RepoMap Managed Projection Adoption Exit
• 00013 — APG-TEST0 Repository Test Layout and Report-Tool Coverage Exit
• 00014 — APG9 v0.1 Release, Decommission, and v0.2 Roadmap Exit
• 00015 — APG10 Karpathy Guidelines Evaluation and Selective Integration Exit
• 00016 — APG11 Skill Authoring, Maintenance, and Legacy Roadmap Closure Exit
• 00017 — APG11A Skill-Library Lexical Correction Exit
• 00018 — APG12 Public Distribution and Release Validation Exit
• 00019 — APG12A Public Lineage and Read-Only Validation Correction Exit
• 00020 — APG13 Six-Skill Post-Superpowers Stability Review Exit
• 00021 — APG14 v0.2.0 Release Candidate and Publication Exit
• 00022 — APG15 v0.3 Foundation Design Exit
• 00023 — APG16 Public Workflow Router Exit
• 00024 — APG17 Repository-Guidance Synthesis Exit
• 00025 — APG17A Public Release Identity Evidence Correction Exit
• 00026 — APG18 Language-Profile Contract and Python Vertical Slice Exit
• 00027 — APG18A Python-Profile Current-State Documentation Correction Exit
• 00028 — APG19 Shell and Shell-Test Profiles Exit
• 00029 — APG19A Semantic Phase Identity and APG19 Reconciliation Exit
• 00030 — APG20 Go and Ruby Language Profiles Exit
• 00031 — APG20A Go and Ruby Profile Corrections Exit
• 00032 — APG21 Nix, PostgreSQL, and SQLite Profiles Exit
• 00033 — APG21A Nix Profile Correction Exit
• 00034 — APG22 Cross-Repository Dogfood and Guidance Migration Exit
• 00035 — APG22A Approved-Roadmap Manager Assignments Exit
• 00036 — APG22B Version-Bounded ZUnit Profile Exit
• 00037 — APG22C ZUnit Startup-Isolation Evidence Correction Exit
• 00038 — APG23 v0.3 Readiness, Maturity, and Application Smoke Exit
• 00039 — APG24 v0.3.0 Release Candidate and Publication Exit
• 00040 — APG24A v0.3 External Smoke and Router Transition Closeout Exit
• 00041 — APG25 v0.4 Structured Project Work Foundation Exit
• 00042 — APG26 Pytest and Bash-to-Python Capabilities Exit
• 00043 — APG26A Formal-Phase Commit-Message Enforcement Exit
• 00044 — APG27 Python Agent Reporting and Git-Diff Report Exit
• 00045 — APG27A Python Agent Reporting Correction and Adoption Exit
• 00046 — APG28 Pytest Suite and Coverage Migration Exit
• 00047 — APG28A Pytest Migration Correction and Adoption Exit
• 00048 — APG29 Process-Skill Alignment Exit
• 00049 — APG30 ChatGPT-Manager Topology and Subrouter Exit
• 00050 — APG31 Personal-Hygiene Shadow and Transition Exit
• 00051 — APG31A Personal-Hygiene Transition Completion Exit
• 00052 — APG32 Minitest Test Profile Exit
• 00053 — APG33 Dockerfile Profile Exit
• 00054 — APG34 Vagrantfile Profile Exit
• 00055 — APG35 v0.4 Remaining-Skill Authoring Exit
• 00056 — APG36 Claude-Authored Skill Integration Exit
• 00057 — APG37 Go and Nix Test Profile Redesign Exit
• 00058 — APG38 APG37 Go and Nix Integration Exit
• 00059 — APG39 matryer/is and Nix Final Redesign Exit
• 00060 — APG40 APG39 matryer/is and Nix Integration Exit
• 00061 — APG41 v0.4 Readiness and Pre-Release Smoke Exit
• 00062 — APG42 v0.4 Release Publication and Active Deployment Exit

This site is open source. Improve this page.