Evidence Modes/Instrumentation
Evidence Mode: Service-Level Proof

Service-level proof from your own code.

Emit structured evidence events from your services via the Lamdis SDK. Prove that actions happened at the code level with confirmation levels and boundary definitions.

What Instrumentation does

Structured events
Emit typed evidence events directly from your application code via the Lamdis SDK.
Boundary definitions
Mark where your visibility ends. Know exactly what you can and cannot prove.
Confirmation levels
Every event is scored A through E based on evidence strength — from intent to end-to-end proof.
Correlation engine
Automatically link events across services using workflow instance IDs.
Policy checks
Same policy checks run against SDK events as against runs and assurance evidence.
Coverage dashboard
See which workflows have instrumentation gaps and get actionable suggestions.

How it works

1
Install the SDK
Add @lamdis/sdk to your service. Initialize with your API key and workflow definitions.
2
Emit evidence events
Call lamdis.emit() at key points in your code. Include structured data and confirmation metadata.
3
Define boundaries
Mark where your service's visibility ends — external APIs, third-party services, user devices.
4
Review coverage
Dashboard shows confirmation levels per workflow. Get suggestions to upgrade evidence strength.

Key features

TypeScript SDK
Fully typed SDK with auto-completion for event schemas and workflow definitions.
Distributed tracing
Workflow instance IDs correlate events across microservices automatically.
Boundary marking
Explicitly declare where visibility ends — no false confidence from missing data.
Level upgrades
Get suggestions to upgrade from Level A to Level D by adding confirmations.
Schema validation
Event schemas are validated on ingest — catch instrumentation errors early.
Event replay
Re-evaluate historical events against updated policies without re-emitting.

Ready to get started?

See pricing or talk to our team about your use case.