Quality

agentic-proteins quality should tell a reviewer what must remain true, what proof is required, and which risks are serious enough to block a change.

Trust Model

flowchart LR
    invariants["invariants"]
    tests["test strategy"]
    validation["change validation"]
    risks["risk register and limitations"]
    decision["trust or block the change"]

    invariants --> tests --> validation --> risks --> decision

This page should show quality as a trust path rather than a page list. For the legacy bridge package, trust means proving the bridge still forwards correctly and stays easier to retire instead of becoming a second product surface.

Start With

• open Invariants before changing package meaning
• open Change Validation when you need the minimum proof for a real edit
• open Risk Register when the package boundary feels under pressure

Section Pages

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

What Quality Means Here

• proving that the legacy bridge still forwards correctly and becomes easier to retire over time

First Proof Check

• packages/agentic-proteins/tests
• src/agentic_proteins/interfaces/cli.py and api/app.py
• src/agentic_proteins/runtime/

Design Pressure

If the quality section reads like generic reassurance instead of a concrete bridge-proof path, the legacy package will linger on habit instead of staying reviewable and intentionally temporary.