ADR
Architectural Decision Records for Terp Network
ADR Index
| # | Title | Status | Last Updated |
|---|---|---|---|
| 1 | Standard Template and Design Guidelines for ADRs | Accepted | 2026-03 |
| 2 | Expected Testing Library Design for Terp Network Tooling | DRAFT | 2026-03 |
| 3 | Community Expectations for LM/Agent Participation | DRAFT | 2026-05 |
| 4 | Sovereign Custody and Authentication Specifications | DRAFT | 2026-05 |
| 5 | HashMerchant — Verifiable Merkle Reflection Market | Proposed | 2026-05 |
| 6 | zk-wasm — Custom WASM Module for Authentication | DRAFT | 2026-05 |
| 7 | External ADRs — Reference for Followed External Decisions | DRAFT | 2026-05 |
| 8 | Closing the Loop — Sustainable Revenue and Automation | DRAFT | 2026-05 |
| 9 | LM-Augmented Development and Semantic Tooling | DRAFT | 2026-05 |
| 10 | Community Working Groups and Resource Coordination | DRAFT | 2026-05 |
Status Definitions
- DRAFT — Under initial authorship, not yet open for review
- Proposed — Open for community and core-team review (minimum one week)
- Accepted — Approved and binding on all future work
- Rejected — Not adopted; preserved for historical reference
- Deprecated — Superseded by a later ADR; the replacement is linked in the document
- Superseded — Replaced by a specific later ADR
Three-Layer ADR Hierarchy
Terp Network inherits architectural decisions from three upstream layers. Before proposing any change, traverse all three:
- Cosmos SDK ADRs — 63 ADRs covering store management, module wiring, testing, and core SDK mechanics. Start with ADR-041, ADR-059, ADR-063, ADR-065.
- IBC-go ADRs — 15 ADRs governing inter-chain communication, relayers, and middleware. Critical: ADR-027 (IBC wasm client).
- Terp-core module specs — Local specs under
x/<module>/spec/covering feeshare, drip, and custom module behavior.
When layers conflict, the most specific layer wins — but the conflict must be documented as a Terp-specific ADR.
Proposing a New ADR
- Open a PR with the ADR in DRAFT status using the template from ADR-1
- Allow at least one week for community and core-team review
- Security reviewers must sign off on crypto-related ADRs
- Only maintainers may change status to Accepted/Rejected
- Link the ADR from code, specs, and upgrade documentation
Upstream ADR Discovery
All three layers are indexed in QMD's abstract collection. Use semantic search to find relevant decisions:
oline-qmd search 'store migrations' -c abstract— keyword searcholine-qmd query 'how does the SDK handle module state upgrades' -c abstract— hybrid semantic search
See ADR-9 for the full LM-augmented development pipeline.