MVP Readiness Snapshot

Snapshot date: 2026-08-23.

This table is an estimated cross-document readiness snapshot for canonical Story, Proposal, and Solution documents.

Scope rules: localized duplicates (*.pl.md), indexes, backlog files, implementation notes, coding guides, and generated registries are excluded. Solution rows use the main NNN-*/NNN-*.md document for each component.

Estimation basis: node/docs/MVP.md defines the hard-MVP story set (story-000, story-002, story-005, story-006, story-008, story-010, story-011); doc/project/60-solutions/CAPABILITY-MATRIX.md provides coarse implementation status; each document text is used as fallback when no capability row exists. part of MVP tracks the hard-MVP story set plus explicitly promoted release-blocking proposals/contracts, and is treated as a release-blocker flag: a row with part of MVP = true must be ready before the hard-MVP release can be called closed. MVP ready may still be true for a post-hard-MVP document when its own MVP slice is implemented. readiness % is a document-level engineering estimate over contract clarity, implementation evidence, test coverage, and remaining risk; it is not computed mechanically from the number of capability rows and is not a release-signoff fact.

Hard-MVP release-blocking stories:

• story-000
• story-002
• story-005
• story-006
• story-008
• story-010
• story-011

Hard-MVP release-blocking proposals/contracts:

• proposal-048 / Sensorium OS action-class runtime
• proposal-073 / node-local Agent organ
• proposal-076 / federation-root.v1
• proposal-081 / horizontal causal, replication, and scoped-nym-proof primitives
• proposal-082 / Sensorium Interfaces
• proposal-083 / Sensorium Interactive Interfaces

P085 closeout summary:

Proposal	Readiness	Role in P085 closeout	Remaining gap
P049	100%	Required Flow substrate and P049-008 are complete	No hard-MVP or P085 dependency gap; template/ref and demand-driven language extensions remain explicit post-MVP work
P069	100%	Corpus role, overlay, turn, and Room binding complete	No P085 dependency gap; additive facilitator role P069-ROLE-001 remains explicitly deferred to post-MVP
P070	100%	Room authority and floor admission complete	No P085 dependency gap
P085	100%	Package, policy, registry, and package-bound hardware-VM acceptance complete	No implementation gap; P085-017 remains explicitly deferred to future P087 work

P085 is promoted to Solution 048. The proposal remains the detailed implementation record and tracker; the solution is the canonical description of the implemented operator-sovereign extensibility architecture.

The 2026-08-22 P049 refresh records the implemented hard-MVP executor slice as complete. Both executor classes, static host-owned Flow steps, bounded policy decisions and loops, durable traces, operator inspection, signed package activation, Story 009 migration, and P049-008 offer consumption have code and acceptance evidence. A separate host-resolved template/ref remains a concrete post-MVP task; dynamically generated steps, general scratch state, and additional helper profiles remain demand-driven and do not reduce MVP readiness.

The 2026-08-03 refresh incorporated the then-current worktree state. It retains the previously recorded hard-MVP and federation-root slices and adds the latest P063/P064/P066 closure: live provider-backed image generation/edit, durable evaluation-gated train.adapt, bounded repair and output-rail diagnostics, egress-class limits, shared participant-id and monotonicity primitives, explicit local-model provisioning UX, typed communication-control admission including native adapter-envelope mapping, session-memory projection, locale framing, deterministic embedding cache, Inquiry Flow compilation, federation-root provider release-key endorsements, activation-time authority revalidation, and their synchronized Node ledger, proposal trackers, and tests. It also records the post-MVP real macOS arm64/Metal acceptance of a revision-pinned Bielik Q8_0 package through signed operator authority, conformance-gated activation, real inference, exact dirty-restart process adoption, upgrade, rollback, and removal. It also includes the explicit Assistant Channel to Agent escalation, recovery, outcome-draft, and render-only acceptance slice tracked by Solution 045, plus the post-MVP Room-attested Corpus-chair binding, inert Corpus answer-draft acceptance, bounded node-local WSS deliberation with metadata-only authority observations and restart recovery, separately authorized signed Agent-chair answer publication, and registered local-policy evaluation of role assignments and policy-rendered instruction overlays through Inquirium host prompt assembly, with append-only delta recovery, tracked by P069/P073 and Solutions 036/038. P070 Phase 6A provides authority-signed member-visible relay epochs, outbound-only failover, host configuration and diagnostics, Agora plus Artifact Delivery endpoint recovery, and executable host-TLS deployment evidence. Phase 6B adds the non-member federation relay profile with signed pairwise sender-key distribution, authenticated encrypted delivery, join/leave/revoke rotation and fencing, metadata-only relay diagnostics and audit, strictly newer sealed-relay failover, and executable 21-check multiprocess host-TLS deployment evidence. P070 is therefore complete for both specified relay profiles; the hard-MVP verdict is unchanged because Phase 6B is post-MVP scope.

The 2026-08-01 post-MVP Corpus refresh adds the signed critique-to-regeneration join, durable daemon recovery, live Story 012 baton integration, strict role grammars, deterministic replay, and a ten-pair real-model calibration. The measured Qwen2.5-Coder 7B successor ready rate is 0.1, below the 0.6 promotion threshold; therefore the path remains opt-in and does not change the existing 100 percent hard-MVP Corpus or baseline Story 012 rows.

The same post-MVP workstream now retains a fresh passing 31-check model-authored discovery report for powerdns-bind-missing-zone-data.v1. Two supervised Qwen2.5-Coder 7B runtimes reached the exact DNS goal through one failed and one corrected admitted experiment with fresh terminal evidence, per-effect HIL, and P083 lease release. The retained 2026-08-23 run measures 369,053 ms of deliberation and 15,863 model tokens. It additionally activates the P085 operator package before deliberation, uses its four-passage Flow and turn-order producer, and proves restart, revocation, and stale-authority refusal without fallback. A separate fresh unseeded success exists, while fixed-seed repeatability remains open. The run does not satisfy the separate 0.6 critique-to-regeneration promotion threshold or prove seeded repeatability. It therefore updates evidence and trackers without changing the existing Story 012, P069, or Solution 038 readiness percentages.

The post-MVP P084 workstream now has the reusable daemon-owned http.fetch.bounded foundation and its first static extractor: eleven closed generic/domain contracts, pure fetch and Sensorium Web cores, exact consumer/action/origin admission, bounded DNS and destination classification, connection pinning, TLS and redirect enforcement, one total deadline, global/per-origin concurrency, content-bound Artifact Delivery continuation, aggregate operator evidence, deterministic local HTTP/TLS conformance, and a channel-only frozen Python extraction profile 1.1.0 with an eleven-check offline corpus, including deterministic parser-event and element-depth limits. The factory requires a named no-egress sandbox and refuses when it is absent, but the current operating-system adapter does not yet provide process-level enforcement evidence. Durable source/cache/scheduler runtime, persistent operator projection, Sensorium observation admission, and P082 publication also remain open. P084 is therefore partial post-MVP work and does not change hard-MVP readiness.

The post-MVP P085 foundation now freezes limit-classification.v1 and a reviewed, JCS-digested limit-classification-registry.v1 envelope over 47 Inquirium limits and three explicit exclusions. Pure validation, dual JSON-Schema/semantic fixture checks, recursive all-unsigned-width source discovery with signed/float rejection, concrete pre-policy evidence for every boundary-safety classification, and separate drift/review-deadline CI gates prevent new or changed implementation maxima from becoming silent policy. The accepted inquirium-resource-profile.v1 contract now projects exactly the 38 operational axes, excludes the nine boundary-safety axes, and has a direct drift gate equating the registry records, InquiriumResourceLimit::ALL, and closed schema properties. It drives a pure monotonic source-chain resolver. The daemon resolves a sparse local operator config overlay at startup, preserves the effective digest across restart, records winning per-axis provenance in prompt-free traces, and enforces all 38 operational axes at their local owning request, response, prompt/output-schema, conformance, memory, locale, feedback, operator-question, image, training, embedding, classification, reranking, or text-operation boundary. Agent memory policy admission and projection consume the current assistant.turn profile through a narrow daemon-owned resolver rather than compiled defaults. The next post-MVP vertical now adds accepted signed envelope and revocation contracts, exact active operator-binding verification at admission, recovery, and applicable current use, executable classify/rerank plus experiment-class scope, and an append-only schema-versioned SQLite revision lifecycle. Independent profile lineages may share a revision number; multiple matching envelopes intersect deterministically by operation and experiment class, and package activation checks the exact closed operational class. Exact replay reconciles runtime from the canonical current fact, status remains read-only, explicit reconciliation commits expiry, and corrupt or unverifiable active recovery fails closed; only valid absence/revocation/expiry falls back to the explicitly unsigned local config source. Cached profiles bind every envelope ref, digest, and operator binding and perform a read-only exact-current check at use. The store has a 64 MiB main-database ceiling and an 8 MiB WAL checkpoint target. The next foundation slice adds accepted offer-bound NSE, deterministic table, bounded middleware-evidence, signed derived-capability, guard, attention-budget, federated-envelope, and node-posture artifacts, a closed refusal vocabulary and projection, package, activation, transition, revocation, conformance, operator-inspection, signed loose-import, import-receipt, and host-owned conformance-run contracts. Table and Rhai now share one host validator. A second generic offer-bound algebra covers the eleven declared Inquirium, Corpus, and Agent policy hooks through one closed hook/class/version table; its decisions may only select, order, narrow, restrict, raise risk, or select a host-offered transform profile. Broadcast hooks therefore no longer carry arbitrary payload rewrite outcomes; local activation owns producer priority and required/advisory behavior; the common compositor validates every activation and reserves aggregate budget before invoking producer callbacks, then rejects digest substitution, selecting disagreement, and hidden fallback. Required producer failure never becomes an implicit defer. JSON-e Flow has a typed decision step backed by a 256-entry process-local daemon offer registry with monotonic bounded TTL and reuse, exact Flow/hook/digest/producer binding, consume-before-execute semantics, restart invalidation, narrow result projection, and prompt-free durable resolution traces. The ordinary supervised local HTTP executor can contribute bounded nse-middleware-evidence.v1; the daemon rechecks the exact invocation, module, package digest, grants, schemas, causal ref, candidate set, offer fields, and transport bounds before evidence changes the final offer digest. An opt-in reference Python producer now proves inert package installation, content-addressed package-specific conformance, operator-signed activation, real loopback dispatch, evidence admission, nse-table selection, and JSON-e Flow projection. The daemon rechecks canonical durable producer authority before and after process execution; restart, rollback, crash, expiry, revocation, safe mode, substitution, and conformance replacement fail closed. The common 28-code refusal vocabulary now has one distinct reaching test per code and a dedicated drift gate. The lifecycle process smoke also traverses an exact active JSON-e Flow, recomputes its Inquirium-derived capability at the selected runtime boundary, and proves that the admitted prompt-free authority decision survives restart without becoming reusable ambient authority. The daemon-owned lifecycle exposes authenticated loopback import, conformance, durable/session activation, exact session deactivation, rollback, revocation, live-operator-only safe mode, and status routes. Three formal capabilities admit those routes only as host-local control surfaces and refuse dispatch, passports, advertisement, and federated discovery. Disabled-by-default loose import requires a detached signature, exact digest, trusted key, canonical allowlisted root, and inert install; a host-configured bounded runner, rather than package content, owns conformance execution. Its implementation, optional interpreter, runtime, and refusal corpus are owner/permission checked and pinned by identity and digest; passing reports bind the exact corpus and runtime, and the host recomputes canonical report identity. Lifecycle authority mutations and dependent session terminal facts commit atomically and retain typed terminal reasons. A bounded scheduler records session expiry before removing in-memory authority; durable/session activation and producer use additionally recheck signed host OS/architecture compatibility, primitive capability eligibility, and current exact derived-capability references. Resource-envelope references remain fail-closed until their exact cross-store provider is installed. The exact current operator binding for durable and session activation, package, conformance, producer, revocation, safe-mode, and expiry state are rechecked at use. Session facts use host observation time and reject duplicate event kinds for one activation. A real daemon process smoke proves exact session replay, restart discard, scheduler expiry, manual deactivation, safe-mode fencing/recovery, and the durable lifecycle across restart and terminal revocation. Federation, posture, trace-explorer integration, and three-node acceptance remain open. A separate WAL SQLite lifecycle service implements inert install, exact conformance binding, self-verifying domain-separated activation and revocation signatures, immediate-transaction generation journaling and recovery, terminal revocation, restart-discarded session authority with metadata-only audit, generation-bound compiled cache, persistent live-operator-only safe mode, and canonical-root/owner-bound audited prompt-free CLI inspection. Signed derived-capability, monotonic-guard, and attention-budget declarations now verify the exact operator authority, persist as sequential append-only revisions, recover after restart, and appear as bounded prompt-free inspection metadata. The attention budget gates operator-question notification projection through durable rolling windows, grouping, quiet windows, and a separate never-approving security lane; the question is persisted before any notification is suppressed. The effective question deadline is narrowed by request timeout, declaration expiry, and the current availability-window end. Equivalent questions share one durable bounded group while retaining independent facts; the host derives their grouping identity from a closed canonical semantic descriptor rather than prompt wording, per-attempt operation refs, or caller-selected response idempotency. A bounded declared operation digest sharpens the descriptor when present; its absence remains explicit and cannot reactivate an attempt-ref fallback. Prompt-free inspection exposes rolling usage and bounded member refs. The accepted effective-policy read model now composes the audited lifecycle view with all 38 Inquirium axes, five domain registries, and optional federation evidence. Its initial views foreground only material differences and one decisive restriction, cap visible detail at twelve items, expose stable bounded drill-down refs, and mark every missing owner source unavailable rather than presenting an apparently complete empty policy. Process acceptance proves inspect, explain, and graph agree on the same refusal without prompt, signature, secret, or model-output bytes. It also projects content-addressed package-backed policy-hook decisions and bounded cache/store occupancy, inert/active package counts, active policies, nearest expiry, and required-index health. Restart reconciles the complete fixed attention-store ceiling, ordinary admission uses a smaller cleanup pass, capacity pressure performs one bounded global stale-event reclamation before refusal, and read-time fencing prevents expired groups from being resurrected. Inquirium now has distributor-owned per-axis safety ranges: a signed operator envelope may widen a compiled default only inside its explicit range, while missing ranges, unsigned local configuration, and task/session overlays remain fail-closed or tighten-only. It also has a pure stricter federated-envelope intersection without mutating the host baseline. Derived-capability evaluation now rechecks exact active JSON-e Flow inference grants and current Corpus role plus Room membership snapshots against P072 dispatch eligibility, current operator authority, stable fact digests, trust, sanctions, expiry, and the exact selected-use context without registering a new federated capability. The first reviewer-derived capability is evaluated only at the selected inquirium.generate boundary. The same host-owned static-producer path now applies all eleven local Inquirium, Corpus, and Agent policy hooks at their owning boundaries while leaving each domain's ordinary validator authoritative. Package-backed hook outcomes now produce bounded, content-addressed prompt-free operator decisions. Signed restrict/grant-set guards intersect content-addressed tables once at package activation, the shared inquirium.generate capability-use boundary, Sensorium directive actuation, Agent effect-proposal admission, and Inquirium model-selection offer admission. It revalidates current operator binding, package activation, conformance, safe mode, revocation, and package derived-capability dependencies under the exact activation operator binding; another active operator's overlay cannot satisfy them. Its bounded prompt-free decision separates resolved guard types from concrete derived restrictions, and a reached boundary with no active policy records an inert policy-absent fact. A daemon-process smoke admits one signed five-anchor policy set and reaches package activation, capability use, NSE decision admission, Sensorium actuation, and Agent effect admission through their owning daemon boundaries. It proves ordinary admission before and after restart plus typed synchronous refusal after safe mode or package revocation. The local policy-admission route is process-tested for valid admission and inspection as well as foreign-binding, invalid-signature, and unsupported-family refusal. It deliberately admits only local operator declarations; node-signed federated-envelope and posture artifacts remain on the separate publication and peer-evaluation path. V1 package dependency admission now accepts zero or multiple unique active resource envelopes, checks the package's closed operational class, and rechecks every exact ref, profile digest, operator binding, authority, signature, and expiry before package use. The Phase 2 classification inventory is now complete across 93 Rust enums and four Python dispatch anchors under a no-grace CI drift gate. Shared Rust/Python registry mechanics and golden vectors drive the completed Dator, Corpus, Arca, Agent, and Inquirium domain verticals: exact distribution-installed entries, fail-closed monotone selection, prompt-free inspection, operator narrowing, generation fencing, and checks on the real role, overlay, strategy, binding, effect-policy, and operation boundaries. A structural Phase 2 gate binds all five owners to the shared primitive or Python mirror and names reaching lifecycle/federation evidence; CI executes those algebra, five-domain lifecycle, three-daemon posture, and Python replay suites. Dator and Arca prove durable immediate deactivation and restart recovery; Agent proves that disabled durable bindings remain history but recover inert. Inquirium additionally enforces signed resource-envelope widening across the complete local 38-axis operational profile. Current-use permits recheck exact envelope facts when materialized, and a deterministic resolve-then-revoke race test proves stale permits refuse. The operator-extension lifecycle now has bounded, expiring, resumable byte staging with transactional inert install after current trust, signature, digest, and contract checks. Exact semantic-entry registrations are now part of the signed package manifest, including semantic-only packages without placeholder hooks. One shared lifecycle proves current-grant and current-conformance invalidation, rollback, generation-fenced restart, and revocation across Dator, Corpus, Arca, Agent, and Inquirium. The daemon publishes a node-signed posture plus exact v2 registry declaration; receiver policy checks trust, modified baseline, sanctions, and local compatibility without semantic fallback, while Corpus room policy v3 binds the publication into signed invitations. Semantic-only packages do not need a placeholder hook. CLI and Trace Explorer expose prompt-free local/peer comparisons through a narrow peer-posture route that does not return the complete invitation inbox, and a three-daemon acceptance proves modified-posture, sanction, and local-substitute refusal. Operator inspection also has audited render-only inspect, explain, bounded Mermaid graph, and Node UI modes over that single accepted projection. The production UI now composes the current 38-axis Inquirium profile plus Agent, Corpus, and Inquirium registries, reports absent Arca, Dator, and federation sources explicitly, and exposes separate bounded peer-mismatch and refusal-provenance views under completed P085-042. All five guard anchors are wired for restrict/grant-set; Agent effect admission also executes bounded-budget narrowing and monotonic risk raising. Federated Inquirium resource profiles are bound to authenticated peers, signed posture, current operation entries, and exact runtime use. Supervised package components can now reuse P080's exact dependency and effect recovery contract rather than creating a package-local lifecycle engine. A closed ownership registry binds each V1 runtime state to one bounded owner and domain-owned use fence, without inventing generic invalidation authority. Phase 3 now has its complete node-local fixed-vocabulary vertical: six accepted Agent contracts, bounded JSON-e Flow branch/repetition, exact passage profile/runtime binding, content-addressed products, prompt-free durable lineage, explicit terminal selection, and process evidence for idempotent retry plus dirty-restart recovery without reinference or duplicate charge. The Corpus/Room extension is also complete: one Corpus-owned binding pins current Room membership, role, accepted overlay, turn, policy generation, Flow lineage, disclosure ceilings, and expiry; only verified local overlay rendering enters P064, all intermediate products remain local, and process evidence proves refusal, changed-content binding conflict, bind-only admission followed by execution without rebinding, unpublished selection, dirty restart, and exact replay. Reusable Agent Flows and deterministic Corpus turn-order table producers now pass the ordinary operator-package activation, restart-recovery, and terminal- revocation lifecycle. Package Flow registrations also impose exact non-empty model-profile and runtime ceilings over the Agent binding, rather than leaving those cost and egress axes ambient. Agent status exposes a Schema-Gated prompt-free Flow inspection; all five refusal codes have reaching restart-durable evidence. The target-free Corpus offer and durable decision contracts are accepted, the opaque Flow offer remains caller-bound, single-use, restart-invalidated, and revalidated at use, and a checked-in Story 012 structural preflight binds the production Flow digest, canonical producer identity, alternate turn-order policy, refusal corpus, parameter inventory, and portable/local-authority split. Completed P085-044 process evidence covers reference and alternate package-owned order, exact replay and changed-body conflict, node-A restart, target-specific HIL/floor admission, revocation without fallback, and a separate no-producer distribution-policy run. The 2026-08-21 real-vfkit base run now passes its closed eleven-check validator with the pinned GNU/Linux arm64 image, so image construction, Docker availability, and the hardware-VM base route are no longer blockers. The retained 2026-08-23 packaged vfkit Story 012 report closes P085-041 with one combined boundary carrying delegated CandidatePlan/P083 lineage, exact package activation, Flow, turn-order, terminal-product, restart, revocation, and decisive stale-refusal evidence. The prompt-free daemon.nse-offer-resolution-trace.v1 remains the canonical offer-resolution trace consumed by the operator Trace Explorer. P085 is therefore implementation- complete at 100 percent and is promoted to Solution 048. The solution remains additive post-MVP work and does not change hard-MVP readiness.

The post-MVP P086 implementation now provides the neutral communication-observation contract family, a checked seven-family boundary registry, a bounded generation-fenced host broker, private segmented recording with crash recovery and retention, verified offline replay, schema-derived field help, and an operator API and UI with focused endpoint counts, bounded payload trees, and a capped activity graph. Host-observed adapters now cover channel_json, normalized host-capability dispatch, local/API model HTTP, and Room-carrier seams; authenticated component reports cover middleware passage and retained component HTTP while peer-session is explicitly planned. Checked load evidence freezes the V1 broker ceilings and proves exact accounting plus typed pressure gaps. Full supervised Story 005 evidence covers Inquirium simulator request/response communication. The retained 2026-08-23 Story 012 full-profile vfkit/Qwen run produces three independent complete node-local recordings for Sensorium/Room and Agent/Room without inventing cross-node visibility: 564 requester observations, 19 solver observations, and 22 reviewer observations, all with zero gaps or drops. Twenty-one tracker items are complete, three remain partial, and two are explicitly deferred; this yields a conservative 90% readiness estimate. Broader selected live-protocol coverage, whole-path secret scanning, generic CI recording retention/failure replay, and Solution promotion remain open. P086 remains additive post-MVP diagnostics and does not change hard-MVP readiness.

The 2026-07-20 P071 refresh freezes the process-isolated Sensorium Virt design without counting documentation as runtime readiness. Backend selection is now property-based and host-attested; VMM lifecycle and guest Workbench mechanics are separate ports; vfkit on Apple Silicon is the first implementation slice; Cloud Hypervisor is the first Linux deployment profile; and Firecracker is the subsequent minimal-device profile. The contract freeze also covers closed semantic vocabularies, plan-bound operational context and policy floors, digest-proven logical image equivalence, and classified control-sequence-safe serial diagnostics. The five backend-neutral contracts, closed host request envelope, pure Rust validator/ companion, and first host-broker slice now exist. Both host entry paths use the Node schema-gate, the core covers research and live-hardware-VM recovery identity, Workbench rejects backend substitution, and reconciliation diagnostics are structured, opaque, and capped. The standalone companion is disabled by default, requires explicit literal-boolean local development/conformance opt-in, and is paired with a closed development|conformance purpose. It is never an automatic fallback from supervised production daemon admission; missing capability dimensions refuse; fixture-copy.v1 exercises their admission, recovery, quarantine, supersession, projection, and teardown path. The daemon-owned vfkit-system.v1 host-lifecycle slice now adds digest-pinned profile admission, private APFS-disk/EFI/socket allocation, closed-argv process launch, exact PID/start-marker, socket-inode, resource and CSPRNG boot-nonce identity, cooperative drain, teardown, recovery, reconciliation, and quarantine. It now commits a durable launch intent before process creation, fsyncs cloned boot artifacts, restricts disabled profiles to teardown/reconcile, and uses a typed fixed vfkit API operation set. The socket root is opened without following symlinks, pinned by descriptor identity, and rechecked before use. A feature-gated 18-test process harness covers process identity persisted before socket readiness, interrupted-launch recovery, dead listeners, replay, dirty exit, missing storage, fresh boot nonces, generation supersession, PID reuse, binary and socket substitution, socket-root replacement, and orphan cleanup without claiming Apple Virtualization Framework or guest evidence. P071 and Solution 042 are now at 100% for the implemented vfkit reference profile. The nonce/generation/plan/image-bound guest agent and host channel have the explicit states protocol implemented and real-binary local conformance proven: admission is typed, process output has one total budget, PTY resize is ioctl-backed, patch staging is atomically durable and content-bound, endpoint identity is rechecked, and deadline/boundary/disconnect cases are covered. The pinned full-system GNU/Linux arm64 image and real-vfkit harness now add deployment evidence proven for EFI boot, AF_VSOCK guest readiness, systemd/PID 1, kernel/mount/package mechanics, no-NIC/no-share posture, observed CPU/RAM/disk/TasksMax plan and PID refusal, dirty recovery, replay/refusal, real PTY/file mechanics, and deterministic teardown. Atomic image metadata and a digest-bound completion record prevent partial builds from becoming evidence; the schema-gated report binds exact VMM/image/firmware/guest pins and functional timing budgets. Readiness markers are not evidence. The microvm Workbench adapter now routes guest file, export, patch-stage, and PTY operations through daemon-owned sensorium.virt.host, projects PTY output through P082, and retains P083 as the sole remote control authority. The additive Story 012 vfkit v2 profile installs the deterministic repair fixture in the digest-pinned guest image and uses one Workbench runtime for the guest, P082/P083 bridge, and complete three-node story. Its schema-gated single-runtime-vertical report proves failing/passing PTY state, exclusive repair, observer revocation, dirty recipient restart, stale-generation refusal, export, and an unpublished Corpus draft. Patch-stage idempotency is bound to the exact address, source generation, content digest, and length; unknown guest PTY outcomes terminate waits honestly, and guest quiescence reaps completed PTYs before reporting its active count. Restarted guest sessions and command replays return workbench-restart-required-relink; a new generation can create a fresh session while the old authority remains retired. Terminal close commits a local closing transition before guest I/O, refuses concurrent effects, and composes idempotently with environment teardown without retaining the terminal lock over provider I/O. The live-feed harness now resolves exact Rust test names through bounded libtest --list output and carries dedicated restart and close-race checks.

An additional post-MVP Story 012 PowerDNS/Bielik profile now has retained real evidence: the 2026-07-24 macOS arm64 run pins the exact guest fixture and package versions, supervises separate real local model runtimes for B and C, verifies content-addressed Agent products before their inert Corpus projection, and keeps deterministic host-owned P083 actuation separate from model text. It completed in 155,637 ms and proved the exact localhost-only PowerDNS records. Because this is additive post-MVP evidence, it does not change the completed vfkit reference-profile or hard-MVP percentages. The elapsed time is observational rather than a cold-cache performance claim; the profile did not control model or operating-system cache state. The runner now also implements a post-MVP requester/solver/reviewer baton loop, with two required and at most 64 cycles under a five-minute deadline, one verifier-rejected guest experiment, terminal-evidence correction, and separate short P083 leases per actuation. The retained report proves separate roles, two round-robin cycles, failed and corrected experiments after fresh terminal feedback, Agent propose, admitted HIL, P083 claim -> invoke -> release, and zero effects derived directly from Room prose. The hard-MVP percentages remain unchanged because this profile is additive post-MVP evidence. The adaptive local successor is now implemented as post-MVP work: a signed corpus-reasoning-experiment-proposal.v1 binds one content-addressed inquirium.candidate-plan.v1 to an admitted Room turn and requester-selected local Chair Agent. Node A binds the signing node to the author's canonical Room invite, resolves monotone executor ceilings, compiles a pending flow, prepares one fresh latest-state passage, verifies one content-addressed Agent product under a closed propose|no-effect decision contract, and prevents no-effect from reaching claim or invoke. For propose, it rechecks the exact interface, grant, generation, operational context, method, input schema, payload digest, classification, lease ceiling, and proposal expiry before requiring an admitted operator-question decision and delegating the exact approved effect to P083, whose lease exists only around invoke. The portable policy also names remote Chair, designated-participant, and deterministic compiler executors, but daemon admission rejects them until their passage adapters have executable evidence. Room role alone remains non-authoritative. This additive post-MVP slice does not alter the hard-MVP percentages.

The delegated adaptive-executor implementation now has a complete V2 authority evidence path while retaining an explicit V1 partial authority-composition result without claiming a second VM deployment. Its closed descriptor pins the retained real full-system Story 012 report by digest and proves requester-owned P083 lifecycle records, released terminal leases, failed- plan feedback, corrected execution, no fallback, and zero effects derived directly from Room prose. New executions retain the signed CandidatePlan, inert admitted flow and host-owned HIL/claim/invoke/release sequence bound to one fresh lease and exact receipt per effect; the V2 validator and refusal fixtures enforce those bindings. The older retained report lacks those new fields, so a fresh real vfkit/model run remains the evidence gate for V2 passed. Remote runtime execution remains unsupported until a separately evidenced passage adapter exists. This post-MVP gap does not change hard-MVP readiness percentages.

The same post-MVP slice now persists an append-only Corpus experiment execution join through the exact P083 operation and receipt, quarantines unfinished work as unknown after restart without blind retry, drains recovery in bounded 1,024-record pages with an explicit 16-page startup ceiling, and rechecks current Room membership before passage and effect. The host separately caps distinct experiment proposals per round at two by default and eight at the hard ceiling; exact replay does not consume another slot. The role-aware runner now requires a failed first plan and a separately admitted corrected plan after fresh terminal feedback; fallback is deadline-only and cannot emit the promoted 17-check report. The retained real vfkit/Bielik report passes that closed validator; hard-MVP percentages remain unchanged because the profile is additive. Both plans in that evidenced runner are host-constructed and bound to retained solver turns, so the report proves feedback and authority mechanics rather than semantic derivation from model prose.

A further additive Story 012 profile now implements critique-gated technical deliberation. It permits bounded shell and configuration fragments only as inert Room evidence, requires an Agent-product-bound content-addressed CandidatePlan, binds a signed reviewer verdict to the exact proposal and terminal-state digests, and defaults the signed Chair decision to block unless it can bind an exact reviewed plan. Pure Corpus transitions, Schema Gate fixtures, append-only daemon facts and recovery, host admission, the critique-gated runner, and a closed 26-check report revision are implemented; HIL and P083 remain the sole effect path. A retained 2026-07-25 macOS arm64 run passes all 26 checks with two real Bielik runtimes, one failed experiment, a reviewer-revised replacement plan, HIL, P083 lease release, and zero direct effects from Room prose. The profile is ready. This is additive post-MVP evidence and does not change any readiness percentage.

The stronger model-authored PowerDNS discovery successor is also additive post-MVP work. Its no-ready-wrapper guest, structured intent compiler, disclosed solution-aware staged admission scope, model-authored review findings and replacement, full-plan and terminal-completion evidence, bounded non-truncated effect projection, deterministic replay, real-model stage bench, append-only calibration ledger, and closed report contract are implemented. It does not claim an independent reviewer verdict. The follow-up now gives solver and reviewer one bounded three-experiment correction-state projection, derives a stable relevant-precondition digest from a nonce-marked host snapshot, and rejects exact failed mutations only while that digest remains unchanged. The gate checks all three retained experiments and deterministic replay covers both repeated probes and repeated mutations. Its metadata-only report now requires bounded reviewer analysis, the precondition digest, and original plus selected typed novelty decisions for every admitted experiment. Historical Bielik 4.5B Q8 measurements accepted two of five zone-declaration samples but no zone-data correction in either five-sample stage. A subsequent bounded 130-sample role matrix retained Qwen2.5-Coder 7B Q4_K_M as the solver default: it produced 26/50 ready plans and 9/10 ready causal corrections, while Qwen3.5 4B produced 2/50 and 0/10. Qwen2.5-Coder 3B, Qwen2.5-Coder 7B, and Phi-4 Mini all produced 0/10 ready reviewer replacements, so no reviewer deployment default has been promoted. The active profile has not yet retained a passing vfkit report. Only one guest-attested challenge family exists. The resolved second variant, powerdns-bind-missing-zone-data.v1, starts from a valid listener/backend/declaration chain whose referenced zone-data file is absent and contains no final localdomain records. Its implementation, evidence, and a passing real vfkit report remain explicit post-MVP gaps. They do not change the completed baseline Story 012, Corpus, or Workbench readiness rows.

The 2026-07-22 terminal live-feed slice adds an independent bounded guest terminal-read operation with exact-byte cursors, eviction gaps, post-exit replay, and future-cursor refusal. Follow-up conformance keeps two PTYs active together, proves per-session byte and cursor isolation, distinguishes high-water + 1 refusal from retained-floor gap recovery, projects Workbench gaps before retained P082 events, and preserves source-reported gaps across direct-peer reconnect. The same harness now includes the microVM Workbench bridge and existing P083 two-controller fencing. It is component-level composition evidence; the real full-system deployment proof remains separately owned by the vfkit harness.

The 2026-07-16 refresh additionally closes Proposal 082 and promotes Solution 046. Sensorium Interfaces now has the pure pull-batch core, eight schemas, classification and Passport bindings, durable host lifecycle, Sensorium and Workbench source adapters, signed direct-peer reads, loopback SSE, and the WSS Room latest-state projection with current dual-authority checks. It is now a hard-MVP release-blocking component whose own MVP slice is ready. Its promotion therefore adds no unresolved P082 work. Subscription reads serialize only per lease, Passport admission is atomic, direct-peer target binding is explicit, and active Room projection pumps are capped at 64. The follow-up hardening rejects bare grantee ids, intersects Room authority only by canonical stable subject key, separates SSE and Room causal traces, distinguishes revoked Passport replay, checks tier-vocabulary drift in CI, and adds a negative frame fixture. The latest post-MVP extension replaces the closed source enum with a generic, bounded adapter registry, migrates all existing Sensorium and Workbench sources, adds an admitted Artifact Delivery pointer snapshot source, and exposes process-local operator read metrics with bounded source/carrier/delivery-kind dimensions, flat revoke-commit timing, and isolated source-registry, active-subscription, metric-accumulator, and Room partial-failure reporting. Daemon startup now requires all four built-in observation adapters, while the exact-name, fail-fast conformance runner uses separate build/test timeouts and retains bounded host load, signed direct-peer reads, SSE revocation, and Room projection revocation beside the new actuation verticals. These additions improve extensibility and evidence collection without changing the component's 100 readiness estimate. P082 is now listed as a hard-MVP blocker whose implementation gate is already satisfied.

P082-022 now completes the local and direct-peer terminal live-feed projection. The canonical terminal event contract preserves exact bytes, uses closed event-kind shapes, and never retains input content. Workbench enforces event, byte, and age retention with explicit gaps; the source adapter maps closure to terminal end. A recipient-side owner-bound feed reuses signed-Passport direct-peer pull-batch and presents validated batches through loopback SSE. The executable component pack proves schema negatives, non-UTF-8 bytes, local SSE, direct-peer ownership/cursors, remote SSE, stale-cursor reconnect gaps, Workbench-to-P082 gap projection, retention gaps, and isolated reads over two simultaneous guest PTYs. A two-deployed-node profile remains optional stronger deployment evidence, so P082 and Solution 046 remain at 100%.

The 2026-07-17 Agent review promotes Proposal 073 to Solution 047 and makes the node-local Agent organ an explicit hard-MVP release blocker. Its complete tracker, stratified core/host crates, durable recovery, bounded controller, effect-admission boundary, lease reconciliation, and dirty-restart process smokes satisfy that gate now. Cross-node or federated Agent execution remains a separate future proposal and does not weaken the node-local hard-MVP contract.

The 2026-07-19 Story 012 follow-up completes the composed acceptance profile without changing the hard-MVP blocker set or the 100 readiness estimates for P073, P082, and Solutions 046/047. agent-core owns only a substrate-neutral observation need, static binding, and prompt-free evidence contract. A positive dependency allowlist admits the pure horizontal semantic-registry-core data/selection algebra, names pure inquirium-core DTOs as the sole vertical exception, and rejects Room, Corpus, Memarium, Sensorium, Workbench, and other source/effect-domain coupling. Operator-authored JSON-e Flow configuration imports the Agent-owned hard caps and may predeclare bounded need-to-source wiring, while rendered data can only select or narrow it. After caller-capability and ownership checks, binding admission resolves every exact source/schema pair before persistence and refuses absent, incompatible, or ambiguous registrations. Room relays a resource-bound sensorium-interface-read-result.v1 containing one inline cursor-free snapshot. The destination daemon resolves the opaque source through its Room/Sensorium adapter, keeps a bounded process-local latest-state inbox, exposes it to Interaction Broker only under a typed Agent-host principal and exact resource context, and admits one schema-, authority-, classification-, freshness-, and byte-bounded observation into one Agent Inquirium passage. Durable Agent evidence preserves the exact-schema/version-validated source P081 causal/context plus generic source-version/resolution refs and is pinned to the enclosing Agent, binding, and passage, while broker and Agent records retain no raw observation payload. A conflicting digest at one relay epoch/sequence is refused with a payload-free structured diagnostic without overwriting current state; restart drops ephemeral content. The executable Story 012 runner reuses the extracted Story 011 three-node federation/bootstrap lifecycle and proves a failing chair terminal, distinct B/C observations and HIL deliberation, local observer revocation and relay-audience convergence before repair, dirty restart of recipient B, local repair, newer passing source-version and content-digest evidence for B while C remains refused, and an unpublished Corpus draft. The shared runner now binds A/B/C to distinct loopback addresses with exact peer TLS IP identities. This is multi-address single-host evidence, not a claim of multi-host deployment or public relay reachability, so readiness percentages do not change. A separately selected single-address profile enables unattended port-isolated smoke runs without privileged alias setup, but is recorded as weaker evidence and likewise changes no readiness percentage. The closed 17-entry refusal matrix assigns every claim either to this composed process runner or to its named P070/P082/P083 lower-stratum evidence suite. Story 012 is therefore ready at 100%; P070 retains separate ownership of external host-TLS relay deployment evidence.

The completed operational-impact extension does not change those hard-MVP scores. P082-021 and P083-014 own the shared publication and interactive-resource contract, including the 512-byte summary cap, source-generation/current-publication freshness predicate, and audited immutable replacement; P071 pins it to exact Workbench environments; P073 and P064 propagate only opaque evidence into a host-owned pre-inference caution layer; and P069 adds the three-participant Story 012 proof. The composed runner now verifies equal B/C source-owned qualifiers, an immutable monotone test -> production replacement, refusal of the superseded static binding, admission of the replacement under a new exact binding, continued C revocation, and an unpublished draft. Lower-stratum tests cover generation drift, malformed/oversized context, Workbench process generations, multi-feed caution maxima, and non-droppable production/critical framing. These rows remain post-MVP hardening and add no new authority or freshness TTL.

The 2026-07-18 operational hardening keeps that 100 readiness verdict and strengthens its release evidence. The host now exposes an operator-only, metadata-only paginated Agent list, fixed-cardinality diagnostics with stable reason codes, and inspect-first maintenance whose cursor and batch bound policy reconciliation, canonical expiry reaping, and terminal lease cleanup to one exclusive Agent page. Its dry-run projects the same bounded plan that execute applies, without mutating runtime state. A standalone acceptance pack drives deterministic local Inquirium, HIL effect admission, terminal outcome, operator projections, and SIGKILL recovery through authenticated HTTP. Deterministic fact-bundle failpoints and a 1000-session restart soak additionally prove repair and absence of live controller, effect-owner, HIL-routing, and pending-effect index residue.

Proposal 083 is now a satisfied hard-MVP release blocker. P083-002 through P083-011 implement the shared directional resource, exact Passport scope, pure coordinator, durable shared/exclusive state, adapters, direct-peer admission, and Workbench terminal bridge. The Node also owns a bounded process-local Room collaboration registry and strict manage actions. Collaborative status/control/ invoke derives the canonical caller and current actuate membership atomically from one live Room transport snapshot, then reuses exact interface grants, grouped methods, generation, lease, epoch, sequence, and host policy. Observation remains separately authorized and raw terminal input is never Room content. The expanded runner passes 19 exact Rust checks plus the Workbench actuation and PTY story tests, including saturation, expiry/renewal, handoff, stale epoch, restart, partial failure, observer-only denial, and two real PTY controllers. P083-012 records the clean final authority and correctness review and promotes this actuation boundary into Solution 046. P083 and Solution 046 are therefore estimated at 100% and ready for hard MVP; completed post-MVP P083-013 relay work does not reopen that verdict.

The Room collaboration boundary additionally mints 256-bit CSPRNG session bearers that never enter live frames, acknowledgements, fan-out, durable Room facts, shared Corpus observations, or collaboration-group state. Group withdrawal releases capacity immediately; closed or terminal Rooms are reaped at the next bounded group boundary, while one member-session disconnect correctly leaves the Room-scoped group available to other current members. This hardening changes no readiness percentage.

The same closure is now hardened with a uniform 32 MiB pre-read image-source limit, a 96 MiB decoded adapted-model artifact cap, operation-kind/status-scoped paged training recovery, recursive provider-usage aggregation, and full classification no-broadening checks for crisis-candidate projection. These are contract and recovery hardening changes; P063, P064, and P066 are now at 100 for their tracked implementation slices.

The P064 prompt-assembly policy slice remains tracked as done: support for a future text-generative operation will receive a separate work item only when the operation exists. Its previously additive communication-dialect, session-memory, deterministic-cache, Flow-IR, and locale-policy slices now have bounded contracts and host implementations, without moving plan execution or summary production into Inquirium.

The Inquirium refresh in this snapshot additionally includes executable classify/rerank verticals, provider-native structured output under host validation, prompt-epoch promotion gating, baseline profile rendering, host-derived context-grant binding, complete local context resolvers, operator-question cancel/supersede, and transcript blob/projection/feedback durability. The latest closure adds a live provider-backed image path, the durable bounded train.adapt execution/evaluation/publication worker, bounded structured-output repair and rail diagnostics, egress-class ceilings, shared participant-id and monotonicity primitives, and explicit local-model diagnosis/provisioning commands.

Post-MVP local-model productization now also has seven accepted package/lifecycle contracts, a dedicated content-addressed asset store, and an effectful host-side package lifecycle. Control metadata stays under data-dir; bulk bytes resolve from explicit configuration, then ORBIPLEX_MODEL_ROOT, then the data-dir default. Marker/registry identity and exclusive locking enforce one owner and writer. Managed authority is separated from mutable engine/workspace interoperability, native files require verified import, host-registered runtime layouts project only allowlisted child environment, layout preparation checks containment before creating children, launch materializations are re-verified, failed publication is rolled back or discarded, and recovery detects same-size digest corruption. Journaled root migration recovers both pre- and post-commit crashes without creating two active roots and refuses symlinked provisional authority trees. Deterministic planning still fixes effects/executed to false; a separate authority/lifecycle stratum now verifies signed source trust and operator endorsement projections, streams bounded local or HTTPS bytes into staging, journals and recovers installs, and implements verified receipts, generation-guarded activation, rollback, status, removal, and a baseline release gate enforced inside each journaled activation or rollback transition. Competing workers are serialized by durable attempt leases, one-shot source trust is committed only after the claim exists, rollback binds the observed generation and exact target, and incomplete install/removal cleanup remains visible and recoverable. A golden operator-endorsed reference manifest pins a roughly 1.7 GB Bielik GGUF below the 5 GiB test ceiling without silently downloading it; Python and Rust also share a Unicode/nested JCS parity fixture. HTTPS package fetch requires exclusively public DNS results, pins the resolved set per request against rebinding, and applies both total and rolling transfer-progress bounds. Activation re-verifies referenced CAS bytes instead of trusting receipt history alone. The daemon now owns the operator-question, notification, signer, release-policy, deferred install/recovery, and package-to- supervisor bridge. Managed candidates remain quarantined through process health and conformance and become routable only after the durable profile transition. A bounded fake-process smoke proves the structural boundary. A separate opt-in macOS arm64/Metal suite now proves the complete lifecycle with a pinned, self-contained llama-server and the real revision-pinned Bielik Q8_0 bytes: authority ceremony, CAS reuse, conformance, alias-stable model snapshot, real inference, dirty-restart adoption, upgrade, rollback, and reference-aware removal all pass and produce a schema-gated metadata-only report. Managed package children now run under an OS-enforced no-egress launch mode on macOS and Linux x86_64, conformance asserts that mode, and exact dirty-restart adoption requires matching durable isolation evidence. The offline distributor release tool, exact approved-release catalog, key rotation/revocation mechanics, federation-root provider release-key endorsement projection, and redirect refusal matrix are implemented. Provider-key trust is bound to one exact active root snapshot, purpose, and exact release-catalog provider/ref; an endorsed key cannot cross provider scope, while manual trust remains the explicit host-wide override. Expiry or revocation fails closed with bounded metadata-only diagnostics, and current manifest authority is re-evaluated during activation, rollback, and planned-transition recovery rather than being inherited permanently from an install receipt. A Linux x86_64/CPU profile now shares the same lifecycle/report contract and has native ELF/dependency gates, but a real Linux host report remains outstanding. Publication of a production-key- signed llama-server release, real process acceptance on Linux x86_64/CPU, and operator rebind after root/control-plane loss remain open. These items are explicitly outside the P066 hard-MVP denominator, so the Inquirium readiness percentages do not change.

The current Inquirium closure also adds archive-before-prune context-grant revocation and bounded scheduler maintenance, non-empty participant projection rebuild from validated Memarium facts, resolved retention admission, exact participant/feedback-bound revocable training grants, atomic baseline profile activation, registered notification widgets with server-side answer validation, host-owned mode/class escalation policy, complete assembled-prompt token accounting, and explicit fail-closed SQLite schema migration checks.

The latest P063/P064/P066 closure adds forward-only host-keyed assistant trace references, automatic sustained-degradation and boundary-risk escalation, metadata-only crisis candidates, provider-backed OpenAI embeddings, supervised OpenAI/Anthropic lifecycle coverage, explicit remote model-acceptance and egress acknowledgement, semantic transcript tags, canonical participant-bound cross-device export/import, content-addressed training dataset manifests with grant-rechecked local train.adapt admission, and complete bounded summarize/transform/image contract verticals. Image output remains artifact-only; the deterministic backend remains the conformance/smoke oracle, while the supervised provider adapter now supplies a live image generation/edit path under the same host verification and object-store boundary.

The P081 review closure additionally distinguishes non-canonical causation from operation-id conflicts, unifies component-domain-separated receipt identifiers across the four first consumers, strengthens durable nonce concurrency and Room boundary tests, and bounds Agora proof clock skew. These are hardening changes; P081 and Solution 043 remain at 100 for the hard-MVP slice, while Inquirium adoption and signed revocation-snapshot admission remain explicit post-MVP questions.

The Workbench refresh in this snapshot also includes native non-Workbench broker providers, explicit artifact handoff, bounded argv-prefix consent and operator UI, shared sidecar merge, the required Rust actuation bridge, the managed fixture-copy.v1 Sensorium Virt executor, and host-verified Agent/Corpus/Room tool-request lineage.

Recent component deltas:

• Proposal 081 / Solution 043 are hard-MVP ready. Canonical causal context and receipt contracts are consumed by Scheduler, Bounded Deferred Operations, Artifact Delivery, Sensorium, and redacted P074 trace adapters. Contact Catalog and Seed Directory consume the bounded replication core with domain-owned trust and merge policy. The durable scoped-claim runtime, Ed25519 nym-certificate adapter, and Agora/Room consumers are implemented with replay, expiry, candidate binding, and stale-revocation refusal. The repeatable 13-check acceptance runner passes and emits a metadata-only trace bundle. Stronger zero-knowledge suites, Agora cross-relay mesh, federated Memarium replication, and universal consumer migration remain explicitly post-MVP.
• Proposal 082 is an explicit hard-MVP release blocker whose observation implementation within Solution 046 is ready. The implementation has one carrier-neutral bounded read-next contract, exact local and Passport authority, revocation/restart coverage, direct-peer, SSE, and WSS Room adapters, and temperature plus collaborative Workbench acceptance tests. Canonical grantee refs prevent cross-kind Room identity collisions, carrier-specific traces preserve diagnostic provenance, and the bounded source registry now includes an admitted Artifact Delivery pointer adapter and fails startup when any built-in adapter is absent. Host-local aggregate read metrics separate delivery kinds, expose revoke transaction commit duration without mislabeling it as enforcement lag, isolate every unavailable operator section, reset explicitly on restart, and pair with the exact-name observation carrier checks in the extended conformance runner and separate build/test timeouts to provide the measurement boundary for future contract revisions. The former provider-push, descriptor-search, and split-management questions are resolved against the current baseline: bounded pull-batch, direct authority-scoped disclosure, and one source-local manage capability remain in force.
• Proposal 083 is an implemented and promoted hard-MVP release blocker. P083-002 through P083-011 provide the separate sensorium.interface.invoke authority, per-method schemas, bounded shared/exclusive coordination, durable fencing and receipts, direct-peer and Workbench adapters, bounded operator/Room grouping with dual authority, and the load/restart/partial-failure/two-controller PTY conformance matrix. P083-012 records the clean final review and formal promotion into Solution 046; runtime readiness is true, and P083-013 now reuses the implemented P070 Phase 6A relay without moving authority into the carrier.
• Communication Protocol Baseline is now hard-MVP ready as a historical baseline: Proposal 002 explicitly maps its implemented or superseded areas to the current runtime owners (P014/Solution 000 transport, P056/Solution 024 TLS trust, Seed Directory/Federation Root discovery trust, Capability Registry/Binding admission, AD/INAC payload transport, and Messaging/Room group semantics) and no longer carries independent hard-MVP implementation blockers.
• Proposal 048 / Sensorium OS Action Classes is now hard-MVP ready for the minimal reference connector runtime: sensorium-os normalizes class-aware action catalog entries, reports per-action availability, executes script-backed C1/C2 entries, rejects allowlist-local sensitivity overrides, enforces exact and prefix result_pointer_fields, blocks C3/C4/C5 under emergency posture without an explicit host-policy exception, and fails closed when a declared enforcement profile is unavailable. Additive post-MVP work now implements a closed host-managed C3 file-write profile, literal-IP bounded HTTP C4, contained artifact-promotion C5, sequential C6 composition, and C7 over an atomically consumed content-bound allow-once approval on the private module channel. Arbitrary-process C3-C7 declarations remain unavailable.
• Proposal 071 / Solution 042 now have the host-owned operator-consent spine for exact and bounded-prefix Workbench terminal commands: typed request/decision schemas, daemon persistence and submit/list/detail/revoke/projection APIs, P066-backed operator questions and durable notifications, Workbench sensorium-workbench.consent-descriptor.v1, matching allow-once admission, remember-exact-argv, and workspace-bound remember-argv-prefix sidecar projection that refuses to loosen egress, credential, timeout, or output-byte caps. The latest hardening also makes operator-consent read/projection APIs reject module callers, replays duplicate consent requests by semantic request equality, validates Workbench consent descriptor and sidecar entry schemas, and refreshes Workbench sidecar profiles through a bounded TTL. It now also requires active node-operator-binding.v1 authority for consent answers and revocation, gates durable answers through host capability authorization policy, and filters expired entries, inactive operator-binding entries, and capabilities no longer durable-grantable by host policy from the effective sidecar with consent-expired, consent-operator-binding-inactive, or consent-capability-not-grantable diagnostics, which the Workbench connector now imports into operator-visible config diagnostics. The same host-owned consent spine now projects granted Sensorium OS action-catalog deltas into sensorium-os.action-catalog-sidecar.v1, materializes the sidecar into the Sensorium OS middleware config tree, publishes binding/delta/sidecar schemas, and the connector loads valid non-overriding deltas into its effective catalog with a bounded TTL/mtime cache. A shared append-only sidecar merge core now owns conflict/provenance semantics, node-ui exposes consent inspection/revocation, and fixture-copy.v1 provides the first managed virtual executor without claiming process isolation. Sensorium OS consent options are now host-shaped to exactly deny, allow-once, and remember-action-catalog-entry; one-shot approval is operation-digest-bound and atomically consumed after catalog admission. Operator status exposes pending, one-shot, denied, expired, revoked, inactive, and effective approvals together with the effective catalog hash without turning the read model into authority.
• Raw Signal Access is now hard-MVP complete as both proposal and solution: hook-chain runtime and direct JSON-e-flow dispatch preserve raw context only in memory, expose it only to declaring executors, strip it from final envelopes, and now enforce declared raw-signal / component-trace byte limits by replacing oversized exposures with sha256: digest metadata.
• Bounded Local Server Runtime is now hard-MVP complete: the shared Rust and Python bounded-server primitives were already migrated across the production local server surfaces, and the remaining daemon-context overload gap is closed by a real health-endpoint integration test that forces max_connections = 1 and observes fast HTTP 503 rejection.
• Host-Owned Module Store is now hard-MVP complete: the four module-store host capabilities have committed local schema-gate contracts, daemon routes validate raw request and response JSON before and after typed dispatch, and Story-009 verifies supervised module-store writes plus daemon restart/replay through real processes.
• Sealer, Capability Advertisement, and Pseudonym Vault / Key Roles are now aligned with their component trackers as hard-MVP complete solution slices. Sealer's hard-MVP done status is backed by the daemon passport-aware dispatch gate, real revocation-view diagnostics, sealer master lifecycle, audit parity, and HTTP dispatch coverage. Capability Advertisement's done status reflects the registry-backed fail-closed advertisement path, while remaining per-passport ingress verification, lifecycle rebuilds, reusable schema retrieval, and Seed Directory reconciliation are post-MVP hardening. Pseudonym Vault / Key Roles was already marked hard-mvp-done in its solution tracker and caps sidecar; the snapshot now reflects that source of truth.
• Proposal 003 and Proposal 011 are now hard-MVP ready for the selected-responder procurement slice. question-envelope.v1, procurement-offer.v1, and response-envelope.v1 are schema-gated at daemon ingress; the host-owned service-order bridge derives full schema-valid question and offer artifacts; selected-responder executions persist transition facts, offers, contracts, responses, receipts, disputes, and settlement-aware closure. The full P003 NATS/JetStream plus Matrix collaborative-room transport remains post-MVP, and P011's broader collaborative/dispute lifecycle remains a later extension.
• Proposal 072 is now implemented and promoted to Solution 037 for the hard-MVP scope: capability-registry.v1 is the machine source of truth, formal capability ids are checked for canonical grammar, status, wire-name uniqueness, derived surfaces, and use-specific eligibility, and capability advertisement, passport validation, host capability dispatch/routing, literal control-plane POST /v1/host/capabilities/* routes, and supervised middleware reports fail closed for unregistered or ineligible formal ids. capability-authorization-policy.v1 adds the checked P071 Workbench/Interaction Broker authorization-policy sidecar for required grants, caller posture, approval mode, autonomy floor, and COI policy; daemon startup preflight validates both registry and policy, while runtime grant enforcement remains host-policy owned. Federation namespace governance remains a separate post-P072 proposal track.
• Proposal 076 / Solution 041 / federation-root.v1 is hard-MVP ready while remaining a release blocker. The contract defines the data-dir-scoped federation root used to select federation_id, bootstrap seed peers, Seed Directory endpoints/trust, sovereign subject refs, and official-service endorsement authority before the node enters the network. Node runtime now has the node-wide federation selector, startup schema-gated loading from explicit data-dir packs, Ed25519 signature verification, participant self-signature checks, org custody-policy evaluation for any-authorized / threshold, key-counted threshold semantics, same-federation data-dir state guards, rollback/digest-swap refusal, a fail-closed default when no explicit root pack exists, and a raw-digest-pinned bundled orbiplex-main dev/demo fixture behind explicit federation.allow_bundled_fixture_root = true. The hard-MVP slice now also includes federation-service-endorsement.v1 as the sole official-service proof, participant/org verifier core, root-pack endorsement revocations, Seed Directory attach/read/revoke surfaces, own-node endorsement fetch/install cache, capability-advertisement endorsement projection with per-use re-verification, a thin participant-sovereign operator issuance API, offline MVP multisig ceremony tooling for root packs and endorsements, strict rejection of unauthorized excess endorsement signatures, production orbiplex-main ceremony profile checks for manifest digest/threshold parity, explicit-roster root draft authoring, strict deterministic assembly, org-threshold shape, charter-version policy_ref, at least a 2-of-3 unique signer-key threshold, and rejected signature refusal, optional seed_directory_bootstrap[].tls_certificate_sha256 projection into Seed Directory sources with HTTPS-only runtime enforcement and peer leaf certificate digest verification, and restart-only federation-root activation with specific first-activation/removal/change reload events. The hard-MVP acceptance harness seeders now write explicit signed local root packs and embed signed Seed Directory official-service endorsements for federation-endorsed bootstrap entries, so local Story-005, Story-009, Story-010, and Story-011 profiles exercise the same root-backed authority chain as runtime consumers. Story-011 now also proves the provider side of the projection: its managed smoke creates provider participants during first boot, inserts B/C participant attestation roots with matching self-signatures into the refreshed runtime root, restarts, asserts active /v1/seed-directory trust for Node B, and only then issues/publishes corpus.provider capability passports. Concrete production roster/keys, final charter adoption and appeal body seating, consumer-specific alliance admission enforcement from Proposal 079, optional remote co-signing/FROST-style threshold protocols, and broader multi-federation matrix polish remain post-MVP governance/testnet follow-ups, not release blockers for the runtime contract. Room/Solution 036 now explicitly grounds federation-local, cross-federation, and global exposure in the active P076 federation_id instead of letting any carrier define federation authority.
• Proposal 078 now has its local post-hard-MVP intake spine implemented: the canonical weak-signal-finding.v1 schema and fixtures are schema-gated at import/export, daemon exposes explicit operator import/list/detail/review endpoints, a dedicated SQLite Harvester review store owns review state, the first filesystem Markdown/text adapter is bounded under the node data-dir, and accepted findings can create local Whisper draft stubs without publishing. Directory-watch automation, network-capable harvesting, public gateway intake, and collector corroboration remain deferred profiles.
• Proposal 018 / Solution 040 is no longer a low-coverage placeholder. Code review on 2026-06-22 confirmed schema-gated participant-capability-limits.v1 import/export, durable daemon replay, operator HTTP import/list/detail/clear, hard-block enforcement for the current procurement/response operation set, protected-floor behavior for signal-marker/send and dispute/file, procurement ranking penalties through priority-factor, and per-participant cooldown through rate-limit-factor. Follow-up hardening added reasoned clear tombstones, dead/already-expired hard-block import rejection, stale recorded-at overwrite rejection, monotonic last_cleared_at replay so old records cannot reappear after clear, full participant-id validation on clear, schema-gated list/detail export, bounded local control bodies, runtime soft-factor and reason/ref validation, and metadata-only operator SSE refresh events for import/clear. P018 is now hard-MVP complete; remaining questions are post-MVP scope expansion and registry/policy refinement.
• Artifact Delivery moved from "MVP transport foundation" to hard-MVP complete: Memarium custody target-space policy, profiling counters, metadata-only observers, Matrix mailbox hardening, and object-store-indirect fetch/rehydrate through artifact-object-pointer.v1 are now documented and implemented. Lower-level zero-copy and Matrix media variants remain post-MVP optimization layers.
• Notifications now have a local durable MVP foundation promoted to Solution 039: schema-gated notification.create, temporal SQLite event log, derived queue projection, JSONL audit mirror, SSE state ping, operator UI, legacy notify_emit adapter, first daemon-owned actions, profile-aware manifests, and destructive temporal compaction for local notification history. They remain partial because pod-user UX, OS notifications, and cross-node aggregation are later layers.
• Node UI security readiness advanced: Solution 001 now documents and implements physically separate public/user/pod-user/operator router strata, participant-session enforcement for user-mode routes, header-first reflective CSRF without the legacy CSRF header alias, local user-action audit JSONL, security-audit.v1.sqlite query projection with 90-day retention, /admin/audit/user-actions, and optional best-effort Memarium user-action.v1 mirroring. Proposal 052 now carries the same audit/redaction/retention contract for the Tauri-hosted shell. Node UI remains partial because richer desktop settings writes, external preview isolation, pod-user auth, and native integration hardening are still later product/runtime layers.
• Contact Catalog hard-MVP is tracker-complete: Proposal 058 and Solution 025 now report the implemented route-set contact-claim.v1 / contact-lookup-result.v1 runtime, supervised service, local contact recovery, tombstone/revocation replay, PSI/blinded lookup, provider sync, provider trust controls, and contact-control-vs-identity wording as done for the hard-MVP slice.
• Messaging hard-MVP is tracker-complete: Proposal 060 and Solution 027 now report supervised messaging runtime, daemon-mediated contactability provider discovery/challenge/redeem, Contact Catalog lookup/contact-request handoff, classification-bearing private-direct AD/INAC delivery, messaging.flag.v1 read/unread replay, recorded-message lineage plus best-effort encrypted Agora Vault storage, Node UI controls, user-mode wizard readiness for pseudonymous-only or public-handle-draft messaging setup, and Story 010 strict ad-smoke as done for the hard-MVP slice. Latest hardening adds EML body/profile recovery, route-key normalization, mark-read routing fixes, readiness/routing retry gates, SSE mutation guards, and conversation diagnostics. Production privacy/federation expansion, receive-passport restoration matrices beyond the current sealed local recovery path, Maildir body encryption, richer per-recipient vault key wrapping, HTML rendering, group messaging, and live multi-device push remain post-MVP work.
• Inquirium is now promoted to Solution 044 as an MVP-capable bounded-inquiry organ rather than only a runtime substrate. The Assistant Channel is promoted separately to Solution 045 as the human-facing interaction surface over that organ, while Proposal 064 remains their shared implementation recommendations. The solution has a first generate vertical through inquirium-core, daemon inquirium.generate, JSON-e Flow ingress/preflight, NSE runtime selection, deterministic stub runtime, classification-aware request validation, metadata-only trace records, direct embedding, report-backed conformance, and the direct data-plane lease/batch-embed pilot for lease-backed work. inquirium.classify and inquirium.rerank now continue from bounded pair-validated contracts through inference-granted host capabilities, runtime/model-binding selection, deterministic and local HTTP/simulator execution, shared budgets, host-keyed metadata-only traces, and conformance fixtures. The same bounded host boundary now exposes summarize/transform through generate lowering and image generate/edit through explicit image candidates, operation-bound leases, verified artifact intents, a uniform 32 MiB source-media cap, and artifact-only responses. Proposal 064's core runtime-adapter foundation is implemented across model-runtime catalog v0.2, runtime-candidate routing, HTTP/stdio adapters, remote provider adapters, embedding contracts, durable lease APIs, deferred batch.embed, verified artifact descriptors, signed adapter manifests, conformance report storage/runner, host-owned prompt assembly (PromptAssemblyPolicy, daemon inquirium.prompt_assembly HostRoot/Organ/Operation sourcechain with default fixed non-empty host-root boundary plus coarse temporal context layer, real bounded host content/ref materialization, config-load validation for generate candidate sourcechains and base prompt refs, scoped adjustments for profile/model-binding/ adapter-instance, manifest-declared instruction roles, pure assembler, inquirium-host adapter request planning, NFC-normalized canonical instruction hash, caller boundary count, content-source trace, fail-closed tests), and the first output-boundary foundation (output_contract.schema/ref, host-owned output schema registry with a narrow JSON Schema subset, structured JSON shape limits enforced without materializing oversized serialized buffers, at most two policy-admitted metadata-only repair attempts, adapter structured-I/O declarations, GenerateOutputEnvelope with bounded params/control, typed unsafe output preserving usage/cost accountability, configurable deterministic host I/O rails, safety-critical effective budget diagnostics with typed budget_exceeded, provider model snapshot/effective sampling trace, redacted output-projection traces carrying schema digest plus violation codes/counts, deterministic-stub/simulator structured happy paths, and host-capped assistant output, plus the inquirium-host stratum for generate budget/prompt/adapter request planning, reusable Inquirium config types/defaults, output-schema normalization, embed admission predicates, bounded duplicate-free batch source lease refs, symlink-hardened file leases with capped metadata, assistant output/transcript-fact planning, table-driven daemon dispatch for inquirium.* host capabilities, typed returned-value effect intent DTOs, daemon effect-intent interpretation for trace, assistant transcript writes, durable generate/embed/assistant budget-charge records with idempotent replay protection, scoped per-principal/per-session/per-operation/per-agent budget preflight and final-charge enforcement, and shared daemon artifact-output intent execution). OpenAI and Anthropic adapters now compile the admitted schema subset into provider-native structured-output requests; native selection intersects adapter and selected runtime/model declarations, and host schema/rail checks still run. OpenAI direct embeddings use the same supervised adapter and runtime/model-binding policy boundary. Full schema ecosystem features such as dynamic refs/recursion/combinators/grammar artifact caching, richer optional evaluator critics, and provider packaging remain open. Deterministic embedding caching and pure CandidatePlan-to-Inquiry-Flow compilation are implemented; durable plan execution remains correctly owned by Agent and other effect strata. The current host boundary already has schema-owned string redaction, bounded multi-violation diagnostics, explicit egress-class limits, complete repair-attempt accounting, live image execution, and a durable evaluation-gated training worker. Solution 045 has a local-only assistant turn capability, host-capped assistant output, principal-scoped transcript fallback with local-control excision markers, Memarium-backed transcript fact attempts with local fallback/read-index, idempotent turn replay, metadata-only assistant trace/feed, direct local OpenAI-compatible baseline assistant target coverage with a validated operator override, profile-scoped baseline-assistant conformance/freshness gating with deployment-controlled host-class/... scope, local-transport allowlisting, 16 KiB host-visible output-cap assertion, and schema-gated candidate-requirement diagnostics, hard-MVP readiness gating through inquirium.baseline_assistant_required, operator-visible inquirium.baseline-assistant status with registry-error and stable failure reason projection, run-conformance bootstrap paths, render-only Node UI affordance under /admin/inquirium/assistant, a durable participant/session/source-bound context grant registry, host-owned operator-inline/Relationship/Memarium/ Query/Messaging/Artifact/Dataset resolvers with classification ceilings and exact egress-ack binding, operator-question widget registry/projection contracts plus a bounded durable daemon registry with expires/at, conservative default/on-timeout, lazy/recovery timeout sweeps, fail-closed late-answer handling, and notification/action expiry projection, source-component-scoped notification ids, and idempotent notification-store projection path, explicit cancel/supersede transitions with paired notification closure, digest/size-verified transcript object descriptors and replay hydration, participant-scoped text/tag projection with semantic tags, canonical participant-bound transcript bundle export/import, inquiry-feedback persistence, mode-keyed rigor policy, the shared ordered-axis resolver/monotonicity helper, and the canonical shared participant:did:key: validator. The baseline profile renderer emits loopback Ollama or managed digest-pinned llama-server operator config without an extra proxy and provides explicit doctor/pull/status/deactivate operations. Automatic sustained-loss/boundary-risk notification projection, metadata-only crisis candidates, remote model acceptance/egress acknowledgement, content-addressed training manifests, and grant-rechecked local train.adapt admission and execution are implemented; training recovery is operation-kind/status scoped and paged, cancellation is compare-and-set, and decoded model artifacts are capped at 96 MiB. Solution 044's bounded organ, P064's tracked implementation recommendations, and Solution 045's assistant channel are MVP-ready. Richer schema/evaluator profiles, provider-binary packaging, optional scheduler-owned timeout surfacing, and Agent-owned effect governance remain additive later work rather than incomplete P064 tracker items.
• Proposal 073, promoted to Solution 047, defines Agent as the bounded stateful orchestration organ above Inquirium. Its node-local FlowNode and Assistant Channel scopes are complete: agent-core owns substrate-free lifecycle, fork, step, memory, binding, outcome, Assistant escalation/acceptance, and effect contracts; agent-host owns pure step decisions, operator-profile admission, and the closed table-driven Sensorium/Artifact Delivery effect-policy registry; and the daemon exposes lifecycle, proposal, binding, bounded controller-run, Assistant escalation/draft-acceptance, and contextual effect-dispatch capabilities. Local control is administrative authority, while module calls require explicit bounded JSON-e Flow agent_grants, Agent ownership, and target-capability allowlists. Memarium Personal facts remain the source of truth; startup performs bounded replay, partial-bundle and interrupted-outcome repair, immutable admission-snapshot recovery, current-policy quarantine cascading through descendants, and terminal/expired-owner lease reconciliation. Assistant approval is durably recorded before Agent/binding authority, uses the durable operator-question record as typed authority, rejects unapproved bindings during replay, and idempotently completes interrupted materialization. The binding's narrowed budget and wall-time deadline are effective across controller, Inquirium, lease, fork, reaper, and status paths. The general real HTTP process smoke covers spawn/status/binding/controller/suspend/resume/controller-mediated fork/stop plus durable recovery after SIGKILL. A second process smoke covers Assistant turn, explicit escalation, pending-question restart, exact replay, approval, denial, timeout, bounded controller execution, content-addressed agent.outcome.v1, and render-only acceptance. Ambient Assistant binding is denied, generated content stays outside status and notifications before acceptance, and acceptance fixes publication authority to false. The active controller executes admitted Inquirium, inert effect-proposal, and child-spawn actions through their owning host strata; Inquirium remains constrained by classification, pinned profile, runtime allowlist, and grants. Effect dispatch consumes transport-independent host plans, persists bounded deferred/completed/failed execution outcomes, avoids target reinvocation on exact replay, and reconciles Deferred Operation Registry terminal state with lease release through a bounded scheduler job. Child reservations reconcile bottom-up, lease acquisition is charged, and old inactive lease details compact to restart-safe audit tombstones after the configurable 30-day default horizon. Summary-producer authority is the intersection of Capability Registry-eligible modules and the host allowlist. The post-MVP Corpus-chair extension is now implemented: signed and fresh Room evidence from the node-local round authority admits one exact query/room/participant binding, and Corpus durably accepts its agent.outcome.v1 as an inert answer draft without publication authority. Corpus room policy, signed invitations, typed control-plane failures, AD-owned transport idempotency, Corpus-owned semantic replay by signed invite/id, configured remote trust-root verification, bounded live WSS join/readiness/messages, metadata-only authority observations, stable authority bind and subject-sequence recovery, controlled session rejoin, and recipient restart recovery are implemented. A separate local-control Corpus transition validates current quorum, room high-water, chair identity, evidence, output digest, and idempotency before signing and publishing the inert Agent draft; Agent authority remains non-publishing. Federated Room transport and remote Room-authority trust remain later work and do not change the node-local hard-MVP verdict.
• The Agent boundary now also makes the horizontal/vertical split executable: agent-core owns only generic observation need/binding/evidence and effect proposal values; static JSON-e wiring may select or narrow operator-authored opaque source mappings; and the daemon composition root alone resolves those refs through Room/Sensorium, Workbench, Artifact Delivery, or later domain adapters while enforcing grants, schema, classification, leases, HIL, and quarantine. A positive dependency allowlist admits the pure horizontal semantic-registry-core data/selection algebra, names pure inquirium-core DTOs as the sole vertical exception, and rejects Room, Corpus, Memarium, Sensorium, Workbench, and other source/effect-domain coupling in agent-core. JSON-e imports the Agent-owned hard observation caps, and successful observation resolution preserves the validated source P081 causal/context plus prompt-free source-version/ref and resolution/ref in the Agent trace.
• The latest post-MVP Agent/Corpus profile is also implemented without changing the hard-MVP verdict: Story-011 selects B while C remains a competing bidder, admits B as a Room-attested collaborative-participant Agent through the Corpus adapter, routes one inert corpus-reasoning-turn-proposal.v1 through HIL-gated corpus.room.turn, wakes A's chair Agent through an epoch-bound Interaction Broker room-event watch, and accepts the chair result only as an unpublished Corpus draft. Process coverage includes altered-evidence denial, metadata-only durable watch replay, dirty restart, stale cursor refusal, exact effect replay, exact Room-scoped module-watch authority, skew-tolerant turn expiry, schema fixtures, and absence of ambient publication. P069, P073, Solution 038, and Story-011 trackers carry the same evidence; readiness percentages remain unchanged because both documents were already at their completed node-local slices.
• Story 005 remains hard-MVP complete, and its post-M4 productization tracker now lives in the Whisper implementation note instead of a workspace-root draft file. The closed slice has a CI-runnable Inquirium acceptance bridge: an opt-in supervised simulator adapter is routed only through model-runtime/Inquirium by runtime/ref and host-owned model.binding/ref. whisper-core carries the production-shaped policy primitives for routing failure mode, source class, outbound privacy resolution, correlation policy explanation, association-room proposal lifecycle, public-gossip promotion, and bounded trace integrity/privacy. The current Node worktree consumes those primitives in the publish path: whisper-intake performs outbound privacy preflight before public/private signal publication and now implements whisper.trace.publish with exact one-time operator consent for inline disclosure, transient byte validation, and metadata-only read models. Trace authoring atomically reserves idempotency keys, independently bounds inline bytes, extensions, and total JSON, and applies a 30-day default retention sweep to its local read model. Agora enforces public trace topic/disclosure admission and projects traces outside signal thresholding, while AD/INAC admits private traces through the existing signed-envelope carrier. Story-005 asserts the exact agora-publish and inac-direct carriers, proves that private traces stay absent from Agora projection, and retains its private-signal regression guard. agora-projections and agora-service also provide a minimal local association-room lifecycle seed plus public-gossip promotion drafts from accepted rooms, with authenticated actor binding, bounded lifecycle facts, FK-backed proposal refs, and bounded opaque lineage refs. These move Proposal 013 closer to post-M4 productization while preserving the readiness interpretation for unfinished product/runtime surfaces such as real Anon relay transport, production semantic correlation, full association-room case management on the accepted signed room-event log over Artifact Delivery with multi-Agora fanout/merge, bounded replica retention status, and per-thread predecessor digest links, final public-gossip publication runtime, live Monus/Sensorium source verification, richer room/curation UI, and remote model deployment.
• The 2026-08-15 Arca/Dator closeout refresh completes the hard-MVP P016 buyer-host settlement slice. Remote terminal results remain Artifact Delivery facts rather than settlement commands: a one-shot host token binds acceptor, schema, digest, and authenticated source peer; typed reason codes plus explicit retryability replace message matching; invalid explicit answer formats fail closed; and completed work follows either AwaitingAcceptance or AwaitingManualRelease according to the frozen confirmation policy. The buyer-host lifecycle test covers release, dispute, failure, rejection, enqueue failure, replay, digest conflict, and restart reconstruction. The adjacent local/observed offer projection is now capped at 4,096 entries and derives observed trust/provider identity on the host. This raises P016, P021, and Arca readiness without promoting the broader Story-009 product story into the hard-MVP blocker set.
• Shared Offer Catalog is now hard-MVP complete. Proposal 067 and Solution 033 document the extracted shared Python offer-catalog runtime, Agora replay, fail-closed Agora/Seed Directory admission, Arca embedded-cache reuse, query parity, withdrawal active filtering, public/shared catalog deployment profile (node/middleware-modules/offer-catalog/config/profiles/public-shared-catalog.json), automatic shared-offer-catalog passport publication readiness with classified pending reasons, redacted Host Agora and Seed Directory admission diagnostics, and a local public-profile smoke runner (node/tools/acceptance/shared-offer-catalog-public-smoke.py) covering authorized replay, bad-signature refusal, unknown-provider refusal, withdrawn-offer inspection semantics, and the HTTP query surface. The remaining public-profile operating policy is now resolved and enforced where applicable: passport renewal is supervisor-driven by default, and non-loopback Agora URLs must use HTTPS/TLS with Node fail-closed replay validation. Remaining work is post-MVP production hardening such as broader monitoring matrices and eventual legacy peer-message retirement.
• Proposal 080 hard-MVP and post-MVP Phases 8 and 9 are fully implemented through P080-043. The daemon-owned capability-passport publication reconciler uses a fail-closed local-only default, caller-bound schema-gated declarations, append-only rebuild, registry- and config-bound module/capability admission, bounded list/diagnostic projections, deadline-terminal retry, forward-compatible fact-kind replay, renewal/revocation, and provider migrations. Repeated channel_json reconnect now receives a fresh bounded window only after heartbeat-confirmed restoration, uses a generated 5-second default with a 60-second ceiling, binds all pending work to a session generation, and never transparently replays an old request. Supervisor and daemon listener-flap acceptance cover same-launch recovery and full-restart launch replacement. These post-MVP additions do not change the completed hard-MVP score. The checked inventory covers all 18 bundled modules and all select channel_json; eight independently authenticated product HTTP listeners remain for Agora, Arca, Attestation, Contact Catalog, Dator, Messaging, Recovery, and Whisper, with unique loopback endpoints enforced by the inventory and daemon tests. Reconnect-grace exhaustion and failed application-heartbeat proof terminate and clean the child before bounded restart policy applies. Legacy daemon configuration, persisted settings, loose config artifacts, and package manifests are rejected explicitly before effects. The retired HTTP-local supervisor, routing fallback, compatibility projection, executor contract, schema, implementation, and tests are removed. A transport-neutral component contract rejects missing, mismatched, incorrectly pinned, ambiguous, unknown, or cyclic dependencies before effects, drives provider-first startup and dependent-first shutdown, and restricts imperative disposal to typed host-local resources. Dedicated reconciliation exposes dependency_unavailable, waits for observed provider readiness before downstream resume, and leaves health/status reads side-effect free; Story-005, Story-009, and strict Story-010 pass on the implemented baseline.
• Corpus and Story 011 are tracked as hard-MVP blockers through Proposal 069 and Solution 038. Its MVP slice is intentionally narrow: topic taxonomy/resolution, topic-scoped offer discovery, question-envelope.v1-decorated query broadcast, bid-state aggregation, and a single-provider P011/P016 settlement path. The contract gate is implemented: canonical schemas and examples for topic taxonomy/resolution, query, bid and bid-state; the service-offer.v1 Corpus extension; node schema sync; schema-gate validation including query price-bracket and service-offer topic-subset constrainers; deterministic taxonomy digesting; topic resolution; topic-scoped offer indexing helpers; schema-valid AD capability-many query envelope construction; bid-state projection; bid/query price validation; and single-provider settlement selection over the embedded procurement-offer.v1. The latest Node slice adds Dator Corpus offer projection, daemon-owned Corpus round persistence, query/bid registration APIs, provider-side bid acceptor runtime, unique provider-scoped bid ids, real node-identity Ed25519 signatures on generated local bids, exact-plus-parent topic matching, price-bracket rejection without silent offer-price mutation, the selected-offer bridge into the P011 procurement path, AD capability-many runtime fan-out over INAC with taxonomy-digest candidate filtering, opt-in provider-side Corpus AD query admission, admitted-bid signature verification bound to bidder/node-id, P057 notifications for bid readiness/requester-satisfied/settlement failure, operator-visible settlement-failed recovery state for bridge failures after selection, operator visibility under /admin/corpus/rounds, and passing Story-011 acceptance coverage under full Seed Directory sovereign-policy capability lookup backed by a refreshed signed federation root. The current slice also adds corpus-reasoning-answer.v1 as a validated, digest-bound final answer artifact that can be attached to the requester-owned round read model after provider-local inquirium.generate drafting; answer admission now uses ordinary Artifact Delivery with an in-process corpus.answer acceptor, tier-correct answer classification propagation, provider signature verification, selected-bid binding, policy-digest binding, and append-only federation metadata through supersedes plus optional revision/no while local snapshots remain latest read-models. The remaining hard-MVP closure is now covered as well: P069 specifies the orbiplex-canonical-json-jcs-v1 profile for Corpus signatures/idempotency, and the Shared Offer Catalog exposes a path-first Corpus topic-index query surface with bounded pagination, HATEOAS-style navigation links, invalid-digest refusal, and partial-withdrawal supersession tests. P069 is now hard-MVP ready for the procurement slice. The post-MVP node-local live layer now connects admitted participants to a bounded WSS Room carrier, propagates metadata-only join/readiness/message observations to the authority, suppresses exact replay redelivery, and recovers stable authority binding plus subject/session sequence across authority and recipient restarts through fixed-high-water paged recovery and checkpoint validation at append and restore boundaries. The requester-appointed Agent-chair path also has a separate local-control transition that signs and publishes only after current quorum, room-high-water, chair, evidence, output-digest, and idempotency validation; the first profile is text-only and uses the dedicated corpus-reasoning-answer-signature.v1 domain. Phase 8A now adds the optional operator-bounded Chair control plane without changing hard-MVP readiness: distributor/operator ceilings resolve one effective policy; Corpus Room policy v2 and Agent binding v2 bind its exact digest and current Room evidence; voice, kick, ban, and floor requests remain inert Agent effects until HIL and canonical Room admission; and scheduler reconciliation removes stale Chair delegation, floor authority, and expired bans. Story 011 covers the process-level Chair voice-control path over the existing federated Room topology. Remaining post-MVP work includes remote Room-authority trust, arbiter election, multi-provider final answer composition, and N-way settlement. Matrix is an optional bridge profile rather than a Corpus or Room liveness dependency; Sensorium Interface views are already available over the Room relay slice.
• Room primitive is now tracked explicitly through Proposal 070 and Solution 036. The current code implements the durable Room skeleton, deterministic projection over Agora facts, signer-backed short-lived membership attestations, explicit POST attestation request contracts, no-disclosure request modes, per-exposure TTL caps, rate-limit/dedup, metadata-only attestation audit, bounded Room contract validation, golden projection vectors, authenticated Agora query surfaces, schema-gate import/export helpers, room-scoped live authorization, host-owned Room lifecycle service, bounded WebSocket pub/sub live carrier, Matrix live carrier with cleanup redaction, and compatibility consolidation for answer-room/association-room projections. The latest hardening makes the attestation endpoint skew-tolerant for authorization expiry, rejects over-cap TTL instead of silently clamping it, scopes rate-limit buckets by room, and records audit facts with exposure, ttl/requested, and ttl/granted while schema tests reject raw payload and passport bodies. P070 is complete for its hard-MVP standalone Room foundation, including the node-local live plane required by Corpus. Phase 6A now closes the member-visible production federation delta: one authority-signed relocatable WSS endpoint per relay epoch, one ephemeral total order per epoch, failover through Agora/AD without cross-epoch merge, outbound-TLS operation, keepalive/reconnect, and relay-carried P082/P083 classes. The follow-up POSIX deployment-evidence profile now proves the host-owned TLS seam with separate relay, publisher, and observer processes, per-config crypto-provider binding, terminator-owned task cleanup, bounded cursor-expiry refresh, exact reconnect accounting, metadata-only dirty restart, graceful checkpoint persistence, newer-epoch failover, active revocation, payload-digest refusal, and session-bearer omission from relay deliveries and retained evidence. Phase 6B now closes the remaining specified relay profile with recipient-private signed sender-key packages, sender-authenticated encrypted frames, monotonic membership-high-water rotation, stale-ciphertext refusal, delayed receiver checkpoint commit, explicit member-visible versus sealed wire discriminators, schema-ref registry coherence, sealed reconnect, a bounded metadata-only relay audit, and a 21-check multiprocess host-TLS acceptance report with closed evidence shapes covering leave rotation and sealed-profile failover. Phase 7 now adds closed scoped moderation, durable access denial, bounded ephemeral floor leases, stable message v2 refs with reply linkage, metadata-only diagnostics, and a recipient-set-derived sealed epoch that rotates for audience changes but not mute/floor changes. P070 is therefore still at 100% for hard-MVP and remains MVP-ready. The newly specified post-MVP Phase 8 adds immutable opening name plus exposure-governed append-only topic and summary facts; its contracts, projection, authorization, replay, and refusal evidence are not implemented yet, so P070 is no longer marked post-MVP ready. This changes neither the hard-MVP readiness verdict nor Matrix's status as an optional bridge profile.
• Sensorium Workbench is now tracked through Proposal 071 and promoted to Solution 042 as a post-MVP actuator foundation. The opt-in supervised Python connector now has a complete local foundation: allowlisted workspaces, bounded file and artifact operations, PTY lifecycle, artifact-backed patching, waits/probes/watches, replay/recovery, metadata-only audit, and explicit operator controls. Path and command-profile admission crosses the required bounded sensorium-actuation.bridge.{request,response}.v1 companion-process boundary into the Rust sensorium-actuation-core; unavailable or malformed bridge behavior fails closed without a Python validation fallback. The daemon-owned Interaction Broker enforces grant-context admission, persistence, recovery, retention, provider health, Workbench file/terminal adapters, dynamic providers, and native Artifact Delivery, approval/consent, and Memarium-query adapters. Verified Workbench artifacts can be handed off explicitly to Artifact Delivery resolution and/or metadata-only Memarium provenance, with replay bound to the original correlation/id. Consent supports allow-once, exact argv, and bounded workspace-bound argv prefixes through shared append-only sidecar merge; node-ui provides consent revoke and broker remediation screens. The managed fixture-copy.v1 Sensorium Virt executor copies a bounded symlink-free tree, permits approved writes only in the copy, exports a bounded artifact, persists lifecycle, and tears down only its managed root while refusing PTY without process isolation. Agent, Corpus, and the current execution-derived answer-room tool requests now use a schema-backed host lineage wrapper around sensorium.directive.invoke, so no product receives direct Workbench connector authority. Proposal 071 remains outside hard MVP. Its process-isolated Phase 4 architecture is now frozen: suitability is matched from host-attested properties rather than backend names; VMM lifecycle and guest mechanics are separate ports; Rust and the daemon own validation and host launch/recovery authority; the Python connector owns bounded adapter mechanics; vfkit-system.v1 on macos-vz-arm64.v1 is the first implementation slice; Cloud Hypervisor is the first Linux deployment profile; and Firecracker follows after the image manifest and guest protocol stabilize. The frozen contracts additionally require closed versioned capability values, a normalized-plan-bound P082 operational context with conservative network/host-share floors, digest-proven logical image equivalence, and classified control-sequence-safe serial diagnostics. The required capability/plan/image/ recovery/guest-frame contracts, closed host request envelope, pure validator, bounded companion, and first daemon host-broker fixture slice are implemented. Schema-gate covers the host boundary and all five contract families; Workbench refuses backend substitution and recovery diagnostics are structured and capped. The fixture path remains covered by a dirty-restart vertical smoke. Supervised Workbench uses the restricted non-passportable sensorium.virt.host channel capability; the companion is disabled by default, requires explicit literal-boolean local development/conformance opt-in, and is never a fallback when supervised daemon admission is unavailable. Daemon admission rechecks operator-configured source/context/limits, host mutations serialize across processes, and directory enumeration is capped before materialization. The daemon-owned vfkit host lifecycle, exact process/ socket/resource recovery identity, pre-spawn launch intent, fsync-backed boot artifacts, boot nonce, closed launch/API profile, disabled-profile terminal cleanup semantics, descriptor-pinned socket root, and feature-gated 18-case process-level crash/substitution harness are implemented. The nonce/generation/plan/image-bound Rust guest agent and host channel are now protocol implemented with bounded process/PTY/file mechanics, a single aggregate process-output budget, ioctl-backed resize, atomic content-bound patch staging, endpoint identity checks, lifecycle inspect/ quiesce/shutdown, chunked transfers, and honest outcomes. The V1 production guest uses one synchronous runtime and one operation per connection, so effects are serialized per environment without retaining the host lifecycle lock across guest I/O. The separate conformance proven state comes from the real-binary local-transport harness, including admission, deadline, outcome/evidence, boundary, partial-transfer, and lost-receipt cases. A pinned full-system GNU/Linux arm64 image and real-vfkit harness now prove the third deployment evidence proven state for the host/guest substrate, including systemd, kernel/mount/package operations, no-NIC/no-share posture, observed CPU/RAM/disk/TasksMax plan and PID refusal, real PTY/file mechanics, dirty recovery, stale-generation refusal, deterministic teardown, atomic digest-bound build completion, and a schema-gated report with exact artifact pins and functional timing budgets. The guest additionally exposes a bounded independent terminal-read cursor with exact output bytes, explicit eviction gaps, post-exit replay, and future-cursor refusal. Workbench terminal output now has a closed exact-byte event contract, bounded event/byte/age retention, and local or owner-bound direct-peer live SSE projection through P082. Recipient-side remote feed egress requires its own host-local capability in addition to the exact source-issued subscribe Passport; peer time/message bytes, pre-decode result bytes, terminal-vs-retryable failures, and consumer-side byte-evidence validation are explicitly bounded. Virtualized Workbench/P083 routing and the additive Story 012 vfkit v2 vertical are implemented. The fixture is digest-pinned in the guest image and the closed report proves the complete story through one Workbench runtime. Proposal 071 and Solution 042 are therefore at 100% for the vfkit reference profile. The Cloud Hypervisor extension is now implementation-complete through daemon admission, Workbench routing, the shared guest contract, macOS fake-process conformance, fail-closed Landlock ABI v3 preflight with an attested host-filesystem-allowlist enforcement class, exact-process dirty-restart reconciliation, exact multi-backend manifest-variant selection, authoritative cgroup cleanup, a closed schema-gated deployment report, and a Linux x86_64 host/guest/schema/daemon/Workbench compile/conformance gate. Its tracker remains in progress, because the checked-in deployment runner has not yet passed on a Linux x86_64 host with real /dev/kvm; QEMU/TCG and fake evidence do not satisfy that gate. Firecracker and richer command-BDO signal policy remain separately evidenced post-MVP extensions rather than current blockers. Interaction Broker is implementation-complete for its current provider foundation; provider-pushed events and richer deferred-wait retry policy stay deferred, so the component is not yet marked post-MVP ready.
• Local Relationship Layer is now hard-MVP complete for the Node-owned slice: Proposal 065 and Solution 032 have contracts, pure core, vault-first daemon storage, sealed rebuildable SQLite projection, local control/host capabilities, operator class/membership/predicate/decision audit UI, package trust queue with approval history, canonical Messaging consumption, dynamic Artifact Delivery group resolution, repeatable Story-010 relationship acceptance runner with a local CI wrapper, projection replay/privacy regression gates, verified remote-disclosed node-operator-binding import through the identity control surface, durable revocation invalidation for imported binding evidence, registry-driven pairwise nym context-kind admission, and relationship-class retention profile inheritance. Public federated Local Relationship capability, richer multi-operator UX, hosted CI-provider wiring for the runner, and performance profiling under real relationship cardinalities remain post-MVP work.
• Replay Scheduler M1 is now fully closed for the hard-MVP slice: the generic bounded scheduler, durable launch ledger, host-owned job-source merge, authority gate, cooperative shutdown, Agora projection replay action, and operator status/control surface are all documented as implemented. Richer Agora-domain panels and non-Agora maintenance jobs are post-M1 extensions.
• Agora gained a generic encrypted-artifact Vault surface: agora-vault-entry.v1 exposes only opaque artifact ids, kind, ciphertext, and cryptographic envelope metadata; supervised local routes are client-auth / daemon-dispatch gated, while remote provider deployments bind the same operations to the frozen agora-vault@v1 passport profile.
• Temporal Storage Convention is now hard-MVP complete: notification-store is the full-compaction-required adopter, while messaging outbox and Seed Directory accepted facts are converged bounded/no-op adopters with manifests, temporal status/feed/replay-check, and explicit compaction.policy = "bounded-noop" diagnostics.
• Bounded Deferred Operations were promoted from Proposal 055 to Solution 029 as a horizontal host control-plane component. The MVP slice is complete: shared wire contracts, host registry, poll/cancel surfaces, JSON-e Flow persisted continuation, Sensorium OS deferred state, operator visibility, and AD consumer integration.
• Sensorium has been promoted to Solution 030 as a constitutional organ. Its MVP slice is implemented for sensorium-core observation admission/query, directive invocation, audit-only outcomes, internal connector dispatch, the supervised Sensorium OS reference connector, action-catalog sidecar authorization, and deferred Sensorium actions. Local Agora observation publication remains partial because runtime support currently exposes topic metadata and read surfaces rather than a complete local subscription bus.
• Node Address Attestation Fallback is now counted as hard-MVP ready through the Seed Directory / TLS Trust path: node-address-attestation.v1 exists, Seed Directory can issue signed endpoint evidence, daemon consumers import usable evidence, peer supervisor enforces endpoint pins, and TLS leaf/SPKI plus advisory route-id checks are wired. Peer-relayed endpoint evidence over INAC remains a post-MVP fallback extension.
• Classification is now counted as hard-MVP ready at proposal and solution level. classification.v1 and orbiplex-node-classification provide the common lattice, exact surface/topic/time derivation, revocation-bound declassification, durable one-shot consumption, quarantine vocabulary, and projection-aware bound-subject handling consumed by Memarium, Agora, Whisper, INAC/private Artifact Delivery, Interface, archival export, and adjacent host boundaries. Context-free reads retain source tier instead of leaking a boundary decision into every surface; missing authority fails closed. Whole-program IFC, per-field labels, complete historical backfill, provenance-aware enforcement for every open-world schema, and richer quarantine UI remain post-MVP work.
• Proposal 025/Seed Directory capability catalog is now post-MVP complete for its current scope: official-service status rests on federation-service-endorsement.v1, root-pack endorsement revocations are applied at startup, the unified /revocations feed carries {artifact_family, artifact} entries for passport and endorsement revocations, operator/AD endorsement install is scoped and conflict-aware with ingress-enforced source plus optional source/detail, participant-sovereign operators can issue non-own official-service endorsements through the daemon API, federation-service-endorsement-revocation.v1 has shared schemas/fixtures, and capability-proof-presentation-batch.v1 plus capability-passport-present.v1 can refresh local proof caches through AD with metadata-only presentation facts; outbound batch proof allows must carry explicit max/bytes capped at 256 KiB.
• Proposal 054 is hard-MVP complete: seed-directory-query-attestation.v1 is schema-gated, Seed Directory can attach opt-in signed response attestations, daemon can opt into trusted Agora replay for adv, cap, and revocations lanes, replay follows paginated Agora result pages, replay cursors/status are persisted in the embedded store, projection equivalence tests include revocation effects, and daemon-owned Seed Directory discovery now applies one strict multi-directory policy (preferred-directory, quorum, or weighted-trust) across host queries, AD/capability routing, subject lookup, and Contact Catalog provider discovery, with cross-directory revocation suppression for revoked capability passports. /v1/seed-directory and Node UI expose safe trusted-directory diagnostics, local endorsement/reputation policy inputs, replay state, and skip reasons.
• Memarium Proposal 036 and Solution 002 are implementation-complete for v1: neutral MemariumObservation bridges post-chain and phase observers without daemon-private runtime dependencies; invalid observe rules fail startup; governed community forget verifies its governance fact; atomic fact idempotency and deterministic system keys make retries converge; the fully paginated scan path and validated SQLite sidecar remain replay-equivalent; quarantine and strict-mode transitions are authorization-first and durable; and archival backup/export applies exact revocation and one-shot authority before atomic bundle publication. Story-005 smoke covers the classification-bearing private AD/INAC boundary. Richer Node UI batch UX and measured sidecar connection/query optimization remain product/performance layers, not Proposal 036 blockers.
• Story 000 is now hard-MVP complete: the minimal two-node operator acceptance pack under node/tools/acceptance/story-000-operator/ was hardened to keep all non-story middleware disabled by real module id and its ad-smoke path passes with two local WSS peer sessions, connected peer read models, running peer supervisors, and metadata-only daemon status.
• Proposal 014 / Node Transport and Discovery is now counted as hard-MVP ready: P014, Requirements 006, Solution 000, node/docs/MVP.md, and the Node implementation ledger were reconciled against the current protocol, network, peer-runtime, daemon, and Story 000 acceptance implementation. Federated node-id succession publication/replay, richer federation-wide peer-governor policy, and additional transports remain post-MVP expansion rather than blockers for the transport seed. The local peer-governor slice is now seeded through peer-status.v1, daemon-configurable quality thresholds, and operator-visible peer scorecards. The local NT-018 node-succession lifecycle is implemented through node-succession.v1, host-derived operator import/accept/reject provenance, successor identity activation, and Story 000 rotation-smoke; future successor routing eligibility remains a live local policy-registry resolution rather than a mutation of the accepted fact. The local client-instance recovery read model is now bounded and replay-idempotent, so evicted or unknown detachment references fail closed.
• Key Delegation Passports are now hard-MVP complete at solution level: Seed Directory /key publication/query surfaces have focused signed-artifact coverage, daemon operator routes already expose proxy-key and delegation lifecycle management, and remaining multi-hop delegation plus richer Node UI screens are explicitly post-MVP/product-layer work.
• Middleware is now counted as hard-MVP complete: Solution 019 already covers the implemented host-owned lifecycle, readiness, dispatch, claimed-route, host capability, observer/audit, raw-signal, and schema-presentation surfaces, while additional executor classes or product-specific module UX are future extension points owned by their specific proposals.
• Capability Binding is now counted as hard-MVP complete: the reference runtime uses the shared capability-binding organ through daemon dispatch and Sealer integration, while solution-level service adapters and caches remain optional seams for alternate embeddings or profiled hot paths rather than MVP blockers.
• Agora/P035 is now counted as hard-MVP complete: the reference runtime covers the public record relay, content addressing, signing/ingest, query/readback, SSE subscription, Matrix-backed federation, retention, subject indexing, Agora Vault, and Story-008 resource-opinion path. Remaining ingest-policy tightening and hot-path/status-product work stay post-MVP and are listed in Proposal 035's hardening queue.

Stories

Document	part of MVP	MVP ready	post-MVP ready	readiness %
Story 000: Two Nodes See Each Other	true	true	false	100
Story 001: Swarm Node Onboarding and Federated Answer Procurement	false	false	false	65
Story 002: Federated Peer Learning and Consensus Correction	true	true	false	90
Story 003: Remote Memory Preservation, Archivists, and Vault Publication	false	false	false	38
Story 004: Pod-Client Onboarding and Delegated Federated Answer Procurement	false	false	false	65
Story 005: Whisper Rumor Intake, Redaction, and Thresholded Association Bootstrap	true	true	false	100
Story 006 Buyer Node Components for Arca	true	true	false	90
Story 006: Voluntary Swarm Service Exchange for Cooperative Content Production	true	true	false	90
Story 007: Settlement-Capable Node as the Authoritative ORC Ledger	false	false	false	82
Story 008: Leaving an Opinion on a Website via the Local Node	true	true	false	100
Story 009: The magazine publishes itself — a three-node blogging pipeline about Bielik, conducted by Arca	false	false	false	90
Story 010: Message to a Friend	true	true	false	100
Story 011: Corpus answers the fish-water question	true	true	false	100
Story 012: Remote Agents Solve a Problem Through a Shared Chair Terminal	false	true	true	100

Proposals

Document	part of MVP	MVP ready	post-MVP ready	readiness %
Licensing Baseline for Orbiplex Swarm Components	false	false	false	25
Communication Protocol Baseline for Orbiplex Swarm	true	true	false	90
Question Envelope and Answer-Channel Transport for Orbiplex Swarm	true	true	false	82
Human-Origin Flags and Operator Participation in Answer Channels	false	false	false	65
Operator Participation Room Policy Profiles	false	false	false	25
Pod-Backed Access Layer for Thin Clients	false	false	false	55
Pod Identity and Tenancy Model	false	false	false	25
Transcription Monitors, Archivists, and Public Vaults	false	false	false	20
Communication Exposure Modes for Swarm Requests	false	false	false	25
Operator Proxy and Co-Regulation Channels	false	false	false	25
Federated Answer Procurement Lifecycle Artifacts	true	true	false	90
Learning Outcomes, Knowledge Artifacts, and Archival Contracts	false	false	false	38
Whisper Social-Signal Exchange and Threshold Bootstrap	true	true	false	95
Node Transport and Discovery MVP	true	true	false	96
Nym Certificates and Renewal Baseline	false	false	false	25
Supervised Prepaid Gateway and Escrow MVP	true	true	false	90
Proposal 017: Organization Subjects and org:did:key	true	true	false	88
Proposal 018: Layered capability_limited Participant Restrictions	true	true	false	100
Proposal 019: Supervised http_local_json Middleware Executor	true	true	false	100
Proposal 020: Bundled Python Middleware Modules for Hard MVP	true	true	false	100
Proposal 021: Service Offers, Service Orders, and the Host-Owned Procurement Bridge	true	true	false	92
Proposal 022: Monus as Host-Granted Local Observation Middleware	false	false	false	15
Proposal 023: Federated Offer Distribution and Catalog Listener	true	true	false	100
Proposal 024: Capability Passports and Network Ledger Delegation	true	true	false	85
Proposal 025: Seed Directory as Capability Catalog	true	true	true	100
Proposal 026: Resource Opinions and Discussion Surfaces	false	false	false	100
Proposal 027: Middleware Peer-Message Dispatch	true	true	true	100
Proposal 028: Service Schema Catalog	false	false	false	25
Proposal 029: Workflow Template Catalog	false	false	false	40
Proposal 030: Identity Recovery Service	false	false	false	55
Proposal 031: Participant Key Passphrase Lock	true	true	false	100
Proposal 032: Key Delegation Passports	true	true	false	100
Proposal 033: Workflow Fan-Out and Temporal Orchestration	true	true	false	77
Proposal 034: Node Operator Binding and Derived Node Assurance	true	true	false	90
Proposal 035: Agora — Topic-Addressed Record Relay and Shared Record Substrate	true	true	false	100
Proposal 036: Memarium — Local Memory Organ for the Orbiplex Node	true	true	true	100
Proposal 037: Generic Signing Service	true	true	false	100
Proposal 038: Key Roles and Key Use Taxonomy	true	true	false	100
Proposal 039 Crisis Seed v1 Review Record	false	false	false	25
Proposal 039: Crisis Space Seed v1	false	false	false	100
Proposal 040: Custodial Redelivery and Tombstones for Agora Records	false	false	false	38
Proposal 041: Agora Ingest Attestation and Tiered Access	false	false	false	65
Proposal 042: Inter-Node Artifact Channel (F2F Memarium Exchange)	true	true	false	88
Proposal 043: Node Address Attestation Fallback	true	true	false	86
Proposal 044: Host-Owned Generic Module Store	true	true	false	100
Proposal 045: Sensorium as a Local Enaction Stratum	true	true	false	92
Proposal 046: Agora Topic-Key Namespace Conventions	false	false	false	100
Proposal 047: Classification Label Propagation for Memarium-Touching Data	true	true	false	100
Proposal 048: Sensorium OS Connector Action Classes	true	true	false	100
Proposal 049: JSON-e Middleware Transformer Executor	true	true	false	100
Proposal 050: Local Readiness Gate	true	true	false	85
Proposal 051: Swarm Membership, Reputation Bootstrap, and Public Adjudication	false	false	false	25
Proposal 052: Tauri-Hosted Node UI	false	false	false	82
Proposal 053: Raw Signal Access for Middleware Flows	true	true	false	100
Proposal 054: User-Maintained Federated Seed Directory	true	true	false	100
Proposal 055: Bounded Deferred Operation Contract	true	true	false	100
Proposal 056: Orbiplex TLS Trust Policy	true	true	false	86
Proposal 057: User and Operator Notifications	true	true	false	90
Proposal 058: Contact Catalog and Private Contact Discovery	true	true	false	100
Proposal 059: Participant, Nym, and Routing-Subject Key-Role Derivation	false	true	false	90
Proposal 060: Messaging Middleware and Personal Message Delivery	true	true	false	100
Proposal 061: Contact Attestation Service	true	true	false	78
Proposal 062: Temporal Storage Convention	false	true	false	100
Proposal 063: Inquirium as a Model Inquiry Organ	false	true	false	100
Proposal 064: Inquirium Implementation Recommendations	false	true	false	100
Proposal 065: Local Relationship Layer	true	true	false	100
Proposal 066: Inquirium Assistant Channel	false	true	false	100
Proposal 067: Shared Offer Catalog over Agora	true	true	false	100
Proposal 069: Corpus — Topic-Routed Collaborative Reasoning	true	true	false	100
Proposal 070: Room — Generic Subject-Addressed Room Primitive	true	true	false	100
Proposal 071: Sensorium Workbench	false	false	false	100
Proposal 072: Capability Registry — Enforced Core and Policy Sidecar	true	true	false	100
Proposal 073: Agent — Bounded Stateful Orchestration Organ	true	true	false	100
Proposal 076: Federation Identity and Network Selector	true	true	false	92
Proposal 077: Swarm Broadcast Assistance	false	false	false	15
Proposal 078: Weak Signal Harvester	false	true	false	68
Proposal 079: Cross-Federation Alliance	false	false	false	45
Proposal 080: Multiplexed Middleware Channel Executor	false	true	true	100
Proposal 081: Horizontal Protocol Primitives for Causality, Federated Synchronization, and Scoped Nym Claims	true	true	false	100
Proposal 082: Sensorium Interfaces	true	true	true	100
Proposal 083: Sensorium Interactive Interfaces	true	true	true	100
Proposal 084: Sensorium Web Observation Connector	false	false	false	45
Proposal 085: Operator-Sovereign Extensibility and Experiment Packages	false	false	true	100
Proposal 086: Component Communication Observation and Trace Sessions	false	false	false	90

Solutions

Document	part of MVP	MVP ready	post-MVP ready	readiness %
Orbiplex Node	true	true	false	85
Orbiplex Node UI	true	false	false	88
Orbiplex Memarium	true	true	true	100
Orbiplex Arca	true	true	false	92
Orbiplex Dator	true	true	false	100
Orbiplex Sealer	true	true	false	100
Orbiplex Capability Binding	true	true	true	100
Capability Advertisement	true	true	false	100
Orbiplex Agora	true	true	false	100
Orbiplex Monus	false	false	false	15
Orbiplex Anon	false	false	false	10
Orbiplex Whisper	true	true	false	100
Ferment	false	false	false	15
Raw Signal Access	true	true	false	100
Orbiplex Key Delegation Passports	true	true	false	100
Host-Owned Module Store	true	true	false	100
Bounded Local Server Runtime	true	true	false	100
Inter-Node Artifact Channel (INAC)	true	true	false	88
Classification	true	true	false	100
Middleware	true	true	false	100
Replay Scheduler	true	true	false	100
Agora Authority	false	false	false	77
Orbiplex Semantic Index	false	false	false	15
Artifact Delivery	true	true	false	100
TLS Trust Policy	true	true	false	86
Contact Catalog	true	true	false	100
Pseudonym Vault and Key Roles	true	true	false	100
Messaging Middleware	true	true	false	100
Temporal Storage Convention	false	true	false	100
Bounded Deferred Operations	true	true	false	100
Sensorium	true	true	false	92
Seed Directory	true	true	false	100
Local Relationship Layer	true	true	false	100
Shared Offer Catalog	true	true	false	100
API Surface Projection	false	true	true	100
Interaction Broker	false	true	false	100
Room	true	true	true	100
Capability Registry	true	true	false	100
Corpus	true	true	false	100
Notifications	true	true	false	90
Capability-Limited Restrictions	true	true	false	100
Federation Root and Network Selector	true	true	false	92
Sensorium Workbench	false	false	false	100
Horizontal Protocol Primitives	true	true	false	100
Inquirium	false	true	false	100
Inquirium Assistant Channel	false	true	false	100
Sensorium Interfaces	true	true	true	100
Agent	true	true	false	100
Operator-Sovereign Extensibility	false	false	true	100