What it owns
- Source identity and architecture map
- Capability boundary detection
- Dependency closure
- Adaptation recipe and packaging
- Generated contracts and qualification evidence
P04 · Foundry knowledge node
Autonomous repo-to-block foundry
Automate source understanding, boundary extraction and adaptation evidence while keeping semantic reuse-shape decisions explicit and reviewable.
Problem boundary
What this subsystem owns and what it must hand to the rest of Actionist.
What research already found
- Phase 8 defined source shapes, stages and 23 negative paths
- Full automation is the wrong target: shape choice and semantic adaptation need judgment
- A repository can yield several blocks or no block
Open first-principles questions
- What can AST/runtime probes establish autonomously?
- How do we detect hidden auth, settings and migration ownership?
- What diff/adaptation budget predicts a bad candidate?
- How is an upstream update replayed safely?
Inputs
- Repository
- Target host contract
- Desired capability
Outputs
- PackagedAsset
- CapabilityContract
- AdaptationRecipe
- QualificationDossier
Connected knowledge nodes
Scientific research protocol
Every research owner uses the same evidence funnel. No padding is allowed when a denominator is inapplicable or evidence is unavailable.
Prior evidence auditRead the canonical spine, all domain-linked artifacts, the 17-industry catalogue and existing contradictions before searching again.
Commercial 100 → 10Define a denominator, map approximately 100 companies/products, and produce first-party dossiers for the strongest 10.
GitHub 100 → 10Search and dedupe approximately 100 relevant OSS projects, then deeply inspect the strongest 10 at the capability and architecture level.
Local estate joinInspect AutoSaaS, Great Library, SISOCRM, 21st stores and other domain-specific precedents already on the laptop.
Innovation 100 → 10Generate a wide divergent idea register, score it against the problem and retain the 10 strongest falsifiable innovations.
First-principles synthesisDecompose the irreducible problem, challenge inherited assumptions, reconcile contradictions and state the minimum sufficient design.
Contracts and experimentsReturn the proposed contract, dependency edges, unknowns, falsifiers, experiments, stop rules and decisions.
Independent verificationA separate verifier checks counts, links, source claims, overlap, contradictions and unsupported conclusions before promotion.
Evidence and agent outputs
Existing research remains source evidence. New agent packets are written to one owned workstream directory and linked here after verification.
| Artifact | Location | State |
|---|---|---|
| Repo-to-block pipeline | research/actionmodel-builder-research-2026-08-26/phase-8/lanes/04-repo-to-block-mechanics/outputs/repo-to-block-pipeline.md | existing |
| Universal Block Framework | research/actionmodel-builder-research-2026-08-26/phase-8/lanes/01-universal-block-framework/outputs/universal-block-framework.md | existing |
| Block Contract v1 | research/actionmodel-builder-research-2026-08-26/phase-2/outputs/block-contract-v1.md | existing |
| Future verified agent packet | research/workstreams/P04-autonomous-repo-to-block-foundry/runs/<run-id>/ | planned |