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.

3/4 SDKs configured Live integration health
production Runtime https://crusher.nexartis.com
PROD D1 default nexartis-ticket-crusher-db-prod
online HB3 service-binding

@nexartis/sentinel-sdk

Sentinel

configured

Identity, route protection, bearer-token handoff, and operator attribution.

Used for SvelteKit handle hookAuth route handlersHB3 bearer auth boundary
Powers Protected admin operationsOperator-scoped workflow launchesNo anonymous mutations
Routes and touchpoints
/auth/api/auth/[...path]/admin

@nexartis/abi-chat-sdk-core + @nexartis/abi-chat-sdk-svelte

ABI Chat

configured

Interactive chat, SSE streaming, ABI annotations, and workflow analysis panels.

Used for createChatEndpointAnthropicProviderpostSSEStream client
Powers Context packetsProgress/table/summary/approval annotationsNatural workflow analysis
Routes and touchpoints
/api/chat/api/abi/chat/preview/#command-center

pegasus-hb3-coordinator service binding

Pegasus HB3

configured

Durable Object + Cloudflare Container runtime for real orchestrator and subagent DAG execution.

Used for HB3_SERVICE binding/workflow submission/api/runtime/hb3/health
Powers Containerized Claude Code executionDAG progressWebSocket/event lifecycle
Routes and touchpoints
/api/runtime/hb3/health/api/runtime/hb3/workflows

ticket-crusher-agents

KYM

approval-gated

Agent registry metadata, optimization signals, model accountability, and publication readiness.

Used for kymRegistryId on ABI endpointAgent registry slugsLocal agent_library lifecycle table
Powers Publishable agent cardsQuality signalsApproval-gated external registration
Routes and touchpoints
/sdk/admin

KYM 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.

Ticket Crusher Orchestrator orchestrator · ticket-crusher-orchestrator plan completeness · handoff clarity · verification coverage
Linear Intake Scout subagent · linear-intake-scout dedupe precision · label coverage · source-link retention
Roadmap Normalizer subagent · roadmap-normalizer row stability · status accuracy · evidence usefulness
Parallel Sprint Architect subagent · parallel-sprint-architect parallel efficiency · conflict rate · handoff continuity
Final Verification Agent verifier · orchestrator-final-verifier false-positive rate · missed-risk rate · approval clarity

Runtime contract

HB3 execution, D1 evidence, KYM registry boundary

HB3 URLhttps://hb3.nexartis.com/health Status200 D1 bindingDB_PROD Tables16 KYM APIhttps://knowyourmodel.ai