execution_ref for every write and the behaviour layer emits a
behaviour_ref for every decision, but something has to run the chain and keep those references.
algovoi-keystone-runtime is that piece: it assembles stages, connectors and behaviours into one
pipeline, gates each write through the behaviour layer, and journals everything it emits. Every entry
recomputes offline from its own fields, and the journal itself is a hash chain over those references,
so nothing can be inserted, removed or reordered without detection. Apache-2.0.
This is the open journal. The commercial audit-chain is the same shape
with durable, post-quantum signed, append-only storage. You develop against the open journal and
upgrade the storage without changing your code.
Install
keystone doctor verification are documented once on the
Keystone install hub.
Run a chain, keep the record
bind returns a client that gates each write through the behaviours and records both the
behaviour_ref (every firing) and the execution_ref (every committed write). A denied write never
reaches the data plane, and the block is recorded. Reads pass through and journal nothing.
record_stage journals the upstream stages of the chain.
Query, verify, replay
verify() proves two things at once: each stored reference recomputes from its own fields, and the
journal is a hash chain over those references. Mutate a record, or remove or reorder a row, and
verify() fails. export() dumps every record for external offline verification by any third party.