AWS AI DLC Workshop · Two-day sprint

Alarm Centre

How our team used AWS AI DLC to walk from a customer’s pain to a working prototype — with AI as a full team member.

VORTEX Team D July 1, 2026
The team

Two days, one team.

Two days. One team. Every decision was a conversation — with each other, and with AI.

Workshop Day 1 — team working session
Day 1 · June 30, 2026 · Define & ask
Workshop Day 2 — prototype review
Day 2 · July 1, 2026 · Consolidate & prototype
The pain we started with

Alarm Receiving Centers are drowning.

Alarm Receiving Centers watch homes, buildings, and communities around the clock. Every shift starts with pain that better data alone cannot fix. Three problems keep coming back.

Critical drowned

Life-safety alerts get buried under routine events and false alarms.

Handoff opaque

No one knows who owns which case. Shift handovers are messy.

Metrics untranslated

Performance data can’t be turned into reports for clients or auditors.

The cost: operators spend the shift reading alerts. Real risk waits in the queue.

Our playbook

How we ran two days with AI DLC.

AI DLC — the AI Development Life Cycle — treats AI as a full team member. Not a code generator, a co-worker: it reasons about specs, asks sharp questions across roles, and consolidates decisions into a checkable plan.

1

Define

PM writes the customer pain in an open spec — no solutions yet.

2

Ask

AI runs each engineering role through a tailored questionnaire.

3

Consolidate

AI merges all answers into one spec — conflicts and gaps surfaced.

4

Prototype

AI generates a working UI, ready to run and demo.

In short: AI carries the coordination overhead so humans stay on judgment calls.

The outcome

So what did
two days actually produce?

A working prototype. A real story. And a real trade-off ledger.
Let me show you.

Before we start · the whole picture

The system at a glance.

One Cockpit in the middle. Three roles use it every day. It reads from VORTEX and produces reports for the outside world.

VORTEX Platform Alarms · events · thumbnails · stream Alarm / event Thumbnail / stream VORTEX ARC Cockpit Alarm Receiving Center · triage claim · scoring · KPI · audit Operator Role A · on shift Supervisor Role B · tunes rules Management Role C · reads reports Web UI Notification providers SMS · IVR (external) notify / escalate Report consumers Governments · clients PDF / CSV · audit
The product

VORTEX ARC Cockpit — one spine, three roles.

One backend feeds three views. Operators care about speed. Supervisors tune the scoring engine. Executives prove the impact. The same data, framed for each job.

Role A

Operator

Lives in the queue. Knows what to work on next at first glance.

  • Risk-sorted queue with Critical pinned
  • One-click claim & false-alarm downgrade
  • Auto handover summary at shift end
Role B

Supervisor

Tunes the scoring engine so the team trusts the ranking.

  • Weight sliders with live preview
  • Versioned rule changes
  • Center health at a glance
Role C

Management

Reads risk exposure in 5 seconds. Proves impact to clients.

  • Single-page KPI dashboard
  • Trends across time periods
  • One-click audit PDF export
Team reflections

What we take home.

Team — Day 1
Team — Day 2

PM

  • Customer needs, scenarios & pain — still the anchor.
  • How do I work with RD when AI is in the room?
  • Communication cost — how much is enough?

RD

  • Software skills + AI for market survey.
  • What is the value of a PM to me?
  • Small team beats big — communication cost matters.
  • Lean Startup: build → measure → learn.
Thank you

From pain to prototype in two days.

Happy to answer any questions — and to hear how you would run day three.

Q & A

Appendix

Reference architectures.

Operator Role A · on shift Supervisor Role B · tunes rules Management Role C · reads reports VORTEX Platform Alarms · events · thumbnails · stream VORTEX ARC COCKPIT — SYSTEM BOUNDARY Frontend Web App Vue 3 · Pinia · Tailwind · ECharts 3-role views · realtime queue Auth RBAC P2 · productionization Ingress Adapter Unified event model · idempotent Normalize per source vendor API + WebSocket Gateway Go · REST + WebSocket Rule / Policy Engine org × type → level Action Plan steps · thresholds KPI Aggregator MTTA · MTTR · false-alarm rate Audit Service append-only (+hash chain P2) Data Store SQLite (V1) → PostgreSQL (P2) V1 P2 · productionization Report consumers Governments · clients Notification providers SMS · IVR (P2) Web UI Alarm / event Thumbnail / stream PDF · CSV · audit notify / escalate
VORTEX ARC Cockpit · system boundary (V1 + P2)
VORTEX-D · Event Streaming Architecture ◐ User browser Client ☁ webhook. vivotek.tools SSE fan-out AWS ACCOUNT · ap-northeast-1 FRONTEND DELIVERY CloudFront Distribution · HTTPS caching disabled Origin Access Control OAC S3 Bucket vortex-d-frontend block public access REAL-TIME EVENT FORWARDING App Runner Service VORTEX-D-proxy 0.25 vCPU · 0.5 GB Amazon ECR container-assets CDK bootstrap Pull image IAM ROLE CHAIN SSO Role kiro-sandbox-ai-dlc CloudFormationFullAccess ECR / S3 FullAccess · PassRole role-cloudformation-deploy AdministratorAccess creates AWS resources iam:PassRole CDK Bootstrap · Staging S3 Bucket Lambda assets · templates HTTPS GET / EventSource /events HTTPS SSE · long-lived connection
VORTEX-D · event streaming architecture on AWS