EM-XCT-06 · Enterprise profiles · Published 0.1.0

Enterprise Quantity Values

Embed governed scalar quantities in existing company objects, preserve accepted normalized decimal notation and reproduce exact affine unit conversions without creating a second quantity master.

4 bundles · 8 layers · 20 findings · 20 questions

Required adoption limits

Read the publication addendum before adoption. Every correction requires the retained predecessor and an explicit validate_correction call; head-only validation is insufficient. Read each conversion result with its own target, and govern unit/target changes explicitly. Native reference: one semantic quantity per existing host.

Publication addendum and exact limits

Use in a Company Dimension

Attach the value profile to an existing company object. Begin with an admitted definition, source and context; preserve original values and require explicit nested validation. No independent Quantity object is created.

Research assurance: reviewable-draft. This is a bounded original companion. Native reference: one semantic quantity per existing host, with one value and one conversion slot; multi-field native binding is deferred. Exact scalar/affine subset only. External-definition authority, physical truth, uncertainty, current permissions and source resolution remain with the host. No UCUM parser, price/FX, calendar or localization engine. Adoption limits.

Bundles → Layers → Findings → Questions

Collect the expected evidence for each question. Unknown context remains explicit. Listed actions confer no operational permission.

QV-B1Host and reference2 layers

Decisions and evidence for host and reference.

QV-B1-L1Embedding2 findings

Explicit embedding contract and boundaries.

QV-F01

What hosts this quantity?

Coverage: host.

Questions
  1. QV-Q01 What hosts this quantity?host-guidance
    Expected answer
    • Existing qualified host ID and one semantic quantity slot
    • 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.
Artifacts
  • Existing qualified host ID and one semantic quantity slotRequired evidence; external governance artifacts are supplied by the host, not automatically created.
Actions and unknown handling
  • 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.
QV-F02

Is the host semantic source also the capture master?

Coverage: host.

Questions
  1. QV-Q02 Is the host semantic source also the capture master?host-guidance
    Expected answer
    • Semantic source Pin and capture provenance
    • Keep the semantic assertion owner separate from the system recording a copy.
Artifacts
  • Semantic source Pin and capture provenanceRequired evidence; external governance artifacts are supplied by the host, not automatically created.
Actions and unknown handling
  • Keep the semantic assertion owner separate from the system recording a copy. Proposed action subject to authenticated host permission.
QV-B1-L2Definition2 findings

Explicit definition contract and boundaries.

QV-F03

Which exact unit definition is admitted?

Coverage: mixed.

Questions
  1. QV-Q03 Which exact unit definition is admitted?mixed-guidance
    Expected answer
    • Full UnitDefinition digest and independent source evidence
    • Resolve and admit the complete definition; code equality alone is insufficient.
Artifacts
  • Full UnitDefinition digest and independent source evidenceRequired evidence; external governance artifacts are supplied by the host, not automatically created.
Actions and unknown handling
  • Resolve and admit the complete definition; code equality alone is insufficient. Proposed action subject to authenticated host permission.
QV-F04

Does a new registry edition change this historical value?

Coverage: mixed.

Questions
  1. QV-Q04 Does a new registry edition change this historical value?mixed-guidance
    Expected answer
    • Old revision snapshot and separately approved new definition
    • Preserve the old value; refuse implicit upgrade and require explicit fresh admission.
Artifacts
  • Old revision snapshot and separately approved new definitionRequired evidence; external governance artifacts are supplied by the host, not automatically created.
Actions and unknown handling
  • Preserve the old value; refuse implicit upgrade and require explicit fresh admission. Proposed action subject to authenticated host permission.
QV-B2Numeric meaning2 layers

Decisions and evidence for numeric meaning.

QV-B2-L1Magnitude3 findings

Explicit magnitude contract and boundaries.

QV-F05

Is the value known, withheld or absent?

Coverage: local.

Questions
  1. QV-Q05 Is the value known, withheld or absent?local-guidance
    Expected answer
    • KnownMagnitude or explicit MissingMagnitude with reason
    • Preserve absence and ask the source owner for missing evidence; do not insert zero.
Artifacts
  • KnownMagnitude or explicit MissingMagnitude with reasonRequired evidence; external governance artifacts are supplied by the host, not automatically created.
Actions and unknown handling
  • Preserve absence and ask the source owner for missing evidence; do not insert zero. Proposed action subject to authenticated host permission.
QV-F06

Which decimal notation was asserted?

Coverage: mixed.

Questions
  1. QV-Q06 Which decimal notation was asserted?mixed-guidance
    Expected answer
    • Original lexical string, scale and precisionMeaning
    • Retain trailing zeros and signed zero; do not infer uncertainty from digits.
Artifacts
  • Original lexical string, scale and precisionMeaningRequired evidence; external governance artifacts are supplied by the host, not automatically created.
Actions and unknown handling
  • Retain trailing zeros and signed zero; do not infer uncertainty from digits. Proposed action subject to authenticated host permission.
QV-F07

Does unit one mean the counting subject is known?

Coverage: mixed.

Questions
  1. QV-Q07 Does unit one mean the counting subject is known?mixed-guidance
    Expected answer
    • Resolved unit definition plus kind and context
    • Unit one is explicit; an annotation or missing unit does not resolve the business subject.
Artifacts
  • Resolved unit definition plus kind and contextRequired evidence; external governance artifacts are supplied by the host, not automatically created.
Actions and unknown handling
  • Unit one is explicit; an annotation or missing unit does not resolve the business subject. Proposed action subject to authenticated host permission.
QV-B2-L2Compatibility3 findings

Explicit compatibility contract and boundaries.

QV-F08

Do the quantities have compatible kinds?

Coverage: local.

Questions
  1. QV-Q08 Do the quantities have compatible kinds?local-guidance
    Expected answer
    • Exact kind, dimension and anchor pins
    • Refuse equal dimensions with different kinds, including energy versus torque.
Artifacts
  • Exact kind, dimension and anchor pinsRequired evidence; external governance artifacts are supplied by the host, not automatically created.
Actions and unknown handling
  • Refuse equal dimensions with different kinds, including energy versus torque. Proposed action subject to authenticated host permission.
QV-F09

Is this a point or a difference?

Coverage: mixed.

Questions
  1. QV-Q09 Is this a point or a difference?mixed-guidance
    Expected answer
    • Quantity role and unit allowed roles
    • Use the declared role; offsets apply only to points. Do not infer a role from a glyph.
Artifacts
  • Quantity role and unit allowed rolesRequired evidence; external governance artifacts are supplied by the host, not automatically created.
Actions and unknown handling
  • Use the declared role; offsets apply only to points. Do not infer a role from a glyph. Proposed action subject to authenticated host permission.
QV-F10

Do two values share a comparison basis?

Coverage: mixed.

Questions
  1. QV-Q10 Do two values share a comparison basis?mixed-guidance
    Expected answer
    • Exact context pins and same role
    • Require context/role equality before numeric comparison; domain permission remains external.
Artifacts
  • Exact context pins and same roleRequired evidence; external governance artifacts are supplied by the host, not automatically created.
Actions and unknown handling
  • Require context/role equality before numeric comparison; domain permission remains external. Proposed action subject to authenticated host permission.
QV-B3Transformation2 layers

Decisions and evidence for transformation.

QV-B3-L1Formula3 findings

Explicit formula contract and boundaries.

QV-F11

In which order are multiplier and offset applied?

Coverage: mixed.

Questions
  1. QV-Q11 In which order are multiplier and offset applied?mixed-guidance
    Expected answer
    • Explicit anchor=a*x+b with exact reduced rational coefficients
    • Normalize only under verified authority; refuse direct copying of incompatible source columns.
Artifacts
  • Explicit anchor=a*x+b with exact reduced rational coefficientsRequired evidence; external governance artifacts are supplied by the host, not automatically created.
Actions and unknown handling
  • Normalize only under verified authority; refuse direct copying of incompatible source columns. Proposed action subject to authenticated host permission.
QV-F12

Is a finite catalogue coefficient exact by definition?

Coverage: host.

Questions
  1. QV-Q12 Is a finite catalogue coefficient exact by definition?host-guidance
    Expected answer
    • Independent exact-definition authority and admitted snapshot
    • Do not relabel a rounded coefficient. Exactness is host evidence, not decimal syntax.
Artifacts
  • Independent exact-definition authority and admitted snapshotRequired evidence; external governance artifacts are supplied by the host, not automatically created.
Actions and unknown handling
  • Do not relabel a rounded coefficient. Exactness is host evidence, not decimal syntax. Proposed action subject to authenticated host permission.
QV-F13

Can a logarithmic or procedure unit be converted?

Coverage: local.

Questions
  1. QV-Q13 Can a logarithmic or procedure unit be converted?local-guidance
    Expected answer
    • Unsupported-unit refusal and host escalation destination
    • Refuse the unsupported transform and route extension needs to the host assertion owner; do not invent a linear approximation.
Artifacts
  • Unsupported-unit refusal and host escalation destinationRequired evidence; external governance artifacts are supplied by the host, not automatically created.
Actions and unknown handling
  • Refuse the unsupported transform and route extension needs to the host assertion owner; do not invent a linear approximation.
QV-B3-L2Result2 findings

Explicit result contract and boundaries.

QV-F14

Can the converted result be reproduced?

Coverage: local.

Questions
  1. QV-Q14 Can the converted result be reproduced?local-guidance
    Expected answer
    • Original QuantityValue, target UnitDefinition and reduced rational result
    • Run exact nested replay; schema validity alone cannot validate arithmetic.
Artifacts
  • Original QuantityValue, target UnitDefinition and reduced rational resultRequired evidence; external governance artifacts are supplied by the host, not automatically created.
Actions and unknown handling
  • Run exact nested replay; schema validity alone cannot validate arithmetic. Proposed action subject to authenticated host permission.
QV-F15

Does the result authorize billing or conformity?

Coverage: host.

Questions
  1. QV-Q15 Does the result authorize billing or conformity?host-guidance
    Expected answer
    • Optional separate price/tolerance and domain authority evidence when such an action is requested
    • Route billing or conformity requests to the respective host contract; a numeric coordinate is not an authorization.
Artifacts
  • Optional separate price/tolerance and domain authority evidence when such an action is requestedConditional external evidence for billing or conformity requests; not required for numeric conversion.
Actions and unknown handling
  • Route billing or conformity requests to the respective host contract; a numeric coordinate is not an authorization. Proposed action subject to authenticated host permission.
QV-B4Operation and evolution2 layers

Decisions and evidence for operation and evolution.

QV-B4-L1Storage3 findings

Explicit storage contract and boundaries.

QV-F16

Which native record carries the result?

Coverage: mixed.

Questions
  1. QV-Q16 Which native record carries the result?mixed-guidance
    Expected answer
    • Existing host object and quantity.value or quantity.conversion fact
    • Validate the stored binding after V3 outer checks with authenticated expected host parameters.
Artifacts
  • Existing host object and quantity.value or quantity.conversion factRequired evidence; external governance artifacts are supplied by the host, not automatically created.
Actions and unknown handling
  • Validate the stored binding after V3 outer checks with authenticated expected host parameters. Proposed action subject to authenticated host permission.
QV-F17

What changed in a correction?

Coverage: mixed.

Questions
  1. QV-Q17 What changed in a correction?mixed-guidance
    Expected answer
    • Two retained fact records, predecessor ID, chronology and reason
    • 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.
Artifacts
  • Two retained fact records, predecessor ID, chronology and reasonRequired evidence; external governance artifacts are supplied by the host, not automatically created.
Actions and unknown handling
  • 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.
QV-F18

Is replaying an import safe?

Coverage: host.

Questions
  1. QV-Q18 Is replaying an import safe?host-guidance
    Expected answer
    • Existing native ID and exact stored bytes under host authority
    • Identical native append is refused. A future adapter must inspect conflicts before a governed skip.
Artifacts
  • Existing native ID and exact stored bytes under host authorityRequired evidence; external governance artifacts are supplied by the host, not automatically created.
Actions and unknown handling
  • Identical native append is refused. A future adapter must inspect conflicts before a governed skip. Proposed action subject to authenticated host permission.
QV-B4-L2Adoption2 findings

Explicit adoption contract and boundaries.

QV-F19

Who may inspect old source definitions now?

Coverage: host.

Questions
  1. QV-Q19 Who may inspect old source definitions now?host-guidance
    Expected answer
    • Current access decision and historical-reference admission
    • Check current inspection permission separately from incoming-write permission and source authenticity.
Artifacts
  • Current access decision and historical-reference admissionRequired evidence; external governance artifacts are supplied by the host, not automatically created.
Actions and unknown handling
  • Check current inspection permission separately from incoming-write permission and source authenticity. Proposed action subject to authenticated host permission.
QV-F20

Which broader enterprise functions remain missing?

Coverage: host.

Questions
  1. QV-Q20 Which broader enterprise functions remain missing?host-guidance
    Expected answer
    • Contour disposition, adoption limits and proposed next assignments
    • Keep Price/FX, working calendars, uncertainty and localization open; do not claim EM-XCT-06 completion.
Artifacts
  • Contour disposition, adoption limits and proposed next assignmentsRequired evidence; external governance artifacts are supplied by the host, not automatically created.
Actions and unknown handling
  • Keep Price/FX, working calendars, uncertainty and localization open; do not claim EM-XCT-06 completion. Proposed action subject to authenticated host permission.

Research and validation

Actual independent Claude and Grok contour studies reused, followed by three separate full-candidate quantity audit rounds. Earlier disagreement is retained: Claude requested revisions; Grok accepted with limits. Both final R3 audits accept this bounded embedded profile with limits. Executed code/native checks are separate Codex evidence. Executed tests and native checks are recorded separately. Research dossier · Review and limits · Tests · Native acceptance · Checksums.

Catalogue identity: vr.profile.enterprise-quantity-values. EM-XCT-06 remains a broader, partially covered research contour. Parent models are semantic references; no subtype or whole-parent conformance is asserted.