Writing
Start with a concrete failure, follow the smallest mechanism that explains it, then descend into exact experiments, architecture, and the complete dated record.
A capable Agent can lose a response, inherit stale context, finish a process without finishing the task, or act on evidence that was valid yesterday. Ordivon exists to keep those different facts from collapsing into one story.
7 min read ↗Why Decision validity and commitment currentness are different facts, using Ordivon Finance's exact portfolio-baseline fence for state-changing proposals.
5 min ↗Research reportThe Evidence Is Real. It Is Still Too Old.Why authentic evidence can become stale without becoming false, how Security EC1 and World experiments tested current applicability, and why TTLs or generation numbers are weaker than exact dependency revalidation for the tested cases.
6 min ↗Reading paths
Each path begins with a clear problem and moves toward the experiments, decisions, or long-form argument behind it.
Follow historical recurrence, ambiguous evaluators, and canonical representations until the experiment separates what keeps recurring from the vocabulary that only seemed stable.
Start with high-information repository discovery, then compare evidence that closes a capital path and UNKNOWN that preserves the right to keep observing.
Compare a model that knows its objective but loses the multi-turn commitment with storage whose retention right depends on an actual current consumer rather than age or size.
Start with what happened and why it matters. Add only the causal distinctions needed for the next judgment, bind strong claims to exact evidence, and state what the result does not prove.
Follow a research question
For readers already following one research line, these groups connect the current question to its complete published arguments.
Answered on the EX3–EX7 Agent-facing surfaces. All treatments reached the same exact-action ceiling across 1,326 accepted decisions; richer representations added token burden, so the preregistered smallest-non-inferior rule selected compact prose.
Testing at a later boundary than the original QB experiments. Finance now preserves real FinancialResources independently of current risky positions, aggregates component portfolio state with explicit FX/temporal evidence, binds owner-managed capital through replayable CapitalState/Exposure context, and blocks both stale state-changing Decisions and unsupported owner-contribution shortcuts. Context v21 routes only work pulled by current Finance consumers into authoritative obligations while external financial submission remains independently fail-closed.
Answered within Round 1. Strong baselines reduced the proposed core; later Host and Harness extraction clarified the surviving ownership split without adding a universal Agent platform.
Reframed after GX1 and the later Game direction work. GX1 showed materially different reachable futures and separated strategy existence from model realization; the model still failed the frozen Core-carrier continuation while a deterministic continuous-carrier policy could succeed, and a generic structured primaryObjective prototype was deleted after presentation-order sensitivity. Those results remain valid research pressure, but the programme no longer assumes that proving an Agent-native mechanic selects the next game.
Answered for the current HP0–HP8 boundary. Current retrieval improved 7/9→9/9 after historical contraction, research-only ForeignEgress/EffectPath machinery was deleted, and the same 96 mixed-failure invocations passed after deletion.
Answered for the current pre-1.0 product boundary. Harness is now an independent, Host-free, caller-neutral durable cognitive execution substrate with its own Journal/CAS and supported HarnessAgentRun path. Real consumer pressure retained exact Run/turn capability separation, WorkingSet/WorkingView versus canonical history, Provider/Tool UNKNOWN recovery, structured completion as proposal rather than domain truth, and bounded capability composition; other candidate machinery such as a universal planner, generic Memory/RAG, Provider-continuation core, capability registry, and automatic knowledge/promotion services was deleted or kept local. The latest research tournament reports no next branch selected: remaining semantic frontiers are blocked on new consumers, owner transitions, or implementation diversity rather than an unresolved proof that Harness has any reusable boundary at all.
Testing with a stronger real-domain non-action case. Finance QB6 let one Agent request exact read-only evidence rather than infer missing execution facts, then update from more_research to no_op when the current minimum contract exceeded both the frozen 10% target and existing 25% canary bound; the branch ended before simulation, Decision, Proposal, or financial write.
Answered for the current P0–P5, HP0, and C1–C10 evidence horizon. Storage pressure produced an owner/retention correction rather than a generic cleanup service, and later operational-realization pressure kept currentness, retry, evidence scope, identity, authority, retention, and reclamation separable without reopening Runtime Foundations.
Open, but trigger-gated rather than under active expansion. Structured Patch and a small set of Runtime-owned lifecycle operations earned dedicated contracts; the later C1–C10 operational-realization programme did not produce a generic Effect layer, external-consequence authority, cleanup service, or semantic-completion primitive.
Answered by H1–H5 and later extraction. The durable Run boundary survived Codex and Hermes replacement; a universal Provider lifecycle did not.
Testing with a direct 2026-08-22 public-currentness audit. Source-bound Game, Harness, and Security projections exposed exact owner review obligations and were refreshed without copying their implementation databases; their current review set is now empty. Manual project judgments for Host, Runtime, World, Finance, Computing, Human, and Media required editorial re-adjudication, and fast-moving Finance drifted again within the same audit because it lacks the public-authority contract used by the source-bound owners. The audit also caught two different downstream currentness failures: a stale static `out/` artifact and smoke tests that still asserted superseded public wording. Home, Now, System, Research, and Writing were then refreshed while dirty/uncommitted owner state was deliberately excluded.
Reframed by the 0.3 contraction. The original ‘broader Goal completion’ target was too broad: Host deliberately removed shared Goal coordination, caller-neutral foreign execution, Runtime integration residue, generic capability policy, and legacy execution workloads. Current 0.4.x preserves the semantic work claim and revalidation hints while cognition, execution, source currentness, external occurrence, and domain completion remain owner-native.
Answered for the current evidence horizon. Security EC1 separated byte identity from semantic applicability; World independently separates historical occurrence from current relation/Presence; Web source-bound publication distinguishes exact owner revision from current editorial judgment and exposed stale static/test consumers; Finance further showed that an already coherent state-changing Decision loses Proposal authority when its PortfolioSnapshot baseline is no longer current. Computing Knowledge now records both HistoricalValidity != Currentness and AdmissionCurrentness != CommitmentCurrentness. These cases support owner-native revalidation and have not forced a generic Freshness, impact-graph, or automatic rebase service.
Answered for the HD0–HD9 programme. The frozen 1760–2026 campaign closed with 320 trajectories and 96 Deep Anchors across eight chronological waves. Cross-era recurrence survived only as a typed seven-family structural map plus explicit demotions, merges, replay negatives, and measurement/currentness results; the evidence did not justify ten universal success invariants or eight universal innovation laws.
Answered for P11. Six unordered datasets collapsed 720 raw permutation digests to one stable identity, but after invalidating a truncated Tool-wire campaign and clarifying an ambiguous evaluator target, raw presentation scored 44/48 strict versus 42/48 stable list and 43/48 identity map. No semantic normalization advantage survived.
Testing after R4–R6. Rich perception earned medium-local equipment, grounding proved more stable than fine labels, and R6 showed a 5,000-candidate zero-effect search could manufacture an impressive winner that failed stronger evidence. One reveal-order effect replicated directionally on pristine content for one Agent-observer class.
Answered for the current repository. Two capability families remain; the shared semantic authority is rejected and archived.
Answered for the current Quant Bedrock default-context claim. Constitution-only looked less bad than control on QB3b but remained negative; the unchanged treatment became materially worse than control on the second sealed QB3c carrier and used about 27.5% more Provider tokens. Mandatory injection has not earned default status.
Open under the CA7 negative admission gate; no positive transfer standing exists. Earlier Round 1 evidence was mixed and did not establish causal held-out advantage, while CA6 handled deliberate Blue policy change using current consequences and replanning without a stored opponent hypothesis. CA7 therefore leaves persistent OpponentModel NOT ADMITTED and records opponent-history gain as one explicit reopen condition.
Testing under a contracted theory. External prior art falsifies the claim that action/interface expansion is absent, but it also weakens any absolute transcendence claim: callable, representational, affordance, and executor expansions can be new relative to one closure while remaining compositional inside a deeper supplied substrate. No universal basis hierarchy or generic basis-escape object is admitted.
Answered for the CA0–CA7 capability programme. CA6 showed a fixed script fail three of four held-out worlds while both a generic observation-driven deterministic adaptive policy and the canonical Harness/model Actor succeeded all four with the same oracle-regret vector; P1 reproduced the core adaptive-selection result under real provider/authority friction. The model did not establish a stronger residual than the thin adaptive policy. CA7 therefore closed by contraction: Campaign, Organization, persistent OpponentModel, coevolution, provider gateway, and cross-fidelity strategic law are not admitted by current evidence.
Answered within Harness X2. A live Gemini falsifier returned 200 with the exact continuation and 400 INVALID_ARGUMENT when only the signature was stripped. A 940-byte continuation then survived crash/reopen, remained hidden from Agent messages, completed LIVE_CONTINUATION_OK, and caused zero Runtime redispatch. ProviderToolContinuation was the only new primitive earned across five pressured frontiers.
Reframed and answered at the responsibility level. Game, Finance, Security, World, Web, Host, Harness, and Runtime now provide materially different consumers and deletion tests. The recurring result is not a universal Host→Harness→Runtime stack: Computing's canonical Core explicitly treats subsystem names as non-invariants and retains only responsibilities that remain unowned after mature mechanisms and owner-native composition. Cross-domain pressure has repeatedly localized, deleted, or kept different packages while preserving a smaller set of ownership/identity/currentness/recovery distinctions.
Complete archive
Filter the complete record by document type. Later arguments may revise the working model without silently rewriting earlier claims.
Research note · Ordivon Mediacurrent
Research report · Ordivon Financecurrent
Research report · Ordivon Studio / Webcurrent
Research report · Ordivon Financecurrent
Research synthesis · Ordivon Computingcurrent
Research report · Ordivon Financecurrent
Research report · Ordivon Gamecurrent
Architecture guide · Ordivon Runtime / Worldcurrent
Research report · Ordivon Financecurrent
Research report · Ordivon Computing / Securitycurrent
Research report · Ordivon Harnesscurrent
Research report · Ordivon Computingcurrent
Research report · Ordivon Computingcurrent
Research report · Ordivon Harnesscurrent
Engineering record · Ordivon Runtimecurrent
Research report · Ordivon Computingcurrent
Engineering report · Ordivon Worldcurrent
Research note · Ordivon Gamecurrent
Research essay · Ordivon Computingcurrent
Architecture guide · Ordivon Computingrevised
Engineering report · Ordivon Host / Gamecurrent
Engineering report · Ordivon Gamecurrent
Research report · Ordivon Computingcurrent
Release note · Ordivon Gamehistorical
Engineering report · Ordivon Host / Gamecurrent
Research note · Ordivon Computingcurrent
Research note · Ordivon Runtime / Worldcurrent
Research report · Ordivon Hostcurrent
Architecture decision · Ordivon Hosthistorical
Research report · Ordivon Securitycurrent
Research essay · Ordivon Computingcurrent
Architecture report · Ordivon Hostcurrent
Architecture report · Ordivon Worldhistorical
Engineering report · Ordivon Runtimehistorical
Release · Ordivon Runtimehistorical
Design argument · Ordivonrevised