Context and decision
Corporate strategy is easy to describe and much harder to verify. Annual filings contain carefully framed priorities, while the evidence of execution is spread across capital expenditure, operating metrics, margins, and several years of reported facts.
Narrative vs. Numbers brings those two records together. It asks what management said was strategically important, which financial signals ought to move if the claim is being acted on, and whether the observed history supports, weakens, or leaves that claim unresolved.
The decision is company- and filing-specific. The system does not label management generally credible or incredible, and it does not claim that alignment makes the strategy good. It tests whether stated priorities and visible execution point in the same direction.
Alternatives considered
Summarize the 10-K with a language model
ForA generated summary would make a long filing easier to understand and could surface management's current themes quickly.
AgainstComprehension alone does not test whether spending and operating results support the stated priorities.
Build a conventional financial-ratio dashboard
ForA ratio dashboard would stay grounded in reported numbers and be familiar to a financial reader.
AgainstIt would not connect those numbers to the strategic claims management asked investors and operators to believe.
Ask a language model to judge alignment directly
ForA model could consider more context and handle unusual language without a fixed evidence taxonomy.
AgainstIt is rejected as the scoring engine because the financial judgment would be difficult to audit, reproduce, and distinguish from persuasive language.
Method and model
The latest 10-K supplies the current strategy. A language model is limited to returning a priority label, one category from a fixed taxonomy, the source quote, and extraction confidence. Categories outside the taxonomy are discarded rather than improvised.
Each accepted category maps to approved financial signals with a required direction and threshold. SEC XBRL facts are normalized into annual metrics, then action evidence, outcome evidence, and persistence are calculated. With all components present, alignment equals 0.50 times action evidence, 0.30 times outcome evidence, and 0.20 times persistence.
A component with no data is not scored as zero. Its weight is redistributed across available components and the gap is carried into the limitations. Analytical confidence is calculated separately from extraction certainty, evidence coverage, and available history.
Evidence and results
The system is deployed and can analyze one public company and filing at a time. The live page includes a Microsoft example drawn from its 10-K for the year ended 30 June 2026, placing a capacity-expansion claim beside changes in capital expenditure, property and equipment, and capital-expenditure intensity.
That example demonstrates the product's claim-by-claim structure and the distinction between management language and computed evidence. It is not a general recommendation about Microsoft, and the tool's overall judgment depends on every extracted priority, available metric, limitation, and confidence value in the run.
The current evidence establishes that the ingestion, normalization, mapping, scoring, contradiction, and confidence paths run over SEC data. It does not establish that the taxonomy captures every strategically relevant signal or that the score predicts performance.
SEC filing and XBRL record
Measured, partialThe system resolves a public-company ticker, reads the latest 10-K for current strategic priorities, and retrieves normalized annual facts from the SEC company-facts record for the requested history.
Sources: src-narrative-sec, src-narrative-demo
Deterministic alignment model
Measured, partialAlignment is computed as 0.50 action evidence, 0.30 outcome evidence, and 0.20 persistence when all components are present. Missing components have their weight redistributed and are listed as limitations rather than scored as zero.
Sources: src-narrative-readme
Separate analytical confidence
Measured, partialExtraction confidence, mapped-metric coverage, and available history produce an analytical-confidence measure that is displayed separately from alignment, preventing a strong score on thin evidence from reading as certainty.
Sources: src-narrative-readme, src-narrative-demo
Interpretation
The central distinction is deliberate: AI interprets the filing; data grounds the claim; code performs the financial judgment. A model swap can change which priorities are extracted, but it cannot silently change the arithmetic used to score them.
The most useful disagreement is therefore specific. A reader can challenge the extracted claim, its category, the approved metric, the direction, the threshold, the observed value, or the confidence instead of accepting or rejecting one opaque verdict.
Trade-offReconstructible scoring over semantic freedom
A fixed taxonomy cannot capture every possible strategic nuance, but it keeps the financial judgment tied to approved metrics, directions, thresholds, and arithmetic.
Trade-offCurrent strategy over historical narrative drift
The latest 10-K supplies the current priorities while earlier periods supply financial history. The MVP does not yet test how management's stated strategy changed across filings.
Trade-offVisible gaps over complete-looking scores
Missing evidence lowers coverage and may redistribute component weights. The report is messier because it states the gap, and more honest because it does not quietly turn absence into a neutral observation.
Limitations
Current strategy is read from the most recent 10-K. Historical years primarily provide financial persistence and do not yet show how the strategy narrative itself changed over time.
Evidence depends on the configured strategy-category-to-metric mapping. Relevant qualitative execution or unmapped operational signals may be absent from the score.
Missing components are shown and their weights redistributed, language-model extraction can be imperfect, and analytical confidence must remain distinct from alignment. Alignment is not proof of causality or strategic quality.
OpenExtraction quality
A language model identifies and categorizes strategic priorities from Item 1 and Item 7. It can miss, overstate, or misclassify a claim even though its source quote and extraction confidence remain visible.
OpenEvidence-map coverage
A strategic claim can matter without mapping cleanly to the metrics allowed for its category. The system can only score the evidence framework it has been given.
OpenAlignment is not causality
Movement in spending or outcomes consistent with a claim does not prove that the stated strategy caused it or that the strategy is economically attractive.
Next test
Create a human-reviewed set of strategic-priority extractions across several industries and report category-level misses and disagreements before broadening the taxonomy.
Have strategy and finance reviewers inspect the same claim-level reports, record which part of the evidence chain they dispute, and test whether the exposed arithmetic makes those disagreements more precise.
Sources
src-narrative-readme Narrative vs. Numbers — public repository documentation
Public repository documentation describing 10-K ingestion, strategy extraction, SEC XBRL normalization, deterministic alignment scoring, confidence, caching, and known limitations. The alignment formula shown on this site was verified against the implementation.
src-narrative-sec US Securities and Exchange Commission filings and XBRL data
Public 10-K filing text and company-facts XBRL records used by the application to connect management's stated priorities with normalized annual financial evidence.
src-narrative-demo Narrative vs. Numbers — production deployment
Running production deployment inspected on 14 September 2026 to verify the end-to-end workflow and the Microsoft example represented by the product schematic.