This module classifies a selected order under one buyer, merchant, purchase policy, history declaration and as-of instant. One buyer keeps one identity across purchases, while each classification observation identifies its order and context. The legacy buyer-level buyerStatus relation keeps its original meaning and is not broadcast to every order by this route.
This is the unofficial 0.1.0 module specification. Source review and executable correctness are separate standings. Full generation, runtime and publication verification are pending configured GitHub CI; this draft supplies no release, native write or client-adoption qualification.
Scope and intended use
This module classifies a selected order under one buyer, merchant, purchase policy, history declaration and as-of instant. One buyer keeps one identity across purchases, while each classification observation identifies its order and context. The legacy buyer-level buyerStatus relation keeps its original meaning and is not broadcast to every order by this route.
Agents can inspect the selected retained evidence, ask for missing scope or review, and keep unresolved answers visible. A successful inspection remains separate from permission to act on a live account.
Competency questions
What does the selected purchase policy and history actually support about this order?
Which earlier eligible purchase supports a returning classification?
Which qualified charged-order amounts contribute to the selected subtotal and coverage?
The prefix pc names the existing vocabulary. Term identity and the original RDF types remain stable. Shared advertising and commerce concepts supply scope; captured provider terms retain their provider-specific meaning.
Conceptual model
SourceReported retains a declared offer under its policy. FirstObserved identifies the earliest eligible retained purchase without proving first-ever status. DeclaredCompleteHistory depends on a caller declaration of merchant-inception-to-as-of coverage and stable buyer scope. A real earlier eligible purchase can support Returning in partial retained history. Possible identity matches do not merge buyer histories.
Independent evidence axes
Evidence
What the consumer can conclude
Retained source
The selected bytes and represented claims remain inspectable.
Scoped interpretation
The named contract supplies a result with its own qualification and coverage.
Current action authority
Live permission, native applicability and client adoption require separately qualified evidence.
Supported eligibility policies are PlacedOnly and PlacedAndCancelled. PreservePurchase retains refunded purchases in newness history; refund-reset policies remain unresolved. Equal first timestamps need a supported tie policy. Captures after as-of are excluded. Repeated assertions of one named order do not multiply purchases, and distinct handles with the same merchant/buyer purchase key remain unresolved. Source and context roles cannot repair each other.
RDF permits incomplete descriptions. A conforming execution profile must enforce its declared closed-world input and output constraints. Unknown or conflicting business evidence must keep its explicit standing and cannot be converted into a favorable value.
Validation and interpretation
Unresolved source scalars remain explicit coverage gaps. Charged-order subtotals are grouped by context, classification basis, status and currency; they supply neither accounting net revenue nor profit. A late capture can revise a later observation while the prior observation remains historical evidence. Cross-package aggregation by context IRI alone cannot qualify currentness or deduplication. Executor support is 128 numeric digits, scale 64 and six nonzero fractional timestamp digits after trailing-zero removal; unsupported bounds do not invalidate provider grammar.
Validation establishes conformance to a selected profile. Retained scope, reported evidence and operational success keep their separate meanings. Runtime and generation evidence for this source repair remain pending GitHub CI.
Worked example and boundary
The example separates selected source orders from policy and history declarations. It illustrates declared context rather than merchant completeness. FirstObserved and source-reported New remain separate, and the classification does not establish advertising acquisition or causal attribution.
Inspect the declared roles and independent standings before using this evidence. Omitted source data or an unresolved qualification must remain visible. This example does not attest a live provider request or complete merchant history.
Term reference
Classes, properties and existing controlled evidence values retain their authored labels and definitions. Listing a controlled value here does not change its RDF type or grant execution authority.
pc:AmbiguousPurchaseKey — ambiguous purchase key
Distinct order handles share a source key in one merchant/buyer scope; this route does not infer a merge.
pc:AmbiguousPurchaseTie — ambiguous purchase tie
Independent qualifying purchases have equal first timestamps without a supported tie policy.
An order-scoped assessment under one merchant, buyer, policy, history declaration and as-of instant. A retained observation does not certify provider completeness or advertising acquisition.
The selected refund behavior is unsupported; no automatic newness reset is inferred.
pc:amountValue — amount value
A qualified charged-order amount for the selected monetary basis, preserving decimal arithmetic.
pc:asOf — as of
The declared as-of instant limiting available captures; also retained on each assessment.
pc:basis — basis
The evidence basis for the assessed status; SourceReported and FirstObserved do not establish first-ever or advertising acquisition.
pc:buyer — buyer
The declared buyer role in this evidence scope; possible identity matches do not merge buyers.
pc:capturedAt — captured at
When this retained order record was captured. Later captures are unavailable to an earlier declared as-of.
pc:context — context
The exact supplied classification context retained with this assessment.
pc:contextDigest — context digest
SHA256 of the exact retained supplied context bytes.
pc:currency — currency
The qualified currency for the selected charged amount; currencies are grouped separately.
pc:defaultClassificationService — default classification service
The selected versioned classification service for discovery; it does not change older buyer-level meanings.
pc:eligibilityPolicy — eligibility policy
Explicit purchase lifecycle eligibility. The bounded pipeline supports placed orders only or placed plus cancelled orders.
pc:eligibilityStanding — eligibility standing
The eligibility of this purchase under the explicitly selected policy.
pc:history — history
The declared retained history scope; also retained on each assessment.
pc:historyCoverage — history coverage
Caller-declared complete or partial historical coverage, not provider verification.
pc:historyStart — history start
The declared historical start, represented by MerchantInception or an explicit timestamp. A later start cannot justify first-ever classification.
pc:historyThrough — history through
The declared history coverage end; it must cover the selected as-of to support the complete-history basis.
pc:identityStanding — identity standing
Whether the caller declares a stable buyer identity or retains unresolved possible linkage.
pc:interpretationDigest — interpretation digest
SHA256 of the retained semantic interpretation bytes and executable modes, excluding catalog discovery.
pc:merchant — merchant
The named merchant scope. Same order identifier spelling across merchants is not a shared purchase.
pc:mode — mode
Selects source-reported or inferred classification without equating their evidence bases.
pc:monetaryBasis — monetary basis
The selected monetary basis, retained with assessment amounts. ChargedOrderTotal is not net revenue or profit.
pc:monetaryStanding — monetary standing
Whether one nonnegative amount and currency support the selected charged-total subtotal; unresolved amounts are not zero.
pc:order — order
The purchase assessed; the buyer identity remains distinct from this observation.
pc:policy — policy
The exact declared policy used by the selected context; also retained on each assessment.
pc:purchaseKey — purchase key
A source-declared stable purchase key scoped to merchant and buyer. Different order handles with one key are unresolved rather than automatically merged.
pc:reader — reader
An authored reader available through the selected service.
pc:readerName — reader name
The exact reader identifier selected in the generation pipeline.
pc:reason — reason
The exact qualified or unresolved classification reason for this selected purchase.
pc:refundTreatment — refund treatment
Explicit treatment of later refunds. PreservePurchase retains the purchase for newness; reset behavior is unsupported here.
pc:reportedPolicy — reported policy
The explicit source policy under which a reported purchase status is supplied.
pc:reportedStatus — reported status
A source-reported purchase status, independent of inferred first-observed or declared-complete-history classification.
pc:routeStanding — route standing
The explicit legacy or qualified discovery standing of a published query route.
pc:selectedOrder — selected order
An order selected for an assessment, including orders whose source evidence remains unresolved.
pc:sourceDigest — source digest
SHA256 of the exact retained source bytes used for the assessment.
pc:status — status
The assessed purchase status, never broadcast from the legacy Buyer-level buyerStatus relation.