Skip to content
REFERENCE
← All reference documents
v3.2Specification published

MIXED-RIGHTS FRAMEWORK

Addresses the structural limitation that both Cloudflare Content-Signals and the current cip.md format share: both treat content as having a single rights position per URL, with no mechanism to express different positions for different content layers.

Document: CIP Mixed-Rights Architecture — Content-Rights-Map, Mixed-Rights-Block, and Content-Signals MappingVersion: v3.2Status: Specification published
§1

The problem this specification addresses

A publisher’s page containing a celebrity interview has at least four legally distinct rights layers: journalist’s expression rights, interview subject’s NILP rights, performer’s neighbouring rights in recorded content, and publisher’s database rights. A single domain-level cip.md cannot express different positions for these layers.

§2

CIP-Content-Rights-Map

Per-URL rights declarations within a domain. Maps URL path patterns to named rights profiles defined in the same cip.md file. Patterns evaluated using longest-match-wins resolution. Follows robots.txt conventions extended with wildcard and end-of-string anchor.

§3

CIP-Mixed-Rights-Block

Per-content-element granularity within a page. JSON-LD block embedded in page markup, with per-layer rights declarations. Each layer carries its own rights bundle, consent positions, and operator-specified identifiers. Supports the celebrity-interview worked example with four distinct layers.

§4

Content-Signals mapping

Maps the framework’s granular declarations to the broader Content-Signals format that AI crawlers currently respect. Derivation rules produce conservative Content-Signal values from CIP’s more granular positions.

Citation

CIP Mixed-Rights Architecture v3.2, https://creativeip.org/mixed-rights