Prototype governance & evidence
D2 prototype — demonstration only. Not production, not an approval record, not a screen baseline, not an API specification, not an STI integration.
- Not a D3 production implementation
- Not a requirements baseline or approval record
- Routes and view names are not official WSMS screen IDs
- No production authentication, database, gateway, payment or API
- AI is assistive only — every output is a reviewable suggestion
- Unresolved governance conflicts remain unresolved
docs/prototype-governance-notice.md · docs/prototype-source-map.md · docs/prototype-qa-report.md
Demonstration stories
Governance decisions supplied for this execution
Client-provided inputs per the production instruction — not reopened, ranked or reinterpreted; not written to the repository Decision Register by this prototype
Governance decisions outstanding
Restated from the controlled MISTI source reconciliation register. The prototype reports these decisions; it does not make, rank, anticipate or close any of them.
- Controlling register
- v1.0.2
- Register classification
- READY FOR GOVERNANCE DECISION
- Gate conditions met
- 2 / 8
- Decisions outstanding
- 15
Batch A1 — presentation and provenance labelling: A-01 · A-02 · A-04 · A-05 · A-06 · A-07 · A-08 — not approved, not implemented
Batch A2 — data-quality transparency: A-09 · A-10 · A-12 · A-13 · A-15 — not approved, not implemented
Held for governance review: A-03 · XWK-001 · Unassigned within class A: A-11 · A-14
Source package identity — whether the differently-named copies are the same files, revisions, or a different package
Current prototype treatment: revisionStatus is recorded as UNKNOWN. No copy is treated as superseding another.
Which July production figure is authoritative
Current prototype treatment: Both figures are preserved as their sources state them. Neither is selected, averaged or reconciled.
Which operator / licence denominator applies
Current prototype treatment: Each count is shown against its own source. The counts are never combined into a single total.
Identifier crosswalk, matching methodology, or permanent separation
Current prototype treatment: NO CROSS-SOURCE IDENTIFIER JOIN IS IMPLEMENTED. Each identifier is shown only within its own source.
Provenance vocabulary and the calculation-formula requirement
Current prototype treatment: The existing DataStatus vocabulary is used. The proposed revisionStatus and valueOrigin terms are not implemented.
Meaning of the pipe-type value 'ID'
Current prototype treatment: The value is displayed verbatim. No expansion or interpretation is supplied.
Approved purpose for processing personal data
Current prototype treatment: Names, gender and contact fields are excluded from the prototype entirely. Identity records are demonstration data.
Disclosure of station-identifier duplication, and which batch carries it
Current prototype treatment: Duplication is neither displayed nor de-duplicated. The item is held outside the A1 and A2 batches.
Controlled review of ID-Poor subsidy presentation
Current prototype treatment: Not presented anywhere in the prototype. Held for controlled review; the register names no decision owner (OBS-02).
Protected conflicts (preserved, not resolved)
- Source hierarchyLayered authority applied as supplied; cross-domain conflicts remain visible.DEC-R-009 (input: Option C) · All
- Workflow / SOP numberingIdentities shown by scheme (A, B/C, SRS, module spec); none selected.CFL-002 · DEC-R-002 · All
- WF-006 identityDEFERRED — not resolved by the prototype.DEC-R-001 · P0-05 · M04, M08
- M02 screen identityAppendix A reconciliation pending; prototype view names only.SCR-DEC-002 · P0-07 · M02
- M01 screen / evidence relationshipM01 v2.0 contains 0 screen IDs; 15 SCR-M01 identifiers exist only in the consolidated specification. M01-FINAL-01 not found in the repository.DEC-R-006 · P0-06 · M01
- STI single-window boundaryExternal / upstream boundary; no STI transaction workflow is drawn.CFL-011 · DEC-R-008 (input) · M04, M05, M06, M07
- API directionAPI readiness shown; module-owned intake direction remains Conditional/TBC where recorded.Four-Tier Matrix v1.0.1 §6 · M02, M03, M04, M05, M06, M07, M08, M11, M12, M13, M14, M15, M16
- SRS / requirements authorityRequirement IDs cited as SRS v1.1 (Draft).SRS v1.1 declares Draft · All
Four-Tier capability matrix (Matrix v1.0.1 §6)
Manual, Bulk and API are intake mechanisms; AI Assistant is a cross-cutting assisted capability
Data provenance
Derived from MISTI supporting evidence (read-only). Supporting evidence only — not an approved WSMS dataset or official statistic.
- • Private operator personal names, gender and contact fields are not copied (DB-b, Village Level, KML).
- • Private operators are displayed under anonymised labels; private licence numbers are masked.
- • Station coordinates rounded to 3 decimals; village coordinates to 4 decimals.
- • The DPDM list of operators under construction (personal names) is reduced to a count.
- • The PIP KML station operator name is not carried into the dataset: it names a natural person for a private operator, and the KML provides no institution-type or public/private classification. Only whether a name is recorded is carried (D-PRIV-003). The names remain in the controlled source evidence.
- • The anonymised-operator water-source cell and licence cell are withheld or fully masked in the dataset itself, not only in the interface (D-PRIV-001, D-PRIV-002).
Extracted 2026-09-30 by scripts/extract-source-data.mjs