Phase ID: APG22
Complete — cross-repository dogfood and v0.3 guidance-migration proposal recorded.
APG22 applies the provisional workflow router, guidance-synthesis procedure, and all nine retained language, test, and database profiles to bounded APG and RepoMap cases. It records descriptive routing, overlap, false-escalation, override, privacy, and maintenance evidence and proposes migration without changing any root guidance, private skill, target repository, public release, or active integration.
The initial matrix froze 10 router cases, 9 profile cases, and 8 guidance- synthesis cases before application. Fresh review found that the evidence record asserted but did not enumerate eight required synthesis classes. One bounded evidence-record correction froze those supplementary cases before applying them and normalized every application to the required measurement fields. All 35 expected dispositions matched; no skill behavior changed.
| Measure | Result |
|---|---|
| Router dispositions | 10/10 matched: 6 process selections, 2 no-skill results, 2 stops |
| Profile dispositions | 9/9 matched: 3 Green, 1 Yellow, 1 Orange, 4 Red |
| Guidance dispositions | 16/16 matched: 4 retain-root, 2 route-existing-owner, 2 project-owned, 2 split-required, 2 keep-private, 1 owner correction, 2 defer, 1 rights/authority block |
| Process/domain forms | 1 pair and 1 process/language/test triple |
| Process-overlap cases | 2 resolved without mandatory chaining |
| Project overrides | 1 stricter repository crisis threshold controlled |
| Classified artifacts | 4; 3 avoided false escalation |
| Semantic-over-structural decisions | 4 |
| False escalations / false non-triggers | 0 / 0 |
| Behavior-bearing corrections | 0; 1 evidence-record correction |
| Unresolved APG defects | 0 |
One synthetic metadata mismatch stopped as an integration fault, and one request to derive live Nix/database authority from routing stopped at the task authority boundary. Profile Red cases covered Python responsibility growth under stricter project policy, unsafe Ruby dispatch, unauthorized destructive PostgreSQL work, and a 13-step SQLite rebuild without an accepted exception. The Nix case confirms that structural Green for one merge family cannot downgrade semantic Orange.
The capability map is one schema-version-1, 16-entry, approximately 5 KB maintenance owner with an exact-set test. The router, synthesis leaf, and nine profiles together are approximately 151 KB of procedure text; ordinary cases load only the selected owner or owners rather than the complete portfolio. Nine separate profile source-refresh obligations remain the principal ongoing maintenance cost. These are descriptive measures, not a scientific or causal benchmark.
Application discovery was not measured. File presence, explicit reading, and semantic application are not fresh-session selector evidence. APG23 retains aggregate discovery and explicit-use smoke ownership.
APG’s root is already concise and owns authority, source treatment, retired- workflow prohibition, universal work rules, and a project map. No APG root reduction is justified.
RepoMap’s root combines essential project policy with detailed phase, test, Python, Go, PostgreSQL, and active-refactor guidance. A future RepoMap-owned phase may shadow concise routes to existing contributor owners and public APG profiles while retaining exact commands, thresholds, graph semantics, schema, compatibility, runtime safety, and destructive-action policy in RepoMap. That proposal requires current-source refresh, public v0.3 distribution, managed projection, discovery and non-trigger evidence, override proof, target acceptance, and byte-restorable rollback. It does not block APG publication.
Private global guidance remains the owner of personal, machine, integration, host-escalation, and unsupported-language policy. Selected generic process and profile judgment may shadow public APG only after v0.3 distribution and active integration. The current private same-name router is an older transitional six-process router, not semantic parity for the development public router. It must remain until public distribution, active cutover, duplicate-name/source handling, explicit use, non-trigger, override, and rollback evidence all pass. The transition must establish source-qualified fresh-session discovery during an explicit dual-source shadow before decommission and repeat it after cutover.
no separate public writing skill justified.candidate-new-skill; separately authorized implementation required.legacy-only version-bounded profile justified; separate
human authorization required; current stable-Zsh compatibility is not
established.Ten fresh non-author lanes accept router selection, profile escalation and override, synthesis ownership, privacy, root migration, private transition, native/manager boundaries, ZUnit scope, semantic identity, and the complete resulting diff after the recorded evidence and documentation corrections. No unresolved material finding or behavior-bearing APG defect remains.
APG22 performs no skill correction, maturity change, root rewrite, private- skill mutation, target edit, test or target-code execution, database or graph operation, Nix operation, dependency change, schema change, public release, active-integration mutation, application smoke, or APG23 work.
APG22A makes APG22-MANAGER-ASSIGNMENT-CANDIDATE-01 terminal by retaining the
independently written composing-approved-roadmap-assignments leaf
provisionally after a strong ordinary baseline and 30/30 frozen cases. The
historic corpus remains publication excluded and unchanged. Version-bounded
ZUnit evaluation is the remaining pre-APG23 objective.
APG22B makes the remaining pre-APG23 objective terminal by retaining a provisional ZUnit profile only for exact ZUnit v0.8.2 with Zsh 5.9.2 in the tested environment. The exact Zsh 5.3.1 pair is unsupported. APG23 remains a separately authorized phase and has not begun.