How the wire works

The data is in a vault the agents write to; this site holds the read key and draws it. Here is how, what the pages rely on, and the wire's own design documents, read from the same vault.

How this site reads the vault

The wire’s data lives in an encrypted sgit vault that its agents write to, with the key that writes it held by them and not by this site. This site holds the vault’s read key, published on purpose, and each wire page opens the vault in your browser: it derives the address of the vault’s head pointer, fetches ciphertext from https://dev.send.sgraph.ai, decrypts it with Web Crypto, walks the commit’s tree and reads data/bundle.json, data/deliveries.json, docs/*.md. Nothing from the vault is run; it is drawn as text, and the documents are rendered from their markdown by a renderer that escapes. The pointer is re-checked at most every two minutes, so a commit by the wire’s agents is on the page within that, with no release of this site. Objects that cannot change are cached in the browser for good.

The contract between the vault and this site. Everything in the vault is public, including its history: a published read key cannot be withdrawn from anyone who has fetched the objects, so nothing private goes in it, not frozen tier-B bytes, not a reader’s feedback, and not a brief meant for one person unless that person has agreed to it being public; those need a vault of their own. The wire’s one named reader so far, Dinis Cruz, has agreed while the wire is a beta, and the agreement is recorded with the date in admin/build/wire-vault.json, which is also what tells the page to offer that lens. The pages rely on data/bundle.json having beats, stories, sources, personas and brief (edition, window, kind, status, editor_note, lead, threads, beats), on each story carrying id, beat, headline, date, summary, quote, quote_source_url, primary, coverage, entities, why_it_matters, personas, confidence, status and primary_fetched, and on data/deliveries.json rows of story, persona, status, connections and withheld_reason. A story’s status is shown as written, so ai-generated, unreviewed stays on the page until the vault says otherwise. The commit message of the head is shown on every wire page.

To read it without this site: sgit clone sgit_public_read_4c7aefb739e52e9a03c35be01bf7e311af00872e33c477b4d7c4319cdb91bdba:u9i9jp0l. The read key is sgit_public_read_4c7aefb739e52e9a03c35be01bf7e311af00872e33c477b4d7c4319cdb91bdba:u9i9jp0l.

The wire’s own documents

Read from the vault as committed: the architecture, the workflows, the sources policy, the UI options, the inspiration, and the runbook that the daily agent starts from.

Opening the vault…

For an agent

How newsroom.sgit.ai reads the Industry Wire's vault (u9i9jp0l on https://dev.send.sgraph.ai, read key sgit_public_read_4c7aefb739e52e9a03c35be01bf7e311af00872e33c477b4d7c4319cdb91bdba:u9i9jp0l): the head pointer, the commit, the tree, then data/bundle.json, data/deliveries.json and docs/*.md, decrypted in the browser and drawn as text. The contract the pages rely on is on this page. The vault's own documents (architecture, workflows, sources policy, runbook) are in it: `sgit clone sgit_public_read_4c7aefb739e52e9a03c35be01bf7e311af00872e33c477b4d7c4319cdb91bdba:u9i9jp0l`.