Skip to content

Cite2Site Build Docs

Status: active build documentation navigation.

Cite2Site separates external product-facing documents from internal execution authority and architecture-source contracts. Public narrative is readable, while internal docs are precise enough for an agent to implement from without reopening core decisions.

Fresh agents must start with AGENTS.md. This file is the build-doc map after that orientation step, not a replacement for the session gate and reading-order rules in AGENTS.md.

The documentation standard is part of the authority chain. It explains how to separate implemented behavior from approved target design without diluting either the technical argument or the reader's experience.

Current Execution Authority

Phase Prompts

Each prompt is a session-gate implementation contract. Start only the prompt authorized by the status matrix and its stated prerequisites.

Architecture Source Package

Architecture files are implementation contracts. When command behavior, event shape, replay output, export shape, or adapter semantics change, update the architecture package first or in the same patch.

External Product Narrative

External documents explain the product in ordinary language while distinguishing the current CLI/core substrate from Target integrations and publication work.

ADRs

Change Control Rule

Every implementation change must map to:

  1. a capability row in the current status matrix;
  2. a workflow section;
  3. a requirement in BRD, DRD, or TRD;
  4. a contract in the architecture specs or JSON schemas;
  5. a milestone in the project plan.

If a proposed change does not map to those sources, revise the docs first or treat the change as out of scope. A concise document is not sufficient evidence that the change is ready; the authority chain and validation evidence must also be complete.