Infrastructure & Audit
Run sealing, event pipeline, evidence chain
Every claim on this site is backed by a sealed run-ID, an event log, and an authority chain. This page exposes the live infrastructure underneath: which services are up, which runs are sealed, where events go.
Live event pipeline
β polling every 5sβοΈ
Submission
learner attempt
A learner answers β the only write that starts the chain.
β
π€
Transactional Outbox
0 events
Event written in the SAME DB transaction as the state change β no dual-write race. The auditable trail.
β
β‘
Kafka (Redpanda)
event stream
Outbox relay publishes to topics (.mastery, .submissions, cognition_updatedβ¦). Consumers subscribe.
β
π
Projections
0 read-models
Consumers fold events into read models (learner_projections) β CQRS read side, rebuildable from the log.
β
π
Trajectory
0 rows
Governance trajectory (experiment_trajectories) β every interaction with its full JT attribution, replayable.
Published
0
Failed (DLQ)
0
Delivery rate
β
π Determinism & provenance β "pin me to the rows behind this number"
Because the system is event-sourced, a run can be sealed: its exact row count and a content hash are frozen. Anyone can re-derive the hash from the live rows and confirm a cited figure reproduces. Post-seal writes are rejected (the run is immutable). This is the difference between "trust me" and "here's the sealed artifact."
No sealed runs yet.
β Only 0 run is sealed (the thesis anchor). The validated re-run campaign will seal each new experiment so every cited number has an anchor β that's the provenance discipline the whole frontend is being built to make visible.
Why event-sourcing (not REST CRUD)?
Auditable
Every change is an immutable event. Nothing is overwritten β the full history is the source of truth.
Reproducible
Read models are a fold over the log. Rebuild them, replay them, get the same answer (determinism).
Provable
Seal a run β content hash. "Pin me to the rows" is answerable, not a hand-wave.
Decoupled
Outbox + Kafka means the write path never blocks on the read side; consumers scale independently.