Observe
Filesystem, terminal, desktop, browser, system, and export adapters emit typed material-provenance events.
Local-first · append-only · replayable
Sinex captures activity as typed, timestamped events; carries it through a durable stream; preserves it in an append-only PostgreSQL log; and rebuilds queryable state through explicit, replay-aware derivations.
Runtime architecture
The system keeps ingestion, transport, canonical persistence, and derived state distinct so that capture can evolve without turning historical data into an opaque application database.
Filesystem, terminal, desktop, browser, system, and export adapters emit typed material-provenance events.
NATS subjects provide an explicit transport boundary, backpressure policy, and replayable delivery.
A single canonical write path validates and appends events, provenance, blobs, and operational receipts.
Checkpointed automata rebuild state; sinexctl and the hardened API expose control and read surfaces.
System properties
Canonical records are never silently rewritten. Corrections, curation, and interpretation retain their own authority and provenance.
Automata carry source, temporal, declaration, epoch, and lane metadata so rebuilt results remain attributable.
Staged materials, input adapters, parsers, and source contracts separate what was observed from how it was normalized.
Services, PostgreSQL, NATS, TLS, authorization, backups, and systemd hardening are composed declaratively.
Documentation