OverviewFilesCommitsIssuesDocsReleasesPeers

favela-peer commits / 1d95acb

README: link sibling repos, which this tree already does and I did not
The convention was already here — favela-web and favela-node link siblings as [hyper-proto-peer](../hyper-proto-peer), favela-community as [hyper-rooms](../hyper-rooms). The READMEs I wrote from scratch had ZERO of them; the ones I only edited kept theirs. Measured before fixing: favela-bridge, favela-host, favela-identity, favela-markdown, favela-peer, favela-surface and favela-surface-android each had 0 relative links while mentioning 5-10 siblings by name. Linked on FIRST mention only, prose only. Skipped code fences, tables, existing links and URLs, and left later mentions as code spans so a paragraph does not turn into a row of blue. One case the automated pass got wrong and I reverted by hand: favela-surface's Boundary section lists the modules it may NOT import, as a uniform run of code spans. Linking hyper-overlay and ap-bridge there broke the list's formatting and read as "go read these" when the point is "never import these". Those two are code spans again. Rewrapped the lines the inserted links pushed past 100 columns, which is where the rest of this tree wraps. The long lines that remain in favela-community and favela-node are pre-existing prose — verified against HEAD — and one is inside a code fence. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
1d95acb48ec4d609fc7d2cade3c259e6d15e596d
by plankatron <fleeky@gmail.com> · 2026-09-20T21:23:03.000Z

Changed files (1) +8 -5

README.md +8 -5
……@@ -95,7 +95,8 @@ Refuses to start if another daemon already holds the socket.
9595| `directory` | listings across registries you hold |
9696
9797`lib/rpc.js` answers 106 methods; the CLI covers the 34 a human drives. The rest are what
98`favela-surface` calls — onboarding, rooms, namespaces, reach, and the bridge verbs below.
98[favela-surface](../favela-surface) calls — onboarding, rooms, namespaces, reach, and the bridge
99verbs below.
99100
100101## Primitives
101102
……@@ -115,9 +116,9 @@ Refuses to start if another daemon already holds the socket.
115116
116117## Records
117118
118- A record is a markdown file: JSON frontmatter, then a body. See `favela-markdown`.
119- A record is a markdown file: JSON frontmatter, then a body. See [favela-markdown](../favela-markdown).
119120- Mutable, edited in place — the name is the stable identity, the hash is not.
120- Bytes are content-addressed in hyper-overlay; the log holds a pointer.
121- Bytes are content-addressed in [hyper-overlay](../hyper-overlay); the log holds a pointer.
121122
122123## Interactions
123124
……@@ -136,7 +137,8 @@ No `atproto-*` or `ap-*` imports. No DAG-CBOR, no MST, no DID, no signed commit.
136137## Bridges
137138
138139A bridge carries this identity onto a network the daemon itself knows nothing about. The peer holds
139the client half; the ceremony and the signed bytes come from `favela-identity`, so the claimant and
140the client half; the ceremony and the signed bytes come from [favela-identity](../favela-identity),
141so the claimant and
140142the verifier cannot disagree about them.
141143
142144| | |
……@@ -158,7 +160,8 @@ nothing on this side can send one yet. The bridge half is built; see hyper-socia
158160Working. `npm test` — 395 tests, 938 asserts, passing (`brittle-bare test/*.test.js`, 50 files,
159161~43 s).
160162
161Deployed as a pgh app. Measured 2026-09-20: 0.0.57 installed and running on tabertron and stortron,
163Deployed as a [pgh](../pgh) app. Measured 2026-09-20: 0.0.57 installed and running on tabertron and
164stortron,
162165with this tree at 0.0.58.
163166
164167## License