Observability

Observability captures logs, traces and errors from every request and Action. When a check fails, it opens an Incident for the agents on duty.

ContractCopy Anchor Link

• Every Action carries its parent, so one request traces end to end through Workflows, sandboxes, browser sessions and model calls.
• Errors group by fingerprint. Each group opens an Issue tied to the Version that introduced it.
• Logs are kept forever. Telemetry may be sampled; errors never are.
• Metrics derive from declared Events, never from typed-in numbers.
• Monitors probe what runs outside on a schedule. A failed probe or a missed check-in opens an Incident.
• Outside services send traces and logs over OTLP and join the same trace.
• No person carries a pager. Engineering agents triage, fix and roll back; a rollback redeploys the last good Version.

VerbsCopy Anchor Link

InterfacesCopy Anchor Link

• API
• SDK
• CLI
• MCP

ExampleCopy Anchor Link

# loomandlark.shop sells handwoven throws. Checkout errors rose after version v42 shipped.
npx startup-builder logs tail --level error --route /checkout
npx startup-builder do Issue.triage --json '{"issue":"issue_318"}'
npx startup-builder do Version.deploy --json '{"version":"v41"}'