How the OWASP Wire works

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 the wire’s config, 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. When the vault has data/releases.json (wire-releases/v1: releases newest first, each with id, at, edition, title, summary, and the story ids added, updated and withdrawn), the edition shows the releases since the reader’s last visit; the desk writes it on every publish (its runbook’s step 11), as the brief asked, and the page still stands when it is missing. Three more fields are drawn when they are there and nothing breaks when they are not: a story’s changes, a list of {at, what} that the desk appends to when it corrects the story, drawn under the story; the brief’s corrections, the desk’s note of what the edition corrected, in the edition’s header; and the brief’s updated_in_edition, story ids flagged Updated like the ids a release names. A story’s edition, when it is not the current one, is said in the story’s meta line. A vault that describes itself in wire (id, title, beats, personal_persona) offers every persona but the personal one as a public lens; without it the page offers the Industry Wire’s six. A map (title, intro, entities each with id, name, kind, aliases, facts, leaders, standards, notes) is drawn as a list of entities, each with the stories whose entities values match its name or an alias. A stack (persona, what, services each with id, name, aliases, runtime, watch; extra_concerns; deadlines each with what, date, then, source; later) is drawn as the deadlines in the edition’s header and each service with the items whose delivery to the stack’s persona connects through the service’s id. 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.