System map
Soval gives people one coherent surface. Katra Forge keeps the components, evidence, and authority boundaries underneath it independently testable.
This view describes what the user encounters and the direction of governed requests. It does not turn Soval into the complete system.
Boundary: this diagram shows presentation and dependency direction. No ownership, semantic authority, decision authority, or release authority moves upward into Soval.
Katra Forge remains the complete assembled governed system. Soval is one user-facing application inside that system, alongside bounded controls, domain applications, reusable modules, and adapters.
Complete system
Its identity includes applications, modules, control components, shared-platform capabilities, contracts, integration evidence, and release evidence. No individual layer is synonymous with the whole.
Visible application
It receives intent, establishes actor context, assembles governed context, routes requests, exposes blockers, and presents results—without absorbing the state or authority of the component doing the work.
Each component owns one declared responsibility and an equally important ceiling.
Unified human-agent presentation and routing. It cannot inherit component authority, create identity, or treat a completed interaction as approval.
Canonical pre-formation inquiry continuity and exact-source episodes. It owns no project identity or Product Definition authority.
Product Definition, backlog, Evidence State, Transition Candidate preparation, and work coordination. Planning state is not authority.
Consequential-transition policy and attributable disposition. A decision remains separate from execution, result, and readback.
Knowledge management, digital-brain functions, retrieval, working context, and cognitive continuity. It does not own story canon or system release.
Story creation, narrative development, canon, editorial review, and publication preparation. It does not own platform-wide gates.
Input, Output, requirements, retrieval, review, repository, and handoff capabilities. Reuse never transfers application authority.
Boundaries to repositories, systems of work, runtimes, and providers. Observation, authorization, mutation, and readback remain distinct.
Human-readable governed Markdown remains the durable semantic foundation. Every operational representation is downstream and replaceable.
Conflict behavior
When a site view conflicts with its governing source, Soval marks the view stale or conflicting, identifies the affected claim, and exposes the owner-governed reconciliation path.
Model behavior
The hosted workroom sends bounded drafting requests directly to OpenAI and retains the resulting suggestions separately. That hosted path is not connected to the full Katra conversation coordinator or external execution adapters.