log event tracking
- @qmilab/lodestar-shipReleased16h agoVersion0.5.0
Ship a session's raw event log to a remote collector as the versioned lodestar.session_ship@1 NDJSON wire format, with the locked sensitivity ceiling applied client-side before egress. Part of Lodestar, the trust layer for AI agents.
- @moxxy/coreReleased11m agoVersion0.25.0
The moxxy runtime as a programmatic library: the agentic Session + runTurn loop, the event log, the plugin host, every block registry (providers, tools, modes, compactors, cache strategies, channels, …), session persistence, and the permission engine. Pai
- @qmilab/lodestar-event-logReleased16h agoVersion0.5.0
Append-only NDJSON event log writer and reader for the Lodestar epistemic chain. Part of Lodestar, the trust layer for AI agents.
- @qmilab/lodestar-traceReleased16h agoVersion0.5.0
The read side — project the Lodestar event log into the epistemic chain and render a 'why did the agent do this?' report. Part of Lodestar, the trust layer for AI agents.
- @qmilab/lodestar-viewerReleased16h agoVersion0.5.0
The read-side Governing UI — a local, read-only web viewer over the Lodestar event log. Renders the live epistemic chain and trust report in the browser. Part of Lodestar, the trust layer for AI agents.
- @qmilab/lodestar-otel-exporterReleased16h agoVersion0.5.0
Project the Lodestar event log into OpenTelemetry GenAI spans and export them over OTLP/HTTP — pair the epistemic chain with Langfuse, Phoenix, Jaeger, or Tempo. Part of Lodestar, the trust layer for AI agents.
- @observer-os/coreReleasedyesterdayVersion1.1.0
Observer OS core engine — Event Log, Projection Engine, Session Engine
- @qmilab/asterism-coreReleasedyesterdayVersion0.4.0
The engine behind Asterism: agent identities, scoped memory, secrets, trust levels, and the event log. You probably want @qmilab/asterism.
- @tanstack/workflow-coreReleased1 month agoVersion0.0.3
Type-safe durable execution engine. Closure-based workflows with replay, pause/resume on approvals and signals, typed middleware, and a pluggable event log.
- @kernloop/kernelReleasedyesterdayVersion0.1.3
Kernloop Layer 0 — the kernel (spec §3). P0 scope: the AuditChain only — an append-only, hash-chained, SIEM-compatible JSONL event log with tamper-evident verification (spec §3.1, §3.3, §10 item 1). Registry, router, ladder, bus, and adapters arrive in P1
- @kernloop/parsimonyReleasedyesterdayVersion0.1.3
Kernloop parsimony subsystem (ponytail-derived) — the restraint ladder, the multi-catalog Control Floor, and the parsimony Decision Receipt (a typed event on the existing hash-chained audit log, NIST 800-53r5/OSCAL-mapped). Policy + pure evaluators consum