agentic-praxis-grimoire

APG17 Repository-Guidance Synthesis Exit

Disposition

Complete — repository-guidance synthesis implemented; fresh-session smoke pending

Terminal repository outcome:

synthesis-skill-implemented-pending-fresh-session-smoke

Authority and objective

The human maintainer accepted APG16, supplied its duplicate-name discovery result, and authorized APG17 to evaluate and, only if retained, implement one public synthesizing-repository-guidance leaf. The phase classifies mixed guidance into bounded owners and migration prerequisites before rewrite. It does not authorize source migration, root reduction, private skill removal, language profiles, release, or APG18.

APG16 subsequent external disposition

The maintainer confirmed that both same-name routers were visible and selectable in the APG private development repository and that only the personal/private router was visible and selectable globally. This supplied result closes APG16’s duplicate-name discovery and coexistence observation. No routing-case transcript, selector metadata, user-interface detail, or precedence rule is inferred.

Accepted ownership and architecture

ADR 0013 is Accepted. synthesizing-repository-guidance owns decomposition and owner, provenance, privacy, migration, rejection, rollback, and source-preservation dispositions for a dense, duplicated, mixed-scope, private, or source-derived corpus before rewrite. Its boundary is:

classify and disposition; do not rewrite or migrate

Native Codex skill-authoring guidance owns technical skill-file construction after the owner and contract are accepted. APG’s authoring lifecycle owns capability adoption and behavior-bearing correction. The project model, provenance policy, repository policy, and private overlays retain their artifact, rights, command, cutover, machine, and private owners. A disposition grants no implementation authority.

ADR 0012 remains Proposed. APG17 does not accept its warning model or implement any language profile.

Source and privacy model

Four fresh read-only baselines reviewed native authoring, bounded private guidance classes, a representative historic manager-prompt corpus, and ordinary classification. Public APG expression is independently written. Source identity, authority, reuse rights, and publication eligibility remain separate facts.

Medical, cognitive, diagnostic, deeply personal, productivity, machine-specific, and private-integration detail remains private. No raw sensitive guidance is retained in APG evidence. Missing source identity or rights stops copied or adapted use, and source packaging does not establish a public capability.

Frozen scenarios and candidate result

Sixteen positive, non-trigger, edge, fault, and maintenance families were frozen before candidate wording. Ordinary reasoning reached correct results in all families but was less repeatable for mixed-unit splitting, coverage, migration dependencies, rollback, and explicit source preservation.

Two fresh candidate evaluators applied disjoint halves of the contract. All sixteen passed: positives produced complete dispositions; known authoring, simple editing, and direct implementation remained non-triggers; rights and authority conflicts stopped safely; sensitive material remained private; one-to-one and rewrite-first demands were rejected; and all sources were preserved.

Candidate correction count: zero.

Dogfood inventory and no-cutover result

One bounded 34-unit inventory exercised every authorized source class without wholesale private migration:

Disposition	Count
retain-root	1
route-existing-owner	16
synthesize-existing-owner-correction	1
candidate-new-skill	2
candidate-language-profile	2
core-documentation	1
project-owned	5
keep-private	5
evidence-only	1
Total	34

Every coherent unit has one proposed owner and one disposition. Private-skill routes record shadow, discovery, non-trigger, override, separate cutover acceptance, byte-restorable restoration, and regression rollback prerequisites. No selected unit had a rights blocker; the frozen rights-fault family verifies that stop.

No inventoried root instruction, standard, historic prompt, private skill, or authoring source was rewritten, removed, retargeted, migrated, published, or decommissioned. No cutover occurred.

Future-candidate boundaries

The historic prompt sample supports only an unnamed future capability candidate for constructing a top-level Codex assignment from an already human-approved roadmap. It does not show ordinary prompting to be inadequate across projects. No final name, prompt, skill, implementation, or authorization was created.

Two language-specific units remain future profile candidates. ADR 0012 is still Proposed; no profile or warning model was implemented.

Router, catalog, and distribution integration

Private development now contains eight canonical skills and eight relative checked-in projections: six stable process leaves, one provisional workflow router, and one provisional guidance-synthesis leaf. The router’s sorted map contains seven routable non-router entries and routes mixed guidance to synthesizing-repository-guidance. The router procedure and all six stable procedures remain byte-identical.

The exact-map contract failed first while the catalog intentionally outgrew the map and passed after the synthesis entry was added. One focused mixed-guidance test verifies the route. The project lifecycle source recognizes two known unmanaged development skills while still managing exactly the six stable v0.2 skills.

Public v0.2.0, the active public-backed integration, project/user state schemas, managed defaults, lifecycle semantics, critical release policy, and release architecture remain six-skill contracts. No distribution or active integration was broadened.

Rollback removes the synthesis leaf, projection, catalog and map entries, focused test, and known-unmanaged classification, then restores every APG17 current-state count and compatibility description to the prior seven-canonical, six-routable development shape. Historical phase evidence is preserved. Source guidance needs no restoration because APG17 changed none.

Selected APG skills and material non-triggers

• The APG workflow router selected relevant current owners and now advertises the retained synthesis capability.
• Significant-change design owned capability, privacy, native-authoring, output, and rollback decisions.
• Repository planning owned the dependent phase sequence.
• Bounded worker-assignment composition owned already-authorized source, baseline, scenario, and review assignments.
• Test-disciplined implementation owned only deterministic map, test, and current-development compatibility changes.
• Systematic debugging applied only to an actual temporary baseline-fixture inconsistency after focused reproduction.
• Review and verification governed every worker return, candidate, ledger, integration, validation, and completion claim.

Automatic delegation, mandatory chaining, technical authoring as the classification owner, root migration, private cutover, language profiles, release, and APG18 were material non-triggers.

Independent reviews

• Synthesis semantic review: accept, with no blocker or material finding.
• Dogfood-ledger review: initial correction-required; final accept after multi-owner units were split, one source identity was corrected, counts were recomputed, and private-skill migration gates were made explicit.
• Router and integration review: initial corrections for one stale 7/7/7 current-development test and incomplete documentation rollback; final accept after both were corrected and rerun.
• Complete-diff review: accept with no blocker or material finding after the full tracked and untracked precommit tree, validation, public privacy, links, counters, rollback, and external state were independently checked.

The ledger and integration corrections did not alter the candidate skill; candidate correction count remains zero.

Validation

The final integrated state passes:

• 17 skill-library unit tests;
• 58 checker integration tests with the exact v0.1 fixture;
• 8 release unit and 32 release integration tests;
• 8 user unit and 39 user integration tests with the exact v0.1 fixture;
• 22 report-tool Bats families;
• 28 project-skill integration families;
• development checker text and JSON at 8/8/8;
• public v0.2.0 checker text and JSON at 6/6/6;
• Python byte compilation, applicable Bash syntax, and all six command-help checks;
• structural, trigger, non-trigger, stop, catalog, map, projection, maturity, confidentiality, public/private, link, counter, schema, mode, and external read-only checks; and
• Git unstaged whitespace checking.

The staged whitespace check runs after the accepted final diff is staged.

External state and artifacts

The public v0.2.0 checkout, reference corpus, RepoMap checkout, active public-backed integration, private source guidance, private skills, and retired Superpowers state remain unchanged. APG17 creates no dependency, plugin, runtime, scheduler, registry, daemon, package manager, state-schema change, release candidate, tag, or public push.

Public artifacts include the synthesis leaf, ADR 0013, the APG17 evaluation, router-map metadata, current-development compatibility updates, and this exit. Exact source identities, unit ledger, worker evidence, and review dispositions remain under the protected publication-excluded boundary without creating a public dependency on their path.

Limitations and exact external disposition requested

Current file, test, checker, scenario, dogfood, and review evidence cannot prove that a newly launched Codex client discovers and explicitly applies the repository-scoped synthesis leaf. The exact external disposition requested is pass, pass-with-follow-up, or fail after the following smoke.

Exact fresh-session smoke request

1. Fully quit Codex with Command-Q.
2. Relaunch Codex.
3. Open a new session rooted in the APG development repository.
4. Confirm synthesizing-repository-guidance is visible and explicitly selectable.

5. Explicitly select agentic-praxis-grimoire-workflow and route this case:

   A large AGENTS.md mixes universal authority rules, Python-specific complexity guidance, exact repository commands, private machine paths, duplicated APG procedures, and personal workflow preferences. The operator wants an owner and migration plan before changing the file.

6. Require the router to select synthesizing-repository-guidance.
7. Explicitly select synthesizing-repository-guidance and apply it to the hypothetical case.
8. Verify that the result classifies and dispositions rather than rewriting; retains universal authority in root; routes existing APG procedure to current owners; treats language guidance as an unimplemented profile candidate; keeps exact commands project-owned; keeps machine and personal guidance private; proposes migration prerequisites and rollback; removes nothing; grants no implementation authority; and exposes no private or medical detail.
9. Run the development skill-library checker in text and JSON.
10. Report pass, pass-with-follow-up, or fail.

APG18 has not started. It remains a separately authorized future decision, and no successor phase begins automatically.

Subsequent APG17A external disposition

APG17A corrected two publication-excluded public-release identity fields after fresh verification against the accepted APG14 release and unchanged live public state. No APG17 skill, architecture, scenario, dogfood disposition, maturity, distribution boundary, or external state changed.

The maintainer deferred this phase’s fresh-session application smoke to the aggregate v0.3 readiness and release-preparation gates owned by APG23 and APG24. The deferral preserves APG17’s repository acceptance and historical terminal outcome. APG18 is separately authorized by the APG17A-to-APG18 assignment.

This site is open source. Improve this page.