Report / Statement
Represent a governed factual or analytical report issue, its contextual statements, evidence, audience and issuance history.
Bundle → Layer → Finding → Questions Filled
7 bundles · 14 layers · 14 findings · 42 questions
Identity and definition One report issue and its versioned definition, distinct from recurring series and output files.
Report issue identity
A persistent report issue is an entity with attributed assertions for an audience and declared temporal scope. Its draft revisions belong to that issue; a substantive correction after issuance creates a separately identified successor issue.
Report issue identity
A persistent report issue is an entity with attributed assertions for an audience and declared temporal scope. Its draft revisions belong to that issue; a substantive correction after issuance creates a separately identified successor issue.
- Which authoritative identity distinguishes this report issue from its series and rendered files? identity
- What governed statement makes this a report rather than only an attachment or a processing log? definition
- Which reporting party is accountable for the issue, and which other parties hold rights or custody? ownership
Definition and profile binding
Pin purpose, audience and any schema or template without requiring every narrative report to use a numeric taxonomy or statutory mandate.
Definition and profile binding
Pin purpose, audience and any schema or template without requiring every narrative report to use a numeric taxonomy or statutory mandate.
- Which version of the report definition or adopted profile governs this issue? classification
- Which intended audience and reporting purpose determine the required content? requirement
- What happens when an imported taxonomy or template changes after preparation starts? constraint
Coverage and declared grain The issue declares what its statements refer to, independently of generation or release time.
Temporal and calendar context
Report scope may be an interval, an as-of instant or an explicitly justified open temporal scope. Fact-specific periods can differ. Preserve source local time without inventing an offset.
Temporal and calendar context
Report scope may be an interval, an as-of instant or an explicitly justified open temporal scope. Fact-specific periods can differ. Preserve source local time without inventing an offset.
- What reporting period or as-of scope applies, including boundary conventions and exceptions? temporal
- Which calendar identity, version, timezone and period convention interpret that scope? relationship
- How are information cutoff, generation, issuance and observation times distinguished? event
Population and output grain
Declare subject population, geographic scope and dimensional grain. Grain describes the report; the pinned disclosure policy sets the permitted ceiling and its evaluation is external.
Population and output grain
Declare subject population, geographic scope and dimensional grain. Grain describes the report; the pinned disclosure policy sets the permitted ceiling and its evaluation is external.
- Which population, subject and geographic boundary do the conclusions actually cover? spatial
- At what dimensional grain are rows, figures or assertions presented? composition
- Which incompatible aggregation or disclosure condition prevents reuse of a reported total? exception
Reported content Quantitative observations and attributed narrative assertions retain their own contexts.
Contextual figures
Figures are optional report content. Bind value to concept, subject, time and units or dimensionless status, preserving precision, estimation and missingness semantics.
Contextual figures
Figures are optional report content. Bind value to concept, subject, time and units or dimensionless status, preserving precision, estimation and missingness semantics.
- Which concept, subject, period and dimensions qualify each reported value? measurement
- What unit, scale, rounding, method and uncertainty are needed to interpret the figure? quality
- How are zero, absent, nil, suppressed and not-applicable values distinguished in this profile? validation
Narrative and analytical assertions
Separate reported observation, estimate, interpretation and recommendation, with attribution and supporting or contrary evidence. Narrative-only reports remain possible.
Narrative and analytical assertions
Separate reported observation, estimate, interpretation and recommendation, with attribution and supporting or contrary evidence. Narrative-only reports remain possible.
- What exactly is asserted, in which language and with what epistemic status? definition
- Which author and evidence support or challenge each material assertion? evidence
- Which figures or other assertions does this statement depend on, and what is missing? relationship
Production and quality evidence Consume external processing and assessment evidence without owning their execution engines.
Production lineage
A prepared issue pins one or more processing-run references as evidence, including governed manual preparation where applicable. The run master owns run lifecycle and input execution details.
Production lineage
A prepared issue pins one or more processing-run references as evidence, including governed manual preparation where applicable. The run master owns run lifecycle and input execution details.
- Which processing runs and immutable input snapshots contributed to this exact revision? provenance
- Which method and parameter bindings explain the transformation into report content? process
- Why does a successful execution result fail to establish issuance or publication? state
Quality and validation evidence
Validation outcomes qualify a specific revision against identified rules or metrics. Schema success, substantive reliability and external assurance are separate claims.
Quality and validation evidence
Validation outcomes qualify a specific revision against identified rules or metrics. Schema success, substantive reliability and external assurance are separate claims.
- Which rule set and quality metrics were assessed against the exact report revision? validation
- Which failures, warnings, unchecked rules or waived exceptions remain material? exception
- What confidence and limitations may a reader infer from the assessment evidence? quality
Authority and disclosure Accountability and audience-specific disclosure are explicit gates around report issuance.
Approval and assurance scope
Issue authority, preparer attribution and external assurance are distinct role-qualified evidence. An attestation is optional unless an adopted profile requires it.
Approval and assurance scope
Issue authority, preparer attribution and external assurance are distinct role-qualified evidence. An attestation is optional unless an adopted profile requires it.
- Who may authorize issuance of this revision, under which delegated authority? authority
- What does each responsibility statement or external opinion actually cover? evidence
- Which changes invalidate a prior approval or require a renewed opinion binding? lifecycle
Disclosure policy binding
Pin the policy identifier, version, target, audience, purpose and effective context used to assess the proposed output. This model records the decision reference and permitted-view binding, not policy evaluation or suppression algorithms.
Disclosure policy binding
Pin the policy identifier, version, target, audience, purpose and effective context used to assess the proposed output. This model records the decision reference and permitted-view binding, not policy evaluation or suppression algorithms.
- Which exact policy tuple and external decision govern disclosure of this issue view? security
- Which content or metadata is withheld or reduced, and what explanation may the recipient see? privacy
- What blocks release when a policy decision is absent, expired or inconsistent with declared grain? access
Issuance and correction Issuance is a report-owned decision; transmission, recipient acceptance and publication remain separate.
Issue state and distribution references
Proposed states are draft, ready, issued, superseded and withdrawn. Readiness requires resolved identity, scope, content, production evidence, authority and disclosure. Local state recording does not send or publish content.
Issue state and distribution references
Proposed states are draft, ready, issued, superseded and withdrawn. Readiness requires resolved identity, scope, content, production evidence, authority and disclosure. Local state recording does not send or publish content.
- What evidence supports the current report state and its last authorized transition? state
- Which explicit readiness conditions remain unmet before issuance? requirement
- Which publication or filing events refer to the issued content without changing its identity? relationship
Correction and withdrawal
Post-issue substantive content changes create a new issue linked to its predecessor. Restatement, withdrawal and replacement retain scope and reason without promising indefinite payload retention.
Correction and withdrawal
Post-issue substantive content changes create a new issue linked to its predecessor. Restatement, withdrawal and replacement retain scope and reason without promising indefinite payload retention.
- Which earlier issue or specific assertions are corrected, replaced or withdrawn? lifecycle
- What reason, authority and impact justify the correction while preserving prior reliance context? decision
- How are correction chains kept unambiguous when multiple successors or withdrawn issues exist? validation
Representations and managed persistence Report meaning survives format changes while rendition custody and exchange conformance are delegated.
Rendition and record bindings
Zero or more immutable record artifacts may represent an issue. A rendition or bibliographic edition never substitutes for issue identity; custody, fixity and retention remain record-owned.
Rendition and record bindings
Zero or more immutable record artifacts may represent an issue. A rendition or bibliographic edition never substitutes for issue identity; custody, fixity and retention remain record-owned.
- Which immutable records and renditions represent the exact issue or approved view? composition
- Which representation changes preserve meaning, and which require a successor issue? classification
- Which external retention decision governs payload availability and any remaining lawful locator? retention
Exchange and semantic loss
External vocabularies are optional alignments with explicit version and mapping limits. No XBRL, Data Cube or SDMX conformance is claimed by this research hierarchy.
Exchange and semantic loss
External vocabularies are optional alignments with explicit version and mapping limits. No XBRL, Data Cube or SDMX conformance is claimed by this research hierarchy.
- Which exact exchange profile, vocabulary versions and mapping apply to the selected export? interoperability
- What context, precision, language, missingness or assurance evidence would the projection lose? constraint
- Which round-trip and adversarial fixtures must pass before that mapping is operational? validation
Classifiers Filled
- Family
- World Models
- Category
- Information and virtual systems
- Entry kind
- entity
- Navigation path
- NAV.INF.REC.RPT
- Domain
- INF.REC.RPT
- Industry
- Cross-industry
- Tags
- reportstatementinf.rec.rpt
- Also called
- N2
What it is Filled
One persistently identified report issue, including preparation revisions and immutable issued content bindings. Definitions and recurring series are references. Reporting scope may be an interval, as-of instant or justified open scope. The hierarchy is a proposed cross-domain research structure, not a universal filing standard.
In scope
- Issue identity, versioned definition, audience and accountable reporting role
- Reporting scope, calendar binding, population and declared output grain
- Optional figures and narrative assertions, with at least one material statement for readiness
- Evidence-qualified local readiness, authority binding, issuance and correction lineage
- References to runs, disclosure decisions, records, publication operations and editions
Out of scope
- Processing execution, scheduling and run lifecycle
- Record custody, fixity computation, retention enforcement and storage engines
- Publication transport, delivery guarantees and regulatory filing acceptance
- Disclosure policy evaluation, suppression algorithms and legal permission adjudication
- Calendar arithmetic and calendar lifecycle
- Accounting standards, statistical methodology, external audit opinions and signature services
- Domain-specific weapon, detention or controlled-item operational instructions
Why it exists Filled
Represent a governed factual or analytical report issue, its contextual statements, evidence, audience and issuance history.
Distinguishing features Derived, awaiting review
- Unlike WM-ACT-053: Pin one or more processing-run references for a prepared issue, including governed manual preparation. Run execution, scheduling and run lifecycle remain target-owned.
- Unlike WM-REC-001: Zero or more record and rendition bindings; external master owns custody, fixity and payload retention.
- Unlike WM-ACT-044: Zero or more publication operations reference the issue; distribution and issuance are distinct lifecycles.
- Unlike WM-XCT-003: Pin exact disclosure policy identity/version/target/audience/purpose/context; consume external assessment. Report declares grain; policy controls the permitted ceiling.
- Unlike WM-MED-003: Optional bibliographic publication or edition identity; it cannot replace report issue identity.
- Unlike WM-XCT-009: Pin calendar identity, version, timezone and period convention. Arithmetic and calendar lifecycle stay external.
- Unlike WM-ECO-018: Financial statements are a specialized neighboring report domain; accounting policy and financial recognition rules are excluded here.
- Unlike WM-ECO-033: Regulatory filing holds submission, authority receipt and acceptance semantics; report issuance alone establishes none of those outcomes.
- Unlike Legacy N2 and unreviewed supplement: Reconciled as leads only: remove mandatory filing, numeric figures, attestation and exclusive reporter ownership; preserve contextual facts and correction lineage. Do not inherit wildcard imports or legacy conformance labels.
Note: Derived from boundary notes against neighbouring models.
What robots and AI may and may not do Derived, awaiting review
Must not
- Deny access unless the adopting policy permits actor, purpose and exact view; intended audience alone is insufficient.
- Record exceptional grants with scope, authority, expiry and external decision reference; local research never grants a universal bypass.
May
- Register a draft issue: Proposed local operation, not implemented: Assign identity and bind a versioned report definition and scope.
- Record proposed report content: Proposed local operation, not implemented: Attach attributed assertions or contextual facts to an editable revision.
- Bind assessment and production evidence: Proposed local operation, not implemented: Attach exact external run and assessment references without invoking their engines.
- Assess local binding completeness: Proposed local operation, not implemented: Check the proposed local readiness conditions; consume externally supplied decisions without evaluating disclosure policy.
- Record authorized issuance: Proposed local operation, not implemented: Record an already authorized issue decision for exact content.
- Link an authorized correction: Proposed local operation, not implemented: Create a successor draft or attach an authorized withdrawal decision.
Note: Derived from functions, policies, CRUD and access rules; prohibitions were not authored for agents as such.
Moral aspects Missing, in the backlog
Not described yet. This gap is in the card backlog.
Owners Filled
Steward
Neutral owner archetype: reporting organization or accountable reporting body, with identified report steward.
Roles
- Report steward
- Maintain issue identity, profile and accountable-party bindings.
- Preparer
- Record contextual content and source limitations without simulating approval.
- Reviewer
- Assess exact revision evidence and unresolved quality issues.
- Authorized issuer
- Authorize the specified issue and view within documented delegation.
- Disclosure custodian
- Provide externally evaluated policy decision references and scoped exception evidence.
- Records custodian
- Own external artifact custody, fixity and retention decisions.
Links to other meta-models Filled
references
- WM-ACT-053 - Pin one or more processing-run references for a prepared issue, including governed manual preparation. Run execution, scheduling and run lifecycle remain target-owned.
- WM-REC-001 - Zero or more record and rendition bindings; external master owns custody, fixity and payload retention.
- WM-ACT-044 - Zero or more publication operations reference the issue; distribution and issuance are distinct lifecycles.
- WM-XCT-003 - Pin exact disclosure policy identity/version/target/audience/purpose/context; consume external assessment. Report declares grain; policy controls the permitted ceiling.
- WM-MED-003 - Optional bibliographic publication or edition identity; it cannot replace report issue identity.
- WM-XCT-009 - Pin calendar identity, version, timezone and period convention. Arithmetic and calendar lifecycle stay external.
- WM-ECO-018 - Financial statements are a specialized neighboring report domain; accounting policy and financial recognition rules are excluded here.
- WM-ECO-033 - Regulatory filing holds submission, authority receipt and acceptance semantics; report issuance alone establishes none of those outcomes.
aligned
- XBRL OIM 1.0 - Optional contextual business-fact mapping to the pinned 2021 recommendation; conformance requires tested profile bindings.
- SDMX 3.1 - Optional statistical exchange alignment; technical packages and executable mapping remain unverified.
- PROV-O - Use attribution, derivation and revision as conceptual alignment; no truth or authority guarantee follows from a provenance edge.
- RDF Data Cube - Optional dimension/measure/attribute mapping for quantitative content; narrative assertions need separate mapping.
neighbor
- WM-ACT-053 - Pin one or more processing-run references for a prepared issue, including governed manual preparation. Run execution, scheduling and run lifecycle remain target-owned.
- WM-REC-001 - Zero or more record and rendition bindings; external master owns custody, fixity and payload retention.
- WM-ACT-044 - Zero or more publication operations reference the issue; distribution and issuance are distinct lifecycles.
- WM-XCT-003 - Pin exact disclosure policy identity/version/target/audience/purpose/context; consume external assessment. Report declares grain; policy controls the permitted ceiling.
- WM-MED-003 - Optional bibliographic publication or edition identity; it cannot replace report issue identity.
- WM-XCT-009 - Pin calendar identity, version, timezone and period convention. Arithmetic and calendar lifecycle stay external.
- WM-ECO-018 - Financial statements are a specialized neighboring report domain; accounting policy and financial recognition rules are excluded here.
- WM-ECO-033 - Regulatory filing holds submission, authority receipt and acceptance semantics; report issuance alone establishes none of those outcomes.
- Legacy N2 and unreviewed supplement - Reconciled as leads only: remove mandatory filing, numeric figures, attestation and exclusive reporter ownership; preserve contextual facts and correction lineage. Do not inherit wildcard imports or legacy conformance labels.
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Filled
- Authoritative master-system identifier
- Governed global identifier or IRI
- Dimension-assigned UUID or ULID
Direct properties not applicable Not applicable
Not applicable
Institutional or informational subject: no invented physical properties.
Recognition optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Filled
- Register a draft issue: Proposed local operation, not implemented: Assign identity and bind a versioned report definition and scope.
- Record proposed report content: Proposed local operation, not implemented: Attach attributed assertions or contextual facts to an editable revision.
- Bind assessment and production evidence: Proposed local operation, not implemented: Attach exact external run and assessment references without invoking their engines.
- Assess local binding completeness: Proposed local operation, not implemented: Check the proposed local readiness conditions; consume externally supplied decisions without evaluating disclosure policy.
- Record authorized issuance: Proposed local operation, not implemented: Record an already authorized issue decision for exact content.
- Link an authorized correction: Proposed local operation, not implemented: Create a successor draft or attach an authorized withdrawal decision.
Hazards and failure modes optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Derived, awaiting review
- PROV-O: The PROV Ontology
- RFC 3339: Date and Time on the Internet: Timestamps
Context of use required Filled
- Standards are optional conceptual alignments, not jurisdictional mandates.
- No universal period length, attestation, filing requirement, rights transfer or retention duration is asserted.
Sources Filled
- DCMI Metadata Terms - Dublin Core Metadata Initiative
- PROV-O: The PROV Ontology - World Wide Web Consortium
- Open Information Model 1.0 - XBRL International
- The RDF Data Cube Vocabulary - World Wide Web Consortium
- Data on the Web Best Practices: Data Quality Vocabulary - World Wide Web Consortium
- ODRL Information Model 2.2 - World Wide Web Consortium
- RFC 3339: Date and Time on the Internet: Timestamps - Internet Engineering Task Force
- SDMx Technical Specifications - SDMX Sponsors
Open questions
- Restore independent external review before any canonical or publishable-draft promotion.
- Verify source versions, errata, licensing and linked technical packages outside the blocked sandbox, separately from HTTP success.
- Develop qualified narrative, financial and statistical adoption profiles with exact authority, disclosure, calendar and retention bindings.
- Implement and test nested schemas and round-trip fixtures for contextual duplicates, suppressed values, local time, stale approvals, corrections, multilingual views and lawful payload disposal.
- Executable nested schemas, instance fixtures and mapping conformance are not implemented.
- Specialist statutory filing, accounting, assurance, statistical disclosure and retention profiles require qualified review.
- Direct HTTP status, current releases, licensing and applicability require coordinator verification; DQV dated release and linked SDMX packages are not pinned.
- Narrative, multilingual, corrected and confidential report adoption needs representative field evidence.
Machine files
Provenance
world-models research · reviewable-draft
Built from: models/wm-rec-002-report-statement/spec.yaml