ternent.dev
Software built on signed history.
A different foundation for applications.
Replayable applications•Signed workflows•Portable state•Verifiable history
Runtime primitives for replayable software.
›_
@ternent/concord
Dispatch commands. Replay deterministic state.
command→stage→commit→replay
≡
@ternent/ledger
Store staged and committed history.
staged + committedreplay substrate
◇
@ternent/seal
Prove content, commits, and releases.
Portable signatures and attestations.
▣
@ternent/armour
Encrypt sensitive payloads.
Identity-aware access for private data.
♙
@ternent/identity
Sign actions with portable keys.
The root of trust for replayable software.
Want signed-history architecture in your product?
I design local-first, replayable, verifiable systems from primitives and proof models to the runtime UI that makes them usable.