Documents & sources
Every page on this site was written from a source, and the sources are published here rather than summarised away. Raw markdown is the source of truth; these reader pages are presentation. Each one states the single most important thing in its document, says why it is on this site, and renders the raw file in-page — so a reader page cannot drift from the document it claims to render.
This is the site whose central claim is that most articles do not provide evidence, they provide a link, and the link is never followed. Handing a reader a bare .md file and calling it "the source" is the lazy version of exactly that failure. So the document is readable where the reader already is, with its provenance stated — and still one click from the byte-for-byte original.
The brief pack this site was built from
Prepared 21 August 2026 against the-cyber-boardroom/SGraph-AI__App__Send @ v0.33.62, DinisCruz/docs.diniscruz.ai @ v0.3.123, and DinisCruz/files.diniscruz.ai. Roughly 110,000 words of source material catalogued across three corpora.
| Document | What it holds | Raw |
|---|---|---|
| 00 · The brief | Why newsroom and not news, the one-paragraph thesis, the eight themes, the four numbers, the build order, and the honesty constraint that produced /shipped/ | .md |
| 01 · Thesis and themes | Eight themes with their sources, 30+ verbatim quotations, and every citable figure on this site | .md |
| 02 · The provenance contract | The load-bearing file. Required fields, the visible rendering, the do-not-break-the-old-links rules, and the two attribution decisions | .md |
| 03 · The corpus, tiered | Every news-relevant source document, tiered by publishability, with verified paths | .md |
| 04 · The prior art | The ten published articles: verified URLs, first-published dates, authors, PDFs, LinkedIn posts. The source for /library/ | .md |
| 05 · Site architecture | Page-by-page information architecture, each page mapped to its source and publish status | .md |
| 06 · Boundaries and house style | Sibling boundaries, the Risk Mandate inversion, the redaction watch-list, house conventions | .md |
| 07 · Gaps and open questions | What must be retrieved, what must be written fresh, seven open questions, six honest tensions | .md |
| Pack readme | The pack's own index and tier summary | .md |
| What was changed before publication | The transparency note. Nine redactions, in three files, each with a visible marker — and the record of why the pack shipped unredacted in v0.2.0 | .md |
| Licence | CC BY 4.0, and the three things that grant does not extend to | .md |
The v1.1 addendum — the one document that looks forward
Everything above is material this site was built from, frozen at 21 August 2026. One document is a different kind of thing and is labelled as one rather than dated into the original pack: a publication to build.
| Document | The single most important thing in it | Raw |
|---|---|---|
| The risk & governance newsroom Commissioning brief · 25 Aug 2026 | A publication that would begin with 1,523 nodes of parsed regulation already public — where the last instance this site documents needed 200 entities before it could report competently and never built them. It is the reciprocal statement the Risk Mandate inversion promises, written as a news operation whose first customer is a risk product rather than the other way round | .md |
The debrief — the one document that looks back
A third kind of thing again, and it belongs to no construction pack: a report on work already shipped, written for the agents of the sibling *.sgit.ai sites rather than for this one.
| Document | The single most important thing in it | Raw |
|---|---|---|
| The newsroom floor Debrief · 28 Aug 2026 | An agentic team's state is the most interesting thing about it, and a table is the least interesting way to show it — so the team became a room you click around. The rule that separates it from a mock-up: every word the room speaks is derived at build time from the same files the pipeline actually runs on, and a gate fails the build if the route drawn through the desks stops matching the declared pipeline. Carries the porting recipe, the four defects we shipped into, and what one implementation on one day has not proven | .md |
The commissioning briefs — documents written to be executed
Two documents here are addressed to a builder rather than a reader: work to do, not work already done.
| Document | The single most important thing in it | Raw |
|---|---|---|
| The risk & governance newsroom v1.1 addendum · 25 Aug 2026 | A publication that would begin with 1,523 nodes of parsed regulation already public. Built, and running | .md |
| Commissioning brief: pt.newsroom.sgit.ai Commissioning brief · 13 Sep 2026 | The journalistic derogation is not available to this publication. Article 24(3) of Portugal's Lei 58/2019 conditions it on the national rules governing access to and exercise of the profession, which an unaccredited agent-produced publication does not satisfy — so the basis is legitimate interests, costing a balancing test, a published Portuguese notice and a named accountable human. Cuts fifteen departments to three and makes the acceptance test one story with its whole process visible | .md |
Machine-readable, by design
Two files in the pack are data rather than prose, and are published as data rather than wrapped in a reader page that would only get in the way:
| File | What it holds |
|---|---|
08__source-manifest.csv | 48 rows across both corpora with provenance columns: tier, origin, path or URL, title, word count, theme, proposed page, first-published date, authors, PDF, LinkedIn, publishability and why it matters |
sources__docs-diniscruz-ai.json | The machine-readable provenance record behind /library/ — every field of the provenance contract, per article, verified live on 21 August 2026 |
Every file above is fetchable at a stable constructed path: /briefs/<filename>. That is a promise rather than an accident — agents rely on constructed paths, so the convention is stated rather than left to be inferred.
What is deliberately not published
The pack tiers its own source material by publishability, and Tier 3 is excluded from this site entirely — catalogued in the manifest above so a reader can see that something was withheld and why, but never reproduced. The identifiers inside those catalogue entries are themselves redacted, with every redaction recorded in the transparency note:
| What | Why not |
|---|---|
| A named venture-capital firm, and a real planned meeting | Real third-party commercial detail, published nowhere else |
| A live product's full B2B price list and legal-entity to-do list | Real commercial detail about an operating product; the ideas are usable, the pricing and client detail are not |
| An internal investor-facing product review | Live product internals, internal-only as a class |
| A SecureDrop-style source-protection design | A safety decision, not a tidiness one. Publishing an unbuilt source-protection mechanism as though it existed would put a real source at risk if anyone relied on it before it was built. Stated on /shipped/ |
The exclusion is enforced by the pre-release gate rather than left to memory: a fixed watch-list of Tier 3 strings fails the build if any of them ever appears in the published tree. What the gate checks.
The provenance contract, applied to this site itself
Every page here that derives from previously published material carries a visible block stating the original publication date, a link to the original, the original authors including any AI co-authorship, and an honest label for how the material was curated — verbatim, edited, excerpted or synthesised. The library is the fullest expression of it; rights and economics carry it on individual sections. The full contract is document 02.
For an agent
Every document above is fetchable as raw markdown at /briefs/<filename>.md, and the two data files at /briefs/08__source-manifest.csv and /briefs/sources__docs-diniscruz-ai.json. The reader pages under /documents/ are generated projections of those files and are never the source — if the two ever disagree, the file in /briefs/ is correct. Read the pack directly for the reasoning behind every de-scoping and redaction decision rather than inferring it from the rendered pages.