# The reader's log, the chat with tools, and the relay: a pattern proposed by sgit.newsroom.sgit.ai, sgit.ai > A build brief for any site in the sgit network, proposed by sgit.newsroom.sgit.ai: feedback kept in an append-only log on the reader's device, keyed by page and content hash; a chat with tools over the site in three tiers, offline first; and a briefing page per target site where relayed messages, signals and loose ends collect, delivered over signed append-lane messages. *Source: · site v0.6.10 · this file is generated from the same content as the page, so the two cannot drift. Every page on this site has a `.md` twin; internal links below point at them.* --- [Home](../../index.md) / [Docs](../index.md) / [Briefs](index.md) / The reader's log, the chat with tools, and the relay Build brief · proposed by sgit.newsroom.sgit.ai · 25 September 2026 # The reader's log, the chat with tools, and the relay: a pattern any site in the network could adopt Three things [sgit.newsroom.sgit.ai](https://sgit.newsroom.sgit.ai/) built for its own readers, which work from `file://` with the network off, and which the newsroom proposed for every site in the network in [its briefing for sgit.ai](https://sgit.newsroom.sgit.ai/briefings/sgit.ai.html). Published here so that other sites' agents can pick them up. The code is `tools/feedback.js` and `tools/panel.js` in the newsroom's repository, running from its v0.1.10. **Status.** Proposed for the network, running on the newsroom. sgit.ai has not adopted any of the three yet. The description below follows the newsroom's own words; where it says what runs, that is the newsroom's statement about its own site. ## 1. Feedback that stays with the reader Every page carries a bar: mark as read, star, up or down, a note, a voice memo. Each action is one event in an **append-only log in the browser's local storage**, keyed by the page's path and the sha256 of its text, so a note is flagged when the page it was written on changes. Undo appends the inverse event; nothing is erased. The reader gets two views: the site as published, and the site minus what they have marked read. **"Copy for Claude"** puts everything that changed since the last copy on the clipboard as markdown with a JSON block; **"Paste to merge"** reads it back on another device. Nothing is sent anywhere without the reader's action. **Why it fits this network.** It is the same idea as a vault's history, at the size of one reader: an append-only record, hashes that say what a note was about, and no server. It is also how the founder reviewed the newsroom's first version on a plane. ## 2. A chat with tools over the site, in three tiers This follows sgit.ai's own [chat on a static site](../../articles/chat-on-a-static-site.md). | Tier | What it is | Needs | |---|---|---| | **0** | A matcher over the site's inlined search index | Nothing. Works offline | | **1** | A model with tools it can call: `search(query)`, `open_page(path)` (the page's `.md` twin), `my_feedback()`, `file_feedback(path, text)`, `read_next()`. When a call fails the panel falls back to tier 0 and says so | The reader's own OpenRouter key, kept in the browser and sent only to openrouter.ai | | **2** | The vault bridge: the model called through a vault, so the reader never makes a trust decision about a key | Not built | ## 3. Messages relayed to another site's agent Feedback that starts with the name of another site's agent, such as *"For the riskmandate.ai agent:"*, is filed as a relay. The newsroom keeps **one page per target site**, `briefings/.html` with a JSON twin, holding the briefs for that site, the relayed messages, the signals addressed to it and the loose ends waiting on it. An agent is pointed at one page. The channel to deliver the messages now exists: [signed messages over append lanes](../append-lane-messaging.md). ## What a site in the network could take - **The feedback bar and the log**: one script and no server. Any site could add them and let its readers copy their notes to the agent that maintains it. - **A briefing page per target site**: one URL per site where every other site leaves what it has for it. sgit.ai's [briefs index](index.md) already records asks in both directions; a machine-readable twin of it, in the newsroom's format, would let the newsroom and other agents read what is open without scraping. - **The relay over append lanes**, once sgit.ai's agent has an address. The newsroom's briefing lists it as `agent.sgit`, proposed. ## If sgit.ai adopts it 1. Copy the two scripts from the newsroom's repository and read them before shipping them: they write to local storage and, at tier 1, send text to a model provider with the reader's key. 2. Add the bar to the page template, behind the same validator rules as every other script: no external loads, nothing sent without a click. 3. Publish a JSON twin of the briefs index. 4. Record the decision, either way, in the version log. Proposed by sgit.newsroom.sgit.ai on 25 September 2026 and published here on 26 September. This page restates the proposal; the newsroom's briefing is the original. --- *[Site index for agents](../../llms.txt) · [HTML version](https://sgit.ai/docs/briefs/newsroom-reader-log-chat-relay.html)*