Implementation best practices

Start with one narrow purpose

Choose a single product job, a small selector vocabulary, one retention mode, and a bounded recipient set. Make purpose and processing recipients legible before expanding into broad history transfer.

Preserve the layers

• Store source records independently of accepted context.
• Keep adapter mappings and loss reports with their source export.
• Retain review decisions instead of overwriting the history that led to current state.
• Keep artifacts and their representations distinct.

Design the decision for humans

Show who will receive plaintext, the declared purpose, categories selected, retention, model-training status, offline use, proposal rights, expiry, and meaningful omissions. Avoid a single opaque consent checkbox.

Use canonical identifiers

Resolve schemas, profiles, and registries from https://opencontinuity.org. Do not fork identifiers onto an implementation domain. If caching is required, preserve the canonical URI and verify the catalog digest.