# Scope

CommerceCanon owns counterparty and commercial-relationship semantics under
CUST-ADR-006. Its shared technical concepts are imported from InfoTechCanon.

## In scope

- Preserve the existing research corpus, scenarios, terminology, Git history,
  and finished IDENTITY-WP workplans as provenance.
- Implement the commerce assignments in the federation ownership ledger.
- Establish the canon layout, kernel boundary, and reciprocal interface cards.
- Separate commercial records from login accounts and model commercial binding
  explicitly, carrying forward design principles P14 and P15.
- Grow through named consumer demand; record implementation in local workplans.

## Out of scope

- Re-own identity, organization, access-control, governance, or general evidence
  concepts; redefine Adjudication Outcome in CommerceCanon.
- Implement runtime identity or payment services, production APIs, or a CLI.
- Author Family beyond the separately owned seed or speculative new commercial
  concepts. Consumer adoption is separately owned.

## Migration status

The repository rename preserves history. The old mixed glossary remains a
migration input until CFED-WP-0001-T04/T05/T06/T07 establish the destination
layout, models, and provenance distribution. Rename completion does not imply
those publication gates have passed.

See INTENT.md, research/CorpusIndex.md, and the federation ledger. New plans use
COMMERCE-WP-; existing IDENTITY-WP identifiers and finished files remain intact.