Architecture Guide
ESSENTIAL READING · START HERE
Start with the six-layer request lifecycle V3. It follows one request through admission, conversation/context, Main and subagents, optional tools, publication and visible client results. V2 is preserved and the original V1 remains readable.
The engineering articles separate model judgment from runtime facts and permissions. For a structured starting point, explore the architecture reading path, then the module mechanisms.
The architecture principles now distinguish nine durable judgments from seven on-demand engineering methods; the writing roadmap distinguishes article revisions from unpublished candidates.
The A35 content trust deep dive distinguishes trusted producer identities from source data and effect permissions. Its Phase 1 structural tests are not a real-model security qualification.
October 24, 2026: implementation versus acceptance
Bounded front-end conversation responses and background research now share the original Conversation/Run ownership, but a complete source-grounded research run has not yet passed its separate acceptance criteria. Optional Reviewable details are attached to results and readable from History without becoming a new authority over the answer.
Account-scoped subagent profiles and frozen Run/Child selection have source-level integration; end-to-end account, PostgreSQL, browser, and research validation remain open. The optional Nasdaq 2026 calendar path distinguishes user-local time, task anchors and scheduled sessions, but is disabled by default. A scheduled market session is not proof of actual trading or quote freshness. The curated question catalog likewise does not certify answer quality.
The 43-owner gallery now includes A36 Temporal Semantics and A37 durable Human Interaction as two first-class logical Owners. The interactive map currently retains Chinese labels. A36 source/calendar/ordinary real-agent acceptance is still open. A37 Stages A–D and provider-free formal close are complete in the scoped local lane, while production Human Park remains disabled by default. Its interaction handoff authority does not replace Authorization, Effect, Recovery or Publication.
The original architecture guide contains further Chinese-language details.
October 26, 2026: Updated implementation boundaries
The runtime's initial Child/Human Interaction, run-local Memory, Access/Exposure and private Skill-session slices have scoped evidence, and the eight-group field ownership reconciliation is recorded; the whole Runtime locality change remains open. Governed Source reading now has a conditional default dynamic-rendering fallback with a 1 MiB intermediate HTML limit. Bounded real-path foreground/background conversation qualification has been archived, but does not establish a completed financial report. See the October 26 status update.