---
id: commerce-core
title: CommerceCanon Core
status: draft
version: 0.1.0-draft
---

# CommerceCanon Core

CommerceCanon owns counterparty and commercial-relationship semantics. It is
an independently maintained domain canon governed by Custodian canon and the
accepted CUST-ADR-006 ownership resolutions. This draft kernel establishes the
repository boundary; it does not publish the pending counterparty model.

## Authority and migration

The [federation ledger](../../../prj-canon-federation/ledger/README.md) assigns
one owner per concept and pins the original identity-canon glossary. The old
[glossary](../../canon/CanonicalGlossary.md) and
[principles](../../canon/DesignPrinciples.md) remain migration inputs, not an
alternative registry of CommerceCanon-owned definitions. The
[registry](../../canon.yaml) lists only artifacts present here; its model and
standard registries remain empty until their publication tasks are verified.

## Ownership boundary

| Concept or concept family | Owning model | CommerceCanon treatment |
| --- | --- | --- |
| Actor, Person, Agent, Organization, Group, Role, Membership, Ownership | itc-org | Import; commercial roles do not replace actor or ownership semantics. |
| Subject, Principal, Relationship Tuple | itc-access | Import; commercial binding does not grant authorization. |
| Obligation, Decision, AssuranceCase, AssuranceConclusion, Audit | itc-gov | Import; a commercial commitment may relate to obligations without redefining them. |
| Identifier, Account, Scope, Assurance Level and ledger-assigned identity concepts | itc-ident (pending T05) | Import when published; identifier specializations retain upstream identity semantics. |
| Evidence, Evidence Source, Adjudication Outcome, general evidence strength | itc-evid (pending T11) | Import assertions and their addressable sources as distinct concepts. |
| Community, Household | itc-org extension (pending T12) | Import distinct social collectives when available. |
| Family | Separate InfoTechCanon concept-area seed (pending T13) | Reference only; not a CommerceCanon collective-actor definition. |

Existing upstream models are [organization](../../../info-tech-canon/infospace/models/organization/InfoTechCanonOrganizationModel.md),
[access control](../../../info-tech-canon/infospace/models/access-control/InfoTechCanonAccessControlModel.md),
and [governance](../../../info-tech-canon/infospace/models/governance/InfoTechCanonGovernanceModel.md).
Evidence currently appears in governance; accepted R3/R7 assigns its transfer to
T11. This table records the accepted destination, not a completed transfer.
T05 must also reconcile Delegation Relationship with itc-org Delegation before
publication. Nothing in this kernel resolves that open review by duplication.

There is no single imported concept called “Assurance” covering all uses.
Identity Assurance Level is distinct from governance AssuranceCase and
AssuranceConclusion. The pending Counterparty Assurance Gradient is CommerceCanon's
named application of general evidence strength, not ownership of that dimension.

## Commerce model boundary

T06 will author the ledger's commerce assignments: legal entities and persons,
beneficial ownership relationships and exemptions, customer and vendor roles,
commercial relationships and commitments, payment references and mandates,
pipeline pursuits, commercial records, counterparty assurance, reputation and
performance assertions, and registry/proxy commercial identifiers. These are
assignments for migration, not definitions supplied by this kernel.

Registry Identifier and Proxy Commercial Identifier specialize imported
Identifier. Reputation Signal, Performance Evidence, and Beneficial Ownership
Exemption must distinguish evidence assertions from their sources. Adjudication
Outcome remains imported from itc-evid. Carry P14 (separate commercial records
from accounts) and P15 (model commercial binding explicitly) into T06.

## Contribution and acceptance

New content starts with a named consumer's signal in [demand](../../demand/).
Implementation belongs in repository workplans. A model must declare its owned
concepts, explicit imports, provenance, and examples before registry publication.
Validate assignments against the federation ledger and review for duplicate
ownership. Preserve historical source material until T07 records its disposition.

[Repository layout](../../docs/RepositoryLayout.md) explains content placement.
T08 owns reciprocal interface cards once models and imports are established.
Runtime services, a CLI, and production APIs are outside this foundation scope.