Quality

Open this section when you need to decide whether governed run behavior is proven strongly enough for acceptance, persistence, and replay to be trusted as authority rather than habit.

Trust Model

flowchart LR
    strategy["test strategy"]
    invariants["authority invariants"]
    validation["change validation"]
    limits["limitations and risk"]
    trust["trust decision"]

    strategy --> invariants --> validation --> limits --> trust

Runtime quality is the proof path behind authority. The section should make it clear how accepted and replayable runs are tested, which invariants protect the authority model, and where the package still names limits instead of hiding them behind a green build.

Read These First

• open Test Strategy first when you need the broad proof shape behind runtime authority
• open Invariants when the question is what must not drift across acceptance and replay behavior
• open Change Validation when you need the minimum proof for a safe runtime change

Trust Risk

The main quality risk here is accepting or replaying runs under rules that are weaker in practice than the docs imply.

First Proof Check

• tests and package-local validation surfaces for executable evidence
• invariants, limitations, and risk pages for the trust boundaries that still matter after green checks
• release notes and caller-facing docs when the change alters what readers may safely assume

Pages In This Section

• Test Strategy
• Invariants
• Review Checklist
• Documentation Standards
• Definition of Done
• Dependency Governance
• Change Validation
• Known Limitations
• Risk Register

Leave This Section When

• leave for Foundation when the doubt is really about package ownership rather than proof
• leave for Interfaces when the question is what the contract is rather than whether it is defended
• leave for Operations when the package already seems trustworthy and the real issue is how to run it repeatably

Design Pressure

If authority can drift while tests still look healthy, the package becomes dangerously shallow. This section has to show how trust in verdicts, replay, and persistence is actually defended.