Version 1.0 — Issued by CrownThrive, LLC “Architecture, Operating Model, and the Roadmap for Implementing the Compliance Hybrid Licensing & Ownership Framework.”
Audience: Strategic architects, compliance engineers, governance designers, product managers, integrators, and Help Center editors curating the CHLOM Framework & Model category. Scope: Canonical reference for what the CHLOM Framework & Model is, how it’s structured, how it operates in production, and which 30+ follow‑on docs to read next.
0 · How to Use this Master Doc (Help Center Index)
- Start here for the big picture and concrete implementation paths.
- Each section ends with “What to read next” cross‑links into the Framework & Model category.
- Diagrams and examples are illustrative; the authoritative sources are the runtime repository, governance records, and release notes.
1 · System Overview
The CHLOM™ Framework & Model defines the conceptual architecture and operating model that every implementation must follow. It unifies:
- Licensing & Ownership (tokenized rights, sublicensing, transfers)
- Compliance (jurisdictional packs, KPI enforcement, dispute handling)
- Governance (DAO proposals, councils, conviction voting, reputation)
- Economics (royalty graphs, incentives, fee/burn mechanics)
- Integration (APIs, SDKs, oracles, analytics, sustainability hooks)
This master describes the model independently of any single runtime, while mapping each component to Substrate pallets used in the reference chain.
1.1 High‑Level Architecture
+-------------------------+ +--------------------+ +---------------------------+
| Business Apps & Consoles|<---->| API Gateway / WS |<----->| Reference Chain (Runtime) |
| (Ops, Governance, LEX) | | (REST/WS/RPC) | | FRAME Pallets |
+-------------------------+ +--------------------+ +---------------------------+
| licensing / kpi / royalty |
+-------------------------+ +--------------------+ | dla / lex / gov / oracle |
| Data & Analytics |<---->| Indexers | | reputation / sustainability|
| (Dashboards, BI) | | (SubQuery/Squid) | | treasury / staking ... |
+-------------------------+ +--------------------+ +---------------------------+
+-------------------------+ +--------------------+
| Oracles & Off‑chain |<---->| OCWs + Gateways |
| (KYC, IoT, POS, ESG) | | (signed feeds) |
+-------------------------+ +--------------------+
1.2 Consensus & Accounts
The Framework & Model is chain‑agnostic but the reference chain uses:
- Consensus: BABE (block production) + GRANDPA (finality).
- Staking: NPoS (
- Accounts: SS58 addresses, sr25519/ed25519 keys; multisig via
What to read next: Doc 01 — Conceptual Architecture & Domain Model; Doc 02 — Network & Keys Handbook.
2 · Core Protocols (Functional Specs)
2.1 Licensing Protocol (LP)
Tokenizes rights/obligations as License NFTs with jurisdiction, scope, royalty model, KPI profile, sanctions/escrow rules, transfer constraints.
Extrinsics (reference impl):
- licensing.mint(class_id, metadata, terms_hash)
- licensing.sublicense(item_id, percent, buyer, constraints)
- licensing.amend(item_id, terms_hash)
- licensing.revoke(item_id, cause)
2.2 Compliance Protocol (CP)
Deterministic KPI checks with risk scoring and breach policies; integrates oracle attestations and ZK privacy where needed.
- kpi.set_thresholds(class_id, metrics[])
- kpi.report(item_id, metric_id, value, oracle_sig)
- kpi.flag(item_id, code)
2.3 Governance Protocol (GP)
CHM‑weighted governance with reputation boosts and conviction locking; councils for emergency actions; scheduled/queued execution.
- gov.propose(call, stake)
- gov.set_weighting(model)
- gov.schedule(call, when)
2.4 Economic Protocol (EP)
Royalty accounting, validator rewards, fees/burns, buybacks; KPI‑based bonuses.
- royalty.route(tx_id, splits[])
- royalty.settle(batch_id)
- treasury.buyback(amount)
What to read next: Doc 03 — Licensing Protocol Spec; Doc 04 — Compliance Protocol Spec; Doc 05 — Governance Protocol Spec; Doc 06 — Economic Protocol Spec.
3 · Runtime Pallets (FRAME)
The Framework maps conceptual modules to the reference runtime pallets below.
| Module (Concept) | Reference Pallet | Purpose | Key Storage | Key Calls | Events |
| Licensing & Ownership | pallet_chlom_licensing | Mint/amend/transfer licenses | Licenses, TermsCID | mint, amend, sublicense | LicenseMinted |
| KPI & Performance | pallet_chlom_kpi | Thresholds, oracle reports | Thresholds, Reports | set_thresholds, report | KpiBreached |
| Royalty Engine | pallet_chlom_royalty | Graph & settlement | Splits, Routes | route, settle | RoyaltySettled |
| License Exchange (LEX) | pallet_chlom_lex | Orders, escrow, partial equity | Orders, Escrows | list, buy, partialSell | TradeSettled |
| DLA (Enforcement) | pallet_chlom_dla | Cases, sanctions | Cases, Sanctions | openCase, applySanction | SanctionApplied |
| Governance | pallet_chlom_gov + democracy/collective | Voting & hooks | Weights, Scores | setWeight, addReputation | GovWeightChanged |
| Oracles & Attestations | pallet_oracle_gateway, pallet_attestations | Signed feeds, proofs | Feeds, Proofs | attest, submitProof | Attested |
| Reputation | pallet_reputation | Operator scores | Scores | updateScore | ReputationUpdated |
| Sustainability | pallet_sustainability | Impact ledger & offsets | Impacts, Routes | recordImpact, routeOffset | ImpactRecorded |
What to read next: Doc 07 — Pallet Design Deep Dives (per module).
4 · Data Model & Schemas
- License:
- RoyaltyModel: DAG of splits (weights, currency, rounding, windows)
- KpiProfile:
- Proposal:
- DlaCase:
- ImpactRecord:
What to read next: Doc 08 — Runtime Storage & Schemas.
5 · Protocol Flows (Sequence Specs)
5.1 License Lifecycle
Apply → KYC/KYB (oracle) → Mint License NFT → Operate (events) → Comply (auto checks) → Amend/Transfer via LEX → Expire/Revoke.
5.2 Royalty Settlement
Transaction → royalty.route() compute splits → accrual buckets → settle() by era/threshold → emit receipts.
5.3 LEX Trade
list() → escrow → buy() → DLA constraint check → atomic swap; partial equity via partialSell(%).
What to read next: Doc 09 — Sequence Diagrams & State Machines.
6 · Governance & DAO Mechanics
Voting = CHM stake × reputation (optional hybrid). Quorum/threshold curves; conviction locking; councils; post‑hoc referenda for emergency fast‑tracks; schedulers for parameterized changes.
What to read next: Doc 10 — Governance Parameters & Processes.
7 · Token Model (Runtime View)
- CHM (governance): fixed supply; staking, voting, validator rewards; slashing against misbehavior.
- CHLOM (utility): fees, license bonds, operational staking; fee burns and buybacks; KPI bonus emissions when KPIs exceed targets.
What to read next: Doc 11 — Token Implementation & Fee Model.
8 · Oracles & Off‑Chain Workers
Signed feeds for KYC/KYB, sanctions, IoT occupancy, POS revenue, and sustainability receipts; OCWs batch, rate‑limit, and sign submissions. ThrivePush handles operational alerts; CrownPulse (FOMO/engagement) informs KPI context.
What to read next: Doc 12 — Oracle Gateway & OCW Patterns.
9 · Indexing & Analytics
Index KPIs, royalties, LEX trades, DLA cases, proposals, sustainability. Provide GraphQL for dashboards, Sidecar & /state RPC for raw queries. Prometheus/Otel for observability.
What to read next: Doc 13 — Indexing Blueprints; Doc 14 — Observability & Telemetry.
10 · Security, Privacy, and Compliance
Threats: reentrancy, oracle spoofing, MEV at LEX, governance capture, KPI forgery. Controls: audits, fuzzing, property tests, benchmarked weights, time‑locks, multisig treasuries, kill‑switches, circuit breakers. Privacy: ZK attestations, selective disclosure, metric‑level redaction.
What to read next: Doc 15 — Security Standards & Threat Model; Doc 16 — Privacy/ZK Patterns.
11 · Sustainability & Impact Hooks
recordImpact(kind, amount, ref) for clean water, food, kelp cultivation, plastic removal, tree planting, jobs. Treasury routes 1% (scaling to 5%) via Stripe Climate; rotating EcoDrive campaigns with public dashboards.
What to read next: Doc 17 — Sustainability Module & API.
12 · Developer Environment & Tooling
12.1 Prereqs
Rust stable + nightly; wasm32-unknown-unknown; Substrate node template; subkey; Docker; Polkadot‑JS Apps.
12.2 Build & Run (Reference Chain)
rustup target add wasm32-unknown-unknown
cargo build -p node --release
./target/release/chlom-node --dev
12.3 Testing
Unit/integration tests, try-runtime migrations, proptest, fuzzing; scenario tests for LEX trades, KPI breaches, DLA sanctions.
What to read next: Doc 18 — Local Dev & Testing Guide.
13 · Deployment Topologies
DevNet (ephemeral/faucet), TestNet (permissioned oracles; chaos tests), MainNet (governed upgrades; snapshots & backups; incident response SOPs).
What to read next: Doc 19 — Networks & Chain Specs; Doc 20 — Upgrade Playbook (Forkless Upgrades).
14 · SDKs & API Surfaces
TypeScript SDK (high‑level wrappers), Rust client (indexers/oracles), JSON‑RPC (standard + chlom_*).
Example:
await api.tx.chlomLicensing.mint(classId, termsCid, scope)
.signAndSend(account)
What to read next: Doc 21 — TS SDK Reference; Doc 22 — Custom JSON‑RPC Extensions.
15 · Royalty Graph & Accounting Details
Weighted split DAG; cycle guards; currency adapters; batched payouts; dispute windows; proof receipts (Merkle proofs) for audits.
What to read next: Doc 23 — Royalty Engine Spec.
16 · KPI Catalogue & Measurement
Vertical metric packs (suites, media, commerce) with definitions, windows (rolling 30/90), and breach policies mapped to DLA sanctions; ZK‑eligible metrics list.
What to read next: Doc 24 — KPI Library & Policies.
17 · LEX Market Microstructure
Order types (fixed, Dutch, sealed‑bid); partial equity; reserve prices; on‑chain escrow; oracle‑gated transfers; commit‑reveal anti‑MEV where appropriate.
What to read next: Doc 25 — LEX Market Design.
18 · DLA Case Management
Lifecycle: Open → Investigate → Sanction/Remediate → Resolve; evidence chains; appeal timers; DAO oversight; redaction policy for public records.
What to read next: Doc 26 — DLA Casebook & Sanction Matrix.
19 · Cross‑Chain & Bridging
XCM for assets/commands; bridge allowlist; jurisdictional constraints at ingress/egress; rate limits, time‑locks, circuit breakers.
What to read next: Doc 27 — Cross‑Chain Strategy (XCM/Bridges).
20 · Compliance Packs by Jurisdiction
Pluggable packs per state/country; mapping tables; upgrade calendars; test matrices; conflict‑of‑laws fallbacks and overrides.
What to read next: Doc 28 — Regional Compliance Packs.
21 · Operational Runbooks (Validators & Governance)
Validator SRE (monitoring, incident response, key rotation); Governance Ops (proposal templates, review SLAs, emergency playbook; change management).
What to read next: Doc 29 — Validator Runbook (SRE); Doc 30 — Governance Ops Manual.
22 · Contribution, Versioning, and SLA
Semantic versions; migration notes; state version bumps; deprecation policy; Help Center doc SLAs per release; change control and backporting.
What to read next: Doc 31 — Contributing & Release Process.
23 · Full Documentation Roadmap (30+ Items)
- Conceptual Architecture & Domain Model
- Network & Keys Handbook (SS58, Sessions, Staking)
- Licensing Protocol Spec
- Compliance Protocol Spec
- Governance Protocol Spec
- Economic Protocol Spec
- Pallet Design Deep Dives (per module)
- Runtime Storage & Schemas
- Sequence Diagrams & State Machines
- Governance Parameters & Processes
- Token Implementation & Fee Model
- Oracle Gateway & Off‑chain Workers
- Indexing Blueprints (SubQuery/Subsquid)
- Observability & Telemetry (Prometheus/Otel)
- Security Standards & Threat Model
- Privacy & ZK Patterns
- Sustainability Module & API
- Local Dev & Testing Guide
- Networks & Chain Specs
- Upgrade Playbook (Forkless Upgrades)
- TypeScript SDK Reference
- Custom JSON‑RPC Extensions
- Royalty Engine Spec
- KPI Library & Policies
- LEX Market Design
- DLA Casebook & Sanction Matrix
- Cross‑Chain Strategy (XCM/Bridges)
- Regional Compliance Packs
- Validator Runbook (SRE)
- Governance Ops Manual
- Disaster Recovery & Backups
- Performance & Benchmarking (Weights)
24 · Final Notes for Help Center Editors
- Keep this master current with each runtime and governance release.
- Every new module/upgrade must link back to this index and add a child doc entry.
- Cross‑check examples against the repository CI snapshot before publishing.
Appendix A — Example Types (Rust)
pub struct RoyaltySplit { pub to: AccountId32, pub weight_bps: u16, pub currency: AssetId; }
pub struct ImpactRecord { pub territory: Vec<u8>, pub kind: u8, pub amount: u128, pub ref_cid: Vec<u8>, pub block: u32; }
Appendix B — Example TS SDK Call
await api.tx.chlomLicensing.mint(classId, termsCid, scope)
.signAndSend(account, ({ status, events }) => { /* ... */ })
Disclaimer: Technical documentation; not legal advice. Always align deployments with applicable laws and CHLOM Governance decisions.