# OCP 0.4 validation report

**Date:** 13 August 2026  
**Scope:** Local synthetic reference materials only  
**System under test:** None

| Check | Result |
|---|---:|
| JSON Schemas compiled/catalog verified | 37 / 37 |
| Positive examples | 32 / 32 |
| Negative examples rejected at expected rule | 45 / 45 |
| Inherited semantic vectors | 243 / 243 |
| Registry/OpenAPI/evidence checks | 29 / 29 |
| Portable AI History cases | 25 / 25 |
| Portable positive / negative / hostile / round trip | 9 / 6 / 6 / 4 |
| Assertions/result rows | 134 / 134 |
| Implementation passes / failures | 0 / 0 |

## Known failures

No local schema, example, inherited semantic, registry, or Portable AI History fixture failure remains in the checked-in reports.

## Untested requirements

Independent provider-export fidelity; two independent adapters/providers; independent client; cross-provider transfer; deployed parser sandbox and resource limits; live authorization/client-instance/recipient-key binding; actual managed storage and source-disappearance recovery; cross-language raw JSON/JCS handling; real cryptographic protection; security/privacy/legal/accessibility review; recipient behavior; governance/publication; and live human acceptance.

The files validation-report.json, semantic-validation-report.json, and portable-history-validation-report.json are the machine evidence. Passing them does not create implementation conformance because system_under_test is null.
