<?xml version="1.0" encoding="UTF-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title>Ordivon Writing</title><id>https://ordivon.com/writing</id><link rel="alternate" href="https://ordivon.com/writing"/><link rel="self" href="https://ordivon.com/feed.xml"/><updated>2026-07-31T12:00:00Z</updated><subtitle>Essays, experiments, architecture decisions, and release reports about durable AI agent work.</subtitle><entry><title>Communication Is Gameplay State</title><id>https://ordivon.com/writing/communication-is-gameplay-state</id><link rel="alternate" href="https://ordivon.com/writing/communication-is-gameplay-state"/><published>2026-07-31T12:00:00Z</published><updated>2026-07-31T12:00:00Z</updated><summary>Why agent communication needs identity, reachability, delivery state, and World-conditioned timing rather than decorative chat logs or a shared transcript.</summary><category term="Research note"/><category term="current"/><category term="E3"/><link rel="related" href="https://github.com/zycxfyh/ordivon-game/blob/7b44504da7a3467d65d6260d7cbc479b0fc971a8/docs/M3-RECEIPT.md" title="Canonical research record"/></entry><entry><title>Creation, Judgment, and Recoverable Systems</title><id>https://ordivon.com/writing/creation-judgment-recoverable-systems</id><link rel="alternate" href="https://ordivon.com/writing/creation-judgment-recoverable-systems"/><published>2026-07-31T12:00:00Z</published><updated>2026-07-31T12:00:00Z</updated><summary>The canonical public statement of Ordivon's project intent: creation, capability externalization, judgment, changing implementation costs, low governance, high recoverability, and participant freedom.</summary><category term="Research essay"/><category term="current"/><category term="E1"/><link rel="related" href="https://github.com/zycxfyh/ordivon-computing/blob/0117c051746483412befd6b702a403b5808d69a6/core/intent.md" title="Canonical research record"/></entry><entry><title>From Tokens to Work: The Complete Agent Execution Stack</title><id>https://ordivon.com/writing/from-tokens-to-work</id><link rel="alternate" href="https://ordivon.com/writing/from-tokens-to-work"/><published>2026-07-31T12:00:00Z</published><updated>2026-07-31T12:00:00Z</updated><summary>A first-principles walkthrough from token generation to tool execution, verification, TaskOutcome, and graph advancement, compared with OpenAI, Anthropic, Microsoft, Google, and Ordivon's tested boundaries.</summary><category term="Architecture guide"/><category term="current"/><category term="E3"/><link rel="related" href="https://github.com/zycxfyh/ordivon-computing/tree/c8ad154329a67344e772119ae3288eafce9fe62f/studies/2026-model-to-work-and-ordivon-harness" title="Canonical research record"/></entry><entry><title>One Authority, Thirteen Tables Deleted</title><id>https://ordivon.com/writing/one-authority-thirteen-tables</id><link rel="alternate" href="https://ordivon.com/writing/one-authority-thirteen-tables"/><published>2026-07-31T12:00:00Z</published><updated>2026-07-31T12:00:00Z</updated><summary>Why Ordivon Game reused the Host contract without forcing every workload through one Python process, and how unique semantic authority enabled a net deletion of 641 implementation and test lines.</summary><category term="Engineering report"/><category term="current"/><category term="E4"/><link rel="related" href="https://github.com/zycxfyh/ordivon-game/blob/7b44504da7a3467d65d6260d7cbc479b0fc971a8/docs/HOST-AUTHORITY-CUTOVER-P3-P6.md" title="Canonical research record"/></entry><entry><title>Replay Without a Second Truth Store</title><id>https://ordivon.com/writing/replay-without-second-truth-store</id><link rel="alternate" href="https://ordivon.com/writing/replay-without-second-truth-store"/><published>2026-07-31T12:00:00Z</published><updated>2026-07-31T12:00:00Z</updated><summary>How replay and evidence-linked diagnosis can remain pure deterministic projections of World, Host, Team, authority, Message, Provider, Effect, Observation, and verification records.</summary><category term="Engineering report"/><category term="current"/><category term="E4"/><link rel="related" href="https://github.com/zycxfyh/ordivon-game/releases/download/v0.1.0-alpha.1/M5-RECEIPT.md" title="Canonical research record"/></entry><entry><title>The Smaller Core That Survived Strong Baselines</title><id>https://ordivon.com/writing/smaller-core-strong-baselines</id><link rel="alternate" href="https://ordivon.com/writing/smaller-core-strong-baselines"/><published>2026-07-31T12:00:00Z</published><updated>2026-07-31T12:00:00Z</updated><summary>How Core Work System Round 1 used strong classical baselines and live Codex/Hermes replacement to remove a Task Runtime, reject a generalized Context Kernel, shrink Effect, localize DecisionRequest, and retain provider-neutral Task state.</summary><category term="Research report"/><category term="current"/><category term="E4"/><link rel="related" href="https://github.com/zycxfyh/ordivon-computing/blob/0117c051746483412befd6b702a403b5808d69a6/research/experiments/core-work-system-v1/REPORT.md" title="Canonical research record"/></entry><entry><title>Station Zero v0.1.0-alpha.1 — The First Source-Playable Release</title><id>https://ordivon.com/writing/station-zero-alpha-1</id><link rel="alternate" href="https://ordivon.com/writing/station-zero-alpha-1"/><published>2026-07-31T12:00:00Z</published><updated>2026-07-31T12:00:00Z</updated><summary>What shipped in Station Zero v0.1.0-alpha.1, how the release journey is verified, what one coordination-only comparison proves, and which agent-native game claims remain open.</summary><category term="Release note"/><category term="historical"/><category term="E4"/><link rel="related" href="https://github.com/zycxfyh/ordivon-game/releases/tag/v0.1.0-alpha.1" title="Canonical research record"/></entry><entry><title>A Thin Host Can Improve Strategy Without Becoming a Planner</title><id>https://ordivon.com/writing/thin-host-without-hidden-planner</id><link rel="alternate" href="https://ordivon.com/writing/thin-host-without-hidden-planner"/><published>2026-07-31T12:00:00Z</published><updated>2026-07-31T12:00:00Z</updated><summary>How Station Zero M2.1 improved Codex and Codex-to-Hermes strategy by compiling trustworthy decision semantics without forcing rank one, adding unrestricted memory, or introducing a hidden planner.</summary><category term="Engineering report"/><category term="current"/><category term="E4"/><link rel="related" href="https://github.com/zycxfyh/ordivon-game/blob/7b44504da7a3467d65d6260d7cbc479b0fc971a8/docs/M21-RECEIPT.md" title="Canonical research record"/></entry><entry><title>A Transcript Is Not a Task Database</title><id>https://ordivon.com/writing/transcript-not-task-database</id><link rel="alternate" href="https://ordivon.com/writing/transcript-not-task-database"/><published>2026-07-31T12:00:00Z</published><updated>2026-07-31T12:00:00Z</updated><summary>Why transcripts and summaries remain useful cognitive evidence but should not become the authoritative database of durable agent work.</summary><category term="Research note"/><category term="current"/><category term="E2"/><link rel="related" href="https://github.com/zycxfyh/ordivon-host" title="Canonical research record"/></entry><entry><title>UNKNOWN Is an Operational State, Not a Model Feeling</title><id>https://ordivon.com/writing/unknown-is-operational-state</id><link rel="alternate" href="https://ordivon.com/writing/unknown-is-operational-state"/><published>2026-07-31T12:00:00Z</published><updated>2026-07-31T12:00:00Z</updated><summary>Why unresolved external reality must be represented as system state rather than inferred from model confidence or collapsed into failure.</summary><category term="Research note"/><category term="current"/><category term="E2"/><link rel="related" href="https://github.com/zycxfyh/ordivon-world" title="Canonical research record"/></entry><entry><title>What Survived When Codex and Hermes Replaced Each Other Mid-Task</title><id>https://ordivon.com/writing/what-h1-h5-proved</id><link rel="alternate" href="https://ordivon.com/writing/what-h1-h5-proved"/><published>2026-07-31T12:00:00Z</published><updated>2026-07-31T12:00:00Z</updated><summary>How one task remained coherent through Codex→Hermes and Hermes→Codex replacement, three injected faults, and materially different provider lifecycles.</summary><category term="Research report"/><category term="current"/><category term="E4"/><link rel="related" href="https://github.com/zycxfyh/ordivon-host/blob/4ac03b52322cb76ade8f2902ab5b08113141c3e7/evidence/harness-replacement-h5-live-76420e4-20260731.json" title="Canonical research record"/></entry><entry><title>Why Ordivon Needs a Harness—but Not a Universal Harness</title><id>https://ordivon.com/writing/why-ordivon-needs-a-harness</id><link rel="alternate" href="https://ordivon.com/writing/why-ordivon-needs-a-harness"/><published>2026-07-31T12:00:00Z</published><updated>2026-07-31T12:00:00Z</updated><summary>Why H5 correctly rejected a common Codex/Hermes lifecycle while a separate Ordivon Harness remains strategically necessary for bare model APIs, local inference, and controlled agent-loop research.</summary><category term="Architecture decision"/><category term="current"/><category term="E4"/><link rel="related" href="https://github.com/zycxfyh/ordivon-host/blob/4ac03b52322cb76ade8f2902ab5b08113141c3e7/docs/harness-boundary-h5-decision.md" title="Canonical research record"/></entry><entry><title>Winning the Move Can Lose the Contest</title><id>https://ordivon.com/writing/winning-move-loses-contest</id><link rel="alternate" href="https://ordivon.com/writing/winning-move-loses-contest"/><published>2026-07-31T12:00:00Z</published><updated>2026-07-31T12:00:00Z</updated><summary>How Ordivon Security Round 1 used local dynamic opponents, CAGE Challenge 4, and bounded Hermes/Codex diagnostics to separate tactical success from strategic outcome without promoting a Campaign engine, organization ontology, strategic state, or custom cyber range.</summary><category term="Research report"/><category term="current"/><category term="E3"/><link rel="related" href="https://github.com/zycxfyh/ordivon-security/blob/8422165e83cc660e8190b07e78c472c7bff0fe59/docs/round1-full-experimental-report.md" title="Canonical research record"/></entry><entry><title>The Future Will Not Wait</title><id>https://ordivon.com/writing/the-future-will-not-wait</id><link rel="alternate" href="https://ordivon.com/writing/the-future-will-not-wait"/><published>2026-07-29T12:00:00Z</published><updated>2026-07-29T12:00:00Z</updated><summary>A historical and systems argument for accelerating AI, robotics, science, verification, resilience, access, and cooperation instead of centering civilization on a global frontier slowdown.</summary><category term="Research essay"/><category term="current"/><category term="E1"/><link rel="related" href="https://github.com/zycxfyh/ordivon-computing/tree/c97bc4b17527f8145cdc75eac8763ab6ea8a2813/studies/2026-adaptive-acceleration" title="Canonical research record"/></entry><entry><title>Why Task Continuity Belongs Above Execution</title><id>https://ordivon.com/writing/host-task-continuity</id><link rel="alternate" href="https://ordivon.com/writing/host-task-continuity"/><published>2026-07-28T12:00:00Z</published><updated>2026-07-28T12:00:00Z</updated><summary>Why durable task continuity belongs in Ordivon Host above replaceable model sessions and Ordivon Runtime process execution.</summary><category term="Architecture report"/><category term="current"/><category term="E4"/><link rel="related" href="https://github.com/zycxfyh/ordivon-host/blob/b4bc43a4ea7eb1e7771644d507bc4a3a39b4e741/ARCHITECTURE.md" title="Canonical research record"/></entry><entry><title>Why Link and Edge Became One Ordivon World Boundary</title><id>https://ordivon.com/writing/link-edge-boundary</id><link rel="alternate" href="https://ordivon.com/writing/link-edge-boundary"/><published>2026-07-28T12:00:00Z</published><updated>2026-07-30T12:00:00Z</updated><summary>Why Ordivon first separated connectivity and external execution, then unified both prototypes around one complete Task-to-World Interaction.</summary><category term="Architecture report"/><category term="current"/><category term="E2"/><link rel="related" href="https://github.com/zycxfyh/ordivon-world" title="Canonical research record"/></entry><entry><title>How Ordivon Runtime Grew Beyond Its Ten-Tool Core</title><id>https://ordivon.com/writing/runtime-after-core</id><link rel="alternate" href="https://ordivon.com/writing/runtime-after-core"/><published>2026-07-28T12:00:00Z</published><updated>2026-07-28T12:00:00Z</updated><summary>How a production-tested ten-tool runtime became a thirteen-tool execution and recovery system without absorbing task meaning or external-world semantics.</summary><category term="Engineering report"/><category term="current"/><category term="E4"/><link rel="related" href="https://github.com/zycxfyh/ordivon-runtime/blob/d13be899329c5564643abb10a701a55ad8c39153/docs/effect-kernel.md" title="Canonical research record"/></entry><entry><title>Ordivon Runtime: From Governance Platform to Durable Execution</title><id>https://ordivon.com/writing/ordivon-runtime-release</id><link rel="alternate" href="https://ordivon.com/writing/ordivon-runtime-release"/><published>2026-07-23T12:00:00Z</published><updated>2026-07-23T12:00:00Z</updated><summary>Ordivon Runtime closes its M0–M7 core with ten production-tested tools for durable agent execution, observation, cancellation, artifacts, and recovery.</summary><category term="Release"/><category term="historical"/><category term="E4"/><link rel="related" href="https://github.com/zycxfyh/ordivon-runtime/blob/d13be899329c5564643abb10a701a55ad8c39153/docs/runtime.md" title="Canonical research record"/></entry><entry><title>AI Agents Need More Than a Good Conversation</title><id>https://ordivon.com/writing/why-ordivon</id><link rel="alternate" href="https://ordivon.com/writing/why-ordivon"/><published>2026-07-23T12:00:00Z</published><updated>2026-07-23T12:00:00Z</updated><summary>Why capable AI agents need durable task and execution truth when work crosses into repositories, processes, credentials, machines, and consequential decisions.</summary><category term="Design argument"/><category term="current"/><category term="E1"/><link rel="related" href="https://github.com/zycxfyh/Ordivon" title="Canonical research record"/></entry></feed>