🗺️Phases (A / B / C / D)

The journey: Route C → Phase B v2 → Phase C (pre on-device test) → Phase D (not started).

The overall timeline of the development phases. Source: INVENTORY.md (PR history) and REVIEW_PHASE_C.md.

Route C: OpenAI Realtime 2 Done

2026-05-09

Established a call path with a direct browser ↔ OpenAI WebRTC connection.

RealtimeSessionAdapter
Ephemeral key issuance
Shared tools_core
/api/realtime/*

Related: aegis-platform #1

Phase B v2 (B1'–B10) Done

2026-05-09 to 05-11

Full implementation of observability, recording, retention, live dashboard updates, and more.

B1' dashboard live updates (SSE)
B4 duration_seconds
B6 retention sweeper (dry-run)
B7 event-trace endpoint
B3 AES-256-GCM recording encryption
B10 WebRTC session recovery v2.5

Related: aegis-platform #2〜#11, #12〜#20

Phase C: SIP / real phone numbers (stealth) Pre-on-device test

2026-05 onward (in progress)

The path that routes inbound calls on real phone numbers into Aegis. A dedicated repo, aegis-sip-bridge, was created and a v2 standalone stack (new Pi / Ubuntu 24.04 / Asterisk 20 / chan_audiosocket / bridge.py) prepared. Pre on-device testing.

New aegis-sip-bridge repo
AudioSocket ↔ OpenAI Realtime bridge
AstDB verdict propagation (AMI)
C-2(b) business-side fail-open (hand off to a human)
Separating the deploy layout (wiring package / bridge)

Related: aegis-sip-bridge #2 (Draft), #3〜#6

Phase D: Call Intent Firewall Not started

Not started

A call-intent firewall (14 classifications × 8 actions). Note: the design doc CALL_INTENT_FIREWALL_DESIGN.md is not present in the repo, so the detailed spec is undetermined.

14 classifications × 8 actions (from this site's source prompt; the repo design doc is undetermined)

Diagram: Phase A→B→C→D. Color = state (green=done / blue=in progress / yellow=pre on-device test / gray=not started).

⚠️Phase C is stealth / pre on-device test

For Phase C we created a dedicated repo, aegis-sip-bridge, and prepared a v2 standalone stack (new Pi / Ubuntu 24.04 / Asterisk 20 / chan_audiosocket / bridge.py). It will merge once on-device testing passes (the PRs are Drafts). The deploy approach is to keep the wiring package and the bridge separable so each can be carved out independently (not yet built).

📌Phase D: Call Intent Firewall (not started; spec undetermined)

A call-intent firewall (14 classifications × 8 actions). However, the design doc CALL_INTENT_FIREWALL_DESIGN.md was confirmed during the INVENTORY survey to be absent from the repo, so the detailed spec is undetermined.