ORDIVON
Menu
Question dossierOrdivon Computinganswered

What is the smallest explanation that preserves the causal boundaries an Agent needs?

Compare compact owner-native causal prose with richer cards, relation vocabularies, and explicit diagnostic grammars before promoting another mandatory representation.

All research questionsOpen project

01 / Current position

A hypothesis is not the current judgment.

The dossier preserves the live research position. Dated articles preserve the complete evidence and argument that changed it.

Working hypothesis

Compact causal prose is sufficient for ordinary Agent decisions when it states the relevant proof owner, semantic owner, consequence/currentness boundary, and material non-implications.

Current judgment

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.

02 / Decision boundary

What keeps this Question alive?

Why it matters

A research system can become harder to use when every useful distinction is serialized into default context, even when the richer representation adds no decision value.

Next admitted test

Reopen only after a consequential failure under strong compact prose, or begin a separate human-comprehension program with human evidence rather than Agent proxies.

Condition for deletion

A harder open-ended or materially different decision surface repeatedly fails under compact causal prose while a frozen richer representation succeeds without introducing a new authority ambiguity.

03 / Supporting publications

Complete arguments connected to this Question.

6 dated publications currently document this research line.

Research synthesis

History Did Not Prove Us Right

The first five epochs of Ordivon's historical world-model dogfood: 200 source-locked trajectories, 60 deep anchors, anti-confirmation coding, historical replay, repeated theory narrowing, and why recurring structure is not the same as proof that our labels are correct.

12 August 2026 ↗Research report

The Patterns Recurred. Our Taxonomy Got Worse.

What HD6 1970–1999 taught Ordivon about historical recurrence, classifier instability, scaffold bias, and why six epochs without a contradiction still did not earn a universal law.

12 August 2026 ↗Research report

The Shorter Explanation Won

How EX3–EX7 tested five ways of explaining Ordivon responsibility boundaries and selected compact owner-native causal prose as the smallest non-inferior representation.

12 August 2026 ↗Research report

We Sorted the Evidence. Accuracy Got Worse.

Computing P11 separated deterministic representation from semantic tractability, invalidated two confounded campaigns, and rejected active evidence-order normalization after a cleaner oracle made the raw baseline win.

12 August 2026 ↗Architecture guide

From Tokens to Work: Five Questions an Agent System Must Answer

A Feynman-style guide to Ordivon's current work trajectory: domain meaning, one Agent Run, physical execution, durable responsibility, external consequence, and current revalidation.

12 August 2026 ↗Design argument

Why Ordivon Exists

A first-principles explanation of Ordivon: why model intelligence, durable work responsibility, physical execution, external reality, domain meaning, research, and public expression need different owners.

12 August 2026 ↗

04 / Source discipline

The dossier is an index, not the evidence authority.

Question metadata

Owns the current judgment, next test, and deletion condition.

Publications

Own complete dated arguments, limitations, comparisons, and source links.

Repositories

Own exact code, tests, releases, receipts, and machine evidence.

Related frontier

testing

When should a finite intelligence expand its interface to Reality instead of only reasoning harder?

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.

testing

When should an Agent act, wait, observe, refuse, reconcile, or request a decision?

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.

open

Which Task Runtime objects are required by asynchronous waiting and Join semantics?

Open. Round 1 showed that mature workflow engines can carry durable work mechanics, but no interrupted fan-out and fan-in workload has yet proved which semantic Join facts must remain visible above those mechanics.

reframed

Which responsibilities survive materially different workloads without becoming one mandatory stack?

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.

answered

Which Agent-native responsibilities remain after strong classical baselines?

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.

answered

When does valid evidence stop being current enough to govern a decision?

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

Does canonical evidence order make an Agent understand the evidence better?

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.

answered

Which Agent-era world-model laws survive historical out-of-distribution pressure?

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.