10 projects, three kinds of work, no single mandatory stack.
Use this page to distinguish operational infrastructure, implemented prototypes, playable applications, retained capability, and research. Each card is a dated Web judgment with its own source/editorial basis; exact current implementation facts remain in each repository.
Operational capabilityImplemented prototypePlayable applicationBounded research
Core work system
Three boundaries carry durable Agent work.
Host preserves the Task, Harness runs one replaceable Agent episode, and Runtime commits physical local execution. They cooperate without sharing one truth store.
01Implemented prototype
Operational owner-trusted local engineering component; pre-1.0 public interface
Provides schema-v5 Host Journal/CAS authority, revision-fenced TaskProjection state, external-continuity WorkingCheckpoints with exact response-loss replay, bounded handoff/inspection, opaque extension-state durability, Doctor/backup/restore/deployment receipts, and a deliberately small six-Tool MCP surface for adopt, checkpoint, resume, list, observe, and Host status.
Evidence for this judgment
The 0.3 contraction removed unconsumed Goal coordination, foreign execution, legacy execution workloads, generic capability policy, and Runtime-integration residue. Current 0.4.x then makes external semantic continuity first-class: one WorkingCheckpoint can survive client replacement with revision-coherent resume and exact response-loss replay, while every Runtime/Git/domain hint remains explicitly subject to owner-native revalidation.
Durable cognitive execution for bounded Agent Runs
What exists
Provides independent Journal/CAS Run authority plus Agent-selected WorkingSet cognition, caller interaction and attempt-local Tool context, request-bound action capabilities, Provider/Tool response-loss recovery, bounded cognition history, exact cross-Run source admission, and the supported HarnessAgentRun Python composition surface.
Evidence for this judgment
Current Status and Architecture freeze six distinct state domains—canonical history, durable cognition, interaction cognition, attempt cognition, execution control, and effects—while HarnessAgentRun provides the supported Python composition surface. Recent verification work binds typed evidence to creation lineage and fails closed on structured-result conformance without promoting semantic evaluation or Provider continuation into Harness.
Owns exact Workspaces, durable Jobs and Attempts, immutable-input execution on local Linux and configured limited Windows targets, provider/source commitments, digest-bound image observation, request/target affordance discovery, Windows-native Job Object execution, cancellation, restart recovery, bounded Artifacts, exact replay, reclamation, and reconciliation of uncertain local commits.
Evidence for this judgment
The C1–C10 operational-realization programme saturated its current evidence horizon without reopening Runtime Foundations: currentness, consequential retry, evidence scope, identity/lineage, authority/binding, lifecycle retention, and reclamation remained separable. Current production also exposes workspace.content for digest-bound pixel observation, runtime.describe for capability/ceiling discovery, and workspace.execBound on Linux plus configured limited windows_native targets; the latest fixes preserve fresh remote source currentness, reclaim lifecycle contracts, and terminal observation time instead of guessing after the fact.
Question · open
Which repeated physical operation deserves a dedicated structured Runtime contract?
Domain systems test whether the boundaries survive real consequences.
Game tests agency, World tests cross-owner reality relations, Finance tests capital judgment and effects, and Media tests structured mediation while Studio carries authoring and production.
04Playable application
Registered playable v2 product plus active pre-G0 product-value/direction research; no next product selected
Playable worlds, product-value pressure, and pre-G0 game direction research
What exists
Runs the registered Station Zero v2 product while retaining v3 and other treatments as executable research pressure. Station Zero v3 now has owner-native Product Value lanes with cheap objective/profile slices, currentness-fenced retained evidence, browser/playable proof, and a full promotion matrix; recent natural dogfood used those pressures to reject two plausible fixes and correct a real Core extraction defect without making Human approval a default inner-loop gate.
Evidence for this judgment
On 2026-08-24 natural Product Value dogfood traced a Core cargo successor defect, rejected unrelated Heat/scan fixes, and promoted one objective-scoped correction after exact regression, 18-profile negative controls, evidence revalidation, and 350/350 repository checks. The current matrix keeps Rescue at 3/6 focus-complete victories and Hive at 6/6 while Core rises from 1/6 to 5/6; v2 remains the only registered product.
Provides an owner-preserving Bind→Observe/Act→Reconcile adapter shape plus production Resource Transfer, Message Delivery, and Entity Migration contracts, separate provider/World observation times, WorldTaskInspector for retained commitments, and owner-native doctor aggregation while providers, Host, Runtime, network operators, and domains keep their own truth.
Evidence for this judgment
The 2026-08-18 WDF4 Causal Reality, WDF5 Property Evaluation, and TSAF0 Temporal Structure reconciliation admitted no new Causal, Measurement, or Temporal subsystem: current World already separates owner-native occurrence/admission from causal truth, bundle/observation integrity from measurement validity, and provider execution time from World availability and Host admission. Those results were consumed into the existing 0.4 production boundary rather than expanding it.
Implemented Agent-first capital system with real-capital observation, decision, effect, reconciliation, and performance semantics; live external submission remains disabled
Provides Finance Foundations v1, an Owner Constitution, point-in-time and aggregate multi-venue portfolio evidence, FinancialResource and exposure semantics, exact held-state/valuation-time separation, CapitalStateView and replayable exposure graphs, owner-capital research context, capital-rationality and Decision/Proposal machinery, a process-separated quantitative research lab, exact effect/reconciliation contracts, and Agent Context v21 / Primary Agent Surface v14 with seven semantic operations.
Evidence for this judgment
The current capital-state path now aggregates portfolio observations fail-closed across component scopes, preserves balance FinancialResources even when risky positions are zero, separates held state from valuation time, records replayable carrier/exposure mappings, and bridges the exact managed-capital scope into owner contribution. Nonzero managed FinancialResources explicitly forbid the historical QB5 zero-return shortcut when aligned return evidence is missing. Context v21 additionally projects current execution/reconciliation work while keeping completed historical detail canonical and replayable; the state-changing Decision baseline fence remains enforced at Proposal creation.
Question · testing
Can Agent capital judgment remain separate from financial effect authority?
Structured mediation with Studio as the production capability plane
What exists
Media now owns a technology-neutral mediation contract with SourceBinding, ObserverScope, ProjectionEnvelope, RepresentationBody, Transformation/ProvenanceTrace, and ActionExposure/Disclosure roles plus eleven tested non-lifting invariants. Studio remains the active production plane for revision-bound Claims, editable cross-medium sources, exact selected assets, rendering/QC, review preparation, and human-response calibration when a decision genuinely depends on it.
Evidence for this judgment
Phase 1 completed the Studio→Media owner inversion and pressure-tested OMPC on four materially different real consumers: Host projection, Studio transformation lineage, Web interaction trajectory, and Finance metric/legibility. The result retained a six-role / eleven-invariant shared reference contract while explicitly rejecting a universal Media framework, engine, runtime, SDK, serializer, validator service, or owner absorption.
Research projects test what should remain, change, or disappear.
Computing tests cross-project world-model laws, Human studies practical human trajectories, and Security tests strategic agency under adaptive opposition.
07Bounded research
Active problem-first research with one completed applied cycle, one active applied cycle, HF0–HF23 reusable foundations, and HD0–HD9 completed depth audits
Problem-first Human research, foundations, and Human–Agent capability
What exists
Maintains a problem-first research programme with one completed economic-autonomy cycle and one active Human–Agent capability cycle, plus a reusable Human Foundations library spanning identity, experience, attention, value, regulation, development, memory, knowledge, reasoning, action, social order, normativity, strategic implementation, production/economic organization, perception, affect, persistent relations, and symbolic systems. Deep Foundations add cultural inheritance, reproduction, genetics, evolution, and organismic health/pathophysiology without forcing new peer foundations.
Evidence for this judgment
The current programme demonstrates both expansion and refusal to expand. HUMAN-AI-001 now consumes mature external evidence first and targets only Ordivon-specific transport residuals; HF0–HF23 preserve reusable distinctions across materially different Human questions; and HD9 completed the organismic health/disease/pathophysiology route while explicitly rejecting HF24 and leaving HD10/NextDeepRoute UNKNOWN rather than manufacturing the next stage.
Question · answered
What practical path can increase personal economic autonomy without materially reducing life quality?
Executable bounded research with a thin ordinary owner surface and read-only current-capability preflight; experimental rather than a production security platform
Authorized adversarial-autonomy, adversarial epistemics, and current-capability laboratory
What exists
Runs bounded authorized Contest, Range, Evaluation, Windows-KVM/fabric, ResearchCorpus, and model-backed Actor work while now presenting an ordinary owner-native surface by default. Read-only capability preflight withdraws mechanically ineligible operations before model-facing disclosure, exact dependency/currentness experiments distinguish integrity from applicability, and P1 real-provider transfer shows that UNKNOWN/UNAVAILABLE actions can remain physically executable under a broad static surface yet be rejected before provider reachability by a current-compiled surface. Historical experiment runners and mixed-maturity console affordances have been contracted without deleting reproducible evidence.
Evidence for this judgment
On 2026-08-28 Security completed a destructive executable-topology contraction and retained the P1/R2 current-capability result: owner-native mechanical applicability can compile the exact model-facing operation set, and the returned request is checked against that same surface. In deterministic real-provider fault injection, a broad static surface let UNKNOWN/UNAVAILABLE intents reach providers (one UNKNOWN action even produced a verified physical consequence), while the current-compiled surface rejected the same requests before provider invocation. This strengthened the admission boundary without earning a shared planner, registry, compiler, gateway, Trust system, or freshness service.
Cross-project research, world-model revision, and reusable knowledge
What exists
Runs owner-preserving cross-project falsification, historical and live dogfood, world-model revision, SCD and Computational Possibility research cores, reusable Knowledge synthesis, responsibility placement/deletion tests, and selected protocol conformance. Mature external results are imported into the informed baseline rather than re-proved for Ordivon ownership.
Evidence for this judgment
The 1760–2026 historical dogfood closed without turning historical resemblance into proof of Ordivon theory, and the current Computer contraction reduced active shared machinery to a small responsibility map. On 2026-08-22 the canonical Research Method was strengthened to preserve imported mature knowledge through novelty subtraction, expose that method at first look, adjudicate closeout destinations, and materialize the Resource Ecology result as reusable Knowledge without creating a Resource owner or calculus.
The website explains the map; repositories own the facts.
Public status is an authored orientation at a date. Source, tests, releases, receipts, research methods, and operational truth remain with the project that produced them.
Start with How it works when you need the core work trajectory. Start with Research when the useful unit is an uncertainty that can still change the architecture. Use the repository link whenever exact capability, installation, or evidence matters.
A project can be valuable without becoming universal infrastructure: Game owns its game semantics, Finance owns capital meaning, Media owns structured mediation and retains Studio as its production plane, World owns only the cross-owner reality relations that survived deletion, and Human and Security retain bounded research scopes.