Enterprise Quantity Values

Identity and identifiers required Filled

• Host record ID with its single quantity slot.
• Unit definition ID and version.

Direct properties not applicable Not applicable

Not applicable

A quantity value describes another object; the measured object carries the physical properties.

Recognition optional Filled

• A quantity value has a decimal notation, a unit, a quantity kind and a role (point or difference).

Capabilities and actions required Filled

• Use the existing host and its single semantic quantity slot. Do not create artificial hosts to evade this native limit; multi-field binding needs a separate adapter. Proposed action subject to authenticated host permission.
• Keep the semantic assertion owner separate from the system recording a copy. Proposed action subject to authenticated host permission.
• Resolve and admit the complete definition; code equality alone is insufficient. Proposed action subject to authenticated host permission.
• Preserve the old value; refuse implicit upgrade and require explicit fresh admission. Proposed action subject to authenticated host permission.
• Preserve absence and ask the source owner for missing evidence; do not insert zero. Proposed action subject to authenticated host permission.
• Retain trailing zeros and signed zero; do not infer uncertainty from digits. Proposed action subject to authenticated host permission.
• Unit one is explicit; an annotation or missing unit does not resolve the business subject. Proposed action subject to authenticated host permission.
• Refuse equal dimensions with different kinds, including energy versus torque. Proposed action subject to authenticated host permission.
• Use the declared role; offsets apply only to points. Do not infer a role from a glyph. Proposed action subject to authenticated host permission.
• Require context/role equality before numeric comparison; domain permission remains external. Proposed action subject to authenticated host permission.
• Normalize only under verified authority; refuse direct copying of incompatible source columns. Proposed action subject to authenticated host permission.
• Do not relabel a rounded coefficient. Exactness is host evidence, not decimal syntax. Proposed action subject to authenticated host permission.
• Refuse the unsupported transform and route extension needs to the host assertion owner; do not invent a linear approximation.
• Run exact nested replay; schema validity alone cannot validate arithmetic. Proposed action subject to authenticated host permission.
• Route billing or conformity requests to the respective host contract; a numeric coordinate is not an authorization. Proposed action subject to authenticated host permission.
• Validate the stored binding after V3 outer checks with authenticated expected host parameters. Proposed action subject to authenticated host permission.
• For the same master/writer/access and input kind/dimension/anchor/role/context, append a new native fact and validate the correction pair; preserve old bytes. A semantic or actor change requires a separate governed workflow. Proposed action subject to authenticated host permission.
• Identical native append is refused. A future adapter must inspect conflicts before a governed skip. Proposed action subject to authenticated host permission.
• Check current inspection permission separately from incoming-write permission and source authenticity. Proposed action subject to authenticated host permission.
• Keep Price/FX, working calendars, uncertainty and localization open; do not claim EM-XCT-06 completion. Proposed action subject to authenticated host permission.

Hazards and failure modes required Filled

• Unit confusion (for example pounds and kilograms).
• Offset errors in temperature conversions.

Standards and interfaces required Filled

• UCUM unit codes.
• QUDT quantity kinds and units.
• ISO/IEC 80000 quantities and units.

Context of use required Filled

• Product data, logistics, maintenance and any record carrying measurements.