Skip to main content
Link
Menu
Expand
(external link)
Document
Search
Copy
Copied
distributed-lock-lab
Home
Contributing
AI contributors
Roadmap
Task board
Documentation
00 Charter
01 Requirements
02 Domain model
03 Architecture
04 Contracts index
05 Infrastructure
06 Observability and SLO
07 Correctness and testing
08 Operations
09 Risks
10 Delivery plan
11 Glossary
12 Parallelization map
C1 Database schemas
C2 Java API
C3 HTTP surfaces
C4 Observability
C5 Config, build, naming
ADR-000 — Template {#adr0}
ADR-001 — etcd as the consensus store {#adr1}
ADR-002 — Fencing token source: ModRevision captured at grant time {#adr2}
ADR-003 — lockdb and paydb are separate databases on separate Cloud SQL instances {#adr3}
ADR-004 — The protected operation is a payout execution, not a balance update {#adr4}
ADR-005 — GKE Autopilot: evictions accepted as budgeted unavailability {#adr5}
ADR-006 — Conservative client-side lease expiry {#adr6}
ADR-007 — A fencing proxy in front of a resource with no CAS {#adr7}
ADR-008 — Terraform layout, remote state, and pinned provider versions {#adr8}
ADR-009 — Managed Prometheus, and SLOs that live in the infrastructure repo {#adr9}
ADR-010 — One repository, one Gradle build, one version list {#adr10}
ADR-011 — Version control and publication are deliberately deferred {#adr11}
ADR-012 — Git version control and public publication {#adr12}
ADR-013 — Parallel contribution replaces strict sequencing {#adr13}
ADR-014 — Apache-2.0 with DCO sign-off {#adr14}
Governance
Security
Support
Code of Conduct
Maintainers
View on GitHub