Skip to content

v2.52.0 — console Wave A: analytics + structured dispositions + escalation

Choose a tag to compare

View all tags
@avelikiy avelikiy released this 07 Jun 19:01
v2.52.0
This tag was signed with the committer’s verified signature.
avelikiy Alex
SSH Key Fingerprint: nD9xQzAb/3YFTUEHwDpi26wMHeq89yGJsV5XW/FadYQ
Verified
Learn about vigilant mode.
5996277
This commit was signed with the committer’s verified signature.
avelikiy Alex
SSH Key Fingerprint: nD9xQzAb/3YFTUEHwDpi26wMHeq89yGJsV5XW/FadYQ
Verified
Learn about vigilant mode.

A gap analysis vs the operator consoles of the startups in our verticals (Cohere, Anterior, Hummingbird, Sardine, Unit21, Checkr, Sierra, Decagon, Scytale, Descartes …) found ours best-in-class as a signing surface but a queue, not a platform. Wave A closes the three most-cited gaps:

  • Analytics dashboard — aggregate KPIs over real run data (total · completed · awaiting · approval rate · escalation rate · avg time→decision · SLA breaches), role- and tenant-scoped.
  • Structured dispositions + reason codes on every decision, recorded in the audit trail (no more un-aggregatable free text).
  • Escalation as a first-class state — ↑ Escalate (to a senior; stays queued, flagged) + ↩ Send back (needs-info; recoverable) alongside approve/reject.

New endpoints: /api/autopilot/stats, /escalate, /send-back. Roadmap docs/plans/PLAN-console-gap-roadmap.md captures Waves B–D. 283 lib tests.

Assets 2
Loading