Can the source be collected?
Use permitted RSS/Atom feeds, documented APIs or an original official record. No paywall bypass or disguised scraping.
EDITORIAL METHOD / VERSION 0.5
An honest wire is better than invented news.
The method starts with a permitted original source, keeps legal status provision specific, exposes grouping choices and records every material correction.
APPROVED DISCOURSE RECORD CONTRACT
A public-discourse record needs more than a link.
A future entry must retain its original source URL, observed and check dates, observable source identity and role, a bounded context note, a human moderation decision, deletion or removal status, and a provenance or correction handoff.
Until every field is reviewed, the record stays absent. The preview stores no post or account text and makes no platform request.
EDITORIAL PIPELINE
Six gates before a signal appears.
The Worker pipeline is built but this preview is not connected to it. Automatic discovery stays separate from publication: only static official records have passed editorial review.
What kind of source is it?
Record publisher, observable source type, collection method, original link and update history.
What is legally operative?
Separate in-force provisions, notified future commencement, consultation, explainers and editorial analysis.
Do the records belong together?
Canonical URL, title, time window and named-entity signals may propose a cluster. Discovery cards remain unreviewed until a human accepts the source and grouping basis.
Can every sentence be grounded?
Current descriptions are static and manually reviewed. Future summary modes must store provenance and may not invent quotes or conclusions.
Can a later reader see the change?
Classify the event as a correction, clarification, editorial update or source note, then retain its affected surface, evidence, reason and reader impact.
Inspect the current ledgerSOURCE LENS
Type, not a political score.
Sources are classified by an observable publishing role. DPDP.buzz does not call a source “trusted,” “biased” or “independent” without a separate published method and evidence.
- 01Government / Gazette / regulator
- 02Court or tribunal material
- 03Mainstream reporting
- 04Specialist legal or policy analysis
- 05Industry association
- 06Vendor or commercial commentary
- 07Civil-society / academic commentary
- 08Public social discourse
COMPARISON BOUNDARY
Compare record roles, not authority scores.
Side-by-side presentation can expose why two official records serve different purposes. It must not imply that later means stronger, that an explainer equals a Gazette notification or that any single record decides an organisation's obligations.
The comparison bench therefore uses only fields already visible on each source profile: publisher role, dates, pinpoint, legal-status boundary, supersession and review method. Selection is browser-local and is neither ranked nor saved.
TOPIC-DESK BOUNDARY
A watchlist is not a coverage claim.
The twelve desks organize reporting questions. They do not imply that a source, article, implementation fact or legal conclusion already exists for every topic.
Define what the desk must answer.
Each desk starts with three editorial questions so a keyword cannot become a story premise by itself.
Name the publication gate.
Three evidence requirements identify the source, status and pinpoint needed before a record belongs.
Preserve two reporting boundaries.
Every desk states what its evidence must not be stretched to imply, including compliance or future status.
Current posture: two desks have a reviewed official foundation; ten remain visibly awaiting coverage.
Open the topic directorySUMMARY PROVENANCE
Fluency is not evidence.
The site must show how a summary was made, which source records grounded it and when it was reviewed.
- Current preview
- Static editorial descriptions checked against the listed official records. No summary provider is active.
- Future deterministic mode
- Planned, not implemented. It would still require provenance tests and editorial review before activation.
- Future AI modes
- Optional and server-side only. Any activation must be labelled, grounded in stored source snippets and recorded with prompt/version provenance.
- Prohibited output
- Invented quotations, enforcement facts, source conclusions, expert credentials or claims that an article proves compliance.
CLUSTERING BOUNDARY
A cluster is a navigational judgment.
Similar records can be grouped to help readers compare what changed and who is saying it. The grouping label does not establish that two publishers made identical claims or that one source validates another.
Every cluster must preserve each original link, identify the grouping basis, allow human override and display a correction path.