Methodology
Methodology Changelog
Customer-facing record of analytical methodology, contract, interpretation and historical-republish changes.
Current Meta methodology:
1.1 · Current confidence method: confidence_v3_l2_capacity_requiredHow to read the log
Output-affecting methodology changes are separated from docs-only changes. A historical republish states whether previously published artifacts changed and whether subscribers who cache local copies should re-pull them. Breaking API/schema compatibility is governed separately by Versioning and breaking changes.
| Date | Class | Affected | Methodology impact | History changed? | Subscriber action | Summary |
|---|---|---|---|---|---|---|
| 2026-08-27 | contract/documentation hardening | Trust, security, API/versioning, source and Evidence documentation | No analytical change | No | No | Aligned public documentation with the currently published Meta contract: 1.1 and confidence_v3_l2_capacity_required. This entry records the documentation alignment date; it does not claim the active confidence method was first introduced on this date. |
| 2026-08-13 | historical textual correction | Meta day files and aggregated Meta windows | No | Yes — descriptive status text only | Re-pull affected Meta if cached before correction | Corrected a grammatical fallback defect in status.one_liner / status-note text. No regime, score, confidence, driver or underlying metric changed. |
| 2026-07-05 | docs-only contract coverage fix | Field Dictionary and audit gates | No | No | No | Expanded Gold-field and per-chain axis documentation and added implementation-sync gates. |
| 2026-05-18 | methodology update + historical republish | Meta and Briefs | Confidence v2 / Meta 1.1 | Yes | Re-pull if cached before the republish | Introduced profile-aware data quality and label-specific confidence; structurally non-applicable fields were excluded from denominators and raw evidence was separated from confidence-degraded display scores. |
| 2026-04-21 | methodology/documentation foundation | Methodology, fields, boundaries, integrity and API docs | No additional analytical bump | No | No | Introduced the structured public trust layer, interpretation boundaries, field contract and provenance documentation. |
Future non-docs changes must state
- Exact affected chains, dates, fields and artifact genres.
- Old and new methodology/schema identifiers where applicable.
- Whether historical files were regenerated or replaced.
- Whether determinism/provenance identity changed.
- Whether subscribers should re-pull cached artifacts or change parsers.