EM-XCT-06 · Enterprise profiles · Published 0.1.0

Enterprise Monetary Calculation

Preserve exact monetary inputs and reproduce a same-currency total under an explicit rounding policy, with residuals and immutable correction evidence.

4 bundles · 8 layers · 21 findings · 21 questions

Required adoption limits

Required before use: read publication-addendum.md and final-review-limits.md in addition to the audited agent reading list. This list alone is incomplete (Claude R4 M1). monetary.py 0.1.0 on the tested Python runtime is the only defined verifier; cross-language digest verification is unsupported (M2). Genesis checks do not establish current access. The reference has a 256-receipt lifetime cap per Dimension, enforceable only with complete host-supplied history.

Publication addendum and exact limits

Use in a Company Dimension

Start with an exact monetary slot and an explicit rounding policy. Preserve the receipt and its original inputs; add more same-context inputs when the subject owner permits aggregation. Read the full ZIP and adoption limits before installation.

Research assurance: reviewable-draft. This is a bounded original companion. No FX, quantity-price multiplication, payment, ledger, calendar or localization execution. Currency/source/policy authenticity and rights stay with the host. 256-input/256-unique-register limits are reference bounds. Adoption limits.

Bundles → Layers → Findings → Questions

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

MC-B-identityIdentity and host2 layers

Identity and host for an optional monetary calculation receipt.

MC-L-receiptReceipt2 findings

Explicit recorded facts, questions and limits for receipt.

MC-F01

Which computation has independent identity?

Coverage: local plus host identity.

Questions
  1. MC-Q01 Which computation has independent identity?mixed-guidance
    Expected answer
    • Dimension-qualified request.id and subject
    • Report validated Dimension, receipt ID and subject; the host must establish whether this calculation needs separate identity. Missing gap: host identity/adaptation decision.
Artifacts
  • Dimension-qualified request.id and subjectRequired evidence; host/external artifacts are not automatically created or resolved.
Actions and unknown handling
  • Check immutable key; use existing host records only through a separately specified mapping; no adapter shipped. Proposed action only within authenticated host authority.
MC-F02

Does another label imply a new subject?

Coverage: host/deferred.

Questions
  1. MC-Q02 Does another label imply a new subject?host-guidance
    Expected answer
    • Stable external subject ID
    • A changed label alone is not identity evidence. Request the host subject registry or a governed equivalence decision; this package resolves no aliases.
Artifacts
  • Stable external subject IDRequired evidence; host/external artifacts are not automatically created or resolved.
Actions and unknown handling
  • Keep subject identity; designation belongs to a later profile. Proposed action only within authenticated host authority.
MC-L-sourcesSources2 findings

Explicit recorded facts, questions and limits for sources.

MC-F03

Which exact monetary slots supplied the inputs?

Coverage: local structure/host resolution.

Questions
  1. MC-Q03 Which exact monetary slots supplied the inputs?mixed-guidance
    Expected answer
    • Unique source IDs, revision/digest and original lexical amounts
    • List validated source-slot IDs, revisions, digests and original lexical amounts. Resolving those opaque pins to source bytes and ownership requires host evidence.
Artifacts
  • Unique source IDs, revision/digest and original lexical amountsRequired evidence; host/external artifacts are not automatically created or resolved.
Actions and unknown handling
  • Validate unique source slots; resolve their authority externally. Proposed action only within authenticated host authority.
MC-F04

Are source values asserted exact and readable?

Coverage: host truth/local refusal.

Questions
  1. MC-Q04 Are source values asserted exact and readable?host-guidance
    Expected answer
    • State=exact; host provenance and current read permission
    • The local state must be exact, but source accuracy and current readability require host provenance and current read authorization. Missing permission means no disclosure.
Artifacts
  • State=exact; host provenance and current read permissionRequired evidence; host/external artifacts are not automatically created or resolved.
Actions and unknown handling
  • Request missing value/authority; never replace unknown with zero. Proposed action only within authenticated host authority.
MC-B-calculationArithmetic and context2 layers

Arithmetic and context for an optional monetary calculation receipt.

MC-L-admissionAdmission3 findings

Explicit recorded facts, questions and limits for admission.

MC-F05

Are currency catalogue editions identical?

Coverage: local equality/host resolution.

Questions
  1. MC-Q05 Are currency catalogue editions identical?mixed-guidance
    Expected answer
    • Complete CurrencyReference on each input/policy
    • Compare all five CurrencyReference fields locally; mismatch rejects. Code existence, catalogue authenticity and eligibility still require the host catalogue resolution.
Artifacts
  • Complete CurrencyReference on each input/policyRequired evidence; host/external artifacts are not automatically created or resolved.
Actions and unknown handling
  • Refuse mixed tuples; do not fetch or select FX. Proposed action only within authenticated host authority.
MC-F06

Do valuation basis, role and instant agree?

Coverage: local plus host.

Questions
  1. MC-Q06 Do valuation basis, role and instant agree?mixed-guidance
    Expected answer
    • Complete matching Context plus host aggregation decision
    • Compare basis pin, amountRole and valuationAt locally; mismatch rejects. To approve aggregation also request the host basis and aggregation policy.
Artifacts
  • Complete matching Context plus host aggregation decisionRequired evidence; host/external artifacts are not automatically created or resolved.
Actions and unknown handling
  • Refuse mismatches; ask policy owner about business comparability. Proposed action only within authenticated host authority.
MC-F07

Are decimal precision and original scale preserved?

Coverage: local.

Questions
  1. MC-Q07 Are decimal precision and original scale preserved?local-guidance
    Expected answer
    • ASCII amount string and declaredScale
    • After validation, return the original ASCII amount token and declaredScale; enforce 36 total and 18 fractional digits. No source precision beyond that declaration is proved.
Artifacts
  • ASCII amount string and declaredScaleRequired evidence; host/external artifacts are not automatically created or resolved.
Actions and unknown handling
  • Reject float, exponent, overcapacity and signed zero. Proposed action only within authenticated host authority.
MC-L-roundingRounding4 findings

Explicit recorded facts, questions and limits for rounding.

MC-F08

Who chose increment, mode and stage?

Coverage: local fields/host authority.

Questions
  1. MC-Q08 Who chose increment, mode and stage?mixed-guidance
    Expected answer
    • Pinned policy authority; explicit positive increment
    • Return the policy authority pin, increment, mode and stage. To identify who was entitled to choose them, request authenticated policy evidence from the host.
Artifacts
  • Pinned policy authority; explicit positive incrementRequired evidence; host/external artifacts are not automatically created or resolved.
Actions and unknown handling
  • Apply only explicit declaration; request unresolved policy. Proposed action only within authenticated host authority.
MC-F09

Was each item rounded or only the total?

Coverage: local.

Questions
  1. MC-Q09 Was each item rounded or only the total?local-guidance
    Expected answer
    • Policy stage and ordered step trace
    • Return policy.stage and the validated ordered steps: per-item quantizes each input before summing; after-sum quantizes the exact sum once.
Artifacts
  • Policy stage and ordered step traceRequired evidence; host/external artifacts are not automatically created or resolved.
Actions and unknown handling
  • Replay per-item or after-sum without changing original inputs. Proposed action only within authenticated host authority.
MC-F10

What changed through rounding?

Coverage: local.

Questions
  1. MC-Q10 What changed through rounding?local-guidance
    Expected answer
    • Exact total, result, step residuals, aggregate residual, inexact
    • Return exactTotal, roundedTotal, each signed residual, total residual and inexact. Explain cancellation: zero total residual can coexist with inexact=true.
Artifacts
  • Exact total, result, step residuals, aggregate residual, inexactRequired evidence; host/external artifacts are not automatically created or resolved.
Actions and unknown handling
  • Keep residuals even if they cancel. Proposed action only within authenticated host authority.
MC-F11

Can this total authorize a payment or posting?

Coverage: host/deferred.

Questions
  1. MC-Q11 Can this total authorize a payment or posting?constant-guidance
    Expected answer
    • Result authority=calculation-only
    • No. The result is calculation-only and cannot authorize a payment, posting or access change. A separate authorized host workflow is required.
Artifacts
  • Result authority=calculation-onlyRequired evidence; host/external artifacts are not automatically created or resolved.
Actions and unknown handling
  • Return no operational permission; consult separate domain process. Proposed action only within authenticated host authority.
MC-B-historyHistory and exchange2 layers

History and exchange for an optional monetary calculation receipt.

MC-L-historyHistory3 findings

Explicit recorded facts, questions and limits for history.

MC-F12

Which instant is valuation and which computation/storage?

Coverage: local shape/host plausibility.

Questions
  1. MC-Q12 Which instant is valuation and which computation/storage?mixed-guidance
    Expected answer
    • Context valuationAt, request computedAt, native recordedAt
    • Return context.valuationAt, request.computedAt and, when a genesis envelope is supplied and validated, recordedAt. Missing envelope means storage time is unknown.
Artifacts
  • Context valuationAt, request computedAt, native recordedAtRequired evidence; host/external artifacts are not automatically created or resolved.
Actions and unknown handling
  • Preserve separate meanings; validate strict UTC shape. Proposed action only within authenticated host authority.
MC-F13

How is an incorrect result corrected?

Coverage: local merge/host storage.

Questions
  1. MC-Q13 How is an incorrect result corrected?local-guidance
    Expected answer
    • New receipt ID, predecessor pin, reason
    • Create a new receipt ID with exact predecessor pin and nonblank reason; import the complete register to check issuer/subject continuity and chronology. Never mutate the original.
Artifacts
  • New receipt ID, predecessor pin, reasonRequired evidence; host/external artifacts are not automatically created or resolved.
Actions and unknown handling
  • Append a successor after complete-register validation. Proposed action only within authenticated host authority.
MC-F14

Which conflicting successor is current?

Coverage: host/deferred.

Questions
  1. MC-Q14 Which conflicting successor is current?host-guidance
    Expected answer
    • All immutable branches and governance evidence
    • No current winner is selected. Report all validated branches and request the host current-state governance decision and complete current native history.
Artifacts
  • All immutable branches and governance evidenceRequired evidence; host/external artifacts are not automatically created or resolved.
Actions and unknown handling
  • Return a context gap; do not select newest or overwrite. Proposed action only within authenticated host authority.
MC-L-exchangeExchange3 findings

Explicit recorded facts, questions and limits for exchange.

MC-F15

Can a receipt be replayed after import?

Coverage: local.

Questions
  1. MC-Q15 Can a receipt be replayed after import?local-guidance
    Expected answer
    • Exact request/result/digest/version
    • validate replays the exact versioned request and verifies result/digest. Complete-register import additionally checks conflict and lineage; missing predecessor rejects.
Artifacts
  • Exact request/result/digest/versionRequired evidence; host/external artifacts are not automatically created or resolved.
Actions and unknown handling
  • load then validate; compare replay; reject dropped pins. Proposed action only within authenticated host authority.
MC-F16

Does V3 outer validation prove the nested result?

Coverage: local binding.

Questions
  1. MC-Q16 Does V3 outer validation prove the nested result?constant-guidance
    Expected answer
    • Outer schema plus validate_native and register validation
    • No. Outer V3 validity alone cannot prove arithmetic. Call the companion validator and complete-register import explicitly; host checks current native history separately.
Artifacts
  • Outer schema plus validate_native and register validationRequired evidence; host/external artifacts are not automatically created or resolved.
Actions and unknown handling
  • Run each check explicitly; do not infer automatic dispatch. Proposed action only within authenticated host authority.
MC-F17

Can this package migrate an old schema?

Coverage: deferred.

Questions
  1. MC-Q17 Can this package migrate an old schema?constant-guidance
    Expected answer
    • Versioned mapping and preserved old bytes
    • No old-schema migration is implemented. Only same-version lossless replay is supported. Request a separately reviewed version mapping before migration.
Artifacts
  • Versioned mapping and preserved old bytesRequired evidence; host/external artifacts are not automatically created or resolved.
Actions and unknown handling
  • Refuse unknown versions; future mapping required. Proposed action only within authenticated host authority.
MC-B-governanceAdoption and limits2 layers

Adoption and limits for an optional monetary calculation receipt.

MC-L-governanceGovernance2 findings

Explicit recorded facts, questions and limits for governance.

MC-F18

Who may issue, read and retain receipts?

Coverage: host.

Questions
  1. MC-Q18 Who may issue, read and retain receipts?host-guidance
    Expected answer
    • Authenticated actor, issuer admission, object authority and retention policy
    • Request actor-to-issuer authentication, separate historical/incoming admissions, current access and retention policy. Set membership and a hash do not establish these rights.
Artifacts
  • Authenticated actor, issuer admission, object authority and retention policyRequired evidence; host/external artifacts are not automatically created or resolved.
Actions and unknown handling
  • Require host controls; metadata is restricted. Proposed action only within authenticated host authority.
MC-F19

Does a reference pin prove source truth or license?

Coverage: host/expert.

Questions
  1. MC-Q19 Does a reference pin prove source truth or license?constant-guidance
    Expected answer
    • Resolved source evidence and rights
    • No. A pin does not prove truth, authorship or licence. Request trusted source bytes, defined digest preimage and applicable rights from the host.
Artifacts
  • Resolved source evidence and rightsRequired evidence; host/external artifacts are not automatically created or resolved.
Actions and unknown handling
  • Report unresolved context; digest alone grants nothing. Proposed action only within authenticated host authority.
MC-L-limitsLimits2 findings

Explicit recorded facts, questions and limits for limits.

MC-F20

Can 256-record history scale indefinitely?

Coverage: local cap/deferred scaling.

Questions
  1. MC-Q20 Can 256-record history scale indefinitely?constant-guidance
    Expected answer
    • Measured capacity and complete reference closure
    • No. This reference has a hard lifetime limit of 256 receipt IDs per Dimension. Partitioning is unsupported; production requires a separately reviewed complete-history/index design.
Artifacts
  • Measured capacity and complete reference closureRequired evidence; host/external artifacts are not automatically created or resolved.
Actions and unknown handling
  • Refuse excess; require separately reviewed production storage. Proposed action only within authenticated host authority.
MC-F21

Are quantity, FX, calendar and localization cases implemented?

Coverage: deferred.

Questions
  1. MC-Q21 Are quantity, FX, calendar and localization cases implemented?constant-guidance
    Expected answer
    • Explicit contour disposition and future test assignments
    • No. Quantity, quantity times price, FX, calendar/DST and localization remain future work within EM-XCT-06. This release implements same-context money summation and quantization only.
Artifacts
  • Explicit contour disposition and future test assignmentsRequired evidence; host/external artifacts are not automatically created or resolved.
Actions and unknown handling
  • Keep these open; no default rates, unit conversions or availability. Proposed action only within authenticated host authority.

Research and validation

Actual Claude and Grok independent studies plus four separate frozen full-package no-tools audit rounds. Both final R4 audits accept the bounded original monetary receipt with limits. Claude R4 M1/M2 documentation-sufficiency findings are carried explicitly in a visible publication addendum. Code and native fixture executions 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-monetary-calculation. EM-XCT-06 remains a broader, partially covered research contour. Parent models are semantic references; no subtype or whole-parent conformance is asserted.