The ledger: from a run to origin, and back to a reader

The ledger: from a run to origin, and back to a reader A workflow diagram generated by Archify. 01 / A run records 02 / Push access 03 / origin 04 / Readers Record Carry and publish Read back Run record · status, cost, subject · A run records › Record Run record status, cost, subject lockstep-history · local orphan branch · A run records › Record lockstep-history local orphan branch Run artifact · read-only job · Push access › Record Run artifact read-only job history --push · never automatic · Push access › Carry and publish history --push never automatic --from-bundle --push · write token, no key · Push access › Carry and publish --from-bundle --push write token, no key reconcile sweep · cancelled runs' leftovers · Push access › Carry and publish reconcile sweep cancelled runs' leftovers origin · tamper-evident · origin › Carry and publish origin tamper-evident A colleague's clone · reads the remote ref · origin › Read back A colleague's clone reads the remote ref improve census · a recurring finding · Readers › Carry and publish improve census a recurring finding report, --explain · --scm, --around · Readers › Read back report, --explain --scm, --around append every record findings in CI, bundled untrusted artifact record by record outstanding --pull to merge Legend User UI Agent logic Policy Context / trace External system

Publishing is an act

  • • A local run appends and stops; reaching a remote needs credentials
  • • CI carries the record out as an artifact and pushes from the job that can

Honest reading

  • • report --scm counts what is still in artifacts; without it, a dash
  • • A rewritten history is flagged; an acknowledged rewrite is named