Methodology

How we verify.

Every note this platform publishes has been through an adversarial verification loop before a human decides it goes live. This page states the loop, the rules it enforces, and what happens when something gets through anyway. We publish the process because the process is the product.

The loop

1. Generation from the tape. Notes are drafted against the platform's market tape: every price the writer may use arrives with its value, its as-of date, and its stated basis, drawn from the same data files that power every public page. A missing mark is stated as missing; it is never estimated.

2. Adversarial factcheck. A separate checker extracts every discrete factual claim - every date, number, price, percentage, regulatory status, and causal assertion - and verifies each one: prices against the tape, everything else against primary, dated sources by live search. Stale context is a FAIL, not a pass. Program membership and market-regime claims are never passed without a dated source.

3. Owner review. Verdicts and correction proposals land in a review queue. Corrections are accepted or rejected item by item, applied, and the note is re-checked. Nothing is public until a person has read the verdicts and pressed publish.

4. External audit. A scheduled auditor scores published notes after the fact - errors that escaped, stories missed, and where this desk led - and its lessons are committed to a doctrine file that every generating and checking agent reads. The loop learns in writing.

The mirror rule

Every price in a draft must reconcile against the platform's own published record on the same stated basis. Two dated prints on different bases - a dated spot close beside a quarterly report level - are two facts, never a contradiction. A draft price that contradicts the tape's same-basis figure, or asserts a basis the tape does not carry, fails.

Epistemic tiers

Figures across the platform carry their standing: (e) estimated from a stated method; (f) forecast from a legislated path; (a) a stated assumption, superseded the day law or data publishes. Forward balancing needs assumptions; the discipline is labelling them. Realized history and cap-basis forecasts are charted with the seam drawn, never blended.

When we are wrong

Errors that survive the loop are corrected in place and the correction is acknowledged, not buried. The audit trail - what failed, what was fixed, what lesson was committed - is part of the record. A platform that claims zero errors is hiding its ledger; ours is the product.

Verdict counts are rolling out to note footers. Questions about method: about · the notes themselves: analysis.