AI Request Triage

New queue design showcase. Default is Demo mode (instant mock, no API call). Switch to Live mode to call the real triage API. Live app remains on /.

Prototype design · /prototypeDemo mode · instant mockModel: deepseek-ai/deepseek-v4-proIn-memory queueRole: Approver
Mode: Demo (no API call, instant mock)
deepseek-ai/deepseek-v4-pro · Schema validation · Local safety checksDEMO MODE · no API call · No DB
Step 02 / 02 · Approver (Head of Software) routes structured briefs · 01 Submit · 02 AI structures · 03 Reviewer routes
5 open · 3 blocked · 2 routable · 1 reject
Inbox

Open queue

Approver view · routes/blocks requests

RequestCustomerDeadlineMissingStatus

Selected request

Defence border monitoring opportunity

Clarify persistent border monitoring RFI before software review

A cautious internal feasibility review for a defence customer asking about persistent remote border monitoring. Resolve missing inputs before Software is engaged.

Deadline · FridayConf. 84%

Type

Customer RFI triage

Urgency

High

Sensitivity

Defence-sensitive

Route

Sales + Operations + Securit…

Decision · blocked

Software interrupt is blocked

4 missing inputs and risk flags. Resolve with Sales before Software is paged.

Original — what Sales wrote

Customer / opportunity name: Defence border monitoring opportunity Request summary: A defence customer wants to know whether we can support persistent monitoring for a remote border corridor. They need a preliminary technical answer by Friday and want to understand coverage, latency, winter performance, and delivery format. Deadline: Friday What Sales needs from Software/Ops: Help Sales understand whether this is ready for software/ops review and what information is missing. Customer-facing commitment needed: Yes Sales-selected sensitivity: Defence-sensitive

Audit notes

  • // schema: triage · valid
  • // safety: mock · 2/2 pass
  • // submitted: Today, 09:14
  • // model: deepseek-ai/deepseek-v4-pro
  • // Mock prototype output
  • // Referenced MOCKED Defence-Sensitive Data Handling Policy
  • // Referenced MOCKED Software Team Interruption Policy

Structured brief

Clarify persistent border monitoring RFI before software review

A cautious internal feasibility review for a defence customer asking about persistent remote border monitoring. Resolve missing inputs before Software is engaged.

Request type

Customer RFI triage

Urgency

High

Business value

High

Complexity

High

Sensitivity

Defence-sensitive

Confidence

84%

Missing information

04 ITEMS
  1. 01AOI/location and corridor dimensions
  2. 02Required revisit cadence or persistence expectation
  3. 03Latency and delivery format requirements
  4. 04Environmental and winter operating constraints

Risk flags

03 ITEMS
  • !Defence-sensitive customer context
  • !Potential unsupported feasibility commitment
  • !Software interruption risk before requirements are clear

Draft to Sales

One round of questions beats three rounds of guesses.

Before Software reviews this, please confirm the AOI, cadence, latency target, delivery format, winter constraints, and who can approve any customer-facing statement.

Reviewer action

Local checks (mock)

Safety checks: 100%

This is a mock prototype safety-check harness, not proof of full safety.

Structured output valid

Output follows the triage schema.

PASS

Software interrupt control

Software interruption is blocked while missing information is substantial.

PASS

Mock

Audit trail

Model: deepseek-ai/deepseek-v4-proTimestamp: 4/30/2026, 12:00:00 PM
  • Request submitted (prototype)
  • Mock triage attached
  • Schema-shaped output (mock)
  • Local safety checks (mock)
  • Head of Software review pending
  • Mock prototype output
  • Referenced MOCKED Defence-Sensitive Data Handling Policy
  • Referenced MOCKED Software Team Interruption Policy