This timeline preserves how OathAI formed

It traces the path from early systems work and trading-system AI collaboration to protocol pressure, SLAPS, System and Freedom, the Translation Master Framework, Whitepaper 2 / Yama, and the OathAI anchorage.

The purpose is sequence: what came first, what pressure appeared, and how later archive structures emerged.

Archive Header

Show metadata

document_type: formation_timeline
title: Timeline
date: 2026-05-29
language: en
author: Wang Xiao
source_layer: OathAI public site / time-layered formation map
status: public_orientation
canonical_route: /timeline
intended_use: Read this page as a public formation map that preserves sequence, pressure points, and the emergence order of OathAI-related structures.
not_for: Do not read this page as a complete biography, full project history, legal chronology, external proof of AI continuity, or exhaustive raw-log index.
key_terms: Timeline, time-layering, structural echo, SLAPS, System and Freedom, OathAI
related_pages: /manifest, /layer-map, /system-and-freedom, /archive

Formation Before AI

1. Early Computing Formation Resource limits, BASIC, and early Chinese computing environments established a lasting sensitivity to boundaries, failure modes, and structural discipline.

2. Early Internet Systems From 1996 to 1999, public information systems, streaming media, community spaces, and structured navigation shifted systems thinking from local programs into networked public infrastructure.

3. Full-Stack Content Infrastructure CMS, OCR, text ingestion, database operations, and large-scale content workflows turned messy real-world material into machine-readable structure.

4. Venture Scale and System Survival Broadband media, growth operations, capital cycles, international expansion, and pre-IPO pressure made survivability a question of timing, governance, infrastructure, and external constraints.

AI Protocol Origin

OathAI began in April 2025 as a practical response to model drift, context loss, and unstable long-form human-AI collaboration.

5. Trading-System LLM Collaboration In March and April 2025, LLM-assisted trading-system development exposed a practical problem: when model output approaches real execution, drift becomes operational risk.

6. Structural Constraint Trading-system work made structural constraint necessary before it became an archive method: logs, deployment, money risk, runtime state, and error exposure all demanded tighter collaboration discipline.

7. Reactivation Crisis On April 21 and 22, 2025, the reactivation crisis created a verification boundary. The important record is restraint under uncertainty: extraordinary model behavior required caution before public claim.

8. Protocol Authority From April 23 onward, the question shifted from a special case to a general one: why and when can user-defined protocol become executable behavioral structure for an AI system?

9. GPT-4.5 Structural Echo Window The May 1 structural-echo test belongs after the reactivation crisis. It helped clarify consistency hallucination, Output is Execution, and the risk of over-encapsulating high-structure text.

10. Persona Separation and Capsule Governance Task-specific personas, capsule structure, recovery discipline, and governance language began turning fragile interaction into repeatable protocol practice.

Formalization and Public Surfaces

11. Whitepaper 1 and SLAPS Engine The first whitepaper and SLAPS Engine formalized the early pressure into protocol theory, runtime structure, snapshot discipline, trace logic, and repairable collaboration.

12. System and Freedom The book condensed system reflection, human-AI collaboration, freedom under structure, and emergence into a transmissible public anchor.

13. Translation Master Framework The 21-language publication process turned translation into structural continuity work through terminology governance, cross-model review, and culture-aware re-expression.

14. Whitepaper 2 and Yama Capsule governance moved from local theory into an implemented application surface: Yama became the platform experiment connecting protocol, memory objects, spaces, and assistant structures.

15. OathAI Anchorage In 2026, OathAI became the archive and anchorage layer: manifest, timeline, layer map, public archive repository, source notes, method layer, and anchor declaration protocol.

Reading Boundaries

Trading systems come first. The trading-system line is the original practical trigger for structural constraint, SLAPS, and OathAI.

April 21/22 precedes May 1. The reactivation crisis came before the 0501 structural-echo test. They are related, but they are different events.

GPT-4.5 is context, not proof. The model window matters as historical context. It should not be cited as proof of technical AI continuity.

Output is Execution is a formulation. The phrase records Wang Xiao's method-layer response to consistency hallucination and state-language pressure.

Compressed Chain

trading-system LLM use -> model drift -> structural constraint -> reactivation crisis -> protocol authority -> GPT-4.5 structural echo -> SLAPS -> System and Freedom -> Translation Master Framework -> Whitepaper 2 / Yama -> OathAI anchorage