Skip to main content
ORVENATH
Graph Ref: ADR-MAP // D3 Force Layout

ADR Relationship Graph

Force-directed network visualization of Architecture Decision Records. Nodes are color-coded by lifecycle status, and directed dashed edges indicate supersede lineage.

ADR Network Graph Visualization

Status Legend:
Accepted
Proposed
Superseded
Deprecated
Drag canvas to pan // Click node to navigate
ADR Structured Ledger & Dependency RegisterNon-JS Progressive Fallback
ADR-001Accepted
Adopt Orvenath as the parent brand

Selection of an invented, unclaimed name over available alternatives.

2026-08-20Read Record →
ADR-002Accepted
Single entity with brand-level divisions

Divisions are brands, not subsidiaries.

2026-08-20Read Record →
ADR-005Accepted
Standardise on Next.js and Vercel

Default web stack selection.

2026-08-25Read Record →
ADR-006Accepted
Async-first sales as the default motion

Recorded walkthroughs replace live sales calls.

2026-08-28Read Record →
ADR-007Accepted
Keep client fees confidential in public case studies

Publishing a past fee anchors every future prospect downward.

2026-08-26Read Record →
ADR-010Accepted
Proposal engine as a separate deployment

Client-facing proposal tooling runs on its own subdomain and repository, not inside the marketing site.

2026-09-01Read Record →
ADR-011Accepted
Single Neon project with Postgres schema separation

One database for all Orvenath systems, separated by schema. Supabase rejected on free-tier pausing.

2026-09-02Read Record →
ADR-012Accepted
Proposal view telemetry is intelligence, never automation

Opening a share link never changes proposal status. Status transitions stay manual.

2026-09-04Read Record →
ADR-013Accepted
Rate limiting in Postgres rather than in memory

In-memory rate limiting does not function on serverless. State moved to the database.

2026-09-03Read Record →