{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-eco-033","code":"wm-eco-033-regulatory-filing-disclosure","url":"https://ver.cy/models/wm-eco-033-regulatory-filing-disclosure/","name":"Regulatory Filing / Disclosure","alternateNames":[],"kind":"world-model","status":"published","version":"0.3.0-research.1","language":"en","classifiers":{"family":"World Models","category":"Society, people and institutions","entryKind":"aggregate","plane":"","domain":["SOC.ECO.REG"],"industry":["Cross-industry"],"navPath":"NAV.SOC.ECO.REG","tags":["regulatory","filing","disclosure","soc.eco.reg"],"facets":{}},"whatItIs":"Owns filing and revision identities; periodic, event-driven, initial, amended, corrected, restated, replacement, withdrawal and nil classes; reporting-entity, registration, LEI, account, obligation, period, jurisdiction, preparer, reviewer, approver, signer, transmitter, publisher, repository and regulator bindings; cover metadata, sections, tables, rows, columns, cells, forms, schedules, exhibits, narratives, notes, methodologies and attestations; reported facts, concepts, contexts, dimensions, units, values, decimals, currencies, metrics and nil reasons; source-system, document, dataset, ledger and control evidence; form, schema, taxonomy, entry-point, code-set and validation-rule versions; structural, dimensional, arithmetic, completeness, cross-field and business validation; review, approval, delegation, signature, seal and digest evidence; submission or publication attempts, channels, endpoints, envelopes, packages, payloads, correlations, retries and dissemination events; receipts, acknowledgements, rejection, suspense, errors, warnings and accepted-for-processing or published responses; independent lifecycle axes and deadlines; non-destructive amendment, restatement, replacement and withdrawal lineage; regulator query, review, finding, investigation, decision, sanction, remediation and appeal references; provenance, quality, clocks, confidentiality, privacy, access, retention and loss-aware projections. External reporting entity, regulator, obligation, law, domain fact, permit, application, case, decision, assessment, sanction, payment and generic records masters remain authoritative.","purpose":"Represent a versioned regulatory declaration or disclosure package, its submission or publication attempts and attributable responses so agents can prepare, validate, approve, sign, deliver, amend and reconcile reporting context without confusing transport or dissemination with regulator acceptance, legal truth, compliance, assessment, sanction or finality.","scope":{"in":["Filing and revision identity, mandate, parties, content structure, assertions, evidence, validation, approval, signature, delivery, dissemination and responses","Lifecycle, deadlines, amendments, restatements, downstream references, clocks, provenance, confidentiality, access, retention and projections"],"out":["Owning Reporting Entity, Person, Organization, Regulator, Obligation, Legal Norm, Domain Data, Permit, Application, Case, Decision, Assessment, Sanction, Payment or generic Records masters","Treating prepared as approved, submitted as received, schema-valid as accepted, public as regulator-reviewed, or reported assertion as legal truth, compliance, assessment or sanction","Autonomous legal attestation, approval, signature, external filing, publication, validation override, protected-data disclosure or record destruction"],"boundaries":[{"neighbor":"WM-REC-002","distinction":"The unified registry supplies WM-REC-002 as a provisional parent signal only. Generic records remain external and no settled containment edge exists."},{"neighbor":"Reporting entity, regulator, obligation and law","distinction":"The filing binds external actors, registrations, obligations and versioned legal profiles; it does not own their identity or lifecycle."},{"neighbor":"Disclosure revision, delivery attempt, dissemination and response","distinction":"A revision states assertions, an attempt delivers a payload, dissemination makes content available and a response records a channel, repository or authority outcome."},{"neighbor":"Reported assertion, regulator finding, decision and sanction","distinction":"A reported fact or narrative does not become an accepted legal fact, compliance determination, assessment, enforcement decision or sanction merely through validation or acceptance."},{"neighbor":"Jurisdiction and interoperability standards","distinction":"Each regulatory, reporting, identity, signature, privacy or schema source covers a scoped profile; every mapping is version-pinned and loss-declaring."}]},"distinguishingFeatures":["Holds a disclosure package submitted to a regulator or public repository, separate from the obligation that requires it.","Keeps submission, receipt, technical acceptance, publication and regulatory review as distinct states.","A reported assertion stays the reporting entity's statement, not a regulator finding or legal truth.","Restated and amended filings are new revisions linked to the original."],"structure":{"bundles":[{"id":"identity-mandate-parties-and-authority","name":"Identity, mandate, parties and authority","description":"Identify one regulatory filing or disclosure aggregate, its revisions, mandate and independently mastered participants","layers":[{"id":"filing-identity-and-classification","name":"Filing identity and classification","description":"Groups governed filing identity and classification for Regulatory Filing / Disclosure.","findings":[{"id":"filing-revision-form-report-schema-profile-status-and-master-system","name":"Filing, revision, form, report, schema, profile, status and master system","description":"Records filing, revision, form, report, schema, profile, status and master system as source-qualified Regulatory Filing / Disclosure context while reporting entity, regulator, obligation, law, domain fact, permit, application, case, decision, assessment, sanction, payment and records masters remain independently identifiable.","questions":[{"text":"Which stable filing, revision, reporting entity, obligation, reference period, jurisdiction, form, schema and external-master identities establish filing, revision, form, report, schema, profile, status and master system?","id":"filing-revision-form-report-schema-profile-status-and-master-system-q01","kind":"identity"},{"text":"Who prepares, reviews, approves, signs, transmits, publishes, receives, validates, investigates or may rely on filing, revision, form, report, schema, profile, status and master system, for which purpose and under what authority?","id":"filing-revision-form-report-schema-profile-status-and-master-system-q02","kind":"authority"},{"text":"Which concept, value, unit, rule version, source, evidence, method, event time, knowledge time, uncertainty, successor lineage and projection loss qualify filing, revision, form, report, schema, profile, status and master system?","id":"filing-revision-form-report-schema-profile-status-and-master-system-q03","kind":"security"}]},{"id":"periodic-event-driven-initial-amended-restated-replacement-withdrawal-and-nil-class","name":"Periodic, event-driven, initial, amended, restated, replacement, withdrawal and nil class","description":"Records periodic, event-driven, initial, amended, restated, replacement, withdrawal and nil class as source-qualified Regulatory Filing / Disclosure context while reporting entity, regulator, obligation, law, domain fact, permit, application, case, decision, assessment, sanction, payment and records masters remain independently identifiable.","questions":[{"text":"Which stable filing, revision, reporting entity, obligation, reference period, jurisdiction, form, schema and external-master identities establish periodic, event-driven, initial, amended, restated, replacement, withdrawal and nil class?","id":"periodic-event-driven-initial-amended-restated-replacement-withdrawal-and-nil-class-q01","kind":"classification"},{"text":"Who prepares, reviews, approves, signs, transmits, publishes, receives, validates, investigates or may rely on periodic, event-driven, initial, amended, restated, replacement, withdrawal and nil class, for which purpose and under what authority?","id":"periodic-event-driven-initial-amended-restated-replacement-withdrawal-and-nil-class-q02","kind":"requirement"},{"text":"Which concept, value, unit, rule version, source, evidence, method, event time, knowledge time, uncertainty, successor lineage and projection loss qualify periodic, event-driven, initial, amended, restated, replacement, withdrawal and nil class?","id":"periodic-event-driven-initial-amended-restated-replacement-withdrawal-and-nil-class-q03","kind":"privacy"}]}]},{"id":"reporting-entity-filer-obligation-and-authority","name":"Reporting entity, filer, obligation and authority","description":"Groups governed reporting entity, filer, obligation and authority for Regulatory Filing / Disclosure.","findings":[{"id":"reporting-entity-registration-lei-account-obligation-period-and-jurisdiction-reference","name":"Reporting entity, registration, LEI, account, obligation, period and jurisdiction reference","description":"Records reporting entity, registration, lei, account, obligation, period and jurisdiction reference as source-qualified Regulatory Filing / Disclosure context while reporting entity, regulator, obligation, law, domain fact, permit, application, case, decision, assessment, sanction, payment and records masters remain independently identifiable.","questions":[{"text":"Which stable filing, revision, reporting entity, obligation, reference period, jurisdiction, form, schema and external-master identities establish reporting entity, registration, lei, account, obligation, period and jurisdiction reference?","id":"reporting-entity-registration-lei-account-obligation-period-and-jurisdiction-reference-q01","kind":"relationship"},{"text":"Who prepares, reviews, approves, signs, transmits, publishes, receives, validates, investigates or may rely on reporting entity, registration, lei, account, obligation, period and jurisdiction reference, for which purpose and under what authority?","id":"reporting-entity-registration-lei-account-obligation-period-and-jurisdiction-reference-q02","kind":"constraint"},{"text":"Which concept, value, unit, rule version, source, evidence, method, event time, knowledge time, uncertainty, successor lineage and projection loss qualify reporting entity, registration, lei, account, obligation, period and jurisdiction reference?","id":"reporting-entity-registration-lei-account-obligation-period-and-jurisdiction-reference-q03","kind":"retention"}]},{"id":"preparer-reviewer-approver-signer-transmitter-publisher-regulator-and-repository-role","name":"Preparer, reviewer, approver, signer, transmitter, publisher, regulator and repository role","description":"Records preparer, reviewer, approver, signer, transmitter, publisher, regulator and repository role as source-qualified Regulatory Filing / Disclosure context while reporting entity, regulator, obligation, law, domain fact, permit, application, case, decision, assessment, sanction, payment and records masters remain independently identifiable.","questions":[{"text":"Which stable filing, revision, reporting entity, obligation, reference period, jurisdiction, form, schema and external-master identities establish preparer, reviewer, approver, signer, transmitter, publisher, regulator and repository role?","id":"preparer-reviewer-approver-signer-transmitter-publisher-regulator-and-repository-role-q01","kind":"authority"},{"text":"Who prepares, reviews, approves, signs, transmits, publishes, receives, validates, investigates or may rely on preparer, reviewer, approver, signer, transmitter, publisher, regulator and repository role, for which purpose and under what authority?","id":"preparer-reviewer-approver-signer-transmitter-publisher-regulator-and-repository-role-q02","kind":"process"},{"text":"Which concept, value, unit, rule version, source, evidence, method, event time, knowledge time, uncertainty, successor lineage and projection loss qualify preparer, reviewer, approver, signer, transmitter, publisher, regulator and repository role?","id":"preparer-reviewer-approver-signer-transmitter-publisher-regulator-and-repository-role-q03","kind":"access"}]}]}]},{"id":"content-structure-assertions-and-evidence","name":"Content structure, assertions and evidence","description":"Represent the versioned disclosure package and its domain evidence without absorbing source masters","layers":[{"id":"sections-tables-schedules-forms-and-exhibits","name":"Sections, tables, schedules, forms and exhibits","description":"Groups governed sections, tables, schedules, forms and exhibits for Regulatory Filing / Disclosure.","findings":[{"id":"cover-metadata-section-table-row-column-cell-schedule-form-and-exhibit","name":"Cover metadata, section, table, row, column, cell, schedule, form and exhibit","description":"Records cover metadata, section, table, row, column, cell, schedule, form and exhibit as source-qualified Regulatory Filing / Disclosure context while reporting entity, regulator, obligation, law, domain fact, permit, application, case, decision, assessment, sanction, payment and records masters remain independently identifiable.","questions":[{"text":"Which stable filing, revision, reporting entity, obligation, reference period, jurisdiction, form, schema and external-master identities establish cover metadata, section, table, row, column, cell, schedule, form and exhibit?","id":"cover-metadata-section-table-row-column-cell-schedule-form-and-exhibit-q01","kind":"composition"},{"text":"Who prepares, reviews, approves, signs, transmits, publishes, receives, validates, investigates or may rely on cover metadata, section, table, row, column, cell, schedule, form and exhibit, for which purpose and under what authority?","id":"cover-metadata-section-table-row-column-cell-schedule-form-and-exhibit-q02","kind":"event"},{"text":"Which concept, value, unit, rule version, source, evidence, method, event time, knowledge time, uncertainty, successor lineage and projection loss qualify cover metadata, section, table, row, column, cell, schedule, form and exhibit?","id":"cover-metadata-section-table-row-column-cell-schedule-form-and-exhibit-q03","kind":"exception"}]},{"id":"narrative-note-policy-methodology-attestation-and-explanatory-disclosure","name":"Narrative, note, policy, methodology, attestation and explanatory disclosure","description":"Records narrative, note, policy, methodology, attestation and explanatory disclosure as source-qualified Regulatory Filing / Disclosure context while reporting entity, regulator, obligation, law, domain fact, permit, application, case, decision, assessment, sanction, payment and records masters remain independently identifiable.","questions":[{"text":"Which stable filing, revision, reporting entity, obligation, reference period, jurisdiction, form, schema and external-master identities establish narrative, note, policy, methodology, attestation and explanatory disclosure?","id":"narrative-note-policy-methodology-attestation-and-explanatory-disclosure-q01","kind":"requirement"},{"text":"Who prepares, reviews, approves, signs, transmits, publishes, receives, validates, investigates or may rely on narrative, note, policy, methodology, attestation and explanatory disclosure, for which purpose and under what authority?","id":"narrative-note-policy-methodology-attestation-and-explanatory-disclosure-q02","kind":"measurement"},{"text":"Which concept, value, unit, rule version, source, evidence, method, event time, knowledge time, uncertainty, successor lineage and projection loss qualify narrative, note, policy, methodology, attestation and explanatory disclosure?","id":"narrative-note-policy-methodology-attestation-and-explanatory-disclosure-q03","kind":"interoperability"}]}]},{"id":"reported-facts-metrics-and-source-evidence","name":"Reported facts, metrics and source evidence","description":"Groups governed reported facts, metrics and source evidence for Regulatory Filing / Disclosure.","findings":[{"id":"reported-fact-concept-context-dimension-unit-value-decimals-and-metric","name":"Reported fact, concept, context, dimension, unit, value, decimals and metric","description":"Records reported fact, concept, context, dimension, unit, value, decimals and metric as source-qualified Regulatory Filing / Disclosure context while reporting entity, regulator, obligation, law, domain fact, permit, application, case, decision, assessment, sanction, payment and records masters remain independently identifiable.","questions":[{"text":"Which stable filing, revision, reporting entity, obligation, reference period, jurisdiction, form, schema and external-master identities establish reported fact, concept, context, dimension, unit, value, decimals and metric?","id":"reported-fact-concept-context-dimension-unit-value-decimals-and-metric-q01","kind":"measurement"},{"text":"Who prepares, reviews, approves, signs, transmits, publishes, receives, validates, investigates or may rely on reported fact, concept, context, dimension, unit, value, decimals and metric, for which purpose and under what authority?","id":"reported-fact-concept-context-dimension-unit-value-decimals-and-metric-q02","kind":"evidence"},{"text":"Which concept, value, unit, rule version, source, evidence, method, event time, knowledge time, uncertainty, successor lineage and projection loss qualify reported fact, concept, context, dimension, unit, value, decimals and metric?","id":"reported-fact-concept-context-dimension-unit-value-decimals-and-metric-q03","kind":"decision"}]},{"id":"source-system-document-dataset-ledger-control-and-evidence-reference","name":"Source system, document, dataset, ledger, control and evidence reference","description":"Records source system, document, dataset, ledger, control and evidence reference as source-qualified Regulatory Filing / Disclosure context while reporting entity, regulator, obligation, law, domain fact, permit, application, case, decision, assessment, sanction, payment and records masters remain independently identifiable.","questions":[{"text":"Which stable filing, revision, reporting entity, obligation, reference period, jurisdiction, form, schema and external-master identities establish source system, document, dataset, ledger, control and evidence reference?","id":"source-system-document-dataset-ledger-control-and-evidence-reference-q01","kind":"evidence"},{"text":"Who prepares, reviews, approves, signs, transmits, publishes, receives, validates, investigates or may rely on source system, document, dataset, ledger, control and evidence reference, for which purpose and under what authority?","id":"source-system-document-dataset-ledger-control-and-evidence-reference-q02","kind":"quality"},{"text":"Which concept, value, unit, rule version, source, evidence, method, event time, knowledge time, uncertainty, successor lineage and projection loss qualify source system, document, dataset, ledger, control and evidence reference?","id":"source-system-document-dataset-ledger-control-and-evidence-reference-q03","kind":"identity"}]}]}]},{"id":"preparation-validation-approval-and-signature","name":"Preparation, validation, approval and signature","description":"Preserve rule versions, validation evidence and accountable approvals before external delivery","layers":[{"id":"schema-taxonomy-code-set-and-business-validation","name":"Schema, taxonomy, code-set and business validation","description":"Groups governed schema, taxonomy, code-set and business validation for Regulatory Filing / Disclosure.","findings":[{"id":"form-schema-taxonomy-entry-point-code-set-and-validation-rule-version","name":"Form, schema, taxonomy, entry point, code-set and validation-rule version","description":"Records form, schema, taxonomy, entry point, code-set and validation-rule version as source-qualified Regulatory Filing / Disclosure context while reporting entity, regulator, obligation, law, domain fact, permit, application, case, decision, assessment, sanction, payment and records masters remain independently identifiable.","questions":[{"text":"Which stable filing, revision, reporting entity, obligation, reference period, jurisdiction, form, schema and external-master identities establish form, schema, taxonomy, entry point, code-set and validation-rule version?","id":"form-schema-taxonomy-entry-point-code-set-and-validation-rule-version-q01","kind":"validation"},{"text":"Who prepares, reviews, approves, signs, transmits, publishes, receives, validates, investigates or may rely on form, schema, taxonomy, entry point, code-set and validation-rule version, for which purpose and under what authority?","id":"form-schema-taxonomy-entry-point-code-set-and-validation-rule-version-q02","kind":"validation"},{"text":"Which concept, value, unit, rule version, source, evidence, method, event time, knowledge time, uncertainty, successor lineage and projection loss qualify form, schema, taxonomy, entry point, code-set and validation-rule version?","id":"form-schema-taxonomy-entry-point-code-set-and-validation-rule-version-q03","kind":"classification"}]},{"id":"structural-dimensional-arithmetic-cross-field-completeness-error-warning-and-waiver","name":"Structural, dimensional, arithmetic, cross-field, completeness, error, warning and waiver","description":"Records structural, dimensional, arithmetic, cross-field, completeness, error, warning and waiver as source-qualified Regulatory Filing / Disclosure context while reporting entity, regulator, obligation, law, domain fact, permit, application, case, decision, assessment, sanction, payment and records masters remain independently identifiable.","questions":[{"text":"Which stable filing, revision, reporting entity, obligation, reference period, jurisdiction, form, schema and external-master identities establish structural, dimensional, arithmetic, cross-field, completeness, error, warning and waiver?","id":"structural-dimensional-arithmetic-cross-field-completeness-error-warning-and-waiver-q01","kind":"quality"},{"text":"Who prepares, reviews, approves, signs, transmits, publishes, receives, validates, investigates or may rely on structural, dimensional, arithmetic, cross-field, completeness, error, warning and waiver, for which purpose and under what authority?","id":"structural-dimensional-arithmetic-cross-field-completeness-error-warning-and-waiver-q02","kind":"security"},{"text":"Which concept, value, unit, rule version, source, evidence, method, event time, knowledge time, uncertainty, successor lineage and projection loss qualify structural, dimensional, arithmetic, cross-field, completeness, error, warning and waiver?","id":"structural-dimensional-arithmetic-cross-field-completeness-error-warning-and-waiver-q03","kind":"composition"}]}]},{"id":"review-approval-attestation-signature-and-accountability","name":"Review, approval, attestation, signature and accountability","description":"Groups governed review, approval, attestation, signature and accountability for Regulatory Filing / Disclosure.","findings":[{"id":"review-control-approval-declaration-attestation-signature-seal-digest-and-time","name":"Review, control, approval, declaration, attestation, signature, seal, digest and time","description":"Records review, control, approval, declaration, attestation, signature, seal, digest and time as source-qualified Regulatory Filing / Disclosure context while reporting entity, regulator, obligation, law, domain fact, permit, application, case, decision, assessment, sanction, payment and records masters remain independently identifiable.","questions":[{"text":"Which stable filing, revision, reporting entity, obligation, reference period, jurisdiction, form, schema and external-master identities establish review, control, approval, declaration, attestation, signature, seal, digest and time?","id":"review-control-approval-declaration-attestation-signature-seal-digest-and-time-q01","kind":"provenance"},{"text":"Who prepares, reviews, approves, signs, transmits, publishes, receives, validates, investigates or may rely on review, control, approval, declaration, attestation, signature, seal, digest and time, for which purpose and under what authority?","id":"review-control-approval-declaration-attestation-signature-seal-digest-and-time-q02","kind":"privacy"},{"text":"Which concept, value, unit, rule version, source, evidence, method, event time, knowledge time, uncertainty, successor lineage and projection loss qualify review, control, approval, declaration, attestation, signature, seal, digest and time?","id":"review-control-approval-declaration-attestation-signature-seal-digest-and-time-q03","kind":"relationship"}]},{"id":"delegation-mandate-representation-responsibility-segregation-and-exception","name":"Delegation, mandate, representation, responsibility, segregation and exception","description":"Records delegation, mandate, representation, responsibility, segregation and exception as source-qualified Regulatory Filing / Disclosure context while reporting entity, regulator, obligation, law, domain fact, permit, application, case, decision, assessment, sanction, payment and records masters remain independently identifiable.","questions":[{"text":"Which stable filing, revision, reporting entity, obligation, reference period, jurisdiction, form, schema and external-master identities establish delegation, mandate, representation, responsibility, segregation and exception?","id":"delegation-mandate-representation-responsibility-segregation-and-exception-q01","kind":"authority"},{"text":"Who prepares, reviews, approves, signs, transmits, publishes, receives, validates, investigates or may rely on delegation, mandate, representation, responsibility, segregation and exception, for which purpose and under what authority?","id":"delegation-mandate-representation-responsibility-segregation-and-exception-q02","kind":"retention"},{"text":"Which concept, value, unit, rule version, source, evidence, method, event time, knowledge time, uncertainty, successor lineage and projection loss qualify delegation, mandate, representation, responsibility, segregation and exception?","id":"delegation-mandate-representation-responsibility-segregation-and-exception-q03","kind":"state"}]}]}]},{"id":"delivery-dissemination-receipt-and-response","name":"Delivery, dissemination, receipt and response","description":"Track every external attempt and response without turning transport into regulatory acceptance or legal truth","layers":[{"id":"submission-publication-channel-envelope-and-payload","name":"Submission, publication, channel, envelope and payload","description":"Groups governed submission, publication, channel, envelope and payload for Regulatory Filing / Disclosure.","findings":[{"id":"attempt-channel-endpoint-envelope-package-payload-digest-correlation-and-idempotency","name":"Attempt, channel, endpoint, envelope, package, payload, digest, correlation and idempotency","description":"Records attempt, channel, endpoint, envelope, package, payload, digest, correlation and idempotency as source-qualified Regulatory Filing / Disclosure context while reporting entity, regulator, obligation, law, domain fact, permit, application, case, decision, assessment, sanction, payment and records masters remain independently identifiable.","questions":[{"text":"Which stable filing, revision, reporting entity, obligation, reference period, jurisdiction, form, schema and external-master identities establish attempt, channel, endpoint, envelope, package, payload, digest, correlation and idempotency?","id":"attempt-channel-endpoint-envelope-package-payload-digest-correlation-and-idempotency-q01","kind":"process"},{"text":"Who prepares, reviews, approves, signs, transmits, publishes, receives, validates, investigates or may rely on attempt, channel, endpoint, envelope, package, payload, digest, correlation and idempotency, for which purpose and under what authority?","id":"attempt-channel-endpoint-envelope-package-payload-digest-correlation-and-idempotency-q02","kind":"access"},{"text":"Which concept, value, unit, rule version, source, evidence, method, event time, knowledge time, uncertainty, successor lineage and projection loss qualify attempt, channel, endpoint, envelope, package, payload, digest, correlation and idempotency?","id":"attempt-channel-endpoint-envelope-package-payload-digest-correlation-and-idempotency-q03","kind":"lifecycle"}]},{"id":"transmission-retry-duplicate-replacement-withdrawal-publication-and-dissemination-event","name":"Transmission, retry, duplicate, replacement, withdrawal, publication and dissemination event","description":"Records transmission, retry, duplicate, replacement, withdrawal, publication and dissemination event as source-qualified Regulatory Filing / Disclosure context while reporting entity, regulator, obligation, law, domain fact, permit, application, case, decision, assessment, sanction, payment and records masters remain independently identifiable.","questions":[{"text":"Which stable filing, revision, reporting entity, obligation, reference period, jurisdiction, form, schema and external-master identities establish transmission, retry, duplicate, replacement, withdrawal, publication and dissemination event?","id":"transmission-retry-duplicate-replacement-withdrawal-publication-and-dissemination-event-q01","kind":"event"},{"text":"Who prepares, reviews, approves, signs, transmits, publishes, receives, validates, investigates or may rely on transmission, retry, duplicate, replacement, withdrawal, publication and dissemination event, for which purpose and under what authority?","id":"transmission-retry-duplicate-replacement-withdrawal-publication-and-dissemination-event-q02","kind":"exception"},{"text":"Which concept, value, unit, rule version, source, evidence, method, event time, knowledge time, uncertainty, successor lineage and projection loss qualify transmission, retry, duplicate, replacement, withdrawal, publication and dissemination event?","id":"transmission-retry-duplicate-replacement-withdrawal-publication-and-dissemination-event-q03","kind":"temporal"}]}]},{"id":"receipt-validation-acceptance-publication-and-regulator-response","name":"Receipt, validation, acceptance, publication and regulator response","description":"Groups governed receipt, validation, acceptance, publication and regulator response for Regulatory Filing / Disclosure.","findings":[{"id":"receipt-confirmation-acknowledgement-rejection-suspense-error-warning-and-correlation","name":"Receipt confirmation, acknowledgement, rejection, suspense, error, warning and correlation","description":"Records receipt confirmation, acknowledgement, rejection, suspense, error, warning and correlation as source-qualified Regulatory Filing / Disclosure context while reporting entity, regulator, obligation, law, domain fact, permit, application, case, decision, assessment, sanction, payment and records masters remain independently identifiable.","questions":[{"text":"Which stable filing, revision, reporting entity, obligation, reference period, jurisdiction, form, schema and external-master identities establish receipt confirmation, acknowledgement, rejection, suspense, error, warning and correlation?","id":"receipt-confirmation-acknowledgement-rejection-suspense-error-warning-and-correlation-q01","kind":"evidence"},{"text":"Who prepares, reviews, approves, signs, transmits, publishes, receives, validates, investigates or may rely on receipt confirmation, acknowledgement, rejection, suspense, error, warning and correlation, for which purpose and under what authority?","id":"receipt-confirmation-acknowledgement-rejection-suspense-error-warning-and-correlation-q02","kind":"interoperability"},{"text":"Which concept, value, unit, rule version, source, evidence, method, event time, knowledge time, uncertainty, successor lineage and projection loss qualify receipt confirmation, acknowledgement, rejection, suspense, error, warning and correlation?","id":"receipt-confirmation-acknowledgement-rejection-suspense-error-warning-and-correlation-q03","kind":"spatial"}]},{"id":"accepted-for-processing-published-reviewed-query-finding-decision-and-action-reference","name":"Accepted-for-processing, published, reviewed, query, finding, decision and action reference","description":"Records accepted-for-processing, published, reviewed, query, finding, decision and action reference as source-qualified Regulatory Filing / Disclosure context while reporting entity, regulator, obligation, law, domain fact, permit, application, case, decision, assessment, sanction, payment and records masters remain independently identifiable.","questions":[{"text":"Which stable filing, revision, reporting entity, obligation, reference period, jurisdiction, form, schema and external-master identities establish accepted-for-processing, published, reviewed, query, finding, decision and action reference?","id":"accepted-for-processing-published-reviewed-query-finding-decision-and-action-reference-q01","kind":"lifecycle"},{"text":"Who prepares, reviews, approves, signs, transmits, publishes, receives, validates, investigates or may rely on accepted-for-processing, published, reviewed, query, finding, decision and action reference, for which purpose and under what authority?","id":"accepted-for-processing-published-reviewed-query-finding-decision-and-action-reference-q02","kind":"decision"},{"text":"Which concept, value, unit, rule version, source, evidence, method, event time, knowledge time, uncertainty, successor lineage and projection loss qualify accepted-for-processing, published, reviewed, query, finding, decision and action reference?","id":"accepted-for-processing-published-reviewed-query-finding-decision-and-action-reference-q03","kind":"provenance"}]}]}]},{"id":"lifecycle-deadlines-corrections-and-downstream-references","name":"Lifecycle, deadlines, corrections and downstream references","description":"Represent independent state axes and immutable amendment, restatement and withdrawal lineage","layers":[{"id":"reporting-period-deadline-extension-and-lifecycle","name":"Reporting period, deadline, extension and lifecycle","description":"Groups governed reporting period, deadline, extension and lifecycle for Regulatory Filing / Disclosure.","findings":[{"id":"draft-prepared-reviewed-approved-signed-submitted-received-valid-accepted-published-and-closed-state","name":"Draft, prepared, reviewed, approved, signed, submitted, received, valid, accepted, published and closed state","description":"Records draft, prepared, reviewed, approved, signed, submitted, received, valid, accepted, published and closed state as source-qualified Regulatory Filing / Disclosure context while reporting entity, regulator, obligation, law, domain fact, permit, application, case, decision, assessment, sanction, payment and records masters remain independently identifiable.","questions":[{"text":"Which stable filing, revision, reporting entity, obligation, reference period, jurisdiction, form, schema and external-master identities establish draft, prepared, reviewed, approved, signed, submitted, received, valid, accepted, published and closed state?","id":"draft-prepared-reviewed-approved-signed-submitted-received-valid-accepted-published-and-closed-state-q01","kind":"state"},{"text":"Who prepares, reviews, approves, signs, transmits, publishes, receives, validates, investigates or may rely on draft, prepared, reviewed, approved, signed, submitted, received, valid, accepted, published and closed state, for which purpose and under what authority?","id":"draft-prepared-reviewed-approved-signed-submitted-received-valid-accepted-published-and-closed-state-q02","kind":"identity"},{"text":"Which concept, value, unit, rule version, source, evidence, method, event time, knowledge time, uncertainty, successor lineage and projection loss qualify draft, prepared, reviewed, approved, signed, submitted, received, valid, accepted, published and closed state?","id":"draft-prepared-reviewed-approved-signed-submitted-received-valid-accepted-published-and-closed-state-q03","kind":"ownership"}]},{"id":"reference-period-due-extension-preparation-approval-signature-submission-receipt-publication-and-knowledge-time","name":"Reference period, due, extension, preparation, approval, signature, submission, receipt, publication and knowledge time","description":"Records reference period, due, extension, preparation, approval, signature, submission, receipt, publication and knowledge time as source-qualified Regulatory Filing / Disclosure context while reporting entity, regulator, obligation, law, domain fact, permit, application, case, decision, assessment, sanction, payment and records masters remain independently identifiable.","questions":[{"text":"Which stable filing, revision, reporting entity, obligation, reference period, jurisdiction, form, schema and external-master identities establish reference period, due, extension, preparation, approval, signature, submission, receipt, publication and knowledge time?","id":"reference-period-due-extension-preparation-approval-signature-submission-receipt-publication-and-knowledge-time-q01","kind":"temporal"},{"text":"Who prepares, reviews, approves, signs, transmits, publishes, receives, validates, investigates or may rely on reference period, due, extension, preparation, approval, signature, submission, receipt, publication and knowledge time, for which purpose and under what authority?","id":"reference-period-due-extension-preparation-approval-signature-submission-receipt-publication-and-knowledge-time-q02","kind":"classification"},{"text":"Which concept, value, unit, rule version, source, evidence, method, event time, knowledge time, uncertainty, successor lineage and projection loss qualify reference period, due, extension, preparation, approval, signature, submission, receipt, publication and knowledge time?","id":"reference-period-due-extension-preparation-approval-signature-submission-receipt-publication-and-knowledge-time-q03","kind":"authority"}]}]},{"id":"amendment-restatement-withdrawal-and-regulatory-follow-up","name":"Amendment, restatement, withdrawal and regulatory follow-up","description":"Groups governed amendment, restatement, withdrawal and regulatory follow-up for Regulatory Filing / Disclosure.","findings":[{"id":"amendment-correction-restatement-replacement-withdrawal-predecessor-successor-and-change-set","name":"Amendment, correction, restatement, replacement, withdrawal, predecessor, successor and change set","description":"Records amendment, correction, restatement, replacement, withdrawal, predecessor, successor and change set as source-qualified Regulatory Filing / Disclosure context while reporting entity, regulator, obligation, law, domain fact, permit, application, case, decision, assessment, sanction, payment and records masters remain independently identifiable.","questions":[{"text":"Which stable filing, revision, reporting entity, obligation, reference period, jurisdiction, form, schema and external-master identities establish amendment, correction, restatement, replacement, withdrawal, predecessor, successor and change set?","id":"amendment-correction-restatement-replacement-withdrawal-predecessor-successor-and-change-set-q01","kind":"exception"},{"text":"Who prepares, reviews, approves, signs, transmits, publishes, receives, validates, investigates or may rely on amendment, correction, restatement, replacement, withdrawal, predecessor, successor and change set, for which purpose and under what authority?","id":"amendment-correction-restatement-replacement-withdrawal-predecessor-successor-and-change-set-q02","kind":"composition"},{"text":"Which concept, value, unit, rule version, source, evidence, method, event time, knowledge time, uncertainty, successor lineage and projection loss qualify amendment, correction, restatement, replacement, withdrawal, predecessor, successor and change set?","id":"amendment-correction-restatement-replacement-withdrawal-predecessor-successor-and-change-set-q03","kind":"requirement"}]},{"id":"regulator-query-review-finding-investigation-decision-sanction-remediation-and-appeal-reference","name":"Regulator query, review, finding, investigation, decision, sanction, remediation and appeal reference","description":"Records regulator query, review, finding, investigation, decision, sanction, remediation and appeal reference as source-qualified Regulatory Filing / Disclosure context while reporting entity, regulator, obligation, law, domain fact, permit, application, case, decision, assessment, sanction, payment and records masters remain independently identifiable.","questions":[{"text":"Which stable filing, revision, reporting entity, obligation, reference period, jurisdiction, form, schema and external-master identities establish regulator query, review, finding, investigation, decision, sanction, remediation and appeal reference?","id":"regulator-query-review-finding-investigation-decision-sanction-remediation-and-appeal-reference-q01","kind":"relationship"},{"text":"Who prepares, reviews, approves, signs, transmits, publishes, receives, validates, investigates or may rely on regulator query, review, finding, investigation, decision, sanction, remediation and appeal reference, for which purpose and under what authority?","id":"regulator-query-review-finding-investigation-decision-sanction-remediation-and-appeal-reference-q02","kind":"relationship"},{"text":"Which concept, value, unit, rule version, source, evidence, method, event time, knowledge time, uncertainty, successor lineage and projection loss qualify regulator query, review, finding, investigation, decision, sanction, remediation and appeal reference?","id":"regulator-query-review-finding-investigation-decision-sanction-remediation-and-appeal-reference-q03","kind":"constraint"}]}]}]},{"id":"governance-provenance-confidentiality-retention-and-interoperability","name":"Governance, provenance, confidentiality, retention and interoperability","description":"Qualify every assertion, access decision and external projection for agent-safe regulatory use","layers":[{"id":"source-provenance-quality-and-time","name":"Source, provenance, quality and time","description":"Groups governed source, provenance, quality and time for Regulatory Filing / Disclosure.","findings":[{"id":"source-actor-activity-derivation-conflict-confidence-quality-measure-and-control","name":"Source, actor, activity, derivation, conflict, confidence, quality measure and control","description":"Records source, actor, activity, derivation, conflict, confidence, quality measure and control as source-qualified Regulatory Filing / Disclosure context while reporting entity, regulator, obligation, law, domain fact, permit, application, case, decision, assessment, sanction, payment and records masters remain independently identifiable.","questions":[{"text":"Which stable filing, revision, reporting entity, obligation, reference period, jurisdiction, form, schema and external-master identities establish source, actor, activity, derivation, conflict, confidence, quality measure and control?","id":"source-actor-activity-derivation-conflict-confidence-quality-measure-and-control-q01","kind":"provenance"},{"text":"Who prepares, reviews, approves, signs, transmits, publishes, receives, validates, investigates or may rely on source, actor, activity, derivation, conflict, confidence, quality measure and control, for which purpose and under what authority?","id":"source-actor-activity-derivation-conflict-confidence-quality-measure-and-control-q02","kind":"state"},{"text":"Which concept, value, unit, rule version, source, evidence, method, event time, knowledge time, uncertainty, successor lineage and projection loss qualify source, actor, activity, derivation, conflict, confidence, quality measure and control?","id":"source-actor-activity-derivation-conflict-confidence-quality-measure-and-control-q03","kind":"process"}]},{"id":"reference-effective-due-approval-signature-submission-receipt-publication-observation-ingestion-and-knowledge-time","name":"Reference, effective, due, approval, signature, submission, receipt, publication, observation, ingestion and knowledge time","description":"Records reference, effective, due, approval, signature, submission, receipt, publication, observation, ingestion and knowledge time as source-qualified Regulatory Filing / Disclosure context while reporting entity, regulator, obligation, law, domain fact, permit, application, case, decision, assessment, sanction, payment and records masters remain independently identifiable.","questions":[{"text":"Which stable filing, revision, reporting entity, obligation, reference period, jurisdiction, form, schema and external-master identities establish reference, effective, due, approval, signature, submission, receipt, publication, observation, ingestion and knowledge time?","id":"reference-effective-due-approval-signature-submission-receipt-publication-observation-ingestion-and-knowledge-time-q01","kind":"temporal"},{"text":"Who prepares, reviews, approves, signs, transmits, publishes, receives, validates, investigates or may rely on reference, effective, due, approval, signature, submission, receipt, publication, observation, ingestion and knowledge time, for which purpose and under what authority?","id":"reference-effective-due-approval-signature-submission-receipt-publication-observation-ingestion-and-knowledge-time-q02","kind":"lifecycle"},{"text":"Which concept, value, unit, rule version, source, evidence, method, event time, knowledge time, uncertainty, successor lineage and projection loss qualify reference, effective, due, approval, signature, submission, receipt, publication, observation, ingestion and knowledge time?","id":"reference-effective-due-approval-signature-submission-receipt-publication-observation-ingestion-and-knowledge-time-q03","kind":"event"}]}]},{"id":"ownership-confidentiality-access-retention-and-projection","name":"Ownership, confidentiality, access, retention and projection","description":"Groups governed ownership, confidentiality, access, retention and projection for Regulatory Filing / Disclosure.","findings":[{"id":"owner-steward-public-confidential-restricted-purpose-access-exception-legal-hold-and-tombstone","name":"Owner, steward, public, confidential, restricted, purpose, access, exception, legal hold and tombstone","description":"Records owner, steward, public, confidential, restricted, purpose, access, exception, legal hold and tombstone as source-qualified Regulatory Filing / Disclosure context while reporting entity, regulator, obligation, law, domain fact, permit, application, case, decision, assessment, sanction, payment and records masters remain independently identifiable.","questions":[{"text":"Which stable filing, revision, reporting entity, obligation, reference period, jurisdiction, form, schema and external-master identities establish owner, steward, public, confidential, restricted, purpose, access, exception, legal hold and tombstone?","id":"owner-steward-public-confidential-restricted-purpose-access-exception-legal-hold-and-tombstone-q01","kind":"access"},{"text":"Who prepares, reviews, approves, signs, transmits, publishes, receives, validates, investigates or may rely on owner, steward, public, confidential, restricted, purpose, access, exception, legal hold and tombstone, for which purpose and under what authority?","id":"owner-steward-public-confidential-restricted-purpose-access-exception-legal-hold-and-tombstone-q02","kind":"temporal"},{"text":"Which concept, value, unit, rule version, source, evidence, method, event time, knowledge time, uncertainty, successor lineage and projection loss qualify owner, steward, public, confidential, restricted, purpose, access, exception, legal hold and tombstone?","id":"owner-steward-public-confidential-restricted-purpose-access-exception-legal-hold-and-tombstone-q03","kind":"measurement"}]},{"id":"jurisdiction-form-schema-taxonomy-code-set-language-conformance-and-mapping-loss","name":"Jurisdiction, form, schema, taxonomy, code-set, language, conformance and mapping loss","description":"Records jurisdiction, form, schema, taxonomy, code-set, language, conformance and mapping loss as source-qualified Regulatory Filing / Disclosure context while reporting entity, regulator, obligation, law, domain fact, permit, application, case, decision, assessment, sanction, payment and records masters remain independently identifiable.","questions":[{"text":"Which stable filing, revision, reporting entity, obligation, reference period, jurisdiction, form, schema and external-master identities establish jurisdiction, form, schema, taxonomy, code-set, language, conformance and mapping loss?","id":"jurisdiction-form-schema-taxonomy-code-set-language-conformance-and-mapping-loss-q01","kind":"interoperability"},{"text":"Who prepares, reviews, approves, signs, transmits, publishes, receives, validates, investigates or may rely on jurisdiction, form, schema, taxonomy, code-set, language, conformance and mapping loss, for which purpose and under what authority?","id":"jurisdiction-form-schema-taxonomy-code-set-language-conformance-and-mapping-loss-q02","kind":"spatial"},{"text":"Which concept, value, unit, rule version, source, evidence, method, event time, knowledge time, uncertainty, successor lineage and projection loss qualify jurisdiction, form, schema, taxonomy, code-set, language, conformance and mapping loss?","id":"jurisdiction-form-schema-taxonomy-code-set-language-conformance-and-mapping-loss-q03","kind":"evidence"}]}]}]}]},"agentConduct":{"may":["Assemble a disclosure package from source evidence.","Validate it against the regulator's taxonomy and filing rules.","Track deadlines, submission attempts and acknowledgements.","Prepare drafts and change summaries for reviewers."],"mustNot":["Approve, sign or attest a filing.","Submit or publish a filing without delegated authority.","Override validation errors to force acceptance.","Release confidential supervisory data publicly.","Present public availability as evidence of regulatory approval."],"requiresHuman":["Approving and signing a filing.","Deciding on restatement, withdrawal or a confidential treatment request.","Responding to regulator queries."]},"ethics":{"considerations":["Accurate disclosure protects investors and the public who rely on it.","Filings may contain personal data of officers and owners, which needs minimisation.","Market-sensitive information must not leak before its lawful release."],"affectedParties":["Investors and creditors","Regulators and supervisors","Officers and owners named in filings","The public"]},"owners":{"steward":"Dimension owner, namespace authority, reporting entity and delegated regulatory, legal, compliance, finance, privacy, audit and records authorities","roles":[{"name":"Reporting entity and accountable filer","responsibilities":["Own reported assertions, declarations, approvals and accountable filing or publication decisions."]},{"name":"Preparer and representative","responsibilities":["Prepare authorized disclosures, bind evidence, disclose conflicts and act only within a documented mandate."]},{"name":"Filing and disclosure steward","responsibilities":["Own filing identity, versions, validation, packaging, delivery attempts, acknowledgements, corrections and operational reconciliation."]},{"name":"Regulator or receiving authority","responsibilities":["Own scoped obligations, forms, schemas, receipt, validation, acceptance, review, finding and official response records."]},{"name":"Domain and control steward","responsibilities":["Own source facts, calculation methods, controls and evidence outside the filing aggregate."]},{"name":"Privacy, security and audit authority","responsibilities":["Own confidentiality, purpose, access, segregation, monitoring, exception, legal-hold and review controls."]},{"name":"Interoperability and records steward","responsibilities":["Own mappings, conformance, projection loss, retention and disposition policy."]}],"masterSystems":[]},"relations":[{"target":"WM-REC-002","type":"references","note":"Resolve the provisional generic-record parent signal without granting containment or cascade mutation authority."},{"target":"Reporting Entity, Person, Organization, Regulator, Obligation, Legal Norm, Domain Data, Permit, Application, Case, Decision, Assessment, Sanction, Payment and Records models","type":"references","note":"Resolve external identity, rule, source, authority, transaction and governance records without duplicating their lifecycles."},{"target":"SEC EDGAR, EU ESEF, EBA, EIOPA, FCA and Eurostat reporting profiles","type":"aligned","note":"Project version-pinned regulator and sector profiles with declared scope and semantic loss."},{"target":"XBRL, GLEIF LEI, eIDAS, GDPR, RFC 3339, PROV-O, DQV, ODRL and OpenAPI 3.1.1","type":"aligned","note":"Project reporting, identity, trust, privacy, temporal, provenance, quality, policy and API views without claiming universal conformance."},{"target":"WM-REC-002","type":"neighbor","note":"The unified registry supplies WM-REC-002 as a provisional parent signal only. Generic records remain external and no settled containment edge exists."},{"target":"Reporting entity, regulator, obligation and law","type":"neighbor","note":"The filing binds external actors, registrations, obligations and versioned legal profiles; it does not own their identity or lifecycle."},{"target":"Disclosure revision, delivery attempt, dissemination and response","type":"neighbor","note":"A revision states assertions, an attempt delivers a payload, dissemination makes content available and a response records a channel, repository or authority outcome."},{"target":"Reported assertion, regulator finding, decision and sanction","type":"neighbor","note":"A reported fact or narrative does not become an accepted legal fact, compliance determination, assessment, enforcement decision or sanction merely through validation or acceptance."},{"target":"Jurisdiction and interoperability standards","type":"neighbor","note":"Each regulatory, reporting, identity, signature, privacy or schema source covers a scoped profile; every mapping is version-pinned and loss-declaring."},{"target":"WM-REC-002","type":"parent"}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system identifier for a regulatory filing, disclosure, submission, acknowledgement, repository or records object, qualified by namespace and record kind.","Governed globally resolvable filing, attempt or artifact IRI.","Dimension UUID or ULID when neither preceding identifier exists."]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":["A regulatory filing has a reporting entity, often an LEI, an obligation, a form or taxonomy, a period and a submission identifier.","Often confused with a tax return, a sustainability report and a regulator's decision or finding."]},"capabilities":{"applicability":"required","items":["Initialize filing: Governed operation to initialize filing without autonomous legal attestation, external filing, publication, protected-data disclosure or destruction.","Bind obligation, parties and authority: Governed operation to bind obligation, parties and authority without autonomous legal attestation, external filing, publication, protected-data disclosure or destruction.","Assemble disclosure package: Governed operation to assemble disclosure package without autonomous legal attestation, external filing, publication, protected-data disclosure or destruction.","Ingest source evidence: Governed operation to ingest source evidence without autonomous legal attestation, external filing, publication, protected-data disclosure or destruction.","Validate filing: Governed operation to validate filing without autonomous legal attestation, external filing, publication, protected-data disclosure or destruction.","Review, approve and sign: Governed operation to review, approve and sign without autonomous legal attestation, external filing, publication, protected-data disclosure or destruction.","Submit or disseminate: Governed operation to submit or disseminate without autonomous legal attestation, external filing, publication, protected-data disclosure or destruction.","Record response and follow-up: Governed operation to record response and follow-up without autonomous legal attestation, external filing, publication, protected-data disclosure or destruction.","Amend, restate, withdraw and reconcile: Governed operation to amend, restate, withdraw and reconcile without autonomous legal attestation, external filing, publication, protected-data disclosure or destruction.","Validate, project, retain and audit: Governed operation to validate, project, retain and audit without autonomous legal attestation, external filing, publication, protected-data disclosure or destruction."]},"hazards":{"applicability":"required","items":["Missed deadlines and penalties.","Market abuse through premature release of inside information.","Misstatements that mislead investors.","Lost acknowledgements leaving filing status unknown."]},"interfaces":{"applicability":"required","items":["XBRL 2.1 and Inline XBRL.","ISO 17442 Legal Entity Identifier.","EBA and EIOPA Data Point Model taxonomies.","ESMA ESEF reporting format.","IETF RFC 3339 timestamps."]},"context":{"applicability":"required","items":["Obligation, form, deadline, signature, delivery effect, public dissemination, confidentiality, amendment and retention depend on jurisdiction, regulator and sector.","SEC, EU, EBA, EIOPA, FCA and Eurostat sources are scoped profiles and not universal regulatory law."]}},"sources":[{"title":"EDGAR Filer Manual","url":"https://www.sec.gov/submit-filings/edgar-filer-manual","note":"United States Securities and Exchange Commission"},{"title":"Attach and submit a filing through the EDGAR Filing Website","url":"https://www.sec.gov/submit-filings/filer-support-resources/how-do-i-guides/attach-submit-filing-through-edgar-filing-website","note":"United States Securities and Exchange Commission"},{"title":"Understand messages reported by EDGAR","url":"https://www.sec.gov/submit-filings/filer-support-resources/how-do-i-guides/understand-messages-reported-edgar","note":"United States Securities and Exchange Commission"},{"title":"EDGAR technical specifications","url":"https://www.sec.gov/submit-filings/technical-specifications","note":"United States Securities and Exchange Commission"},{"title":"European Single Electronic Format","url":"https://eur-lex.europa.eu/legal-content/en/ALL/?uri=CELEX%3A02019R0815-20260407","note":"European Union"},{"title":"EBA reporting frameworks","url":"https://www.eba.europa.eu/risk-and-data-analysis/reporting/reporting-frameworks","note":"European Banking Authority"},{"title":"EBA reporting framework 4.2","url":"https://www.eba.europa.eu/risk-and-data-analysis/reporting/reporting-frameworks/reporting-framework-42","note":"European Banking Authority"},{"title":"Supervisory reporting DPM and XBRL","url":"https://www.eiopa.europa.eu/tools-and-data/supervisory-reporting-dpm-and-xbrl_en","note":"European Insurance and Occupational Pensions Authority"},{"title":"RegData","url":"https://www.fca.org.uk/firms/regdata","note":"Financial Conduct Authority"},{"title":"SUP 16 Annex 21 reporting fields","url":"https://handbook.fca.org.uk/handbook/sup16/sup16s38","note":"Financial Conduct Authority"},{"title":"SDMX explained","url":"https://ec.europa.eu/eurostat/web/sdmx-infospace/sdmx-explained","note":"Eurostat"},{"title":"Reference metadata reporting standards","url":"https://ec.europa.eu/eurostat/web/metadata/reference-metadata-reporting-standards","note":"Eurostat"},{"title":"XBRL 2.1","url":"https://specifications.xbrl.org/work-product-index-group-base-spec-base-spec.html","note":"XBRL International"},{"title":"Report Packages 1.0","url":"https://specifications.xbrl.org/work-product-index-taxonomy-packages-report-packages-1.0.html","note":"XBRL International"},{"title":"Taxonomy Packages 1.0","url":"https://specifications.xbrl.org/work-product-index-taxonomy-packages-taxonomy-packages-1.0.html","note":"XBRL International"},{"title":"Open Information Model","url":"https://specifications.xbrl.org/work-product-index-open-information-model-open-information-model.html","note":"XBRL International"},{"title":"LEI Common Data File supporting documents","url":"https://www.gleif.org/en/lei-data/access-and-use-lei-data/supporting-documents","note":"Global Legal Entity Identifier Foundation"},{"title":"Electronic identification and trust services regulation","url":"https://eur-lex.europa.eu/eli/reg/2014/910/oj/eng","note":"European Union"},{"title":"General Data Protection Regulation","url":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","note":"European Union"},{"title":"RFC 3339: Date and Time on the Internet","url":"https://www.rfc-editor.org/rfc/rfc3339.html","note":"Internet Engineering Task Force"},{"title":"PROV-O: The PROV Ontology","url":"https://www.w3.org/TR/prov-o/","note":"World Wide Web Consortium"},{"title":"Data Quality Vocabulary","url":"https://www.w3.org/TR/vocab-dqv/","note":"World Wide Web Consortium"},{"title":"ODRL Information Model 2.2","url":"https://www.w3.org/TR/odrl-model/","note":"World Wide Web Consortium"},{"title":"OpenAPI Specification 3.1.1","url":"https://spec.openapis.org/oas/v3.1.1.html","note":"OpenAPI Initiative"}],"openQuestions":["Canonically adjudicate the WM-REC-002 parent signal and register relations to reporting entity, regulator, obligation, law, domain data, permit, application, case, decision, assessment, sanction, payment and records models.","Evaluate separate canonical disclosure-revision, filing-attempt, dissemination-event, acknowledgement, regulator-finding and decision models while preserving this aggregate as an assembly.","Create securities, prudential, insurance, statistics, safety, environmental, health, data-protection, utilities, transport, customs and other regulator profiles.","Benchmark and conformance-test forms, schemas, taxonomies, validation rules, signatures, deadlines, channels, acknowledgements, amendments and restatement mappings.","Validate jurisdiction, regulator, sector, reporting-entity class, obligation, public-disclosure, confidentiality, privacy, investigation, sanction and retention policies.","Pin exact external releases and obtain independent regulatory, legal, sector, compliance, privacy, security, records and data-governance review before promotion beyond reviewable-draft assurance.","Claude and Grok each timed out on one bounded attempt; no independent external result was admitted.","WM-REC-002 is only a provisional parent signal and the frozen relation ledger contains no settled WM-ECO-033 edge.","Securities, prudential, insurance, statistics, safety, environment, health, data-protection, utilities, transport, customs and other sector profiles need separate validation.","Reporting-entity identity, obligations, substantive law, domain facts, permits, applications, cases, decisions, assessments, sanctions, payments, investigations and retention remain adopting-Dimension profiles.","Every SEC, EU, EBA, EIOPA, FCA, Eurostat, XBRL, GLEIF, RFC, PROV, DQV, ODRL and OpenAPI mapping needs exact release pins and conformance tests."],"resources":{"spec":"/models/wm-eco-033-regulatory-filing-disclosure/spec.yaml","agents":"/models/wm-eco-033-regulatory-filing-disclosure/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-eco-033"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-eco-033-regulatory-filing-disclosure/spec.yaml","ver-cy/world-models/card-supplements/wm-eco-033-regulatory-filing-disclosure.json"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-09-06T18:12:19Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"interaction.properties":"Institutional or informational subject: no invented physical properties.","_supplement":"Sections authored in card supplement 1.0.0 by Claude (Opus 5.5) (2026-10-05, unreviewed). Written from the published specification and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}