34 lines
963 B
Markdown
34 lines
963 B
Markdown
# ADR-0007: Mesh region registry via Autobase + Hyperbee
|
|
|
|
- **Status:** Accepted
|
|
- **Date:** 2026-07-30
|
|
|
|
## Context
|
|
|
|
Mesh enrollment needs a multi-writer, eventually consistent registry of regions (bounds, tunnel keys, metadata) without a central database.
|
|
|
|
## Decision
|
|
|
|
- Use **Autobase** for multi-writer linearization of registry operations.
|
|
- Maintain a **Hyperbee view** (via Autobase `open`/`apply`) keyed by region id and spatial cells.
|
|
- Mesh discovery topic derived from mesh root key; replicate over Hyperswarm.
|
|
- Defer **autobee** until stable (experimental).
|
|
|
|
Writer admission is capability-gated (details in Phase 4; OPEN_QUESTIONS Q4).
|
|
|
|
## Consequences
|
|
|
|
### Positive
|
|
|
|
- Holepunch-native multi-writer
|
|
- Sparse replication of registry only (not block data)
|
|
|
|
### Negative / tradeoffs
|
|
|
|
- Autobase complexity (reordering, indexers)
|
|
- Need clear UX for offline regions
|
|
|
|
### Follow-ups
|
|
|
|
- [ ] Phase 4 apply function + writer policy ADR amendment if needed
|