Index Ref: SEC-06 / ADR // Decision Register
Architecture Decision Records
Immutable records capturing context, alternatives evaluated, trade-offs, and consequences of structural and architectural choices.
Decision Records Table
ADR-001
Order: #1
Adopt Orvenath as the parent brand
Selection of an invented, unclaimed name over available alternatives.
#brand#naming
Accepted
View Record
ADR-002
Order: #2
Single entity with brand-level divisions
Divisions are brands, not subsidiaries.
#structure#legal
Accepted
View Record
ADR-005
Order: #5
Standardise on Next.js and Vercel
Default web stack selection.
#engineering#stack
Accepted
View Record
ADR-006
Order: #6
Async-first sales as the default motion
Recorded walkthroughs replace live sales calls.
#sales#communication
Accepted
View Record
ADR-007
Order: #7
Keep client fees confidential in public case studies
Publishing a past fee anchors every future prospect downward.
#pricing#marketing#privacy
Accepted
View Record
ADR-010
Order: #10
Proposal engine as a separate deployment
Client-facing proposal tooling runs on its own subdomain and repository, not inside the marketing site.
#engineering#sales#infrastructure
Accepted
View Record
ADR-011
Order: #11
Single Neon project with Postgres schema separation
One database for all Orvenath systems, separated by schema. Supabase rejected on free-tier pausing.
#engineering#infrastructure#database
Accepted
View Record
ADR-012
Order: #12
Proposal view telemetry is intelligence, never automation
Opening a share link never changes proposal status. Status transitions stay manual.
#sales#privacy#engineering
Accepted
View Record
ADR-013
Order: #13
Rate limiting in Postgres rather than in memory
In-memory rate limiting does not function on serverless. State moved to the database.
#engineering#security#infrastructure
Accepted
View Record
SHOWING 9 OF 9 TOTAL DECISION RECORDSExplore Interactive ADR Relationship Graph