This room expands the framework report: what counts as a block, the proposed dossier, eligibility/admission rubric, staged adaptation protocol, quarantine policy, automation boundary, first-pilot envelope, ownership and rollback.
From the framework report, not a loose metaphor.
A block is a manifest-backed installable item with a known interface, provenance, license, test evidence, and rollback boundary.
It can be a UI/CRUD surface, data adapter, workflow node, scaffold module, or agent-operation capability. The unit is not “the repo.” The unit is the smallest controlled artifact that can be installed, adapted, tested, and removed.
Every field becomes a reviewable receipt.
Block ID, source URL, pinned commit, fork, extracted paths, transformation history, owner, and intended capability.
Inputs, outputs, routes, data schema, environment variables, required services, provider coupling, and allowed side effects.
License, SBOM, static/AST, unit/build, browser, screenshot, accessibility, human review, admission state, and rejection/quarantine reason.
Original versus adapted files, token substitutions, schema changes, removed features, generated code, and reason for every transformation.
Tenant boundary, secrets, migrations, read/write surface, approval checkpoints, idempotency, retries, read-back, recovery.
Named owner, release date, rollback artifact, data recovery plan, deprecation path, and acceptance decision.
Candidate selection does not skip gates.
| Gate | Question | Receipt | Stop condition |
|---|---|---|---|
| Provenance | Do we know what source and commit this came from? | URL, pin, extraction map, source integrity. | Unknown source, mutable tip, or unverifiable lineage. |
| License | Can the assembled/adapted artifact be used and redistributed? | SPDX result, obligations, dependency/asset scan. | Unknown, incompatible, or unreviewed license. |
| Static / AST | Can we understand the code and find dangerous surfaces? | Scanner output, dependency tree, AST findings. | Unbounded eval/exec, secrets, hidden side effects. |
| Data | What data does it read/write, and who owns it? | Schema/tenant map, migration plan, fixture proof. | Provider coupling or write authority not bounded. |
| Build / smoke | Can the adapted block deterministically install and run? | Install, typecheck/build/test/browser logs. | Sandbox green only, flaky or irreproducible output. |
| Visual | Does it honour the approved direction and interaction contract? | Screenshot baseline/diff, accessibility, review. | Unbounded visual drift or inaccessible critical flow. |
| Human | Who accepts the risk and owns rollback? | Named decision, release/rollback record. | No accountable owner or recovery path. |
Constrain edits by layer.
Read source, manifest, license, dependency graph, screenshots, routes, and data model. No edits or installs in the shared tree.
Copy only the intended capability into a disposable workspace; produce the block manifest and ownership map.
Map tokens, routes, schema, imports, and provider boundaries to the Actionist contract. Record every transformation.
Run source/license, static, build, unit, browser, screenshot, and human gates with repair capped and logged.
Admit only with a complete envelope; otherwise preserve evidence and quarantine the candidate with a reason.
Ship behind an owner and reversible boundary. Observe, compare, and retire without orphaning data or dependencies.
Recommendation from the framework report.
Start with one narrow, permissive, read-only UI/CRUD block and prove the whole envelope.
It constrains side effects while still proving visual fit, routes, schema, registry, build, and browser behavior.
Time to admit, adaptation churn, repair count, token fidelity, build repeatability, evidence completeness.
Only after this works: write adapters, vertical atoms, agent actions, and larger composite blocks.
Local report copy is kept under the pack.
Initial landscape, definition, dossier, rubric, staged adaptation, coverage ledger, final pilot, rollback, and verdict.
Open full report ↗Machine-readable cluster-007 execution sequence used by the AM corpus lane.
Open AM gate plan ↗Schema reference for the machine-readable artifact envelope.
Open schema ↗Action Model-specific block framework and implementation boundary.
Open design framework ↗Choose a source above. The local reader loads the original artifact.