Product infrastructure
The runtime layer behind trusted planning and launch
Ticket Crusher stays calm on purpose. Underneath, Nexartis SDKs provide operator identity, streaming analysis, HB3 orchestration handoff, lifecycle storage, and KYM-ready governance metadata.
@nexartis/sentinel-sdk
Sentinel
Identity, route protection, bearer-token handoff, and operator attribution.
Routes and touchpoints
/auth/api/auth/[...path]/admin@nexartis/abi-chat-sdk-core + @nexartis/abi-chat-sdk-svelte
ABI Chat
Interactive chat, SSE streaming, ABI annotations, and workflow analysis panels.
Routes and touchpoints
/api/chat/api/abi/chat/preview/#command-centerpegasus-hb3-coordinator service binding
Pegasus HB3
Durable Object + Cloudflare Container runtime for real orchestrator and subagent DAG execution.
Routes and touchpoints
/api/runtime/hb3/health/api/runtime/hb3/workflowsticket-crusher-agents
KYM
Agent registry metadata, optimization signals, model accountability, and publication readiness.
Routes and touchpoints
/sdk/adminKYM governance lifecycle
Registry-ready records before public publication
Automation lanes carry stable registry slugs locally today. External KYM writes remain explicit operator actions, while ABI Chat references the registry contract as ticket-crusher-agents.
Runtime contract
HB3 execution, D1 evidence, KYM registry boundary
https://hb3.nexartis.com/health Status200 D1 bindingDB_PROD Tables16 KYM APIhttps://knowyourmodel.ai