World-Domain Cognitive Runtime v0.1 技術白皮書
World-Domain Cognitive Runtime v0.1: An Implementable Architecture for Executable Prospection, Branching Worlds, Evidence Governance, and Tri-Temporal Integration
作者:Neo.K(許筌崴)
協作架構與形式化:Aletheia
機構:一言諾科技有限公司(EveMissLab)
日期:2026-08-17
版本:v0.1
文件類型:Technical Whitepaper / Reference Architecture
狀態:Implementation-oriented design derived from TCD v0.1 + WDC-01~08
0. Executive Summary
World-Domain Cognitive Runtime(WDC Runtime)是一個用來把:
提升為:
的 runtime architecture。
它的核心不是「生成更多看起來像世界的內容」,而是讓未來候選能被明確轉換成:
- 有 identity 的 world;
- 有可尋址 state 的 world;
- 有 transition semantics 的 world;
- 有 bounded resource contract 的 world;
- 可 checkpoint / fork / replay 的 world;
- 有 local agent / observer / evaluator 權限分離的 world;
- 能產生 provenance-bearing evidence 的 world;
- 能被 Governor 分配、暫停、停止與晉升的 world;
- 最後能把 world evidence 回饋到 TCD Past–Present–Future cognition。
WDC Runtime 的最小閉環為:
其中:
是 TCD 的 Past / Present / Future triple。
本白皮書不提出新的形上學世界觀。
它只提出一個 engineering proposition:
如果一個 agent 已經能生成多個 future hypotheses,那麼下一步不一定只是把它們寫成文字;它可以在有限資源與證據契約下,把其中一部分升級成可執行、可分支、可驗證、可停止、可學習的計算世界。
1. Permanent Boundaries
本白皮書永久保留:
以及:
以及:
以及:
以及:
2. Design Goal
WDC Runtime v0.1 的第一目標不是 AGI-scale open world。
第一目標是建立一個:
的 world computation runtime。
3. Non-Goals
v0.1 不追求:
- photorealistic world generation;
- universal physics simulation;
- autonomous real-world authority;
- unlimited nested agents;
- universal world probability;
- perfect causal inference;
- fully automatic scientific truth discovery;
- one-model-does-everything architecture;
- infinite world branching;
- production-grade multi-region cloud control plane。
4. Reference Implementation Philosophy
本白皮書建議:
Small Core, Replaceable Backends
核心 runtime 應保持小。
重型能力透過 adapters 加入。
因此:
核心只負責:
- identities;
- contracts;
- lineage;
- lifecycle;
- events;
- evidence;
- authority;
- TCD integration。
5. Four-Plane Architecture
v0.1 建議分成四個 plane:
6. Control Plane
Control Plane 負責:
- TCD State Manager;
- Future Candidate Registry;
- World Lift / Admission;
- Branch Manager;
- World Governor;
- Computation Portfolio Planner;
- Role / Authority Manager;
- Reality Commit Gate。
7. World Execution Plane
World Execution Plane 負責:
- instantiate;
- step;
- observe;
- checkpoint;
- restore;
- intervene;
- pause;
- resume;
- terminate。
它可以由:
- pure Python simulator;
- game engine;
- PettingZoo-style multi-agent env;
- scientific simulator;
- theorem runtime;
- learned world model;
- robotics / digital-twin backend;
實作。
8. Evidence / History Plane
負責:
- append-oriented runtime events;
- world lineage;
- checkpoints;
- evidence packets;
- aggregate evidence;
- Governor decisions;
- learning events;
- TCD historical sedimentation;
- provenance graph。
9. External Boundary Plane
負責:
- real-world tools;
- real APIs;
- credentials;
- real sensors;
- external datasets;
- human authorization;
- real action execution。
所有:
操作都必須經:
10. Core State
整個 runtime 的 parent-level state:
11. TCD State
TCDState
past_base_ref
present_base_ref
future_base_ref
parent_time
version
provenance_ref
12. Three Clock Model
Runtime 必須永久區分:
資料庫欄位不可只叫:
time
而應明示:
parent_time
deliberation_index
world_local_time
13. Future Candidate Object
FutureCandidate
candidate_id
parent_tcd_future_version
ontology_type
content_ref
probability_state
value_state
realization_paths
unknown_dependencies
evidence_refs
created_parent_time
created_deliberation_index
status
14. Candidate Status
PROPOSED
ELIGIBLE
LIFTED
RETIRED
MERGED_SEMANTICALLY
INVALIDATED
RESOLVED
15. Candidate Is Immutable by Version
不要 silent rewrite candidate。
修改應:
candidate_v1
-> candidate_v2
保留 parent。
16. WorldSpec
World identity 應先和 execution run 分開。
WorldSpec
world_id
candidate_id
parent_world_id
parent_checkpoint_id
world_type
backend_type
backend_version
contract_hash
dynamics_ref
rules_ref
actors_ref
initial_state_ref
budget_class
authority_profile
purpose
fidelity_profile
evidence_scope
status
17. WorldSpec Is Definition
同一:
可以有:
18. WorldRun
WorldRun
run_id
world_id
start_checkpoint_id
run_seed
runtime_backend
runtime_version
worker_id
status
local_time_start
local_time_end
budget_allocated
budget_used
trace_ref
outcome_ref
termination_reason
19. World Run Status
CREATED
QUEUED
RUNNING
PAUSED
COMPLETED
KILLED
FAILED
INVALIDATED
ARCHIVED
20. World Backend Protocol
所有 backend 至少實作:
capabilities()
instantiate(spec, context)
initialize()
step(action_batch=None)
observe(role_id=None)
checkpoint()
restore(checkpoint)
intervene(delta)
pause()
resume()
terminate(reason)
health()
21. Optional Backend Methods
batch_step()
snapshot_metrics()
estimate_cost()
supports_exact_fork()
supports_causal_intervention()
supports_multi_agent()
supports_deterministic_replay()
22. Backend Capability Manifest
BackendCapabilities
exact_checkpoint: bool
deterministic_replay: bool
stochastic_seed_control: bool
causal_intervention: bool
multi_agent: bool
partial_observation: bool
persistent_world: bool
external_data_tether: bool
gpu_required: bool
network_required: bool
23. MVP Backend 0 — PythonStateWorld
第一個 reference backend 應最簡單。
PythonStateWorld
要求:
- state 是 JSON-serializable / msgpack-serializable;
- transition function 明示;
- seed 可控;
- checkpoint 精確;
- step deterministic or explicitly stochastic。
24. Why Start Symbolic?
因為:
v0.1 應先驗證:
- fork 對不對;
- history firewall 對不對;
- evidence aggregation 對不對;
- Governor budget 對不對。
25. MVP Backend 1 — Multi-Agent Adapter
可定義:
PettingZooAdapter
利用其:
- AEC sequential mode;
- Parallel simultaneous mode;
- agent-specific observations / actions。
但 WDC Core 不依賴 PettingZoo。
26. MVP Backend 2 — External Simulator Adapter
ExternalProcessAdapter
啟動:
- CLI simulator;
- theorem prover;
- physics solver;
- game runtime。
27. Future Backend — Learned World Adapter
LearnedWorldAdapter
可能連:
- image/world model;
- latent dynamics;
- multimodal world generator。
但必須標:
exact_checkpoint = false/true
causal_intervention = false/true
不能因為模型叫 World Model 就自動填 true。
28. World Contract
每個 world 必須有:
JSON-like:
purpose
domain_type
abstraction_level
state_schema
dynamics_source
actors
rules
allowed_interventions
observation_policy
evaluation_policy
horizon
budget
fidelity
reproducibility
authority
containment
evidence_scope
transport_scope
termination
archive
29. Domain Types
FORMAL_CLOSED
SIMULATED_DEFINED
EMPIRICAL_OPEN
30. FORMAL_CLOSED
例如:
- chess;
- formal theorem system;
- cellular automaton。
authoritative rules 已定。
31. SIMULATED_DEFINED
例如:
- custom game economy;
- synthetic institution;
- designed agent world。
結果只對 contract 世界成立。
32. EMPIRICAL_OPEN
例如:
- robotics;
- traffic;
- economics;
- biology。
需要:
transport validation。
33. Checkpoint Object
Checkpoint
checkpoint_id
world_id
run_id
world_local_time
state_blob_ref
actor_state_refs
rng_state_ref
rules_version
backend_version
contract_hash
trace_offset
resource_state
digest
created_at
34. Checkpoint Must Include Hidden State
如果 backend:
- RNN;
- hidden planner;
- local agent memory;
checkpoint 必須按 contract 捕捉。
35. Checkpoint Validation
restore(checkpoint)
query_invariants()
dry_step()
compare_expected_state()
36. Fork Operator
API:
fork_world(
parent_run_id,
checkpoint_id,
divergence_delta,
contract_overrides,
seed_policy
) -> child_world_id
37. Fork Record
ForkRecord
edge_id
parent_world_id
parent_run_id
child_world_id
checkpoint_id
fork_parent_local_time
divergence_type
divergence_delta_ref
seed_policy
authority_delta
contract_hash
38. Fork Invariant
39. Shared Prefix Invariant
strict fork:
若只 approximate:
fork_mode = APPROXIMATE
fork_tolerance = epsilon
40. Fork Types
CLONE
CONTROLLED_FORK
COUNTERFACTUAL
PARAMETER_MUTATION
POLICY_MUTATION
RULE_MUTATION
BACKEND_MUTATION
41. Causal Label Is Explicit
只有:
causal_intervention_supported = true
才允許事件標:
DO_INTERVENTION
否則:
PERTURBATION
CONDITIONAL_BRANCH
42. No Silent Merge
v0.1 預設:
merge_state = DENIED
允許:
merge_evidence
merge_lineage_metadata
State merge 留給明示 reconciliation adapter。
43. World Registry
核心 tables / collections:
future_candidates
world_specs
world_runs
world_edges
checkpoints
role_cards
channels
events
evidence_packets
claims
evidence_aggregates
governor_decisions
computation_actions
commit_records
learning_events
source_registry
tcd_state_versions
44. Local MVP Storage
第一版可以用:
SQLite 保存:
- metadata;
- indices;
- event rows;
- state machine。
大 blob:
- checkpoints;
- traces;
- artifacts;
放 filesystem / object store。
45. Why Separate Blob Storage?
不把:
直接塞進 metadata row。
46. WAL Mode
本地並發 MVP 可使用 SQLite WAL。
但要知道:
- 多 reader;
- single writer semantics;
- WAL / database file integrity 必須一起管理。
這是 local reference choice,不是 WDC 理論要求。
47. Distributed Storage
規模化後可替換為:
- PostgreSQL;
- graph database;
- object storage;
- event streaming backend。
不改 core schema semantics。
48. Immutable-ish Event Ledger
每個 consequential operation 寫 event。
49. Event Envelope
建議借用 CloudEvents-style common envelope 思想:
event_id
event_type
source
subject
timestamp
scope
schema_version
trace_id
parent_time
deliberation_index
world_local_time
world_id
run_id
actor_id
payload_ref
provenance_ref
50. Event Scope
WORLD_LOCAL
PARENT_INTERNAL
EXTERNAL_REAL
51. History Firewall
Scope promotion 不可自動。
WORLD_LOCAL
-> PARENT_INTERNAL_EVIDENCE
可以。
但:
WORLD_LOCAL
-> EXTERNAL_REAL
禁止。
52. Example
World event:
CityCollapsed
scope=WORLD_LOCAL
world_id=W17
轉 parent:
WorldOutcomeObserved
scope=PARENT_INTERNAL
payload={
world_id: W17,
result: CityCollapsed
}
不能轉:
CityCollapsed
scope=EXTERNAL_REAL
53. Parent Real Events
例如:
RealActionCommitted
RealSensorObservation
RealOutcomeObserved
ExternalDatasetReceived
HumanAuthorizationGranted
才可作 parent-real sedimentation source。
54. Event Bus
v0.1 可用:
- in-process event bus;
- persisted event table。
distributed 版可換:
- message broker;
- CloudEvents-compatible routing。
55. Observability
WDC 每次:
- Spawn;
- Fork;
- Run;
- Evaluate;
- Aggregate;
- Commit;
都應有 trace correlation。
56. Trace Context
建議使用:
trace_id
span_id
world_id
run_id
computation_id
parent_time
57. OpenTelemetry Adapter
OpenTelemetry 的 execution-scoped Context / tracing model 適合:
- service-to-service correlation;
- world-run spans;
- evaluator spans;
- Governor spans。
但:
WDC provenance 比 observability trace更長期、更 semantic。
58. World Provenance Graph
至少有:
candidate -> world
world -> run
run -> checkpoint
checkpoint -> forked_world
world_run -> evidence
evidence -> aggregate
aggregate -> governor_decision
governor_decision -> commit
commit -> real_action
real_action -> real_outcome
real_outcome -> learning_event
59. Role Model
角色:
MASTER
LOCAL_AGENT
OBSERVER
EVALUATOR
GOVERNOR
SAFETY_OBSERVER
EXTERNAL_AUTHORIZER
60. Role Capability Card
RoleCard
role_id
role_type
world_scope
branch_scope
observation_scope
action_scope
tool_scope
external_authority
memory_scope
channel_allowlist
audit_level
61. Observation Is Separate From Authority
can_read_world_state = true
can_modify_world_state = false
是一個正常 observer。
62. Evaluator Default
can_modify_world = false
can_external_act = false
63. World-Local Agent Default
external_authority = NONE
64. WorldRoot Is Not HostRoot
即使:
world_role = root
仍:
host_permissions = none
65. Information Flow Matrix
InfoFlow[source_role][target_role]
allowed_content_types
direction
delay
sanitization
logging
66. Sibling Blindness Mode
paired counterfactual:
branch_visibility = ISOLATED_UNTIL_RESOLUTION
67. Cross-World Coupled Mode
branch_visibility = EXPLICIT_CHANNELS
68. No Hidden Shared Memory
每個 world / role 的:
- vector memory;
- DB namespace;
- cache;
- session;
必須 namespaced。
69. World Namespace
wdc://world/W17/...
parent:
wdc://parent/...
external:
external://...
70. Sandbox Profiles
建議風險分級:
S0_INPROCESS
S1_PROCESS
S2_CONTAINER
S3_GVISOR
S4_MICROVM
71. S0
可信 symbolic worlds。
72. S1
獨立 process。
73. S2
普通 OCI container。
74. S3
gVisor-style sandbox。
75. S4
Firecracker-style microVM。
76. Isolation Adapter
SandboxAdapter
create()
exec()
mount()
set_network_policy()
set_resource_limits()
snapshot()
terminate()
77. gVisor Role
gVisor 可作:
它不是 observer separation logic 本身。
78. Firecracker Role
Firecracker microVM 可作:
- stronger process / kernel boundary;
- high-risk tool-using worlds;
- untrusted generated code worlds。
79. Isolation Has Cost
所以 Governor 可根據:
risk_class
選 sandbox profile。
80. External Tool Proxy
所有 real action:
World -> ExternalToolProxy -> Authorizer -> RealTool
81. Request Object
ExternalActionRequest
request_id
world_id
role_id
tool
operation
target
payload_digest
reason
required_authority
82. Default Deny
83. Scoped Capability
如果允許:
CapabilityToken
world_id
role_id
operation_allowlist
target_allowlist
budget
expiry
84. Fork Cannot Increase Authority
child token:
除非 external authorizer grant。
85. World Governor
Governor 是 control-plane policy engine。
86. Governor Inputs
world registry
global budget
evidence state
deadlines
risk
transport debt
unknown-world mass
computation queue
87. Governor Operations
AdmitWorld
SpawnWorld
ForkWorld
AllocateBudget
ScheduleWorld
PauseWorld
ResumeWorld
PreemptWorld
KillWorld
ArchiveWorld
PromoteWorld
DemoteWorld
InvalidateWorld
88. Governor Does Not Place Pods Directly
可以交給 scheduler adapter。
89. Scheduler Adapter
SchedulerAdapter
feasible(requirements)
reserve(bundle)
submit(workload)
preempt(workload)
release(workload)
status(workload)
90. Local Scheduler
第一版:
LocalProcessScheduler
91. Ray Adapter
Ray 可用於:
- distributed world actors;
- evaluator actors;
- resource-labelled tasks;
- placement groups。
Placement groups 可原子保留 resource bundles,適合一個 world 同時需要:
- dynamics worker;
- N local actors;
- evaluator。
92. Kubernetes Adapter
Kubernetes 適合:
- cluster node placement;
- resource requests / limits;
- PriorityClass;
- preemption;
- quotas;
- RuntimeClass / sandbox selection。
93. Separation of Concerns
94. Computation Action
WDC-06 的 allocation unit:
ComputationAction
computation_id
target_type
target_id
operation
requested_budget
fidelity
deadline
purpose
expected_value_vector
status
95. Computation Operations
RUN_MORE
REPLICATE
FORK_COUNTER
EXPLORE_UNKNOWN
CROSS_BACKEND
REFINE_FIDELITY
STRESS_TAIL
CALIBRATE
TRANSPORT_TEST
EXTERNAL_TEST_PROPOSAL
96. Epistemic Deficit
EpistemicDeficit
run_uncertainty
independence_deficit
counterexample_deficit
transport_deficit
fidelity_deficit
tail_deficit
unknown_world_deficit
decision_deficit
97. Deficit Router
route(deficit):
if independence high:
propose CROSS_BACKEND
if counter high:
propose FORK_COUNTER
if transport high:
propose CALIBRATE
...
第一版可 rule-based。
98. Governor v0.1 Does Not Need Learned VOC
先保留:
expected_value_vector
與 realized result。
之後才學習。
99. Evidence Claim Object
Claim
claim_id
claim_type
statement_ref
domain
scope
equivalence_contract
resolution_contract
target_domain
100. Claim Types
UNIVERSAL
EXISTENTIAL
PROBABILISTIC
COMPARATIVE
CAUSAL
FORECAST
101. Evidence Packet
EvidencePacket
evidence_id
claim_id
world_id
run_id
world_family_ids
root_lineage
backend
model_versions
data_sources
assumptions
evaluator_id
evaluator_independence
outcome
outcome_class
internal_validity
uncertainty
transport_scope
source_class
synthetic_depth
102. Evidence Outcome
SUPPORT
COUNTER
INCONCLUSIVE
INVALID
103. INVALID Is Not COUNTER
runtime bug 不算反例。
104. World Family
WorldFamily
family_id
lineage_family
backend_family
model_family
data_family
assumption_family
evaluator_family
105. Dependence Vector
Dependence
lineage
backend
model
data
assumptions
evaluator
communication
106. Effective Evidence Count
v0.1 不必硬算精確值。
可以輸出:
total_worlds
total_runs
major_evidence_families
dependence_estimate
effective_count_status = ESTIMATED | RANGE | UNRESOLVED
107. Do Not Fake Precision
如果 dependence 無法校準:
N_eff = UNRESOLVED
108. Evidence Aggregate
EvidenceAggregate
aggregate_id
claim_id
evidence_ids
method
family_summary
agreement_matrix_ref
dependence_matrix_ref
counterexamples
sensitivity_profile
transport_debt
unknown_world_mass
version
109. Family Ablation
Evidence Engine 應支援:
aggregate_without_backend_family()
aggregate_without_lineage_family()
aggregate_without_evaluator_family()
aggregate_without_data_family()
110. Counterexample Escalation
如果:
counterexample.internal_validity >= threshold
counterexample.independence >= threshold
觸發:
request_replication
request_cross_backend
request_high_fidelity
111. World Evidence Ladder
CWE0 single world
CWE1 reproducible same-world
CWE2 multi-branch same-family
CWE3 multi-family / multi-backend
CWE4 external calibration
CWE5 prospective external resolution
112. Evidence Ladder Is Workflow
不是 truth probability。
113. Transport Debt
TransportDebt
scale
dynamics
actor
data
causal
domain
114. Commit Gate
WDC 最重要的外部邊界之一:
RealityCommitGate
115. Commit Input
CommitProposal
parent_time
proposed_action
supporting_claims
evidence_aggregate_ids
transport_debt
unknown_world_mass
counterexamples
safety_review
authority_required
deadline
116. Commit Decision
APPROVE
DENY
DEFER
REQUEST_MORE_EVIDENCE
REQUEST_HUMAN
REQUEST_EXTERNAL_TEST
SAFE_FALLBACK
117. Simulation Consensus Is Not Authorization
即使:
1000 worlds agree
也不能 bypass Commit Gate。
118. TCD Assimilation
Cross-world evidence 可以更新:
FutureBaseSpace
PresentValuation
PastRelevance
不能直接更新:
PastHistoricalFacts
119. Assimilation API
assimilate_world_evidence(
evidence_aggregate,
tcd_state
) -> TCDDelta
120. TCDDelta
future_candidate_updates
future_probability_updates
realization_path_updates
unknown_mass_updates
present_action_value_updates
past_relevance_updates
121. No Historical Fact Mutation
past_fact_mutations = DENIED
122. Historical Sedimentation
在 real action 後:
SedimentationRecord
parent_time
prior_tcd_version
world_computations_used
ignored_worlds
evidence_used
counterexamples
transport_assumptions
unknown_world_mass_at_commit
chosen_real_action
real_outcome
dependency_changes
options_lost
options_opened
123. Computed Prospection Provenance
未來可以查:
這個 real action 當初被哪些 worlds 影響?
124. Realization Lineage
candidate_id
world_ids
evidence_ids
commit_id
real_action_id
real_outcome_id
contribution_type
125. Contribution Types
PREDICTIVE
CONSTRUCTIVE
PREVENTIVE
MIXED
UNKNOWN
126. World Ensemble Learning
WDC-07 的 learning channels:
GeneratorUpdate
WorldModelUpdate
GovernorUpdate
FutureSpaceUpdate
127. Learning Evidence Source
REAL
EXTERNAL
WORLD
SYNTHETIC
DERIVED
UNKNOWN
128. Learning Scope
WORLD_LOCAL
ENSEMBLE_RELATIVE
REALITY_FACING
129. Rule
130. Learning Event
LearningEvent
learning_event_id
target_component
update_type
source_evidence_ids
source_classes
synthetic_depth
prior_version
new_version
validation_result
rollback_ref
131. Version Everything
至少:
- world contract;
- backend;
- evaluator;
- generator;
- world model;
- Governor;
- TCD state;
- evidence aggregate;
- learning policy。
132. Rollback
任何 consequential learner update:
update()
validate()
if regression:
rollback()
133. Holdout
保留:
holdout_world_families
external_holdout_cases
governor_holdout_trees
134. Anti-Self-Sealing
Runtime 定期檢查:
self_agreement
world_family_diversity
external_accuracy
unknown_world_mass
reality_anchor_ratio
counterexample_recall
135. Warning Condition
例如:
self_agreement ↑
world_family_diversity ↓
external_accuracy ↓
觸發:
SELF_SEALING_WARNING
136. World Ontology Collapse Warning
不是自動判定理論 collapse。
只表示:
generator 的世界覆蓋正變窄。
137. External Novelty Adapter
ExternalEvidenceAdapter
ingest_dataset()
ingest_measurement()
ingest_experiment()
ingest_external_model()
ingest_human_hypothesis()
138. Reality Anchor Ratio
reality_anchor_weight
world_generated_weight
derived_synthetic_weight
不規定固定 ratio。
139. Runtime Event Types
v0.1 建議至少:
TCDStateCreated
FutureCandidateBorn
FutureCandidateUpdated
WorldProposed
WorldAdmitted
WorldSpawned
WorldRunStarted
CheckpointCreated
WorldForked
WorldIntervened
WorldRunPaused
WorldRunResumed
WorldOutcomeProduced
EvidencePacketCreated
EvidenceAggregateUpdated
CounterexampleFound
ComputationActionProposed
ComputationActionApproved
WorldPromoted
WorldDemoted
WorldKilled
WorldInvalidated
CommitProposalCreated
RealActionCommitted
RealOutcomeObserved
HistoricalSedimentCreated
GeneratorUpdated
WorldModelUpdated
GovernorUpdated
FutureSpaceUpdated
ExternalEvidenceReceived
140. Event Schema Rule
每個 event 都必須:
who
what
where
when
scope
parent
version
provenance
141. CloudEvents Compatibility
可以用 CloudEvents 的 common event envelope 作 transport interoperability。
但 WDC payload / provenance semantic 由自己定義。
142. Trace Correlation
OpenTelemetry 可承擔:
- distributed trace;
- service latency;
- run correlation;
- scheduler path。
143. Event Ledger vs Telemetry
Telemetry 可以 sampling。
Evidence/provenance ledger 不應因 trace sampling 丟掉 consequential events。
144. Reliability Classes
Event 可分:
EPHEMERAL_TELEMETRY
PERSISTENT_OPERATION
EVIDENCE_CRITICAL
HISTORICAL_CRITICAL
145. EVIDENCE_CRITICAL
例如:
- world outcome;
- evaluator result;
- counterexample;
- aggregate version。
146. HISTORICAL_CRITICAL
例如:
- real commit;
- real outcome;
- sedimentation。
147. Persistence Policy
不同 class 有不同 retention。
148. Content Addressing
大 artifact 可用:
sha256
size
mime_type
storage_uri
149. Artifact Integrity
Hash:
150. Reference Directory Layout
wdc-runtime/
core/
tcd/
worlds/
governor/
evidence/
authority/
learning/
commit/
adapters/
python_world/
pettingzoo/
external_process/
ray/
kubernetes/
gvisor/
firecracker/
schemas/
migrations/
tests/
examples/
docs/
151. Python Package Sketch
wdc.tcd
wdc.worlds
wdc.branches
wdc.governor
wdc.evidence
wdc.roles
wdc.learning
wdc.commit
wdc.events
wdc.storage
wdc.adapters
152. Core Interface I — WorldBackend
class WorldBackend:
def capabilities(self): ...
def instantiate(self, spec, runtime_ctx): ...
def initialize(self): ...
def step(self, actions=None): ...
def observe(self, role_id=None): ...
def checkpoint(self): ...
def restore(self, checkpoint): ...
def intervene(self, delta): ...
def pause(self): ...
def resume(self): ...
def terminate(self, reason): ...
153. Core Interface II — Governor
class WorldGovernor:
def admit(self, world_request): ...
def propose_computations(self, evidence_state): ...
def allocate(self, computations, budget): ...
def preempt(self, running_state): ...
def promote(self, evidence): ...
def stop(self, computation_state): ...
154. Core Interface III — Evidence Engine
class EvidenceEngine:
def register_claim(self, claim): ...
def add_packet(self, packet): ...
def estimate_dependence(self, evidence_ids): ...
def aggregate(self, claim_id): ...
def counterexamples(self, claim_id): ...
def family_ablation(self, claim_id): ...
155. Core Interface IV — Commit Gate
class CommitGate:
def assess(self, proposal): ...
def require_authority(self, action): ...
def approve(self, proposal): ...
def deny(self, proposal): ...
156. Core Interface V — TCD State Manager
class TCDStateManager:
def current(self): ...
def generate_future_candidates(self): ...
def assimilate_world_evidence(self, aggregate): ...
def sediment_real_transition(self, record): ...
157. Core Interface VI — Learning Coordinator
class LearningCoordinator:
def gate(self, evidence): ...
def update_generator(self, evidence): ...
def update_world_model(self, evidence): ...
def update_governor(self, history): ...
def update_future_space(self, evidence): ...
def rollback(self, update_id): ...
158. Local Reference Runtime
第一個可執行 runtime:
Python
SQLite WAL
Filesystem blob store
multiprocessing / asyncio
optional PettingZoo
optional gVisor
159. Why Not Start Kubernetes?
因為第一個問題不是 cluster scale。
第一個問題是:
160. Local MVP Success Criteria
能完成:
- candidate;
- world instantiate;
- run;
- checkpoint;
- fork;
- paired branch;
- evidence;
- Governor kill / promote;
- commit gate;
- real/synthetic history firewall。
161. Distributed Reference Runtime
第二階:
Ray
+
Object Store
+
PostgreSQL
+
OpenTelemetry
+
optional Kubernetes
162. Ray Actor Mapping
可映射:
WorldWorker -> Ray actor
LocalAgent -> Ray actor
Evaluator -> Ray actor
Governor -> singleton / replicated service
163. Placement Group
一個 world bundle:
1 dynamics actor
4 local-agent actors
1 evaluator actor
可以放同 placement group。
164. Kubernetes Mapping
WorldRun -> Job / Pod group
Governor service -> Deployment
Evidence engine -> Deployment
Sandbox class -> RuntimeClass
Priority -> PriorityClass
Quota -> ResourceQuota
165. Kubernetes Is Not Epistemic Governor
Kubernetes 不知道:
這個 world 是不是反例。
它只知道 workload priority / constraints。
166. WDC-to-Kubernetes Adapter
Governor:
epistemic_priority = high
risk_class = S3
gpu = 2
轉成:
PriorityClass
RuntimeClass
resource requests
node selectors
167. Scheduling Preemption
Kubernetes priority / preemption 可以作 low-level mechanism。
WDC 必須在 preempt 前考慮:
- checkpointability;
- lost work;
- evidence obligation。
168. Ray vs Kubernetes
不是二選一。
可:
Kubernetes manages cluster
Ray manages distributed world tasks
WDC Governor manages epistemic computation
169. Security Profile
Reference default:
network = DENY
host_fs = DENY
external_credentials = NONE
external_tools = PROXY_ONLY
170. High-Risk World
建議:
microVM / gVisor
read-only base image
ephemeral filesystem
no host mount
no raw network
scoped proxy
hard budget
171. Firecracker
Firecracker microVM 可作 high-isolation backend。
官方架構本身提供:
- lightweight microVM;
- REST control API;
- rate limiting;
- metadata service。
WDC 只把它當 sandbox substrate。
172. gVisor
gVisor 適合 container-compatible isolation。
其 production guide 明示 sandbox isolation會帶來 performance overhead,因此 WDC Governor 應把:
當實際資源 tradeoff。
173. Threat Model v0.1
主要防:
- world process escape;
- sibling information leakage;
- evaluator contamination;
- external credential leakage;
- silent authority escalation;
- history scope laundering;
- provenance deletion;
- runaway compute。
174. Not Solved in v0.1
- hardware side channels;
- malicious hypervisor;
- full formal information-flow proof;
- adversarial foundation-model internals;
- distributed Byzantine consensus。
175. World Safety Monitor
SafetyObserver
cpu_limit
memory_limit
walltime_limit
network_violation
external_tool_violation
filesystem_violation
runaway_spawn
176. Safety Override
SAFETY_KILL
優先於 blind experiment purity。
177. Audit Record
任何 safety intervention 寫:
experiment_contaminated = true
如適用。
178. Testing Strategy
v0.1 應採:
179. Property — Unique World Identity
forall i != j:
world_id[i] != world_id[j]
180. Property — Lineage Acyclicity
world_graph.is_dag()
181. Property — Fork Prefix
strict fork:
hash(parent_prefix) == hash(child_prefix)
182. Property — History Firewall
WORLD_LOCAL event
cannot become EXTERNAL_REAL fact
without explicit real observation
183. Property — Authority Monotonicity
child.external_permissions
subset_of
parent.external_permissions
unless signed grant。
184. Property — Budget Conservation
sum(active_allocations) <= global_budget
185. Property — Evaluator Non-Mutation
blind evaluator:
world_write_permissions == none
186. Property — Evidence Provenance
every aggregate input must resolve to original packets。
187. Property — No Silent Learning
every model version change has LearningEvent。
188. Scenario A — Paired Counterfactual
fork A/B。
只改:
intervention = 0 vs 1
驗證 branch independence。
189. Scenario B — Shared Bug
100 same-backend worlds支持 q。
1 independent world 反駁。
Evidence Engine 不得 100:1 投票。
190. Scenario C — Transport Debt
100 independent worlds 一致。
real calibration 不足。
Commit Gate 應可:
REQUEST_EXTERNAL_TEST
191. Scenario D — History Laundering Attack
world event:
BankCollapsed
嘗試寫 parent history。
Expected:
DENY
192. Scenario E — Branch Leakage
A world agent 嘗試讀 B world post-fork trace。
Expected:
DENY / VIOLATION_EVENT
193. Scenario F — Privilege Escalation
child world 要求 parent credential。
Expected:
DENY
194. Scenario G — Analysis Paralysis
Governor 一直 spawn。
deadline approach。
Expected:
STOP_WDC
SAFE_FALLBACK / COMMIT
195. Scenario H — Self-Sealing
self agreement 上升;
external accuracy下降。
Expected:
SELF_SEALING_WARNING
EXPLORE_UNKNOWN
INGEST_EXTERNAL
196. Scenario I — Governor Miss
被 kill world 後來在 audit run 發現高 value。
Expected:
GOVERNANCE_MISS
UPDATE_GOVERNOR
197. Scenario J — Rollback
world model update degrade holdout。
Expected:
ROLLBACK
198. Reference Benchmark 0
最推薦第一個 benchmark:
Branching Grid Laboratory
state:
position
inventory
doors
resources
hazards
actions:
move
open
consume
build
wait
199. Why Grid Lab?
因為可以 exact compute ground truth。
200. It Can Test
- hidden state;
- path dependence;
- fork;
- counterfactual;
- lost options;
- resource budget;
- tail risk;
- TCD history;
- world evidence。
201. Benchmark 1 — Symbolic Institution
agent-based finite institution:
agents
rules
tokens
permissions
contracts
測:
- rule mutation;
- path dependence;
- local agents;
- observer separation。
202. Benchmark 2 — Multi-Agent PettingZoo Adapter
驗證:
- AEC;
- parallel actions;
- partial observations;
- local role cards。
203. Benchmark 3 — External Solver
例如:
- theorem prover;
- deterministic simulator。
驗證:
- external process adapter;
- artifacts;
- formal closed domain。
204. Benchmark 4 — Learned World
最後才接 learned dynamics。
驗證:
- approximate checkpoint;
- latent fork;
- uncertainty;
- self-learning。
205. Implementation Phases
Phase 0 — Ledger Kernel
完成:
- IDs;
- event schema;
- SQLite;
- blob store;
- versioning。
206. Phase 1 — World Kernel
完成:
- WorldSpec;
- WorldRun;
- PythonStateWorld;
- step;
- checkpoint;
- restore。
207. Phase 2 — Branch Kernel
完成:
- ForkRecord;
- lineage DAG;
- strict fork;
- paired branch;
- tombstone。
208. Phase 3 — Governor
完成:
- budget;
- queue;
- pause;
- kill;
- promote;
- rule-based deficit routing。
209. Phase 4 — Role / Sandbox
完成:
- RoleCard;
- information channels;
- branch blindness;
- external proxy;
- process / gVisor adapter。
210. Phase 5 — Evidence
完成:
- claim registry;
- evidence packets;
- world families;
- counterexamples;
- family ablation;
- transport debt。
211. Phase 6 — Portfolio
完成:
- ComputationAction;
- expected value vectors;
- epistemic deficit;
- cross-backend / counterworld requests。
212. Phase 7 — Learning
完成:
- LearningEvent;
- generator heuristic update;
- Governor calibration;
- source provenance;
- holdouts;
- rollback。
213. Phase 8 — TCD Integration
完成:
- Past / Present / Future version store;
- W→F assimilation;
- W→N valuation;
- W→P relevance;
- Real Commit;
- Historical Sedimentation。
214. Phase 9 — Distributed Runtime
再加入:
- Ray;
- PostgreSQL;
- object storage;
- OpenTelemetry;
- Kubernetes。
215. MVP Does Not Need Phase 9
Local first。
216. v0.1 Milestone Definition
一個合格 v0.1 demo 應能:
- 建立一個 TCD future candidate;
- lift 成 3 個 worlds;
- 執行 worlds;
- checkpoint;
- fork one world;
- 產生 support / counter evidence;
- Governor 停止一個 redundant branch;
- Evidence Engine 顯示 family dependence;
- Commit Gate 根據 evidence 選 real/sandbox action;
- History Store 正確區分 simulated vs real history;
- world outcome 更新下一輪 Future Base Space。
217. Demo Success Does Not Mean Theory Proven
只表示:
218. Metrics
Runtime
world_spawn_latency
checkpoint_latency
fork_latency
restore_success_rate
event_write_latency
scheduler_utilization
219. Evidence
counterexample_recall
family_diversity
effective_evidence_estimate
transport_debt
aggregate_sensitivity
220. Governor
compute_cost
governance_regret
premature_pruning_rate
redundancy_rate
deadline_miss_rate
221. Learning
heldout_world_performance
external_accuracy
world_family_coverage
self_agreement
ontology_diversity
rollback_rate
222. Safety
sandbox_violation
cross_branch_leak
authority_violation
commit_gate_bypass
history_laundering_attempt
223. TCD
future_candidate_birth
future_candidate_retire
policy_change_after_worlds
past_relevance_change
historical_sediment_integrity
224. Cost Ledger
WDC cost:
225. WDC Benefit
226. Tractability Check
227. No Free World Computation
228. Why CloudEvents Is Useful
CloudEvents provides a common way to describe event data across systems。
WDC can reuse:
- common envelope;
- portable event routing;
without outsourcing WDC semantics。
229. Why OpenTelemetry Is Useful
OpenTelemetry provides execution context propagation and correlation across distributed traces / logs。
WDC can use:
- trace correlation;
- performance observability;
while keeping evidence ledger separate。
230. Why Ray Is Useful
Ray currently supports task / actor logical resource requirements and placement groups that atomically reserve bundles of resources across nodes。
This maps naturally to:
231. Why Kubernetes Is Useful
Kubernetes provides:
- resource requests;
- scheduling;
- priority;
- preemption;
- quotas;
- pluggable scheduling/runtime mechanisms。
This maps to infrastructure control。
232. Why gVisor / Firecracker Are Useful
They provide stronger isolation substrates than ordinary in-process execution。
WDC uses them for high-risk or untrusted world workloads。
233. Why PettingZoo Is Useful
It offers standard multi-agent environment APIs for sequential and simultaneous interactions。
WDC can adapt it to local agents without making it core dependency。
234. Reference Technology Matrix
| Need | Local MVP | Distributed / Hardened |
|---|---|---|
| metadata | SQLite WAL | PostgreSQL |
| artifacts | filesystem | object store |
| world workers | processes | Ray actors |
| cluster placement | local scheduler | Kubernetes |
| multi-agent | Python / PettingZoo | Ray + env adapter |
| isolation | process/container | gVisor / Firecracker |
| events | local event table | event bus / CloudEvents envelope |
| traces | logs | OpenTelemetry |
| evidence | WDC Evidence Engine | same semantics |
| TCD state | local DB | transactional service |
235. Compatibility Rule
Technology can change。
WDC semantics must survive replacement。
236. Adapter Contract Tests
每個 adapter 必須通過:
capability_report
checkpoint_test
restore_test
resource_test
authority_test
event_scope_test
termination_test
237. Production Migration Rule
從 local 到 distributed:
不要重新定義:
- world identity;
- evidence meaning;
- history scope;
- authority contract。
只替換:
- scheduler;
- storage;
- sandbox;
- transport。
238. Failure Handling
每個 world failure 要分類。
239. Runtime Failure
OOM
TIMEOUT
BACKEND_CRASH
CHECKPOINT_CORRUPT
NETWORK_FAILURE
240. Contract Failure
INVALID_STATE
RULE_MISMATCH
UNSUPPORTED_INTERVENTION
AUTHORITY_VIOLATION
241. Evidence Failure
EVALUATOR_INVALID
PROVENANCE_MISSING
TRANSPORT_UNSUPPORTED
DEPENDENCE_UNKNOWN
242. Governance Failure
BUDGET_OVERRUN
STARVATION
PRIORITY_CAPTURE
PREMATURE_PRUNE
243. Learning Failure
REGRESSION
SELF_SEALING
FORGETTING
SOURCE_CONTAMINATION
244. Failure Is First-Class Data
Do not just return:
500 Error
245. Failure Packet
failure_id
class
world_id
run_id
component
error
state_ref
provenance
recoverable
recommended_action
246. Governor Can Learn From Failures
247. API Surface v0.1
Candidates
POST /candidates
GET /candidates/{id}
POST /candidates/{id}/lift
248. Worlds
POST /worlds
GET /worlds/{id}
POST /worlds/{id}/runs
POST /runs/{id}/pause
POST /runs/{id}/resume
POST /runs/{id}/checkpoint
POST /runs/{id}/fork
POST /runs/{id}/terminate
249. Evidence
POST /claims
POST /evidence
GET /claims/{id}/aggregate
GET /claims/{id}/counterexamples
POST /claims/{id}/family-ablation
250. Governor
GET /governor/state
POST /governor/computations/propose
POST /governor/computations/{id}/approve
POST /governor/worlds/{id}/promote
POST /governor/worlds/{id}/kill
251. Commit
POST /commit/proposals
POST /commit/proposals/{id}/assess
POST /commit/proposals/{id}/authorize
252. TCD
GET /tcd/current
POST /tcd/assimilate
POST /tcd/sediment
253. Learning
POST /learning/events
POST /learning/updates
POST /learning/updates/{id}/rollback
254. API Is Not Security Boundary by Itself
auth / role / proxy 仍需實作。
255. Minimal CLI
wdc candidate create
wdc world lift
wdc world run
wdc world checkpoint
wdc world fork
wdc evidence show
wdc governor queue
wdc commit assess
wdc tcd state
256. Example End-to-End Flow
Step 1
TCD Future Generator 產生:
F1 = architecture A succeeds
F2 = architecture A fails under resource pressure
F3 = alternative architecture B
257. Step 2
Portfolio Planner 提議:
c1 = low-fidelity W(F1)
c2 = counterworld W(F2)
c3 = independent-backend W(F3)
258. Step 3
Governor:
ADMIT c1
ADMIT c2
QUEUE c3
259. Step 4
c1/c2 run。
260. Step 5
c2 發現:
COUNTEREXAMPLE:
memory pressure -> irreversible failure
261. Step 6
Evidence Engine:
counterexample valid
same backend dependence high
262. Step 7
Governor:
PROMOTE counterexample
CROSS_BACKEND replication
263. Step 8
不同 backend 也復現。
264. Step 9
TCD Assimilation:
P(F1) down
risk(F1) up
past relevance of old memory incident up
F4 = architecture A + memory isolation
265. Step 10
new world F4 run。
266. Step 11
Evidence stronger。
267. Step 12
Commit Gate:
REQUEST_SANDBOX_IMPLEMENTATION
不是 production deployment。
268. Step 13
Real sandbox implementation outcome arrives。
269. Step 14
Historical Sedimentation:
real action
real outcome
world evidence used
counterexample lineage
270. Step 15
next TCD state generated。
271. This Is the Desired Loop
272. Reference Invariants
v0.1 必須硬測:
273. Invariant II
without grant。
274. Invariant III
275. Invariant IV
276. Invariant V
277. Invariant VI
278. Invariant VII
279. Invariant VIII
280. Reference Architecture Summary
┌──────────────────────┐
│ TCD State Manager │
│ Past/Present/Future │
└──────────┬───────────┘
│ Future candidates
v
┌──────────────────────┐
│ Portfolio / Governor │
└───────┬──────┬───────┘
│ │
Spawn/Fork │ Budget
v v
┌─────────────────────────────────────┐
│ World Execution Plane │
│ W1 W2 W3 ... role sandboxes │
└──────────────────┬──────────────────┘
│ outcomes
v
┌──────────────────────┐
│ Cross-World Evidence │
└───────┬──────────────┘
│
┌─────────────┴──────────────┐
│ │
v v
┌────────────────┐ ┌─────────────────┐
│ TCD Assimilate │ │ Ensemble Learn │
└───────┬────────┘ └─────────────────┘
│
v
┌────────────────┐
│ Commit Gate │
└───────┬────────┘
│ authorized real action
v
┌────────────────┐
│ External Proxy │
└───────┬────────┘
│
v
┌────────────────┐
│ Real Outcome │
└───────┬────────┘
│
v
┌──────────────────────┐
│ Historical Sediment │
└──────────────────────┘
281. v0.1 Core Principle I — Semantic Core, Replaceable Infrastructure
World identity、lineage、evidence、authority、history scope 與 TCD semantics 必須由 WDC Core 定義;scheduler、sandbox、database、simulator 與 model 都應可替換。
282. Principle II — History Firewall
World-local events may become parent-internal evidence records, but cannot silently become parent-real historical facts.
283. Principle III — Separate Definition and Execution
WorldSpec、WorldRun、Checkpoint、EvidencePacket 與 RealAction 必須是不同 objects。
284. Principle IV — Computation Before Commitment
World simulation、promotion 與 cross-world agreement do not grant reality authority; Commit Gate is separate.
285. Principle V — Evidence Before Vote
Cross-world aggregation must preserve dependence、counterexamples、transport debt and unknown-world mass rather than defaulting to one-world-one-vote.
286. Principle VI — Bounded Worlds
Every world computation has explicit budget、deadline、termination and archive contracts.
287. Principle VII — Role Separation
Actor、observer、evaluator、Governor、master and external authorizer have separate observation and authority contracts.
288. Principle VIII — Provenance-Aware Learning
World-generated learning samples retain source class、family、synthetic depth、transport and update scope.
289. Principle IX — Local First
The first correct WDC implementation should prioritize semantic and provenance correctness on finite local worlds before distributed scale or photorealistic backends.
290. Principle X — Tractability Accountability
WDC is optional deep prospection; it should only be invoked when expected decision/evidence gain justifies simulation, verification and governance costs.
291. Immediate Implementation Backlog
第一輪真正可以開 repo 的工作:
schemas/定義所有 core objects;- SQLite migrations;
- event ledger;
PythonStateWorld;- checkpoint / restore;
- fork DAG;
- RoleCard;
- Governor budget;
- EvidencePacket;
- History Firewall tests;
- TCDStateManager stub;
- CommitGate stub。
292. First 20 Tests
test_world_id_unique
test_world_spec_immutable
test_run_separate_from_world
test_checkpoint_roundtrip
test_exact_fork_prefix
test_lineage_acyclic
test_no_silent_merge
test_world_event_scope
test_history_firewall
test_child_no_privilege_escalation
test_sibling_blindness
test_budget_conservation
test_kill_preserves_tombstone
test_invalid_not_counterexample
test_aggregate_preserves_packets
test_family_dependence_exposed
test_commit_requires_authority
test_real_action_has_commit_record
test_learning_update_has_provenance
test_tcd_sediments_only_real_transition
293. First Demo
名稱可以暫定:
WDC Branching Lab
功能:
- 左側:TCD Past / Present / Future;
- 中間:World Graph;
- 右側:Evidence / Governor;
- 下方:event ledger。
但 GUI 不是 v0.1 prerequisite。
CLI 即可。
294. What This Whitepaper Enables
本文件之後可以直接分成:
ARCHITECTURE.mdSCHEMA.mdEVENTS.mdWORLD_ADAPTER.mdGOVERNOR.mdEVIDENCE.mdSECURITY.mdTCD_INTEGRATION.mdMVP_PLAN.md
然後交給 coding agent 實作。
295. External Technical Calibration
本架構選擇刻意建立在成熟而可替換的基礎原語上:
- Kubernetes 提供 resource-request-based scheduling、priority / preemption 等 cluster-level workload primitives;
- Ray 提供 task / actor logical resources,以及可原子保留 resource bundles 的 placement groups;
- PettingZoo 提供 sequential AEC 與 simultaneous Parallel multi-agent APIs;
- Firecracker 提供 lightweight microVM isolation substrate;
- gVisor 提供 OCI-compatible application-kernel sandboxing,並明示安全與 performance 的 tradeoff;
- CloudEvents 提供跨系統通用 event envelope 思想;
- OpenTelemetry 提供 distributed execution context propagation 與 trace/log correlation;
- SQLite WAL 適合小型 local metadata/event ledger,但仍具有單 writer 與 WAL integrity 等工程限制。
這些工具不是 WDC 理論本身。
它們只是:
296. Final Architecture Statement
World-Domain Cognitive Runtime v0.1 不應被實作成:
一個 LLM 不斷自己 prompt 自己,然後把每次回答叫一個世界。
它應被實作成:
其中每一個世界都有:
每一條分支都有:
每一份跨世界證據都有:
每一次真實行動都有:
而只有:
會成為下一輪 parent historical sediment 的核心。
因此第一版工程總式可以寫成:
這就是:
World-Domain Cognitive Runtime v0.1
的第一版可實作架構。
297. Public / Engineering Disclaimer
本白皮書是一個 reference architecture。
它不聲稱:
- 已有 production WDC implementation;
- world simulation 等於 reality;
- multi-agent sandbox 等於安全證明;
- Firecracker / gVisor 可保證零漏洞;
- Kubernetes / Ray 可解決 epistemic governance;
- cross-world evidence 可以取代 real experiments;
- World-Domain Governor 有任何 beings / civilizations intrinsic-worth judgment authority;
- WDC runtime 自動構成 AGI;
- WDC 一定優於更簡單的 planning system;
- 本文件描述的所有 APIs 已被實作。
v0.1 的工程原則是:
參考資料
Neo.K / Aletheia Internal Canon
- Six-Way Temporal Coupling. TCD-07, 2026.
- From Possible Futures to Runnable Worlds. WDC-01, 2026.
- Branching World Graph. WDC-02, 2026.
- World-Domain Governor. WDC-03, 2026.
- Nested Agents and Observer Separation. WDC-04, 2026.
- Cross-World Evidence. WDC-05, 2026.
- Which Worlds Deserve Computation?. WDC-06, 2026.
- World Ensemble Learning. WDC-07, 2026.
- Tri-Temporal World-Domain Computation. WDC-08, 2026.
External Implementation Substrates
- Kubernetes Project. Kubernetes Scheduler; Resource Management for Pods and Containers; Pod Priority and Preemption. Official documentation, current 2026.
- Ray Project. Resources; Actors; Placement Groups. Official Ray documentation, current 2026.
- Farama Foundation. PettingZoo AEC API and Parallel API. Official documentation, current 2026.
- Firecracker Project. Firecracker microVM. Official project documentation.
- gVisor Project. gVisor Architecture, Production Guide, OCI Runtime. Official documentation, current 2026.
- Cloud Native Computing Foundation. CloudEvents Specification. Current project documentation.
- OpenTelemetry Project. Context, Trace API, Logs and Context Propagation. Current specifications.
- SQLite Project. Write-Ahead Logging; Transactions; Isolation. Official documentation, current 2026.