OverviewFilesCommitsIssuesDocsReleasesPeers

favela-markdown commits / b2f989f

spec: fix two cross-references stale after the room reconciliation
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
b2f989f40a51681e3eca78f434892e451e860767
by plankatron <fleeky@gmail.com> · 2026-09-05T20:18:38.000Z

Changed files (1) +3 -2

spec/interaction.md +3 -2
……@@ -444,8 +444,9 @@ content one shape, and an inbound edge is the same idea applied to relationships
444444
4454451. **Edge as empty-body record vs. pointer-valued log entry** (§2.1). Measure the file count for a
446446 realistic like volume before locking it.
4472. ~~**The native URI scheme**~~ **CLOSED 2026-09-05** — `favela://<identity-root>/…`, §3.4. The
448 remaining work is the fail-closed minting rule (§3.4.1), not a decision.
4472. ~~**The native URI scheme**~~ **CLOSED 2026-09-05** — `favela://<roomKey>/<collection>/<rkey>`,
448 with the identity root as the personal-room case (§3.4). Remaining work is the fail-closed minting
449 rule (§3.4.1), not a decision.
4494503. **Inbox admission** (§6) — rate limiting, and how long an unverified claim is retained.
4504514. ~~**Where an edge's `reach` defaults from.**~~ **CLOSED 2026-09-05, then RESOLVED STRUCTURALLY** —
451452 an edge's audience is the room it was written in (§4.5); no computed bound is needed. `reach` (which