0.2.0-alpha.1

Released: March 10, 2026

This is the first public checkpoint for the canonical SFRS v2 pipeline. It should be read as an implementation milestone, not a stable compatibility promise.

Highlights

• Canonical fact-centric v2 model is live in the standard package.
• XBRL import now preserves contexts, units, facts, dimensions, footnotes, and core relationships.
• Canonical validation is profile-aware for sec-us-gaap-annual and ifrs-esef-annual.
• Canonical filings can export to both XBRL and iXBRL.
• Canonical filing packages can be generated with a manifest plus XBRL/iXBRL artifacts.
• Docs now include a dedicated release-notes section as a primary navigation surface.

Added

Canonical Model

• Canonical SFRSV2Filing types and schemas
• profile registry with executable profile definitions
• package rules for supported annual profiles

Compiler

• XBRL -> canonical v2 parser path
• typed-dimension preservation
• footnote relationship extraction
• presentation, calculation, and definition linkbase extraction
• canonical v2 -> XBRL
• canonical v2 -> iXBRL
• package generation with manifest and artifact checksums

Validation

• canonical filing validator
• profile checks for required identifier schemes
• profile checks for minimum required concepts
• stricter relationship and reference integrity rules

API

• POST /api/v1/validate with canonical v2 model support
• POST /api/v1/convert/from-xbrl with targetModel: "v2"
• POST /api/v1/convert/to-xbrl
• POST /api/v1/convert/to-ixbrl with modelVersion: "v2"
• POST /api/v1/package

Corpus

• fixture manifest and assertion schema
• synthetic SEC and IFRS fixtures
• fixture metadata workflow for later public filings
• round-trip semantic checks on the registered corpus

Known Limits

• Supported profiles are still backed by synthetic fixtures, not a broad public filing corpus.
• Output is not yet submission-grade for regulators.
• Profile completeness rules are still hand-authored minimums rather than corpus-derived coverage.
• Compatibility claims should be treated as prerelease.

Next Steps

• ingest the first public SEC annual filing fixture
• ingest the first public IFRS/ESEF annual fixture
• publish a compatibility matrix generated from real fixture outcomes
• tighten profile rules against public fixture evidence

Upgrade Notes

• Treat v1 statement-shaped documents as compatibility inputs.
• Build new integrations against the canonical v2 surface where possible.
• Do not depend on implicit profile support outside the registered profiles.