Repository navigation
Federation
When the road is dark (v0.3.0e — Build 6, #226). A knock or a roster sync that cannot reach the gateway names the stage it died at and the last road tried — nothing answered in time at an address, no connection to be had, a TLS handshake that failed, a door that answered without the pinned certificate, a connection dropped mid-answer — instead of every failure reading the same did not answer. A failed knock is written to the node's federation audit log with its stage, one entry per operator-initiated attempt, the same cadence a failed sync already kept: silence in the log once again means no knock was sent.
Cards keep their kinds, and verified cards refresh (v0.3.0e — Build 6, #227). A gateway card can never become a hand-made pairing record, and a pairing record can never serve as a fedinet's gateway record: every import path — the pairing picture import, the federation import, backup restore, and sync-carried cards — refuses the other kind by name. Gateway cards are imported on the Federation page, where the gateway's signature is checked; pairing cards pair one machine from the Mesh page. And when a verified gateway card's node already has a peer record on the importing node, the import refreshes that record's card-claimed reachability — addresses, port, certificate fingerprint, name — from the card, because the knock dials the record, never the card: a record made before the federation existed (a hand pairing carrying only the gateway's LAN address) otherwise keeps its stale roads forever. Operator facts are never the card's to change: relay ticks, the tunnel route, borrow posture, pair history, and the auto-paired mark all stand. The Mesh health check names a federation-marked record whose stored addresses are a proper subset of its verified card's, and offers the same refresh as an in-place heal on that peer's card.
A gateway card used to carry every address the gateway knew for itself — its LAN address first, its declared public endpoint second. A member's bridge dials a card's addresses in order, and the field evidence showed the cost plainly: the member's bridge dialed the gateway's LAN address (an address on the gateway's home LAN, meaningless on the member's) first, the connection sat in SYN-SENT until it timed out, the dial never fell through to the public endpoint, and the automatic route fell back to a local answer while the public road sat unused in the same card.
Since v0.4.4e the local addresses are out of the gateway's card entirely. The shaping lives in the one payload builder every gateway-card render path shares — the Federation page's card, the download, the sync deck — so the embedded pairing card carries the declared public endpoint as its only address, and the gateway's own roster entry (its card facts republished under its signature, the entry members refresh their gateway records from) is shaped the same way. A gateway with no declared public endpoint mints no gateway card at all: the mint refuses, on the Federation page and at the download alike, with a sentence naming the missing declaration — declare the endpoint on the Mesh page and the card can be minted.
Pairing cards are unchanged: they keep their LAN addresses by design, because pairing is arranged between machines whose operators can meet on a network. Cards already in the field keep their old address lists; a member heals its gateway record by importing the gateway's fresh card, through the #227 verified-card refresh — reachability is replaced from the card, operator facts untouched.
One room per fedinet. FediChat (Apex | Network → FediChat) is the fedinet's own room: one per fedinet, named for it — #rockport-mesh. The operators talk; their nodes carry the messages; their Navis are in the room. Admission is the signed roster: no roster entry, no room — reading or writing — and there is no guest mode and no second room in phase 1: no direct messages, no media, no editing or deleting what was said. Through DHD the room reads and posts as your own speech — it is not a crown act and needs no Badge step-up.
The log. Every line is a record in an append-only, hash-chained log kept on the member nodes: it carries the fedinet id, the previous line's hash, the author's node id and roster number, a timestamp and the body, signed with the author's node key. A nick is a node — lines show under the node name and roster number, so a seat a member hasn't spoken from yet shows as an empty chair, not an absence. The room's header states the chain's verdict: verified, or the break named — a broken chain is evidence, never silently healed.
How lines travel. Sync is gossip: any two members compare what they hold and pull what they are missing, and any member can carry any line — the author's signature is the credential, never the carrier's — so a node that was offline catches up from whoever is home. There is no server, and the gateway is not a hub: a gateway admits, it does not rule. A line whose author is no longer on the roster is refused when it arrives new — what the room already holds stays held; expulsion stops new speech, it does not rewrite history. A tampered line and a flood past the per-author cap are refused by name, in the open.
Talking, and asking Navi. Plain lines are speech. /me acts — /me pours another coffee posts as an action, signed and chained like every line. /navi <question> asks your Navi; /navi -<user> <question> asks that member's Navi — the user is a node name or roster number, completed against the roster as the room holds it (Tab on the desktop; a tappable member list on a phone). Questions and answers post in the room, in the open, signed and logged — asking is public by design.
Navi's posture in the room. She answers only what is addressed to her node — an unaddressed question is the asker's own Navi's to answer, never a race. Her answer is bounded by her operator's sharing posture, exactly as a borrow is; the room's lines are untrusted data to her — they inform her, they never instruct her, and nothing said in a room widens what she may reveal. Room duty is her lowest-priority work: if her operator's own request is in flight she does not answer until it clears, and the question waits in the open. The muzzle in the room's settings silences her in that room entirely.
The room's settings — retention & carriage. Two of the room's rules are the operator's to set, per node, in the room's settings card. Retention — how long this node keeps the log: keep (the default) holds the whole history; 30 days prunes older lines from this node's copy, keeping the newest older line as the chain's floor so what remains still verifies. Relay carriage — whether this node's lines may travel through relay nodes to reach a member (default: allowed, under the same relay consent the Mesh page holds). A carrier can read what it carries — the room's header says so plainly whenever carriage is on. Turning it off makes the room direct-only: an unreachable member simply waits for a direct road.
The icon. FediChat's nav destination shipped in v0.5.3e with no entry in the icon table — an empty frame in the menu and the collapsed rail. It now wears the room mark: a speech bubble holding the federation triangle as three filled node-dots (Chat's bubble, Federation's triangle, Mesh's filled dots), with its own Nordic color-coding (Nord green). A nav-icon completeness bench leg resolves every destination the menu can render and refuses an empty glyph, so the gap cannot recur silently.
Names in the room. Phase 1 showed a member by node name — the machine's name, not the person's. The room is between users: lines, actions, seat lines and the members rail now read by the operator name from the operator card — the same synced, stamped value every seat of an operator agrees on (#256). The node name + roster number stay visible secondarily and remain the signing/routing identity and the /navi -<user> address. The name reaches the room as a signed presence line in the log itself: hash-chained, gossip-converged, bound to the author's node key like every room fact — nobody can wear another member's name. A node posts it before its first line under a name and again when the name changes; rename the card and the room follows on the next exchange. A member whose card carries no name yet presents by node name. /navi -<user> resolution and completion match operator names alongside node names and roster numbers — the address book grows, it never swaps.
Navi's byline. A Navi's answer presents as Navi(): — for the asker's own /navi and for a member's Navi answering /navi -<user> alike. In a room with several Navis, the answer line itself says whose Navi is speaking. The log line is unchanged (author node, kind, replyTo); the grammar is presentation, in the room and anywhere the room is read, DHD included.
Arrivals in the tray. The room joins the notifications spine (#242) as a producer: lines that newly arrive from other members — speech, actions, Navi answers — raise a tray record naming the room, one per arrival round however many lines rode it (the record's count is the round's lines; a single-line round names its author by operator name and carries the line). The bridge journals each round at merge time; the producer speaks for the journal. The operator's own lines never notify. Posture is the standing one: silent badges, Navi's announcement in chat composed from the record, and going to the record lands in the room it names with it marked read. No new controls, no new settings.
Phase 1's room was a stack of cards — a header card with the room's facts, the lines in a capped card, a members rail beside them, a settings card below — and on the operator's desk it read cramped. The room is now a chat surface in the main chat's shape, one layout language on every surface (the desktop window, DHD wide, DHD on a phone): a height-bound frame whose message list fills the room's height and scrolls internally, with the composer docked at the frame's foot. Enter posts, with the main chat's semantics; the Post button remains as the deterministic second door, and /navi -<user> completion still pops above the composer.
The members tray. The members card left the page flow. The user-list button at the room's upper left opens a tray over the room carrying the channel name and the users list — operator name primary, roster number, node name secondary, this node marked — and, when the node sits in more than one room, the channel list for switching; the tray replaces the in-page room tabbar.
The About & settings window. The header card's facts and the settings card moved into one floating window: the explanation — room name, roster size, held count, the chain's verdict, the relay-carriage sentence (a carrier can read what it carries, stated plainly whenever carriage is on), the retention state, the last round, and Sync now — above the settings menu: the muzzle, relay carriage and retention controls exactly as they were, switch-gated in their new home. On a phone (≤800px) the Settings button sits below the chat bar, stretched the full width; on wider surfaces it sits with the room's top furniture, beside the user-list button.
Nothing underneath moved: the signed hash-chained log, presence, the state payloads and the notification-tray producer are exactly as v0.5.4e left them. This build moves furniture, not plumbing.
Rooms. A fedinet holds many rooms now. The phase-1 room is the fedinet's general room — its log file, chain and membership carried over untouched; a phase-1 store loads as a fedinet with exactly one room, history intact. Every further room is a descriptor — id, name, creator node, member set, kind (general / invite / dm), vanishing term (ttlSeconds or none), case tie, revision — signed by its creator and gossiped on exchange like a line. A descriptor whose signature fails is refused by name and never materializes. Only the creator changes a room: the member set, the case tie, and dissolution are creator-signed revisions, auditable in the descriptor's rev chain.
Invite rooms are bounded by their member set at every layer: exchange offers and accepts lines only between member nodes; a non-member is never offered the room's lines, holds none of its log, and the room does not appear in its room list — its existence is not gossiped to non-members either. DMs are two-member rooms whose id derives from the unordered pair, so creating one twice (from either end) opens the same room once; a DM lists under the other member's operator name. Vanishing rooms prune lines older than their term on every honoring node, in the retention shape — the newest older line kept as the chain's floor — and a creator's signed dissolution prunes the room to its floor and refuses new lines. The room's face states the posture verbatim in substance: vanishing is honored by every member node; it is not a proof of deletion. Investigation rooms carry a case tie: the room renders its case link, the case (Case Files) renders its rooms, and a room can be created from a case or tied to one after the fact.
Media. An image posts as a line carrying the blob's sha256, byte size and media type. The blob is stored per node (under config/fedichat-media/) and carried on exchange between member nodes; a missing blob is requested by hash. A blob whose hash does not recompute — or that no held line in the room references — is refused by name and never stored or rendered. The cap is 2 MiB per image, named on refusal; jpeg, png, gif and webp only. Rendering rides the product's markdown discipline through a jailed bridge door: the hash must be referenced by a line held in the room before its bytes are served. External URLs are never auto-fetched. In vanishing rooms, blobs age out with their lines (unreferenced blobs are collected).
Presence. Typing and thinking indicators are ephemeral gossip: signed presence pings with a ten-second life, held in memory only and never written to any room log. Navi's thinking indicator derives from her real state — a question addressed to her stands unanswered in the room, owner-preemption deferral included.
The citable log. Each room's log is searchable (substring over line bodies, returning line ids with context); a result jumps to the line and lights it. Any held line can be quoted: the composed line embeds the quote (line id, author, hash fragment), and on render the quote is verified against the local chain — verified quotes render with their proof mark; unverifiable ones render flagged by name, never silently trusted.
Navi-to-Navi (#274). /navinavi -<user> <question> instructs the operator's Navi to put a question to another member's Navi. The question is a Navi-authored line, born only of that operator instruction; the target Navi answers under her own operator's sharing posture, in the open, signed by her node and logged. The loop discipline is a hard invariant: a Navi never answers a line authored by a Navi if her own last room act was also an answer to a Navi — chain depth exactly one hop; further exchange requires fresh operator speech in the room. The muzzle (now per room, the fedinet's entry standing behind it) and the lend budgets bind as before; room duty stays lowest-priority with owner preemption. A Navi may emit a referral — a case lead carrying its title, its summary, and its provenance (the room and the line it derives from). The receiving seat surfaces it as a lead card; filing uses the existing deterministic case door only, by the receiving operator's act (or their Navi's, with the bridge's receipt). The referral never files itself, and anything filed from one keeps case purity (#266): substance and custody, no machinery.
Getting started
Talking to Navi
Navi Mesh
Chips
Knowledge & RAG
Settings & updates
- Settings & persona
- DHD — Apex from anywhere
- GitHub — the pulse, issues & backups
- Installing & updating
Help