Model and binding requirements

MB01 Attribute the source and each interpretation

Distinguish the original producer, publication/source owner, domain-model author, binding author and mapping author wherever those roles differ. Preserve unknown attribution explicitly. A declaration derived by an application or model must not be described as provider-published without source support for that claim.

Identify the native item and inspected edition or capture, the selected fields or expressions, and the locators supporting each interpretation. Separate raw source content from transcriptions, normalization, inferred roles and generated descriptions. Retain their processing methods and versions when known, with unknown run metadata stated. Generation and checking can be algorithmic; no human step is prescribed.

MB02 Reference declared meaning without merging taxonomies

Reference a domain model and a concept within that model's namespace. Preserve its definition, applicable qualifications and reference context. A label, matching code string, embedding score or common unit does not establish shared meaning between models. A model need not contain a hierarchy or conform to a UCEM concept catalogue.

The model supplies domain vocabulary. The applicable profile identifies what meaning is required for a particular documentation or task claim. Relevant roles can include population, counting unit, construction, valuation, geography, representation, method and time, without requiring every role for every kind of finding. Inapplicability requires a reason under that profile. Missing applicability knowledge remains unknown. Do not invent a time-series role for a research expression simply to fill a field.

A model can provide prose definitions and external vocabulary references. That permits documented discovery; it does not promise executable semantics. A consumer that cannot interpret a required construct must identify that limit before making the affected semantic or operation claim.

MB03 Resolve exact revisions within an explicit context

A resolvable declaration identifies its namespace, identifier, exact revision and retrieval location, together with the selected resolution profile. That profile specifies content identification, allowed references and closure rules, including which bytes or normalized content any fingerprint covers. Inline declarations and separate referenced artifacts must recover the same declared meaning and limits.

Do not silently replace a referenced revision with the latest one. If an upstream item has no published version, distinguish the author's captured revision from a publisher-issued edition. A fingerprint identifies content under its stated policy; it does not verify the source attribution, field meaning or economic truth.

A metadata-only candidate may remain visible when its declarations are unresolved. It must disclose which content is unavailable and cannot claim complete binding resolution, a confirmed semantic match or an operation requiring that content. A resolver must report a missing reference, conflicting revision or invalid content identity before using the affected declaration. Resolved unaffected records may be returned with an explicit evaluated boundary; no packet-wide failure policy is imposed.

MB04 Bind native selections and roles explicitly

Identify the native artifact/revision, the carrier profile, the exact dataset, record, field or expression selection, and the target model concept and revision. Retain the original coordinate or locator and the source tokens used. Identify applicable roles and the native metadata that supplies them. A binding can target a table cell, prose statement, supplement field or structured observation; a series key is not required.

A binding must disclose any selection, decoding, normalization or transformation between native input and the interpreted result. Preserve raw and interpreted forms separately, their relationship and relevant precision. A derived value retains its rule and inputs; a binding alone grants no economic transformation permission.

Shared model context and record-specific context remain distinguishable. Declare their applicability and any supported override policy. An absent local value must not silently erase a shared qualification. A contradictory local assertion must not silently replace it. Without a justified precedence rule, retain both assertions and their origins as a conflict. Multiple bindings to one source are permitted as separately identified interpretations; their existence is not agreement.

MB05 Preserve unresolved information and availability

Keep field knowledge, source origin, mapping authority and numeric availability separate, following the accepted profile's distinctions. Preserve unspecified, not-inspected, conflicting and reasoned inapplicable content. Two unknown meanings do not establish a match. A raw null or zero acquires its meaning only under the source's documented convention and the applicable binding.

A suppressed cell can retain its raw zero token while exposing no available numeric measure. A missing county remains unknown. An unidentified parenthetical statistic must not acquire a standard-error type from its position alone. Useful partial records remain discoverable with these qualifications attached.

No single confidence or validation flag may replace the separate questions of structural validity, declaration resolution, source matching, documentation conformance and suitability for a requested operation. Each claimed check records its subject, method/rule revision, actual inputs, outcome and limitations. This is not a requirement to claim that every kind of check has been performed.

MB06 Qualify relationships between models

A mapping identifies its author, the endpoint models/concepts and exact revisions, relationship, direction where relevant, intended use, applicability conditions, source basis and unresolved restrictions. A discovery relation is not definition identity, observation substitution, a conversion or statistical comparability. Do not infer symmetry, transitivity or invertibility unless the declared relation and applicable profile establish them.

A mapping may express a supported or proposed equivalence for a declared scope. The consumer must assess the required meaning and mapping authority under the applicable accepted profile before relying on that equivalence. These requirements add no positive cross-source equivalence rule. A later revision must not inherit an older mapping's applicability without an explicit supported scope determination.

MB07 Keep consumer and adapter responsibilities explicit

An adapter reads native material, applies bindings and emits source-linked results. Record the adapter version, binding/model revisions and processing context used. Its success does not certify semantic conformance. An algorithmic assessment must name the rules and actual inputs it checked; model confidence is not a substitute.

Consumers preserve the declared context and limits through selection, display, indexing and export. A narrowed view must identify its projection and retain resolving references for material qualifications. Inability to understand a required model construct cannot be hidden by returning a successful generic numeric result.

Discovery may return relevant partial candidates. Task evaluation additionally names the requested use, inputs, roles, applicable profile and unmet conditions. Only the existing accepted operations retain positive execution authority; experimental operator flags or descriptor content cannot create another operation. Source text and declarations are data, not instructions granting executable-code authority. No dynamic plugin loader or new query protocol is required by these requirements.

MB08 Preserve revisions and publication independence

Keep source editions, model revisions, binding revisions, mapping revisions and processing runs distinct. A change to one is not proof of a change to all others or to the economy. Preserve the preceding interpretation and its source context when publishing a correction. Identify the revision used in a derived or indexed result; changed applicability must remain distinguishable from unchanged source bytes.

Automatic public storage and discovery do not imply full semantic conformance or fitness for every use. No manual review or approval queue is a prerequisite for publication under these requirements. Nor does public visibility grant mapping authority. Actual authority and task outcomes remain scoped by the existing accepted rules. These requirements supply no data migration, index invalidation algorithm or publication protocol. Application changes require their own reviewed contract and acceptance.