Runtime, verification and release

Run heterogeneous capabilities in explicit profiles, verify the complete workflow, and release an exact recoverable composition.

Problem boundary

What this subsystem owns and what it must hand to the rest of Actionist.

What it owns

Package/microfrontend/service/worker runtime profiles
Preview isolation
Build, contract, visual and workflow tests
Deployment and subdomains
Version pinning, recovery and rollback

What research already found

A passing build is not client workflow proof
Different reuse shapes need different runtimes
Existing work defined receipt families and negative paths but admitted zero production blocks

Open first-principles questions

Which runtime profiles are v1?
What sandbox/deploy infrastructure should be rented?
How are failures attributed per capability?
Can blocks upgrade independently?

Inputs

AssemblyPlan
Packaged assets
Host bindings
Acceptance fixtures

Outputs

QualificationDossier
ReleaseManifest
Deployment
RollbackPlan

Connected knowledge nodes

P04 · Autonomous repo-to-block foundry P09 · Data and state plane P10 · Identity, settings and navigation host P11 · Connector and external-action plane P12 · Deterministic composition planner P13 · Preview, editor and change loop P15 · Continuous corpus and production learning

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
Evaluation and admission plan	`research/actionmodel-builder-research-2026-08-26/phase-2/outputs/evaluation-and-admission-plan.md`	existing
Pilot receipt runbook	`research/actionmodel-builder-research-2026-08-26/phase-4/outputs/pilot-receipt-runbook.md`	existing
Builder architecture	`architecture/feature-matrix/ARCHITECTURE.md`	existing
Future verified agent packet	`research/workstreams/P14-runtime-verification-and-release/runs/<run-id>/`	planned