reporting
What must be reported and the act of filing
reportDefinition`: templates, taxonomies, mandates · `submission`: filed reports, periods, receivers
This meta-model describes structured reporting: financial statements, statistical returns and compliance filings understood as sets of figures and assertions about a defined period, prepared against a template, filed with a receiver, validated and attested. It is its own model because the report lifecycle (prepare, file, validate, restate, attest) and the fact-in-context semantics of figures are shared across finance, regulation and statistics, distinct from the general document semantics of N1.
What must be reported and the act of filing
reportDefinition`: templates, taxonomies, mandates · `submission`: filed reports, periods, receivers
What the report says
figures`: quantitative facts with units and contexts · `assertions`: declarative statements and disclosures
Why the report can be relied on
validationChecks`: rule checks against templates · `attestationAndOpinion`: responsibility statements and external opinions
Catalogue-native findings must describe the information grouped by each layer. This legacy version does not declare them separately.
Questions, artifact requirements and serial naming rules are required by Vercy vNext; they remain unassigned in this reference version.
Format-independent core. Concrete artifact formats and naming prefixes are not declared in this legacy version.
CRUD procedures and interface bindings are not declared in this legacy version.
The neutral owner archetype is the reporting organization, which owns its reports and figures even after filing; receivers hold copies under their own mandates. Access is always granted by the owner through the catalogue's S1/S2 ownership and access models, with disclosure and reuse audited via S4.