doc.haus Atlas Legal-document workflows on OpenCode, bound to their code
219 documents

V2 specs tour

The upstream OpenCode contracts underneath doc.haus: who owns what, how sessions admit and execute prompts, how tools are built and bounded, and the two accepted decisions on events and provider policy.

Authority

Authority follows the concern:

Concern Owner
HTTP operations and transport errors Protocol endpoint definitions assembled by Server HttpApi
Public domain shapes and durable event payloads Schema
Runtime behavior and persistence Core
Contributor-critical regression guardrails Root AGENTS.md

Current specifications explain cross-module contracts without copying exact types. Decision records explain why a design was selected. Historical documents describe earlier states and may use obsolete names.

Generated clients follow the assembled public HttpApi. GitHub issues own active work; Git history preserves removed plans and scratchpads.