An icon is not finished when an SVG looks good. It is finished when meaning survives at native size, confusable pairs stay distinct, provenance is known, and the right actor has made the decision.
- Open the operations workspace — protected by Authelia; it displays only sanitized exported gallery artifacts and may offer the authorized live-human arena while an authenticated person has started
/loom bridge. - This wiki — public reference to the implementation and the larger design. Reading it grants no decision authority.
- Three layers, not one finished autonomous product:
- The OMP extension runs the implemented human-gated candidate workflow and is the only ledger reader/writer.
- The React workspace presents a validated snapshot/gallery export and can proxy the strictly limited authenticated browser arena contract to the human-started extension bridge.
- The Foundry blueprint describes the broader autonomous system; unconnected design remains design.
flowchart TD A["Frozen contracts"] --> B["Agent proposals"] B --> C["Deterministic checks and proofs"] C --> D["Independent inferred critique"] D --> E["Live human arena: TUI or authenticated browser bridge"] C --> F["Blocker: no override"] E --> G["Exported snapshot + gallery"] G --> H["Sanitized visual workspace"]
Prototype routes — D-071, 2026-09-15
The React entry now selects three full-set prototype views from the same validated /api/foundry snapshot: /prototype01 selects surgical, /prototype02 selects batch, and /prototype03 selects automatic. The Node host maps only those three exact additional paths to the client entry; this is not a general SPA fallback.
These are read-only exported-snapshot workbenches, not a connected full-set generation service. Scope, keep-lock, policy and exclusion controls are local view drafts; the automatic view inspects exported state rather than running automation. They do not grant the root cockpit’s restricted human-review channel, approval or release authority. See private page (sign-in required) for the current deployment and verification receipt; route wiring alone is not proof of public availability, human acceptance or launch.
Choose a route
| Question | Read |
|---|---|
| What actually exists, and what is still a design? | Architecture |
| Which agents do what, and where must they stop? | Agents and authority |
| What can I run in OMP? | Command reference |
| What makes an SVG admissible, and what counts as evidence? | SVG and evidence |
| How do budgets, frontiers, checkpoints and recovery work? | Search and decisions |
| Which sets and runs are represented, and how fresh is the data? | Sets and current state |
| How is this hosted, refreshed, verified and recovered? | private page (sign-in required) |
The boundary that matters
- Models can propose candidates and record explicitly inferred findings.
- Shortlisting, unshortlisting, rejection, restoration, champion promotion, undo, approval, and release belong to live humans. The TUI remains a full human path; the independently Authelia-authenticated browser path is a second arena only after the human starts
/loom bridge. - Browser authority ends at
shortlist,unshortlist,reject,restore,promote_champion, andundo. It requires explicit confirmation, exact 64-hex candidate binding for non-undo actions, current revision, authenticated identity, and the extension’s single-use authorization. Approval and release remain typed TUI-only. - A deterministic blocker cannot be voted away, averaged away, or overridden by a human, model, browser, bridge, or release governor.
- Root web code may render only sanitized exported gallery artifacts and proxy only the restricted authenticated request; it never reads
.iconloom/**or writes ledger state. The extension preserves immutable lineage, stale-revision refusal, typed decisions, and append-only hash-chained human events. - A mechanically eligible candidate is not an approved icon. An exported snapshot is not a live generation feed. An attractive proof is not certification.
- Quarantine and conservative fallback are valid safe outcomes in the design, not embarrassing states to hide.
Reading the evidence
- Implemented behavior: grounded in source and the extension’s enforced command/tool boundaries.
- Current state: a dated observation. The exported
generatedAttimestamp matters more than the time you opened the workspace. - Authorized policy: the 2026-09-08 browser-decision amendment defines a second human channel; it is not a runtime-verification receipt.
- Designed behavior: the intent in
docs/blueprint.yaml; not evidence that a worker, adapter or automatic release pipeline exists. - Source pointers use repository-relative paths and line numbers. They are audit coordinates, not public source-download links.