Architecture
Why OARE is built this way.
Single-spawner principle
Only OARE generates. Nothing it generates generates anything else. Complexity stays flat, not recursive.
Ephemeral / durable split
Agents are disposable. Blueprints are permanent. That split is the entire architecture.
Novelty detection
New situations get built. Familiar ones get retrieved. The system gets faster and cheaper over time, not slower.
Ownership model
You own every blueprint in your tenant. OARE learns only from anonymized, aggregated patterns — never your data directly.
Observability
Every Thread emits structured events from birth to dissolution.
Nothing runs invisibly.
17:05:01 [THREAD_SPAWN] thread_id=tr_88a91
17:05:02 [THREAD_DISSOLVE] lifecycle=complete
Governance
Plans above a threshold require your approval before a single Thread spawns.
THRESHOLD RULEAPPROVAL REQUIRED
Write Access to Production DB → Human Gate Active