Verified Functionality

Every claim on this page is anchored to observable evidence — a diagnostic run, a defect closure, a smoke test, or a dated operational proof. The internal register underlying this section holds a substantial set of items; those presented here are the ten that most directly serve a Board or Sponsor reader.

The discipline reflects how ZSF is built. No claim ahead of the evidence. No assertion beyond what the current state supports. Where a capability is in development but not yet substantiated, it is not represented here. When it lands, this page updates.

1. The board reads the material judgment on page one

   The diagnostic's cover page carries the directional position — the overall assessed dimensions, where the reporting and the evidence align, where they diverge, and the count of recommendations available to the board. A senior executive reading only page one has the substance to direct the meeting.

   What this deliversThe board meets prepared. The material to direct sits on the first page.

   Bounded scopeThe verdict is directional and quantified. The board's judgment about how to direct remains theirs.

2. The recommendations arrive ready for direction

   Each recommendation the diagnostic surfaces is specified across a defined structure: the action, the owner, the deliverable, the date, the verification the board will see when delivered, the escalation path, the criteria for the affected dimension to return to green, and the consequence at the next assurance review.

   What this deliversThe board's meeting shifts from analysis to direction. Recommendations are executable in the form presented.

   Bounded scopeThe board's judgment about which recommendations to endorse remains theirs; the diagnostic provides the framework for direction.

3. The assessment frame matches the work

   A single-project status report is assessed at project tolerance. A multi-project programme is assessed at programme tolerance. Portfolio-level reporting applies portfolio aggregation. The frame determines what the tolerance rules apply to — matching the frame to the work is the discipline that puts the recommendations the board needs in front of them.

   What this deliversThe board sees the recommendations sized to the work being assessed. Neither over-calling severity nor under-calling it.

   Bounded scopeThe frame is set at engagement; the diagnostic applies the frame consistently.

4. The report and the evidence are unravelled together

   The diagnostic reads the status report, its commentary, its footnotes, its cross-references, and its attachments. Where the reporting aligns with the evidence, the diagnostic confirms it. Where the evidence supports a different recommendation, the diagnostic surfaces the recommendation with the source cited. Where the framework expects evidence the report does not provide, the absence is surfaced as a criterion the board sees.

   What this deliversThe board reads what the whole reporting supports, not just what the summary carries.

   Bounded scopeThe unravelling works from the evidence the report contains. It does not verify the source systems underneath the report.

5. Every recommendation traces to source

   Every recommendation the diagnostic surfaces is anchored to specific evidence in the report. Where the source does not provide what a recommendation would require, the diagnostic records the absence rather than substituting inference. The diagnostic does not manufacture evidence the source material does not contain.

   What this deliversThe board directs on evidence they can point to. The recommendation and the source that supports it travel together.

   Bounded scopeThe discipline concerns evidence available in the source material provided; ZSF cannot anchor to evidence outside its input.

6. Multi-project programmes are handled as programmes

   Programmes carrying multiple projects are assessed as programmes. Each constituent project's assessed position contributes to the programme-level view under defined aggregation rules. Recommendations identify which constituent project they engage, so programme-level attention can be directed to the specific project where it most rewards.

   What this deliversThe board directs programme resources with granularity — attention to the projects that most reward it, not blanket programme-level intervention.

   Bounded scopeAggregation rules are documented and consistent. The board's judgment about resource direction remains theirs.

7. Issues predicted with dated triggers and actions

   The diagnostic identifies issues likely to crystallise at the next assurance review, with dated triggers naming the specific point at which each issue will surface if it remains unaddressed. Predicted issues arrive with the actions that address them, anchored to observable evidence patterns in the report.

   What this deliversThe board directs forward, not just backward. Issues arrive with the steps that resolve them.

   Bounded scopePredictions are grounded in evidence patterns in the current report; they do not incorporate information not present in the source material.

8. Language calibrated to organisational context

   The diagnostic's language reflects whether the organisation is government or non-government. Government programs work within assurance frameworks where compliance language applies. Non-government programs receive the same discipline framed as what sound delivery governance would apply, not as compliance requirement. The discipline holds; the vocabulary respects the reader's context.

   What this deliversThe board reads recommendations calibrated to their actual accountability — not lectured in a language that doesn't apply to their organisation.

   Bounded scopeThe organisational context is set at engagement setup; the diagnostic language reflects the setup.

9. The diagnostic itself is an audit artefact

   The diagnostic records the source material read, the assessment applied, where the assessed position aligns with the reported position, where it differs, and the criteria that anchored each recommendation. When the decision made on the diagnostic is later examined — by an audit committee, by a regulator, by an inquiry — the record demonstrates that the board directed on evidence, tested independently at the point of decision.

   What this deliversThe record of how the board directed stands the test of retrospective scrutiny. Well-founded direction and defensible record travel together.

   Bounded scopeThe audit trail records the diagnostic's own methodology and evidence; it does not audit the program itself.

10. Confidence and stability recorded per recommendation

    The diagnostic records confidence per recommendation, so the board reads each recommendation knowing how firmly it is anchored. Recommendations tied to explicit source statements carry higher defensibility than recommendations derived from pattern inference. Both are honestly named — the reader sees the reasoning behind each recommendation.

    What this deliversThe board reads the diagnostic with epistemic transparency. What is deterministic is named as deterministic; what is interpretive is named as interpretive.

    Bounded scopeConfidence and stability are recorded; the board's judgment about how to weight each finding remains theirs.

The discipline behind the page

Every capability described here has landed live. The page updates as new capabilities ship. The discipline of the update — evidence-anchored, publicly stated, honestly bounded — is the same discipline the diagnostic itself applies to the reports it assesses.

Where a capability is in development but not yet substantiated, it is not represented here. When it lands, this page adds it.