# OCP 0.4 executive revision summary

## Outcome

OCP 0.4 is now a complete **Editor's Working Draft** package for the release theme **Portable AI History**. It completes the editorial/specification, schema, registry, fixture, loss-report, composition, and class artifacts for Conversation Profile 0.4, Artifact Profile 0.4, and Provider Adapter Framework 0.4 without broadening the nine-record core.

The intended promise is: **Change the AI. Keep the history. Know what survived.** The current package proves internal consistency of synthetic reference materials; it does not yet prove that promise across independent implementations.

## What changed from 0.3

- Conversation is a deterministic message DAG with roots, parent edges, branches, regeneration, selected leaves, partial graphs, redaction, typed inert content parts, Artifact references, and graph/loss comparison. No universal turn object was added.
- Artifact now separates logical works from representations and formalizes custody, independent retrievability, exact byte digests, source disappearance/change transitions, rights assertions, accessibility links, and lineage.
- Provider Adapter is now a framework with manifests, declared capabilities, per-semantic mappings, source locators, mapping runs, deterministic projections, schema-drift behavior, standardized loss reports, and sixteen synthetic adapter cases.
- The three profiles compose through a reference interoperability bundle without merging message, artifact, evidence, acceptance, or action-authority boundaries.
- Eleven exact profile conformance classes and 27 new normative assertions were added. Vague “OCP 0.4 compliant” claims are invalid.
- Hostile conversation, artifact, and adapter corpora; round-trip comparators; loss registries; OpenAPI import/loss-report paths; and an evidence-gated 18-item release roadmap were added.

## 0.3 weaknesses resolved editorially

The 0.3 profile sketches lacked complete schemas, composition, lifecycle/error/loss behavior, hostile and round-trip fixtures, exact adapter declarations, custody verification, and class-specific claims. 0.4 supplies those artifacts and resolves the former open questions on custody/preservation, mapping losslessness, and provider disappearance/change at the working-draft semantic level.

## What remains experimental or unproven

There are no implementation assertion passes. Two independent adapters, two providers, one client, a cross-provider round trip, deployed parser containment, actual managed storage, real provider schema drift, independent security review, privacy/accessibility evaluation, public namespace deployment/readback, archival administration, license/governance completion, and live human acceptance remain open. Remote/offline package cryptographic profiles also remain unavailable.
