diff --git a/.agents/skills/README.md b/.agents/skills/README.md index 80bc94c..dbb8be6 100644 --- a/.agents/skills/README.md +++ b/.agents/skills/README.md @@ -3,7 +3,7 @@ This directory contains repo-local copies of canonical skills from `The-Interdependency/skill-lib`. -Source commit: `289d4959f7920efc214f180cca3443d8090f4095` +Source commit: `6ef2e4c123225f9db20e5230e5894c9c86b42ee6` Repo-local copies are not the source of truth. Edit `skill-lib` first, then propagate from the canonical source. diff --git a/.agents/skills/interdependent-work-graph/SKILL.md b/.agents/skills/interdependent-work-graph/SKILL.md index c960cbf..fc0ad3d 100644 --- a/.agents/skills/interdependent-work-graph/SKILL.md +++ b/.agents/skills/interdependent-work-graph/SKILL.md @@ -123,6 +123,53 @@ When this skill is active, produce or maintain: For machine-consumed work, also emit the versioned stack manifest or an explicitly named equivalent. +## Repository plan reports and overall portfolio plan + +When the question is not one bounded work graph but **what part of the overall effort each self-contained repository owns**, use the repository-report projection rather than inventing a centralized plan document. + +Each participating repository owns: + +```text +docs/work-graphs/repository-plan-report.json +``` + +That report states its exact source commit, authority and non-transfer boundaries, portfolio role, current claim, delivered surfaces, active frontier, next actions, blockers, cross-repository relations, machine entrypoints, and `hmmm`. + +The frozen input contract is: + +```text +interdependent-work-graph/repository-plan-report.schema.json +schema: the-interdependency.repository-plan-report +version: 1.0.0 +blob SHA: 9b347b2dff7692054b571602f30ee6d00c2e7265 +``` + +The deterministic reference aggregator is: + +```text +interdependent-work-graph/portfolio_plan.py +``` + +Its output contract is: + +```text +interdependent-work-graph/portfolio-plan.schema.json +schema: the-interdependency.portfolio-plan +version: 1.0.0 +``` + +Read `interdependent-work-graph/PORTFOLIO_PLAN.md` before producing or changing this projection. + +The portfolio plan is a **derived index of repo-owned claims**. It owns no repository canon. Missing or stale repo reports remain visible `hmmm`; do not reconstruct them from memory, package metadata, a neighboring repository, or the aggregator itself. Local checkout paths are excluded from the portfolio identity so the same report set hashes identically across machines. + +A repository plan report and a stack manifest are complementary: + +```text +repository plan report -> what this repository owns and where its work stands +stack manifest -> exact identities in one bounded cross-repository work graph +portfolio plan -> deterministic projection across supplied repo reports +``` + ## Validation A successful application demonstrates: @@ -136,6 +183,16 @@ A successful application demonstrates: - at least one cross-repository fixture, import, adapter, artifact, or workflow proves the connected path; - later agents can resume from the graph record without guessing which commits were used. +For the portfolio projection specifically, also require: + +- every supplied report validates against the frozen report contract; +- every report pins a source commit and the exact schema blob identity; +- duplicate repository reports fail closed; +- every cross-repository relation carries `authority_transfer: false`; +- report order does not change the derived portfolio identity; +- the portfolio digest excludes machine-local checkout paths; +- missing portfolio members are reported as incompletion rather than synthesized. + ## Anti-patterns - Assigning one AI to one repository when the task's truth conditions span several. @@ -146,6 +203,8 @@ A successful application demonstrates: - Using a digest as though it were a signature. - Hiding unresolved mappings behind constructor defaults. - Allowing validation workflows to mutate the source they are validating. +- Copying repo canon into the portfolio plan instead of deriving a report from the owning repository. +- Treating repository discovery or GitHub visibility as automatic portfolio membership. ## Minimal example @@ -168,3 +227,4 @@ One agent can follow the complete path. Separate agents can work on different pa - Whether the stack-manifest schema remains a procedural-skill reference contract or later becomes its own metadata-block/schema skill. - The next stack-manifest schema revision is expected to add explicit `certification_status_transfer` and `empirical_status_transfer` boundary fields, a canonical `repositories` ordering (for example by `repository` then `commit`) in place of declared-order identity, typed non-repository participants with digest/version/schema identities, and an explicit hashed edge list (`from`, `to`, `relation_type`) so distinct work graphs over the same participants cannot share one digest. Version 1.0.0 stays as sealed by the EDCM OEWN 2025 run. - Cross-repository merge orchestration remains repository-host dependent; the skill defines order and evidence, not a universal transaction mechanism. +- Automatic organization-wide portfolio discovery remains deliberately unselected; explicit report sets preserve intentional membership and visible incompletion. diff --git a/.github/workflows/quality.yml b/.github/workflows/quality.yml index ecb10fb..202ec0f 100644 --- a/.github/workflows/quality.yml +++ b/.github/workflows/quality.yml @@ -12,9 +12,9 @@ jobs: verify: runs-on: ubuntu-latest steps: - - uses: actions/checkout@v4 + - uses: actions/checkout@v7.0.1 - - uses: actions/setup-python@v5 + - uses: actions/setup-python@v7.0.0 with: python-version: "3.12" cache: pip diff --git a/docs/work-graphs/repository-plan-report.json b/docs/work-graphs/repository-plan-report.json new file mode 100644 index 0000000..8a5def1 --- /dev/null +++ b/docs/work-graphs/repository-plan-report.json @@ -0,0 +1,168 @@ +{ + "schema": "the-interdependency.repository-plan-report", + "version": "1.0.0", + "repository": "The-Interdependency/ptcna", + "contract": { + "repository": "The-Interdependency/skill-lib", + "path": "interdependent-work-graph/repository-plan-report.schema.json", + "version": "1.0.0", + "blob_sha": "9b347b2dff7692054b571602f30ee6d00c2e7265" + }, + "source": { + "branch": "main", + "commit": "4509d33419aa25e6a9cfef415055e378b8f37edc", + "generated_at": "2026-08-15", + "note": "This report describes the executable PTCNA 0.1.1 runtime at the cited main commit plus the current repo-owned plan. Operational-shell and report-only maintenance do not upgrade runtime, mathematical, measurement, or architectural evidence standing." + }, + "authority": { + "owns": [ + "PTCNA neural, circle, seed, and core runtime definitions and implementation", + "PTCNA neural-only reverse-mode differentiation and structural host boundaries", + "PTCNA local composition, checkpoint, propagation, timing, and audit behavior", + "PTCNA producer-side integration boundaries and runtime evidence" + ], + "does_not_own": [ + "UCNS mathematical representation canon, higher-gonol producer profiles, or proof status", + "EDCM measurement definitions, empirical validity, or result authority", + "METAPAT semantic authority", + "skill-lib organization-wide build and evidence doctrine", + "ZFAE repository authority outside the PTCNA-local implementation boundary" + ], + "non_transfer": [ + "PTCNA runtime success does not establish UCNS mathematical validity", + "UCNS proof or representation status does not establish PTCNA learning efficacy", + "EDCM measurement results do not become PTCNA-owned evidence merely because a caller injects them", + "a functioning four-layer implementation does not establish that prime structure, current ring constants, or current weight topology are necessary or superior", + "suspended integration remains suspended until an exact producer contract is independently available and reviewed" + ] + }, + "portfolio_role": { + "summary": "Own and test the executable neural/circle/seed/core architecture while keeping mathematical representation and measurement authorities external and fail-closed.", + "upstream_contract": "PTCNA consumes only explicitly authorized external producer or measurement contracts; absent contracts remain typed suspended states rather than inferred integrations.", + "downstream_contract": "PTCNA emits runtime behavior and state without transferring architectural necessity, UCNS proof status, or EDCM measurement validity to consumers.", + "reports_to": { + "repository": "The-Interdependency/skill-lib", + "skill": "interdependent-work-graph", + "relation": "repo-owned runtime and architecture-plan input; no authority transfer" + } + }, + "status": { + "state": "active alpha runtime; architecture modernization suspended on upstream falsification", + "current_claim": "PTCNA 0.1.1 implements one four-layer runtime in which reverse-mode gradients are owned by the neural layer while circle, seed, and core remain non-differentiating structural hosts. UCNS higher-gonol integration is explicitly suspended, EDCM remains external, and no claim is established that the current prime/ring topology or learned weight path is necessary, superior, or the final architecture.", + "latest_main_milestone": { + "commit": "4509d33419aa25e6a9cfef415055e378b8f37edc", + "description": "merged the reconciled four-layer v0.1.1 runtime with one CircleTensor, neural-only reverse-mode scalar ownership, fail-closed UCNS integration, and external EDCM measurement injection" + } + }, + "delivered": [ + { + "surface": "four-layer PTCNA runtime", + "status": "implemented alpha runtime", + "boundary": "implementation demonstrates executable composition, not architectural necessity or superiority" + }, + { + "surface": "neural-only reverse-mode differentiation", + "status": "implemented and tested runtime boundary", + "boundary": "circle, seed, core, fiq, and other structural hosts do not thereby gain mathematical or empirical standing" + }, + { + "surface": "UCNS integration boundary", + "status": "typed suspended fail-closed adapter", + "boundary": "no PTCNA-specific higher-gonol producer profile is currently authorized or consumed" + }, + { + "surface": "external measurement boundary", + "status": "implemented injected-provider contract", + "boundary": "PTCNA does not own EDCM measurement semantics or validity" + }, + { + "surface": "0.1.1 cross-repository input manifest", + "status": "sealed historical coordination record", + "boundary": "its July producer identities are evidence for the 0.1.1 reconciliation only, not current stack identities" + } + ], + "active_frontier": [ + "keep the operational shell aligned with current skill-lib doctrine and supported GitHub Actions runtimes without changing PTCNA architectural evidence standing", + "leave UCNS higher-gonol integration suspended while the UCNS-EDCM architectural reconstruction claim is under preregistered falsification", + "if the upstream reconstruction architecture survives, freeze a PTCNA experiment that compares UCNS-derived relational initialization or assignment against the current learned/hash-projected path and simpler matched baselines before replacing runtime architecture", + "if the upstream reconstruction architecture is falsified, deprecate dependent UCNS-specific PTCNA integration assumptions rather than repairing them inside PTCNA", + "resolve whether the embedded ZetaEngine remains a bounded PTCNA-local measurement-to-learning adapter or should be removed in favor of separate ZFAE authority before further Zeta development", + "test sustained-load and long-horizon state behavior only after the architecture under test and its authority boundaries are frozen" + ], + "next_actions": [ + { + "action": "maintain the current four-layer runtime and fail-closed UCNS boundary while the UCNS-EDCM run-to-completion resolves the load-bearing reconstruction claim", + "owner": "The-Interdependency/ptcna", + "dependency": "do not introduce a PTCNA-specific UCNS producer profile or redesign weight topology before upstream architectural evidence is resolved" + }, + { + "action": "on upstream survival, preregister the smallest decisive PTCNA architecture test comparing UCNS-derived relational initialization or assignment with the current implementation and simpler matched-information baselines", + "owner": "The-Interdependency/ptcna", + "dependency": "requires exact surviving UCNS identities, frozen construction rules, explicit EDCM measurement authority, and outcome criteria fixed before execution" + }, + { + "action": "on upstream falsification, record and remove dependent UCNS-specific PTCNA architecture assumptions before further implementation", + "owner": "The-Interdependency/ptcna", + "dependency": "triggered only by a falsified load-bearing upstream claim with propagated downstream effect" + }, + { + "action": "freeze the authority decision for the embedded ZetaEngine before modifying its learning role", + "owner": "The-Interdependency/ptcna", + "dependency": "requires comparison with the current ZFAE repository contract; unresolved authority must remain hmmm" + } + ], + "blocked": [ + "activation of UCNS higher-gonol composition is blocked on an exact reviewed PTCNA-specific UCNS producer profile and on survival of the load-bearing upstream reconstruction architecture", + "replacement of current learned/hash-projected neural topology with UCNS-derived relational initialization is blocked until a preregistered comparison can be interpreted against simpler baselines", + "further architectural expansion is blocked from treating current prime constants, ring sizes, heptagram propagation, or hard-coded ring weights as established necessities", + "ZetaEngine ownership migration or expansion is blocked until the PTCNA-local versus separate-ZFAE authority boundary is frozen" + ], + "cross_repository_relations": [ + { + "repository": "The-Interdependency/ucns", + "relation": "mathematical and relational producer candidate; PTCNA integration remains suspended until an exact reviewed producer profile and surviving architectural evidence exist", + "authority_transfer": false, + "proof_status_transfer": false + }, + { + "repository": "The-Interdependency/edcm", + "relation": "external measurement authority whose explicitly injected outputs may influence PTCNA learning without becoming PTCNA-owned measurement claims", + "authority_transfer": false, + "measurement_status_transfer": false + }, + { + "repository": "The-Interdependency/skill-lib", + "relation": "canonical build, evidence, skill propagation, and cross-repository coordination doctrine", + "authority_transfer": false + }, + { + "repository": "The-Interdependency/interdependent-lib", + "relation": "downstream library consumer of the PTCNA package surface", + "authority_transfer": false + }, + { + "repository": "The-Interdependency/zfae", + "relation": "separate repository whose authority relationship to the embedded PTCNA ZetaEngine must be resolved before further Zeta development", + "authority_transfer": false + } + ], + "machine_entrypoints": { + "repo_report": "docs/work-graphs/repository-plan-report.json", + "historical_stack_manifest": "docs/work-graphs/ptcna-0.1.1-inputs.json", + "system_overview": "README.md", + "architecture": "docs/architecture.md", + "neural_runtime": "ptcna/neural/pcna.py", + "ucns_boundary": "ptcna/ucns_integration.py", + "external_measurement_adapter": "ptcna/neural/zeta.py", + "quality_workflow": ".github/workflows/quality.yml" + }, + "hmmm": [ + "whether the UCNS-EDCM prime-view reconstruction architecture survives its run-to-completion adversarial program", + "the exact PTCNA-specific UCNS producer profile, if one remains justified after that program", + "whether UCNS-derived relational initialization or assignment outperforms the current implementation and simpler matched baselines", + "whether the current ring sizes, heptagram propagation, prime constants, and fixed ring weights contain irreducible useful structure or historical accident", + "the authority boundary and migration path between PTCNA's embedded ZetaEngine and The-Interdependency/zfae", + "sustained-load behavior across the complete four-layer seam", + "PyPI 0.1.1 publication artifact identity; the GitHub repository currently exposes no release record" + ] +}