00014v0-1-closed-v0-2-roadmap-acceptedAPG9 authorized one bounded investigation, reconciliation, architecture- decision, roadmap, documentation, validation, private development commit, push, and report phase. It accepts the maintainer’s completed public v0.1.0 release, public-sourced user-global integration, Superpowers decommission, and bounded post-decommission RepoMap smoke; reconciles current owners while preserving historical exits; and accepts APG10 through APG14.
The public and reference repositories remained read-only. APG9 changed no skill, maturity state, dependency, project-skill implementation, test policy, Superpowers state, or v0.2 public surface.
The fetched development and reference repositories matched their expected clean upstream heads. The public repository matched the expected v0.1.0 head, tag, and one-commit squashed history. Public v0.1.0 contains the six canonical skills, repository discovery links, reporting components, governance, evaluations, status records, and licensing and contribution terms. Public and private histories remain intentionally independent.
The public tracked surface omits the documented bin/apg-project-skills
wrapper while retaining the guide and implementation modules. Public v0.1.0
also predates APG-TEST0’s test layout and retains pre-publication current-state
text. APG9 records these as v0.1 limitations and assigns deterministic release-
surface correction to APG12 without modifying or republishing public.
The maintainer’s user-global APG integration resolves to a clean public v0.1.0 checkout. The current environment exposed all six public skill leaves with content matching the release. That integration remains separate from repository-local and managed project-local projections.
The maintainer explicitly decommissioned Superpowers. The accepted fresh RepoMap smoke discovered six skills, explicitly applied the review skill, passed default and explicit managed checks, preserved RepoMap, and did not use Superpowers as workflow authority. APG9 independently reran both managed check forms successfully and preserved RepoMap’s clean tracked state.
Preserved Superpowers source remains external historical evidence rather than installation or restoration authority. APG9 does not claim an exhaustive active-project inventory, universal workflow coverage, automatic selection, comparative superiority, or tested restoration.
This APG9 human mandate supplies APG8’s previously requested final external acceptance. APG0 through APG8 are the closed v0.1 epic, with all historical terminal outcomes preserved, including APG3’s blocked preflight. Existing exits were not rewritten.
APG-TEST0 is the first post-v0.1 development-foundation phase. Its repository layout owns 22 Bats report-tool behavior families and 28 Python project-skill integration families. Both suites passed before APG9 edits and again from the resulting APG9 state.
Accepted ADR 0006 defines these separately authorized phases:
The roadmap is dependency ordered but is not a preapproved execution envelope. Each phase requires a separate human assignment.
All six skills remain provisional. The maturity audit found no current
material authority, privacy, safety, or procedure defect. ADR 0006 targets each
skill for individual stable review in APG13. Repeated positive use and
representative non-triggers remain separate requirements. Cross-repository
breadth and clean comparison are useful evidence but are not independent
blockers; one unresolved material defect may block an individual skill under a
recorded correction condition.
The tracked Karpathy Guidelines source remains experimental. Its declared MIT frontmatter is not complete upstream provenance or notice evidence. APG10 owns final adopt, defer, and reject decisions, defaults to independent synthesis, and may not add a seventh skill without a separate consequential decision. APG9 copies or adapts no source expression.
Every former unnumbered theme has a preliminary owner or terminal condition. APG11 owns the durable closure ledger; APG12 owns distribution and release validation; APG13 owns maturity; and APG14 owns publication. Existing artifacts satisfy the core v0.1 procedure, project-local projection, governance, decommission, rollback, and source-preservation topics. Project-owned or unjustified themes are rejected, and the remaining research topics have explicit reconsideration conditions.
Historical phase exits and all six SKILL.md files remain unchanged.
Five read-only workers returned release reconciliation, six-skill maturity, legacy-theme closure, experimental-source overlap, and roadmap-critic evidence. The manager independently inspected and dispositioned their findings. The critic identified the public wrapper omission, stale current claims, earlier maturity-policy ambiguity, decommission overclaim risk, distribution-scope confusion, duplicate correction phases, and automatic-successor risk. Current artifacts record the bounded corrections.
A fresh non-author finished-diff review inspected publication and history claims, distribution boundaries, decommission and smoke limits, APG8 and APG-TEST0 treatment, skill immutability, maturity deferral, experimental-source policy, legacy ownership, public/private boundaries, unchanged external repositories, exit truthfulness, and the APG10 stop boundary. Its terminal disposition is recorded in publication-excluded evidence.
Fresh validation from the resulting state established:
SKILL.md content and six provisional states;0006 and exit sequence through 00014;No public/ref mutation, Superpowers restoration, v0.2 publication, or APG10 work occurred.
APG10 is the next decision and did not start. It requires a separate human assignment. APG9 authorizes no successor implementation, skill edit, maturity change, public or reference mutation, Superpowers restoration, dependency, validator, framework, or v0.2 publication.
External review is requested to accept APG9 as Complete — v0.1 epic closed
and v0.2 roadmap accepted; preserve all historical exits; retain all six skills
at provisional; accept ADR 0006 and APG10 through APG14 as separately
authorized phases; retain the v0.1 public-wrapper limitation for APG12; and
authorize no APG10 work automatically.