Complete CommerceCanon rename and declare concept ownership boundary

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a070b5-4994-7271-bd8b-7c3dbcedec4b

SCOPE.md

@@ -1,54 +1,32 @@
-# SCOPE
+# Scope
 
-## One-liner
+CommerceCanon owns counterparty and commercial-relationship semantics under
+CUST-ADR-006. Its shared technical concepts are imported from InfoTechCanon.
 
-Orthogonal vocabulary and canonical model for identity-related concepts.
+## In scope
 
-## Core Idea
+- 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.
 
-`identity-canon` is a research and terminology repository. It defines an
-implementation-neutral vocabulary and conceptual model for identity, accounts,
-actors, organizations, tenants, communities, families, agents, relationships,
-and synonymity across IAM, directory, federation, social graph, authorization,
-decentralized identity, and entity-resolution domains.
+## Out of scope
 
-## In 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.
 
-- Maintain research notes, source summaries, terminology inventories,
-  conflict maps, canonical glossary entries, conceptual model notes, scenario
-  tests, open questions, downstream recommendations, and State Hub workplans.
-- Compare overlapping terms across standards, product documentation, social
-  graph models, authorization systems, and privacy/entity-resolution research.
-- Keep canonical definitions separate from external product mappings.
-- Record decisions, progress, and workplan status through State Hub.
-- Verify changes with markdown review, `git diff --check`, and ADR-001
-  consistency checks.
+## Migration status
 
-## Out of Scope
+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.
 
-- Implement identity providers, account-management services, provisioning
-  adapters, authorization engines, UI components, CLI commands, databases, or
-  production APIs.
-- Own unrelated adjacent systems or operational identity lifecycle tooling.
-- Make irreversible operational decisions without human approval.
-- Treat draft canon artifacts as finalized schemas before source-note backfill
-  and scenario review.
-
-## Current State
-
-- Status: active research scaffold.
-- The repository is currently documentation-only. It has no package manifest,
-  build system, runtime app, or executable test suite.
-- `IDENTITY-WP-0002` seeded the first terminology, canon, model, scenario,
-  open-question, and downstream recommendation artifacts. The next research
-  pass should backfill individual source notes and revise the draft canon from
-  evidence.
-
-## Getting Oriented
-
-- Start with: INTENT.md
-- Research proposal: ResearchProposal.md
-- Corpus index: research/CorpusIndex.md
-- Draft canon: canon/CanonicalGlossary.md and model/ConceptualModel.md
-- Agent instructions: AGENTS.md
-- Workplans: workplans/
+See INTENT.md, research/CorpusIndex.md, and the federation ledger. New plans use
+COMMERCE-WP-; existing IDENTITY-WP identifiers and finished files remain intact.