Read this as a boundary, not a launch claim.
Current web tools are browser-only. Any release, commercial, server, account or external-service capability remains deliberately disabled until its evidence and owner decisions exist.
Finding model
Outputs distinguish present structural cues, review cues, heuristic classifications and unknown facts. They carry a source/status note and a boundary describing what the tool cannot infer.
Notice context model
The Notice Linter compares bounded, lower-cased surface, expected-data and expected-purpose terms with the draft, then reports exact matched-term counts beside visible wording and route heuristics. Rule 3 and Act section 13 cues stay separate from the local version/surface method. A Cue present state never establishes independent presentation, plain-language comprehension, factual accuracy, route usability or legal sufficiency.
Consent evidence lanes
The receipt validator shape-checks fourteen bounded fields across event identity/time, notice/purpose/surface, choice/withdrawal/propagation and integrity/provenance. Comparison checks classify added, removed or updated fields and expose receipt-ID continuity and timestamp ordering. They do not authenticate an event, prove consent, calculate a digest or test live withdrawal and processor behaviour. Raw values stay in the on-screen diff and are deliberately excluded from the downloadable report.
Inventory review lanes
The mapper normalises twelve canonical fields into system/accountability, data/people/source, purpose/movement and lifecycle/evidence lanes. Blank and explicit open phrases remain Open; Not applicable stays separate; every other value is merely Recorded. Semicolon-separated labels feed an editable source → system → recipient projection, while exact system-purpose-owner matches are flagged as possible duplicates. None of these cues discovers data, proves a flow or supplies a legal conclusion.
Parser evidence
SBOM results identify the detected format, version, parser mode and active safeguards. Nested CycloneDX JSON components are counted in preorder without recursive traversal; SPDX JSON records are validated before normalisation. Category questions come from visible name/reference patterns; finding truncation is reported rather than hidden.
Retention decision lanes
The retention builder keeps organisation policy, legal holds and other-law assertions, final Rule 8 source paths, and deletion coverage in separate lanes. A potential Third Schedule selection exposes its source class, purpose scope, period wording and warning wording; it never decides applicability or calculates a date.
Rights case lanes
The Rights Request Kit keeps intake and identity risk, system/processor search, decision/execution, and response/escalation separate. Access, correction/completion/updating, erasure, grievance and nomination-related workflows expose different Act/Rule structures. A task closes only when Complete or Not applicable carries an evidence note or rationale; no identity, exception, deadline, system action or communication is determined.
Processor review lanes
The Processor Register keeps role/purpose and chain facts, instructions/contract evidence, locations/access/safeguards, and incident/lifecycle review separate. Blank or explicit pending values remain open, real YYYY-MM-DD syntax is checked without calculating freshness, and a completed row remains an unverified assertion rather than a vendor assessment or role conclusion.
Breach evidence lanes
The breach planner maps recorded facts to the affected-person, initial Board and detailed Board structures in Rule 7. Empty, unknown and pending entries remain open; the awareness timestamp retains an explicit timezone; no deadline, obligation, recipient or legal conclusion is calculated.
Legal status
The source ledger distinguishes provisions operative from 13 November 2025, provisions scheduled for 13 November 2026, and provisions scheduled for 13 May 2027. Dates come from the Gazette commencement text, not a marketing countdown.
Evidence packet method
The workspace accepts only explicit current-result staging. Generated outputs are minimised where a tool result also contains source fields; raw inputs are excluded by default. Exact built-in synthetic notice, receipt and SBOM fixtures may be added only through a separate warned checkbox. Locally staged snapshots become stale when their instrument input changes and block export until removed or re-staged. JSON and HTML are open, deterministic interchange formats rather than proprietary blobs.
Review expectation
Tool output is a starting artefact. Operators must confirm factual accuracy, current commencement, exceptions and legal interpretation with qualified reviewers.