| run_id | RUN-OQ007-002 |
|---|---|
| fixture_id | FX-IDENTITY-SCHEMA-DIGEST-CONFIG-001 |
| packet_id | OQ-007 |
| observation_status | pass |
Fixture working directory:
docs/research/phase-0/fixtures/FX-IDENTITY-SCHEMA-DIGEST-CONFIG-001
The exact fixture command was executed twice on 2026-08-22:
PYTHONDONTWRITEBYTECODE=1 python3 runner.py
- both executions returned exit
0, 30/30 assertions andall_assertions_pass=true cmpof the two JSON stdout values returned exit0- paired stdout SHA-256:
sha256:4adfd380c2f0094803b2b3645a330b5645472418a7ea6ea8953d32398626f051 - the result declared
network=disabledandexternal_writes=false
- reordered contract and plan object keys retained their base digest;
- contract semantic goal change and plan semantic step addition produced different digests;
- the raw Markdown editorial variant differed under raw-byte hashing;
- the fixture's invalidation observation was
contract_and_downstream_plan_stalefor a semantic contract change anddigest_unchanged_under_semantic_projectionfor an editorial change.
The fixture also passed the shared identity, frontmatter/SQLite projection, stale-write and portable/runtime boundary assertions. Those observations remain fixture-local and are not production schema or serializer evidence.
- current result manifest: result.json
PYTHONDONTWRITEBYTECODE=1 python3 -m py_compile runner.py→ exit0python3 -m json.tool input/fixture.json >/dev/null→ exit0PYTHONDONTWRITEBYTECODE=1 python3 runner.pytwice → exit0for both runscmpof paired stdout → exit0python3 -m json.toolon paired stdout → exit0jqassertion summary on a current run → exit0,true 30 30 disabled falsesha256sumon paired stdout → exit0,4adfd380c2f0094803b2b3645a330b5645472418a7ea6ea8953d32398626f051
The subsequent delegated C-01 decision is recorded in USER-DECISION-OQ007-001
and ADR-0017. This evidence does
not select a production serializer, schema or implementation CLEAR.