# WCAB normalized observation protocol, version 2 WCAB evaluates tools that inspect a baseline/candidate workbook change. Native tool reports differ, so an adapter should translate its result into this small JSON protocol before invoking `wcab score`. The protocol is deliberately separate from the fixture truth schema: a tool may keep its own report format, but its benchmark adapter has one portable target. Version 2 adds scoreable **coverage declarations**. They let the benchmark separately ask whether a tool surfaced a known static-analysis boundary rather than merely finding the surrounding formula edit. Version 1 remains available with the immutable WCAB 0.3.0 release. ## Start with a template ```bash wcab observation-template --fixtures fixtures --output observations.json # Run an adapter that replaces unsupported entries with observed evidence. wcab score --fixtures fixtures --observations observations.json \ --output score.json ``` The template is valid and marks every case `unsupported`. That is intentional: unsupported coverage is visible in the score rather than being treated as a pass. ## Document shape ```json { "schema_version": 2, "benchmark": {"fixture_schema_versions": [3]}, "tool": {"name": "example-tool", "version": "1.4.0"}, "cases": [ { "id": "structural.dynamic_reference_introduced", "status": "analyzed", "facts": [ { "fact": { "kind": "dynamic_formula_reference_added", "sheet": "Summary", "cell": "B2", "functions": ["INDIRECT"] }, "evidence": {"native_rule": "dynamic-reference-added"} } ], "review": "block", "coverage": { "declarations": [ { "expectation": { "kind": "dynamic_reference_static_coverage", "sheet": "Summary", "cell": "B2", "functions": ["INDIRECT"] }, "evidence": {"native_rule": "dependency-coverage-warning"} } ], "notes": [] } } ] } ``` `schema_version` is the observation protocol version. `fixture_schema_versions` must name the truth-schema versions the adapter analyzed. `tool.name` is required; `tool.version` is optional. Each `facts` item wraps an exact WCAB truth fact in `fact`. The optional `evidence` object is adapter-owned metadata and is never scored; it can record a native rule ID, report location, or another reproducible pointer without making one tool's report schema normative. ## Coverage declarations `coverage.declarations` contains zero or more objects with an exact truth `expectation` plus optional adapter-owned `evidence`. A declaration means that the native tool visibly surfaced that specific analysis boundary. Its matching is exact and deterministic, just like fact matching. For example, the introduced-dynamic fixture requires the `dynamic_reference_static_coverage` expectation. `INDIRECT` turns text into a reference, so a static dependency reviewer must not silently imply complete target or impact coverage. WCAB 0.5 also includes `dynamic_reference_driver_changed`: its exact expectation names both the changed driver and the unchanged dynamic formula. An adapter can use a native input-change record plus a candidate-profile feature as evidence; it need not and must not invent a resolved target value. A tool may have richer evaluation capabilities, but the declaration measures whether the boundary was made visible—not an untestable claim that every possible Excel evaluation is resolved. For a changed `INDIRECT` driver, an adapter declaration can therefore look like this (the evidence keys remain adapter-owned): ```json { "expectation": { "kind": "dynamic_reference_driver_changed", "driver": {"sheet": "Inputs", "cell": "E12"}, "formula": {"sheet": "Summary", "cell": "B2"}, "functions": ["INDIRECT"] }, "evidence": { "native_change_kind": "value_changed", "native_profile_feature": "dynamic_reference_cells" } } ``` `coverage.notes` is an optional array of human-readable adapter notes. It is not scored and is the right place to explain an intentionally unavailable mapping. Unsupported or errored cases may include notes but cannot include facts, reviews, or coverage declarations. ## Case status and review | `status` | Required behavior | Score treatment | | --- | --- | --- | | `analyzed` | May report facts, coverage declarations, and one optional `review` disposition. | Its recognized observations can contribute to recall. | | `unsupported` | Must not report facts, a review, or coverage declarations. | Explicitly counted as unsupported, never as a pass. | | `error` | Must include a non-empty `error` string and must not report facts, a review, or coverage declarations. | Counted separately from unsupported coverage. | `review` is `allow`, `review`, `block`, or `null`. A non-null disposition is compared with WCAB's reference convention and reported as **reference-policy agreement**. It is not a claim that every organization must use the same approval policy. Omitting a known case is permitted for partial runs, but it is reported as `not_reported` and cannot contribute to coverage or agreement. ## What the score means The scorer returns deterministic per-case details plus these aggregate metrics: | Metric | Meaning | | --- | --- | | `fact_recall` | Matched declared facts divided by all declared benchmark facts. | | `coverage_disclosure_recall` | Matched required coverage declarations divided by all declared coverage expectations. | | `analysis_coverage` | Cases marked `analyzed` divided by all WCAB cases. | | `review_agreement` | Cases whose analyzed review matches the reference convention divided by all WCAB cases. | | `complete_case_count` | Analyzed cases with every fact and coverage expectation matched, no unrecognized observation, and matching reference review. | | `unrecognized_fact_count` | Reported normalized facts that are not one of the case's declared facts. | | `unrecognized_coverage_declaration_count` | Reported coverage expectations that are not declared for that case. | WCAB intentionally declares targeted observable facts and explicit boundaries; it does **not** claim an exhaustive inventory of every workbook difference. For that reason, the scorer does not call unrecognized facts or declarations false positives and does not publish a precision metric. They remain reviewable evidence rather than a silent score adjustment. This follows the basic distinction between precision and recall used in the [NIST static-analysis study methodology](https://www.nist.gov/system/files/documents/2021/03/24/CAS%202012%20Static%20Analysis%20Tool%20Study%20Methodology.pdf), while respecting WCAB's deliberately partial oracle. Use `--strict` when a complete reference-policy run is required. It exits nonzero unless every case is complete and no unrecognized normalized fact or coverage declaration was reported. ## Optional FormulaFence reference adapter FormulaFence remains optional and is not a package dependency. If a trusted local executable is installed, WCAB can emit a normalized report from its existing adapter mapping: ```bash wcab formulafence-observations --fixtures fixtures \ --executable formulafence --output formulafence-observations.json wcab score --fixtures fixtures --observations formulafence-observations.json ``` The adapter copies a WCAB fact into the normalized report only after it matches the documented native FormulaFence change category. It copies an introduced dynamic-reference expectation only after FormulaFence emits `FF012`; for a pre-existing dynamic formula with a changed driver, it requires both the native `value_changed` record and the candidate profile's `dynamic_reference_cells` feature. For the external-data refresh case, it requires FormulaFence's `external_data_connections_changed` details to contain the exact connection ID and `refresh_on_load` false-to-true transition; the stored control is a fact, not a coverage declaration. For the external-data web-query source case, it requires the high-severity `external_data_connections_changed` record and `FF023` with identical safe one-web-query profiles, `source_configuration_material_changed=true`, and exactly `source_material_change_categories: ["web_query_url"]`. FormulaFence does not serialize either URL, a connection string, a command, a parameter, or a source fingerprint. WCAB's raw validator—not the adapter—then establishes the two reserved endpoint texts, the stable package graph and formula context, and the `xl/connections.xml`-only package boundary. Neither report opens a connection, fetches a URL, refreshes a query, materializes rows, calculates a workbook, or claims a client result. For the OPC package-signature Manifest case, it requires one high-severity `digital_signature_controls_changed` record and matching `FF050`: FormulaFence's redacted before/after profiles must retain one signature origin, one XML signature, one Manifest direct-part reference, no certificate/VBA/unrecognized signatures, and no relationship selectors while the direct-part category moves from one workbook part to one worksheet part. It also requires both package-signature material and Manifest-coverage flags. FormulaFence does not expose a URI, selector, digest, signature value, certificate, identity, or trust assertion. WCAB's raw validator—not the adapter—then establishes the synthetic URI transition, fixed bounded package shape, stable cells/formula, and `_xmlsignatures/sig1.xml`-only boundary. Neither report validates a digest, signature, transform, certificate, trust chain, or consumer decision. For the package-signature relationship-selector case, the adapter likewise requires one high-severity `digital_signature_controls_changed` record and `FF050`, but its before/after profiles must be exactly equal: one Manifest reference, one relationship reference, zero direct-part references, one origin, one XML signature, and no certificate/VBA/unrecognized evidence. It accepts the case only when the separate package-signature material and Manifest-coverage flags are both true. FormulaFence exposes no URI, selector, digest, signature value, certificate, identity, or trust assertion; WCAB's raw validator independently establishes the root-relationship source-ID retarget, exact transform sequence, and `_xmlsignatures/sig1.xml`-only boundary. Neither report executes a transform or validates a digest, signature, certificate, trust chain, or consumer decision. For the threaded-comment resolution case, it requires one exact high-severity `threaded_comment_controls_changed` record and matching `FF045`: FormulaFence's redacted one-thread profile retains one worksheet binding, one threaded-comment part, one comment thread/comment/person, zero replies or mentions, two local bindings, and no external or unrecognized metadata while only `resolved_comment_count` moves from `0` to `1` and `threaded_comment_definition_material_changed=true`. FormulaFence exposes no comment text, comment-cell reference, timestamp, relationship ID, comment ID, person ID, or identity data. WCAB's raw validator—not the adapter—establishes the fixed synthetic package graph, ordinary cells/formula context, and `xl/threadedComments/threadedComment1.xml`-only boundary. Neither layer proves review or approval, resolves a notification, authenticates a person, enforces authorization, opens a client, or claims workflow completion. For the legacy shared-workbook revision-log case, it requires one exact high-severity `shared_workbook_revisions_changed` record and matching `FF062`: FormulaFence's redacted before/after profiles remain equal with one header part/header, one log part, three log entries, enabled shared/tracking/history/retention/ protection controls, and no unrecognized metadata, while only `revision_log_material_changed=true` differs. FormulaFence exposes no historic value, cell location, author, timestamp, GUID, or relationship ID. WCAB's raw validator—not the adapter—establishes the fixed synthetic workbook-to-header- to-log graph, ordinary cells/formula context, and `xl/revisions/revisionLog1.xml`-only boundary. Neither layer verifies provenance or identity, replays a revision, resolves a conflict, proves review or approval, authenticates or authorizes a person, or claims workflow completion. For the QueryTable case, it requires one exact `query_table_refresh_controls_changed` record and it requires one exact `query_table_refresh_controls_changed` record and matching `FF023`: its redacted profile must retain one `ImportedData` table, connection ID 1, fixed refresh/edit/fill/growth controls, name metadata, and no opaque metadata while only `refresh_on_load` moves from `false` to `true`. FormulaFence does not expose the stored endpoint, XML part, or result rows. WCAB's raw validator—not the adapter—then establishes the direct worksheet-to-QueryTable and workbook-to-connections graph, stable saved cells/formulas, fixed connection-level control, and QueryTable-part-only package change. Neither report opens a connection, fetches a URL, refreshes a query, materializes rows, calculates a workbook, or claims a client result. For the cell-hyperlink target case, it requires one exact `cell_hyperlink_controls_changed` record and matching `FF047`: FormulaFence's redacted profile must retain one external worksheet hyperlink binding and no location, display, tooltip, or unrecognized declaration while its binding, definition material, and relationship material all change. FormulaFence does not expose the raw target or relationship ID. WCAB's raw validator—not the adapter—then establishes the fixed ID/type/mode, exact reserved-target transition, stable visible text/formulas, and relationship-part-only package change. Neither report resolves, opens, fetches, visits, or otherwise interacts with a target, or claims that a client follows it. For the external-workbook source case, it requires one exact `external_link_packages_changed` record and matching high-severity `FF025`: FormulaFence's redacted profile must retain one external workbook and source sheet, no DDE/OLE link, no cached external data, and no opaque metadata while only `source_material_changed` is set. FormulaFence does not expose the raw source target or relationship IDs. WCAB's raw validator—not the adapter—then establishes the exact reserved-target transition, fixed workbook-to-externalLink graph, stable formula context, and externalLink-relationship-part-only package change. A generic external-relationship record remains unmapped because it is not sufficient evidence for this narrower fact. Neither report resolves, opens, fetches, authenticates to, trusts, refreshes, calculates, or otherwise interacts with a source, or claims that a client updates a link or returns a value. For the external-defined-name source case, it requires both one exact `external_workbook_link_surfaces_changed` record with high-severity `FF081` and one matching `defined_name_changed` record with `FF008`. The source-surface ledger alone is deliberately insufficient: the adapter also requires the one `ScenarioRate` definition to move between WCAB's two generated qualified expressions. FormulaFence does not expose a package-member boundary. WCAB's raw validator—not the adapter—then establishes the exact definition text, absence of an `externalLink` package and `externalReferences` declaration, stable formula context, and workbook-XML-only package difference. Neither layer resolves, opens, fetches, authenticates to, trusts, refreshes, calculates, or otherwise interacts with a source, or claims a client result. For the named-LAMBDA case, the adapter requires one exact `defined_name_changed` record and `FF008` whose before/after strings match the generated `ScenarioValue` LAMBDA body. FormulaFence does not establish the raw package boundary. WCAB's validator independently proves the one-name workbook shape, exact body transition, stable inputs/calling formula/dashboard path, and workbook-XML-only difference. Neither layer evaluates the function, calculates a result, infers Excel-version support, or claims client behavior. For the Table calculated-column case, the adapter requires one exact `table_definition_changed` record and `FF013` with the stable one-Table profile and `calculated_column_formula_material_changed=true`. FormulaFence intentionally does not expose the master text. WCAB's validator independently proves the exact generated master transition, worksheet-to-Table relationship, stable row/dashboard formulas, and Table-part-only difference. Neither layer fills a column, reconciles a master with row formulas, calculates a structured reference, infers a total, or claims client behavior. For the Power Pivot/Data Model relationship case, the adapter requires one exact high-severity `power_pivot_data_model_changed` record and `FF033`. Its redacted before/after profile must retain one internal model-data part, one workbook binding, one `x15:dataModel` declaration, two model tables, one model relationship, one fingerprinted payload, and no direct/external/uninspected or unrecognized material; only `workbook_data_model_declaration_changed=true` is accepted. FormulaFence does not expose model names, keys, DAX, relationship targets, XML, or payload bytes. WCAB's raw validator independently proves the exact `DateKey`-to-`FiscalDateKey` declaration transition, fixed opaque payload, and workbook-XML-only package difference. Neither layer deserializes a model, evaluates DAX, refreshes it, calculates or renders a report, infers model-to-cell impact, or claims client behavior. For the XLM Auto_Open binding case, the adapter requires one exact high-severity `xlm_automatic_macro_bindings_changed` record and `FF076`. Its redacted before/after profile must retain exactly one automatic-macro binding, one `Auto_Open` binding, and no `Auto_Close`, `Auto_Activate`, or `Auto_Deactivate` binding; only `automatic_macro_binding_material_changed=true` is accepted. FormulaFence does not expose the macro-sheet name, cell targets, XML, package-member boundary, or macro instructions. WCAB's raw validator independently proves the `$A$1`-to-`$A$2` stored target transition, fixed byte-identical two-`HALT()` macro sheet, very-hidden state, fixed relationship/content types, and workbook-XML-only difference. Neither layer opens Excel, enables or executes XLM code, parses or emulates macro instructions, resolves a dynamic name, inspects security or trust state, infers dispatch behavior, calculates a workbook, or claims client behavior. For the sheet-protection sort-permission case, it requires one exact `sheet_protection_changed` record with high-severity `FF022`: the protected `Controls` profile must retain every action lock except `sort`, which moves from locked to permitted. FormulaFence does not establish the raw attribute or package boundary. WCAB's raw validator—not the adapter—then establishes the exact `1`-to-`0` transition, stable formulas, and worksheet-only package difference. Neither layer tests a password, encryption, authorization, an actual client sort operation, or a resulting value. For the standards-form protected-range descriptor case, it requires one exact high-severity `protected_range_permissions_changed` record and `FF022`: the redacted before/after profiles must retain one named `Controls!B2:B2` range, one legacy verifier, one security descriptor, and no opaque metadata while only `security_descriptor_material_changed=true` differs. FormulaFence must not expose an account descriptor, identity, range name, or verifier. WCAB's raw validator independently establishes the nested child, stable locked input and formula path, and worksheet-only package difference. Neither layer tests a password, encryption, authentication, authorization, editable-range enforcement, a spreadsheet client, or a resulting value. For the sensitivity-label metadata case, it requires one exact high-severity `sensitivity_label_metadata_changed` record and `FF118`: equal redacted profiles must retain one relevant custom-property part, one standard label-ID property, seven MIP properties, one label ID, one LabelInfo part, one internal LabelInfo relationship, and no malformed or external metadata, while only `sensitivity_label_metadata_material_changed=true` and `sensitivity_label_custom_properties_changed=true` differ. FormulaFence must not expose a label ID or name, action/site ID, timestamp, property name/value, LabelInfo XML, relationship ID, or target. WCAB's raw validator independently establishes the root relationship and LabelInfo shape, stable formula context, and `docProps/custom.xml`-only package difference. Neither layer resolves a label, contacts a policy service, determines effective classification, inspects encryption or permissions, infers access rights, enforces a policy, or claims Office, SharePoint, OneDrive, or storage-service behavior. For the relationship-bound worksheet-control macro-assignment case, it requires one exact critical `worksheet_embedded_controls_changed` record and `FF029`: equal redacted profiles must retain one control sheet, one worksheet control, one form-control-properties part, one control macro assignment, one related relationship, and no ActiveX, OLE, legacy VML, external, or unrecognized surface, while only `worksheet_control_definition_material_changed=true` differs. FormulaFence must not expose a control identity, shape ID, macro name, relationship ID, or raw XML. WCAB's raw validator independently establishes the bounded private assignment transition, stable formula context, and worksheet-XML-only package difference. Neither layer loads a control, inspects or executes VBA, resolves a macro, evaluates permissions, or claims Office client behavior. For the PivotCache case, it requires one exact `pivot_cache_refresh_controls_changed` record and matching `FF023`: its redacted cache-level profile must retain the worksheet source type, cache ID, and all controls except `refresh_on_load`, which moves from `false` to `true`. WCAB's raw validator—not the adapter—then establishes the `Source!A1:B5` binding, `Report!A1:B2` PivotTable location, stable stored report/dashboard cells, direct dashboard edge, and cache-definition-only package change. Neither report refreshes or renders a PivotTable. For the PivotTable aggregation case, it requires one exact `pivot_table_definitions_changed` record and matching `FF031`: FormulaFence's redacted profile must retain one PivotTable, one local cache, one data field, two cache fields, four cache records, and no other material flag except `pivot_table_layout_material_changed`. FormulaFence does not expose the source labels, selected aggregate function, or a rendered report. WCAB's raw validator—not the adapter—then establishes the local graph, stable stored cells, exact `sum`-to-`average` `dataField/@subtotal` transition, and PivotTable-part-only package change. Neither report refreshes, calculates, or renders a PivotTable. For the PivotTable Slicer-selection case, it requires one exact `slicer_timeline_cache_definitions_changed` record and matching `FF032`: FormulaFence's redacted profile must retain one Slicer cache, one local PivotCache binding, one PivotTable binding, two Slicer items, one selected item, and no timeline or auxiliary material while only `slicer_filter_state_or_definition_material_changed` is set. FormulaFence does not expose the Slicer name, selected item/value, or a rendered report. WCAB's raw validator—not the adapter—then establishes the local graph, stable stored cells, exact selected `North`-to-`South` item transition, and Slicer-cache-part- only package change. Neither report creates a visual Slicer, applies a filter, refreshes, calculates, or renders a PivotTable. For the Power Query M-filter case, it requires one exact `power_query_changed` record and matching `FF024`: FormulaFence's redacted profile must retain one parsed mashup, one formula document, one metadata item, three package parts, local permission controls, and no embedded or opaque content while only `formula_material_changed` is set. FormulaFence does not expose M text, local-table values, or a query result. WCAB's raw validator—not the adapter—then establishes the package-root custom XML binding, connection-only controls, exact local `SourceData` source, stored `North`-to-`South` M literal, and custom-XML-part-only package change. Neither report executes M, refreshes a query, materializes output, calculates a workbook, or infers returned rows. For the Scenario Manager stored-input case, it requires one exact `scenario_manager_changed` record and matching `FF035`: FormulaFence's redacted profile must retain one scenario-bearing worksheet, one scenario, two stored inputs, one selected/locked scenario, one summary reference, one formatted input, and no malformed declaration while only `scenario_definition_material_changed` is set. FormulaFence does not expose the scenario name, stored values, input references, comment, or user metadata. WCAB's raw validator—not the adapter—then establishes the generated `B2` `0.08`-to-`0.16` stored transition, stable scenario metadata, visible cells, formula path, and Inputs-worksheet-only package change. Neither report shows or applies a scenario, calculates a result, or generates a Scenario Summary. For the What-If Data Table case, it requires one exact `what_if_data_tables_changed` record and matching `FF034`: FormulaFence's redacted profile must retain one Data Table, one column-oriented one-variable table, three declared output cells, one recalculation request, no deleted input reference, and no unrecognized declaration while only `data_table_definition_material_changed` is set. FormulaFence does not expose the output range, input references, or calculated table values. WCAB's raw validator—not the adapter—then establishes the generated `D3:D5` master, exact `B2`-to-`B3` `r1` transition, stable input grid and formulas, ordinary static model/dashboard lower bounds, and Sensitivity-worksheet-only package change. Neither report substitutes inputs, calculates, resolves a circular dependency, or claims client behavior. For the list data-validation source case, it requires one exact `data_validation_changed` record and matching `FF020`: FormulaFence must expose the one list rule's `Inputs!B2` range, source-formula transition, and every entry-control attribute. It does not evaluate either source list or decide whether a future input is permitted. WCAB's raw validator—not the adapter—then establishes the exact `Lists!$A$2:$A$4`-to-`Lists!$B$2:$B$4` declaration, stable source values and ordinary formula path, direct static lower bounds, and Inputs-worksheet-only package change. Neither report accepts/rejects an entry, calculates a workbook, or claims client behavior. For the conditional-formatting threshold case, it requires one exact `conditional_formatting_changed` record and matching `FF021`: FormulaFence must expose one `Operations!B2:B4` `cellIs` rule whose only before/after rule difference is its `100`-to-`50` formula threshold. FormulaFence exposes stored rule metadata but does not render a workbook or determine which cells receive a format. WCAB's raw validator—not the adapter—then establishes the stable priority, operator, differential fill, metric values, calculation properties, and Operations-worksheet-only package change. Neither report evaluates the rule, calculates a workbook, or claims client behavior. For the custom number-format case, it requires one exact `number_format_controls_changed` record and matching `FF039`: FormulaFence's redacted before/after profiles must each contain one direct-cell custom assignment, no default/row/column or built-in assignment, no unrecognized control, and only `number_format_definition_material_changed`. FormulaFence deliberately does not expose a code or target. WCAB's raw validator—not the adapter—then establishes the declared `0.0%;[Red](0.0%);-`-to-`;;;` code transition, target/style/value/formula context, and styles-only package change. Neither report renders a format, calculates a workbook, or claims client behavior. For the stored ignored-error case, it requires one exact `ignored_error_controls_changed` record and matching `FF037`: FormulaFence's redacted profile must move from no controls to one standard container, one target range, and one `formula_range_omission` category with no unrecognized controls, while only `ignored_error_definition_material_changed` is set. FormulaFence deliberately does not expose the target range or formula. WCAB's raw validator—not the adapter—then establishes the generated `Operations!B5` target, `formulaRange=1` flag, stable cells/formulas, and worksheet-only package change. Neither report determines whether Excel would show a warning, evaluates a formula, renders an indicator, or claims client behavior. For the workbook-structure case, it requires one exact `workbook_protection_changed` record and matching `FF022`: FormulaFence's non-secret before profile must have only `lock_structure=true`, while the after profile has all three workbook locks false and neither side reports a credential or opaque metadata. WCAB's raw validator—not the adapter—then establishes the generated `workbookProtection/@lockStructure` `1`-to-`0` transition, stable hidden-sheet and formula context, and workbook-XML-only package change. Neither report tests a password, encryption, authentication, authorization, or client action. For the chart-series case, it requires one exact `chart_definitions_changed` record and matching `FF030`: FormulaFence's redacted profile must retain one host sheet, one drawing, one legacy chart, one series, three data references, no chart cache, and no related payloads while only `chart_definition_material_changed` is set. FormulaFence does not expose a chart source formula or visual result. WCAB's raw validator—not the adapter—then proves the Dashboard-to-drawing-to-chart binding, `D2` anchor, stable title/category references, exact local value-reference transition, and chart-part-only package change. Neither report calculates or renders the chart. For the external-workbook policy case, it requires the exact `external_data_refresh_settings_changed` details: `update_links` moves from `never` to `always`, while the three other workbook-wide refresh controls retain their defaults. For the array-mode case, it requires `array_formula_mode_changed` at the exact anchor with the declared legacy-CSE and dynamic modes plus the declared output range; a generic array change is not enough. For the iterative-calculation case, it requires the exact `calculation_settings_changed` details: `iterate` moves from `false` to `true`, while the explicit 100 / 0.001 bounds and other stored calculation controls remain unchanged. For the precision-as-displayed case, it requires the exact `calculation_settings_changed` details: `fullPrecision` moves from `true` to `false`, while the declared input, number format, formula, and all other stored calculation controls remain unchanged. For the saved-formula-result case, it requires one `formula_cached_result_changed` record with FormulaFence's stable two-formula/one-numeric-cache profile, exactly one unexplained cache change, and material-change evidence. FormulaFence deliberately redacts raw cache values and formula-cell locations from that record; WCAB's independent raw validator establishes the declared `Model!B2` location and `20`-to-`25` value change. For the workbook-date-system case, it requires one `workbook_date_system_changed` record and `FF117` with normalized `date1904=false` to `true`, explicit `dateCompatibility=true` on both sides, and zero unrecognized date controls. WCAB's raw validator—not the adapter—then establishes the stable serial, style, formulas, direct dependency edges, and workbook.xml-only package change; neither report calculates a date or infers a client display. For the active-AutoFilter case, it requires one exact `filter_visibility_controls_changed` record and `FF036` with FormulaFence's redacted one-filter-column/one-criterion profile and material-definition flag. WCAB's raw validator—not the adapter—then establishes the `North`-to-`South` criterion, stable `SUBTOTAL` and dashboard formulas, direct dependency edge, and report-worksheet-only package change. Neither report applies the filter, calculates a subtotal, or infers a visible row set. For the saved Named Sheet View case, it requires one exact `named_sheet_views_changed` record and `FF038`: FormulaFence's redacted profile must retain one worksheet, part, view, filter, column, and criterion; no sort rule or condition; no unrecognized control; and only `named_sheet_view_definition_material_changed`. FormulaFence does not expose the view name, IDs, bound range, or selected value. WCAB's raw validator—not the adapter—then establishes the `North`-to-`South` criterion, base AutoFilter binding, stable formulas, direct dashboard edge, and Named-Sheet-View-part-only package change. Neither report activates, renders, or applies the view, calculates a subtotal, or infers visible rows. The adapter requires one exact `xml_mapping_controls_changed` record and `FF049` for the XML Map case. FormulaFence's redacted profile must retain one map part, schema, map, data binding, file binding, table binding, and sheet-level single-cell binding with no unrecognized metadata, while only its binding material flag changes. It does not expose the schema, map, XPath, table, or cell values. WCAB's raw validator independently establishes the synthetic `NetAmount`-to-`TaxAmount` XPath transition, stable map/schema/bindings and formulas, direct dashboard edge, and table-part-only package change. Neither report accesses a file, imports or exports XML, materializes data, or infers a result. The adapter requires one exact `office_web_addins_changed` record and `FF028` for the Office Web Add-in case. FormulaFence's redacted profile must retain one declared task-pane part, task pane, web-extension part, and store reference; one locked hidden task pane; no bindings, snapshots, external relationships, in-content references, or unrecognized parts; and an auto-show count from zero to one. It does not expose add-in IDs, the store name, or the property value. WCAB's raw validator independently establishes the generated local relationship graph, false-to-true property transition, stable ordinary workbook context, and web-extension-part-only boundary. Neither report installs, loads, executes, or fetches an add-in or manifest, or claims that a task pane opens. The adapter requires one exact `worksheet_embedded_controls_changed` record and `FF029` for the embedded OLE auto-load case. FormulaFence's redacted profile must retain one control-bearing worksheet, one OLE object, one internal fingerprinted payload, and no ActiveX, VML, linked object, external relationship, or unrecognized control, while only its auto-load count moves from zero to one. It does not expose the ProgID, relationship target, content type, or bytes. WCAB's raw validator independently establishes the inert local relationship, fixed opaque bytes, false-to-true property transition, stable formula context, and worksheet-only boundary. Neither report deserializes, opens, renders, executes, registers, or invokes an object server, or claims successful loading. The adapter leaves `review` as `null`: FormulaFence surfaces evidence but does not impose WCAB's reference policy as a universal approval decision. Any intentionally unmapped fact or coverage expectation becomes an adapter note and remains missing from its respective recall metric.