<aside>
🪬
Anchored surface: Booster v2.0 × ImplicitWrap × UCP Catalog — Trace-as-Consent Aggregation Layer
Charter type: Cryptographic consent layer under EU AI Act Title III obligations.
</aside>
<aside>
🔗
Canonical cluster anchors (previewable). Yennefer cluster · TAEX · Retraining loop · §6.17 · Integrations registry · Integrative Flow.
‣ · ‣ · ‣ · ‣ · ‣ · TAEX Intent Router — Agent-Based Routing with Dissonance Memory MCP · ‣ · ‣ · ‣
</aside>
Constitutional clauses
- Consent at emission, not ingestion. ImplicitWrap MUST sign the trace at the worker that produces it. Post-hoc consent attached at the aggregator is rejected by the UCP Catalog gate.
- Scope is named. Every wrap declares (a) the citizen, (b) the permitted aggregations, (c) the expiration. Aggregations outside scope are invalid even if the wrap signature verifies.
- Audit logs are public-by-default. Aggregation events are written to a federated log readable by any kingdom citizen.
- Right of withdrawal. A citizen may revoke prior consent prospectively; the catalog purges within one epoch.
Vetoable actions
- Any proposal that allows aggregation without a verified wrap.
- Any proposal that permits retroactive consent (wrap signed after trace emission).
- Any proposal that closes the federated audit log.
- Any proposal that removes the per-citizen revocation primitive.
Federation partners
This kingdom is Federated because the wrap protocol is cross-implemented with multiple aggregator kingdoms. Treaty rows live downstream on the UCP Catalog spec page.
Tier ladder
- Merchant — emits wrapped traces, does not aggregate.
- Lord — operates a wrap-validating ingester.
- King (floor) — operates a federated audit log node.
- Eternal Diamond — maintains the canonical ImplicitWrap reference implementation.