CounterpediaExplore knowledge. Follow the sources.

/research/lineage/realwork9-heppner-change

REALWORK9 · Changed-input rerun

The same deterministic question over two real committed ARCS reports: input changed, exact result changed, high-level conclusion stayed the same.

What actually changed

Input bytes changed

yes

Result bytes changed

yes

Conclusion vector changed

no

Initial report

Canonical input

sha256:13b44d2a953c753cf9daee4f2dcede31814d628840dabdb2c8f7a9664041e0fe

Deterministic result

sha256:d2228156ef548afe2e5ee9e7d8b53f69f826ee1b48216fa1b7f8ed4ddfd5c352

Git blob

499c62a3012d23ca062a74b3983916a4ce97562c

Revised report

Canonical input

sha256:779250bb3073ddf31f3a0294089f8679fdbf3dadaf8e26657e8086df9d63a342

Deterministic result

sha256:ae1b3552e0f061fd26319a150eb163cfcbd926c829a8d7ad232c633ecf1bb3fe

Git blob

eaf73392c61c1d718304cf22e2133c7b7533ee83

Stable conclusion, changed dependencies

Both reports carry the same conclusion vector digest:

sha256:0cb1e301a45f625b8bf2dfb6c5e80aef882040aa59d37fc470e5902f3ca20d07

But the deterministic result changed because these exact report-projected bindings changed:

  • verified_artifacts.claim_graph_substrate_hash
  • verified_artifacts.context_packet_hash
  • verified_artifacts.context_packet_id
  • verified_artifacts.packet_inspection_hash
  • verified_artifacts.packet_walk_hash
  • verified_artifacts.packet_walk_id
  • verified_artifacts.rendered_packet_hash
  • verified_artifacts.source_capture_hash
  • verified_artifacts.sovereignty_receipt_hash

Countergraph lineage

`RERUN_OF = 1` · `CHANGED_RESULT_FROM = 1` · `SAME_RESULT_AS = 0`

sha256:b1b88f7c08c4ec2bbf4a6f0e29597d58a096d3908d0d4285fc11715562a5fb6e

A changed result means only that the bounded deterministic answer bytes differ. It does not say the prior report was wrong, the world changed in the same way, or standing moved.