The compared, locally evaluated representation identities are byte-identical under the same comparison method.
PRESERVE · DERIVE · COMPARE · VERIFY
Compare representations without flattening their differences.
Select governed cases, evidence planes, and reviewed transformations. The workbench calls existing focused engines, identifies each bounded result, and refuses comparisons that would conceal a method or domain mismatch.
Quick answer
What does the Cross-Representation Differential Workbench compare?
It preserves two to four governed fixtures, invokes only their existing allowlisted laboratory engines, identifies selected local representations by SHA-256, compares them only when domain and method permit, and records signal survival plus exact unresolved verification. It does not create a universal anomaly score, verdict, trust decision, or production assurance claim.
- Governed cases
- 14 checksum-bound cases spanning Unicode, web, documents, media, messages, agents, browsers, supply chains, and defense planning.
- Evidence planes
- 12 independent planes from source bytes through operational evidence.
- Transformations
- 7 reviewed source, analysis, projection, inert, reconstructed, variation, and safe-export states.
Request-local deterministic workflow
Choose cases, planes, and reviewed transformations.
The server accepts only allowlisted identifiers. Governed fixtures are verified against their manifest before any focused engine is called.
Five exact comparison states
Equality is reported only under one local method.
When domains or methods differ, the workbench preserves that difference instead of forcing a binary result.
Same under the selected representation means the domain, local method, and resulting identity agree. “Different” records a local identity mismatch under that same contract; every other relationship remains conditional, not comparable, or not evaluated locally.
The compared, locally evaluated representation identities differ under the same comparison method.
The records address the same evidence plane, but the engine, method, implementation, or evidence status differs and must remain visible.
The records belong to materially different representation domains, so equality or inequality would be misleading.
At least one selected case or transformation does not produce this representation in the local bounded workflow.
Four reviewed survival states
Transformation survival is not a robustness score.
These labels describe only the reviewed fixture and transformation pair. They do not establish adversarial resilience or production safety.
Survived
The reviewed signal remains represented after the selected transformation.
Changed
The reviewed signal remains relevant but its representation, ordering, structure, or identity changed.
Removed
The reviewed signal is explicitly absent from the selected transformed copy or alternate run.
Not evaluated
The local workflow does not establish signal survival for this case and transformation.
Deterministic result record
Your differential record will appear here.
Select the bounded inputs above. No fixture is processed on initial load.
No differential generated.
Select two to four cases, at least one plane, and at least one transformation.
Source and method identities
Every derived record points back to a governed fixture and focused engine.
Component previews are bounded. Complete arbitrary source content is not duplicated into the differential export.
No case identities yet.
Generate a record to see fixture, laboratory, transform, method, and representation hashes.
Pairwise evidence matrix
Compare cases only where the representation contract permits it.
Every row records transform, plane, domains, methods, identities, and one exact comparison state.
No comparisons yet.
Generate a differential to create the pairwise matrix.
Reviewed fixture transformations
Signal-survival matrix
Survival records describe the selected fixture and reviewed transformation only.
No survival record yet.
Generate a differential to review Survived, Changed, Removed, and Not evaluated states.
Do not fill gaps with inference
Exact external verification requirements
Each unresolved requirement is inherited from the reviewed evidence boundary for its selected case.
No verification routes yet.
Generate a record to identify the exact browser, parser, model, trust, registry, DNS, or organizational work still required.
The workbench refuses to turn representation differences into a verdict.
- Governed sources remain preserved and focused laboratories remain the only analysis owners.
- Same and Different require a shared local domain and method.
- Unsupported conclusions remain external verification requirements.
- The workflow stores no visitor record after the request.