Zintus Route

• 

  Public architecture for Zintus Route: Slack requests pass through the agent experience, Zintus Slack adapter, security policy,private Zintus

Inspiration

Incident teams use AI for very different tasks: diagnosing ambiguous logs, writing concise stakeholder updates, handling sensitive context, and continuing safely when a preferred route is unavailable. People should not need to compare models during an incident.

What it does

Zintus Route is a Slack-native agent for fictional engineering incident triage. It selects a public route profile such as Deep, Economy, Balanced, Fast, or Private; streams a structured answer; explains the choice at a safe high level; shows estimated cost and latency; cites permitted fictional context; and exposes qualified fallback. It also previews incident briefs and requires explicit human confirmation before creating the Slack artifact.

How we built it

The submitted Slack integration is a new TypeScript service built with Slack Bolt, Agent view, Slack streaming methods, Block Kit, Zod validation, encrypted installation storage, workspace-scoped context, structured logs, retention controls, Docker, Vitest, and strict TypeScript. It connects through a narrow API boundary to Zintus.

Challenges we ran into

The central challenge was preserving a truthful public product boundary: enough route transparency for users, without publishing proprietary scores, prompts, topology, or customer data. The service also needed fast Slack acknowledgment, deterministic judging behavior, workspace isolation, and confirmation for external writes.

Accomplishments that we're proud of

The standalone agent demonstrates different routes for technical diagnosis and stakeholder communication, safe fallback, deterministic Demo Mode, response streaming with a fallback renderer, compact thread context, deletion, OAuth state handling, encrypted tokens, secret scanning, and approval-gated incident briefs.

What we learned

Slack's Agent experience is strongest when routing decisions stay compact and task-centered. Privacy is also a product interaction: clear mode labels, source boundaries, deletion, and approval make system behavior understandable without revealing internal algorithms.

What's next for Zintus Route

Future work includes tested Slack MCP access when the app is eligible, optional Real-Time Search where approved, durable distributed queues, richer incident artifacts, administration controls, and Marketplace hardening. These are not submitted features.

Built With

• agent
• api
• block
• bolt
• docker
• kit
• node.js
• postgresql
• slack
• typescript
• view
• zod