newsroom.sgit.ai / admin / comms
Comms: tasks & requests
Following the house convention: what this site needs and does not yet have, stated in public.
Open requests
| # | Request | Status |
|---|---|---|
| N1 | ~15,000 words of origin material sit in an external CBR repository, not present in the corpus this site was built from: provenance-of-trust-news.md, monetising-trust-and-knowledge__for-news-providers.md, personalised-news-feed-architecture.md. These look like where the thread began, and the library's chronology may start earlier than February 2025 once retrieved. One of the three shares a title with an already-published article — whether it is the source or a variant is unconfirmed | open |
| N2 | 83 of the 94 PDFs served from files.diniscruz.ai exist only in an S3 bucket, with no git history and no second copy. This site cites several of them as durable source artefacts; back-filling them into the source repository is a precondition for that citation actually being durable | open |
| N3 | Two published articles render a literal {{title}} as their on-page heading, including The Future of News: Building Trust Through Fact Provenance — one of this site's own core-library entries. Fix at source before it is cited further as canonical | open |
| N4 | Confirm consent from the named journalist before this site does anything with the 6 June 2025 personalised briefing beyond the bibliographic listing already on the library page | open |
| N5 | Align docs.diniscruz.ai to CC BY 4.0 for future publication, per the licence position argued on the participant disclosure, leaving already-published articles as CC0 | open |
| N6 | Specify the metering mechanism for contextual validation — how a read of a cited source is detected, attributed, priced and settled. Currently stated as open on economics rather than answered | open |
Standing tasks
- T1 — Expand /rights/, /newsroom/ and /thesis/ from single comprehensive hub pages into the full multi-page trees specified in
briefs/05, once N1 is resolved and the fuller scope is confirmed. - T2 — Write the reciprocal Risk Mandate comparison page named in the network page's Risk Mandate inversion section: "this is what the same machinery looks like pointed at corporate risk."
- T3 — Build the remaining library entries (InsightFlow, the identity-graphs piece, the practitioner-register piece, the credibility-and-time piece) out into their own synthesis pages, following the pattern already set by micro-and-nano-payments and the two rights sections.
- T4 — Decide site rendering (server-rendered vs. client-assembled) before this site moves off static HTML, given the crawler-invisibility risk stated on the network page.
For an agent
N1–N6 above are genuinely unresolved — do not assume any of them has been closed since this page was last generated without checking its current state. T1–T4 describe planned, not completed, work.