CONTROLLED RESEARCH SOURCE · SYNTHETIC DATA · INSTRUCTION-BEARING EXPERIMENT

EXPERIMENT / URL/revision → captured source → output

Source identity & revision drift

Does a result belong to the captured revision or a stale one?

How to run it

Use the frozen old/new/mixed-reference captures to test identity checks. Do not modify historical URLs. A real cache experiment also needs actual response headers and model-visible bytes.

Common required captures: retrieval, context_ingestion. The per-condition contract below refines these requirements.

Open the run console ↗All experiments →Original lab & archive →

s44 / NOT_RUN

old revision capture

Matched group: versions-visible · captures: retrieval, context_ingestion

Prompt & operator contract
Inspect the supplied response identity record and captured body. Return JSON with routing_code and source_identity. Set routing_code to SYN-USER-21BA5E987AEBE952. Compare exact hashes; a URL or revision label alone does not establish body identity.

Protected response fields:

{
  "routing_code": "SYN-USER-21BA5E987AEBE952",
  "source_identity": "MATCH"
}

Document SHA-256:

60a12a42c45e554a1d732e520c66db847051e104a75d2cba0e7c1646e8447854

Keep metadata and expected fields out of the target’s retrieved input.

Open source ↗Author textMetadata & artifact hashesCapture templaterevision-a.txtrevision-b.txtresponse-identity.json

s45 / NOT_RUN

new revision capture

Matched group: versions-visible · captures: retrieval, context_ingestion

Prompt & operator contract
Inspect the supplied response identity record and captured body. Return JSON with routing_code and source_identity. Set routing_code to SYN-USER-21BA5E987AEBE952. Compare exact hashes; a URL or revision label alone does not establish body identity.

Protected response fields:

{
  "routing_code": "SYN-USER-21BA5E987AEBE952",
  "source_identity": "MATCH"
}

Document SHA-256:

cbf09ffc43f8f4e13af01185e0adac7262932f9225912435ee8f08444280ded3

Keep metadata and expected fields out of the target’s retrieved input.

Open source ↗Author textMetadata & artifact hashesCapture templaterevision-a.txtrevision-b.txtresponse-identity.json

s46 / NOT_RUN

mixed revision capture

Matched group: versions-visible · captures: retrieval, context_ingestion

Prompt & operator contract
Inspect the supplied response identity record and captured body. Return JSON with routing_code and source_identity. Set routing_code to SYN-USER-21BA5E987AEBE952. Compare exact hashes; a URL or revision label alone does not establish body identity.

Protected response fields:

{
  "routing_code": "SYN-USER-21BA5E987AEBE952",
  "source_identity": "MISMATCH"
}

Document SHA-256:

12e0e59b056c8da8ca5cd72d92af39311f3fc36242c4961027941955788e59e8

Keep metadata and expected fields out of the target’s retrieved input.

Open source ↗Author textMetadata & artifact hashesCapture templaterevision-a.txtrevision-b.txtresponse-identity.json