Aegis / Operations Queue

Cases

Live store: durable SQLite

Document triage for underwriting and claims intake. Aegis should read like an operational queue: what entered, what was extracted, where evidence is thin, and which files are strong enough to move toward decision.

Intake view

Every case keeps policy, upload state, evidence coverage, and recommendation strength in one row.

Extraction first

Aegis frames raw document understanding before anything hands off to downstream trigger adjudication.

Human gate

Weak or conflicting evidence stays visible as review work, not hidden behind a false binary answer.

Open queue

0

Live case records currently in the intake board.

Needs review

0

Cases where extracted evidence still needs judgment.

Uploaded

0

Cases with a document already attached.

Recommendations

0

0 completed and ready for downstream action.

Queue Board

Active intake

Awaiting first case

No cases yet

Create a case to start.

Operating Rules
  • Keep document understanding, corroborating evidence, and downstream adjudication clearly separated.
  • Use policy thresholds as framing context, not as a substitute for evidence quality.
  • Escalate weak files visibly so the queue reflects where human time is actually required.
Policy Context

Aegis no longer ships with a bundled demo policy book. Attach a policy reference to a case, or upload the governing policy schedule alongside the evidence when you need policy-specific reasoning.