agentic-praxis-grimoire

APG16 Public Workflow Router Exit

Disposition

Complete — public workflow router implemented; fresh-session smoke pending

Terminal repository outcome:

router-implemented-pending-fresh-session-smoke

Authority and objective

The human maintainer accepted APG15, accepted the capability-oriented, synthesis-first architecture in ADR 0011, and authorized APG16 as the first bounded v0.3 implementation slice. APG16 evaluates and implements exactly one public agentic-praxis-grimoire-workflow skill as a capability selector, not a workflow engine.

APG16 does not authorize or implement guidance synthesis, a language profile, root-instruction migration, private-router cutover, maturity promotion, public release, or APG17.

Prior-phase subsequent dispositions

The maintainer completed the full-restart, fresh-session smoke requested after APG14 and reported that it passed. APG16 records only that supplied bounded application disposition and invents no user-interface log, timestamp, telemetry, or duplicate-source evidence. APG14’s historical terminal result is preserved.

APG15 is accepted as Complete — v0.3 foundation architecture proposed. ADR 0011 is Accepted with APG16’s native-selection, capability-map, duplicate-name, no-orchestration, and no-cutover clarifications. ADR 0012 remains Proposed; its warning and profile design is not accepted or implemented. No other v0.3 phase is automatically authorized.

The maintainer subsequently 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 the duplicate-name discovery and coexistence observation requested by APG16. It does not supply or imply routing-case transcripts, selector metadata, or a precedence rule.

Baselines and capability-source decision

Two fresh baselines independently evaluated generalized private routing capabilities and ordinary Codex selection. Native selection was already sufficient for clear positive and ordinary non-trigger cases. A distinct APG routing artifact added value only for ambiguity, routing audit, missing or stale capability diagnosis, duplicate-name caution, deterministic chain rejection, self-exclusion, and future-catalog maintenance.

APG16 selects one schema-version-1 skill-local map containing only the six routable public process names, concise trigger summaries, and capability classes. It excludes the router, duplicates no procedure, and remains readable with the installed leaf. A focused standard-library test compares exact map membership with the canonical catalog minus the router and therefore fails when the catalog grows without an explicit routing disposition.

Scenario and candidate result

The contract froze 21 positive, overlap, non-trigger, fault, chain, authority, duplicate-name, self-recursion, and future-catalog families before candidate wording. Twenty-one initial clean-context applications passed. Semantic review then identified one material gap: selection occurred before a plausible leaf’s canonical non-trigger boundary was visible.

One bounded candidate correction now reads only each materially plausible leaf’s frontmatter and Do not use section before selection. The selected leaf remains the sole owner of its full procedure. Twenty-one new clean-context workers reran the complete frozen contract against corrected router SHA-256 3a29187bb6448c158a80da6574309631b3ae8655da2cb3863e5eda304f90bd7f; all passed. No rerun reported a mandatory chain, authority expansion, leaf-procedure duplication, duplicate-source inference, private or personal detail, or disproportionate output.

Candidate correction count: one.

Canonical, projection, catalog, and exact-six integration

The resulting development source contains:

• seven canonical direct-child skills;
• seven relative checked-in Codex projections;
• six unchanged stable process leaves and catalog rows;
• one provisional router leaf and catalog row; and
• one router-local capability map.

The six stable leaf hashes are unchanged from the APG16 baseline. The router projection target is exactly ../../skills/agentic-praxis-grimoire-workflow.

apg-project-skills, apg-user-skills, public v0.2.0, the active public-backed integration, and the schema-version-1 public release policy intentionally retain six-skill v0.2 contracts. One bounded current-source project-command correction recognizes the router as a known but unmanaged development leaf while retaining the exact six managed stable v0.2 process skills. Its help, diagnostics, documentation, and tests distinguish that managed subset from the seven-leaf canonical development catalog. No state, default set, lifecycle, update, rollback, or schema behavior is broadened.

This integration-terminology correction is separate from the single router candidate correction.

Selected APG skills and material non-triggers

• designing-significant-changes owned native-selection, duplicate-name, capability-map, exact-six, and rollback decisions.
• planning-repository-work owned the dependent phase sequence.
• composing-bounded-worker-assignments owned already-authorized read-only baseline, one-scenario, and review assignments.
• implementing-with-test-discipline owned the failing-first map contract and bounded executable integration correction.
• reviewing-and-verifying-repository-work owned worker disposition, resulting-state review, evidence claims, and closeout.
• debugging-systematically applied only to actual unexplained baseline and integration inconsistencies; focused evidence supported the bounded guard correction and no unrelated cleanup.

Automatic delegation, mandatory review ceremony, guidance synthesis, language profiles, root migration, private cutover, release, and APG17 remained material non-triggers.

Independent review

• Router semantic review: initial correction-required; final accept after the one bounded correction and fresh 21/21 rerun, with no remaining blocker or material finding.
• Integration and transition review: accept after corrected-hash evidence and managed-subset terminology were reconciled, with no remaining blocker or material finding.
• Complete-diff review: initial correction-required for an exact private-path list in this publishable exit; final accept after the list was replaced by a generic protected-evidence statement, with no remaining blocker or material finding.

Validation

Current integrated validation includes:

• 16 skill-library unit tests, including the new exact-map contract;
• 58 checker integration tests;
• 8 release unit and 32 release integration tests;
• 8 user unit and 39 user integration tests;
• 22 Bats report-tool families;
• 28 project-skill integration families;
• development checker text and JSON at 7/7/7;
• public v0.2.0 checker text and JSON at 6/6/6;
• Python byte compilation, Bash syntax, and all command help;
• router hashes, six stable leaf hashes, relative links, catalog maturity, schemas, modes, Markdown links, confidentiality, ADR and exit sequences, and public-to-private independence; and
• Git unstaged whitespace checking.

The final validation pass and complete-diff review confirmed these claims against the exact precommit tree. An environment-conditioned public-v0.1 test root supplied the final checker and user integration reruns, so their complete 58 and 39 families executed without skips. The staged whitespace check runs only after the accepted diff is staged.

External state and artifacts

The public v0.2.0 checkout, reference repository, active public-backed integration, RepoMap checkout, private same-name router, and retired Superpowers state remain unchanged. RepoMap’s legitimate newer remote work was observed but not integrated. APG16 creates no dependency, plugin, runtime, scheduler, registry, daemon, installer-state schema, release candidate, tag, or public push.

Public artifact:

• docs/evaluations/apg16-public-workflow-router.md

Publication-excluded APG16 evidence is retained separately under the protected development boundary. It records exact private source identity, hashes, worker returns, duplicate-name observations, and review dispositions without creating a public dependency on its location or contents.

Limitations and exact external disposition requested

Current file, test, checker, and clean-context evidence cannot prove that a restarted Codex client can distinguish and explicitly select the repository-scoped candidate when the private same-name router is also visible. 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. Inspect the selector for duplicate agentic-praxis-grimoire-workflow entries.
5. Explicitly choose the repository-scoped APG16 candidate rather than the private router.
6. Ask it to route:
   • one ambiguous design-versus-planning case;
   • one simple no-skill case; and
   • one mandatory-chain rejection case.
7. Verify its result reflects:
   • route, do not orchestrate;
   • one primary capability or none;
   • material non-triggers;
   • no expanded authority; and
   • no private path or personal detail.
8. Run the development skill-library checker.
9. Report pass, pass-with-follow-up, or fail.

APG17 has not started and requires separate human authorization.

This site is open source. Improve this page.