Skip to content
FDE BI Evidence Workbenchobserved → compared → decided → scoped
AI-authoredmethodcurrent

Evidence and authority method

The wiki separates audit observations, workbook declarations, analytical interpretations, recorded decisions, consultant evidence and unknowns, with limitations stated beside affected findings.

fde-finance.evidence-method · wiki_7c268dbf7f8b78844080cae53f6f0a0e

Senior-authored Markdown

# Method

This build uses three evidence paths:

- the deterministic audit of the connected Power BI Desktop model;
- the inspected workbook `TargetArchitecture_Partial.xlsx`;
- an active consultant source about journal-control attributes.

Recorded consultant decision receipts provide authority for mapping confirmation and gap scope.

## Authority classes

| Authority | Use in this wiki |
|---|---|
| `observed` | Returned directly by the audit or exact workbook/evidence read |
| `declared` | Stated in the selected target workbook |
| `interpreted` | Analytical conclusion derived from evidence |
| `decided` | Confirmed by a recorded consultant or client decision |
| `consultant` | Evidence explicitly supplied by a named consultant; preserved as consultant provenance |
| `unknown` | Not established inside the selected access boundary |

## Comparison approach

The workbook's target field list was compared with normalised current-model elements. Exact qualified-name candidates were reviewed and confirmed. Cases without a current candidate descended to bounded evidence packets and were then resolved by recorded consultant decisions.

The journal-control source is separate from that process. It adds upstream knowledge but does not create target rows, mapping cases or decisions and does not rewrite the audit.

## Evidence discipline

- Existing names and data types support structural comparison, not full semantic equivalence.
- A workbook declaration is not an implementation record.
- A no-candidate result is bounded non-observation.
- A `confirm_gap` decision supports scope treatment but does not prove enterprise-wide absence.
- Consultant evidence is presented with its provenance and is not relabelled as MCP observation.
- Environment-specific capture labels are excluded from business semantics.
- Unknowns remain explicit rather than being inferred away.

## Revalidation

A later snapshot, broader estate access, approved source design, revised target workbook or recorded journal-control decision should trigger revalidation of affected pages.