Platform Integration Evaluation 001
A completed, reproducible test of the constructed path from a current-state Review Engine response to a conforming Manifest, customer-controlled evidence entry, offline validation, integrity check, and human-review route. The Review Engine remains unvalidated and in operational validation.
Question tested
Can a technically competent evaluator use the documented repository components to convert a constructed current-state response into a conforming Decision Reconstruction Manifest, retain it in a synthetic platform evidence entry, validate it offline, detect alteration, and preserve the human-review boundary without undocumented founder instruction?
Workflow tested
Constructed record
A synthetic dated record with an identified source and secondary-review proposal entered the test harness. No personal, customer, privileged, or production data was used.
Current-state shape
A deterministic response carried a request identifier, engine and API versions, all five condition keys, an engine routing value, and derived notes.
Manifest generation
The controlled builder recorded distinct JRS, Codebook, engine, API, model, Manifest, vocabulary, routing, input-hash, content-class, human-review, and integrity fields.
Evidence entry
The synthetic platform entry retained the request identifier, human-review route, and Manifest without embedding the raw record.
Offline validation
The offline validator tested schema conformance, semantic controls, content classification, truncation coherence, and Manifest hash consistency.
Refusal and tampering
Changing the routing value produced a hash mismatch. Attempting to relabel Review Engine keys as Codebook conditions without an established mapping was refused.
Control results
| Control | Result | Evidence |
|---|---|---|
| Schema conformance | Pass | Manifest v1.0 accepted. |
| Five-condition preservation | Pass | All five current engine condition keys stored. |
| Request correlation | Pass | Platform entry retained the API request identifier. |
| Input correspondence | Pass | sha256:7a52ec09f2bc6c524d26f3563a98d7ae78c8b4608d3377edc45715e9d6c51731 |
| Version pinning | Pass | JRS 1.0, Codebook 1.0, engine 0.1.0-validation. |
| Vocabulary declaration | Pass | No silent Codebook or routing translation. |
| Human-review preservation | Pass | Human secondary review remained required. |
| Content classification | Pass | Derived record content declared. |
| Raw-record exclusion | Pass | Evidence entry contained the input hash and derived notes, not raw record text. |
| Integrity self-check | Pass | Self-consistent, unsigned, and not represented as authenticated. |
| Tamper detection | Pass | Changed routing value produced a Manifest hash mismatch. |
| Unsupported mapping refusal | Pass | Generator refused unestablished Codebook relabeling. |
Integration effort observed
The evaluator used the published schema, controlled Manifest builder, offline validator, current response vocabulary, and one executable harness. No change to the Review Engine, builder, schema, or validator was required. In this 22 September 2026 evaluation, one explicit adapter step was required because the API did not then emit the Manifest.
What the evaluation established
Portable artifact path
A documented current-state response can be represented as a conforming Manifest when required versions and vocabularies are supplied explicitly.
Traceable storage
The result can be stored with request correlation and a human-review route without embedding the raw record in the evidence entry.
Detectable alteration
The offline validator detects a changed routing value against the recorded integrity hash.
Documented operability
The bounded test can be executed from repository documentation and code without oral founder instruction.
Limitations discovered
Delivery gap
At the time of this evaluation, automatic API-to-Manifest delivery was not deployed. This historical finding does not describe later releases.
No live-service evidence
The evaluation did not measure authentication service, inference, latency, availability, rate limits, model variance, or production scale.
Vocabulary boundary
Review Engine and Codebook vocabularies cannot be treated as interchangeable until the correspondence is formally established.
Integrity is not authenticity
An unsigned hash can show internal consistency against a retained reference. It does not prove who created the artifact.
Derived-content sensitivity
Condition notes may paraphrase the evaluated record. Removing raw text does not make every Manifest non-sensitive.
Rights remain separate
Technical portability does not establish ownership, exclusivity, commercial availability, or transferability of every potential asset.
Next evidentiary step
The next material proof is the same bounded procedure completed by a qualified external platform under written terms, using approved constructed or de-identified cases, with its own record store, security review, implementation log, and independent closeout decision.