🛟 Recovery Card

If This Happens	Do This
WiFi dies	Merna switches to backup video. Malak narrates.
Chat slow	Merna keeps talking. 15s narration. Lya finishes.
STT fails	Merna types query. Pre-recorded voice plays.
Lya wrong	"Let me rephrase." Rephrase. Move on.
GitHub comment missing	"Posts within 30s. Let me refresh."
Forgot a line	Pause. Look at slide. Breathe. Continue.

Press R to close

SPECTRE IMPACT

A Day Inside NilePay

🔧 THE BUILDING

Where you see the code, the architecture, the tests.
That's how we built it.

          ✓ 8 microservices

          ✓ Terraform IaC

          ✓ CI/CD pipelines

          ✓ 12 engineers

🏢 THE COMPANY

Where you see the pager at 2:47 AM, the CTO's revenue worries, the $47,000 loss.
That's how you'll use it.

          ⚠️ Pager: 2:47 AM

          💸 Loss: $2,800/min

          📉 Downtime: 4 hours

Engineers

Microservices

Users

Per Minute Cost

🎬 ACTION

2:47 AM

"Nobody calls at 2:47 AM with good news."

It's Merna. The payment service is down.
$12,000 is bleeding out every minute.

She asks one question:

"What did you merge?"

The PR was already merged. The comment? Unread.

MERGED Terraform change → customer_database.tf 99+

4 hrs

Rollback

4 min

The Fix

$47,000 lost

That was last month. Then Merna quit. Then I quit.

The real cost isn't the money.

It's the people who leave.

🔄 Transition 1: Switch to Dashboard (Merna)

☀️ 9:00 AM — Morning PR Review

Lya Speaks Arabic

إيه الخدمات اللي هتتأثر لو غيرت customer_database.tf؟

What services are affected if I change customer_database.tf?

🤖 Lya — Spectre Impact

15 services affected by this change.

Evidence: Terraform dependency graph → BFS traversal → 15 downstream services identified

🧠 She remembers. Session context active. Not a fresh chatbot — a colleague.

"Which of those are customer-facing?"

🤖 Lya — Filtered Results

web_frontend mobile_app checkout_journey login_journey profile_journey

✅ Rollback Plan — Auto-Generated

✓ terraform state list — verify current state
✓ terraform plan -target=customer_database — review changes
✓ terraform apply -target=customer_database — execute rollback
✓ Verify payment service health check

Feature 1: Blast Radius Deterministic BFS Truth First, Explanation Second

Any company can register. Lya walks them through it. Five minutes. Zero configuration.

Lya is the onboarding team.

👔 CTO MODE: ACTIVATED

Business Impact

"It's 2 PM. I'm the CTO. Get out of my way or I will fire you."

Query:

"What's the business impact of changing checkout_journey.tf?"

85%

Users Affected

14–17

Peak Hours (Cairo)

$1.2M

Daily Transactions at Risk

That number comes from two places:

📊 Business Impact Map

Which services map to which revenue

📈 Incident History

Which services fail at peak load

Without data, it's a guess.

With data, it's a decision.

Feature 2: Business Impact

Not just what breaks — who pays.

🔄 Transition 2: Switch to GitHub PR #5 (Malak)

🔒 4:00 PM — Still the CTO. Still skeptical.

The Trust Layer

"Can we trust an AI to touch production?"

🛡️

Deterministic Fallback
Even if AI is unavailable, we still produce a plan.

👤

Human Approval Gate
Before any step executes, a human approves.

📋

Full Audit Log
Every action logged with user ID and timestamp.

🏅

SOC 2 Type One
On roadmap for Q1 2027.

🔄

Feedback Loop
Every correction feeds back. The next answer is better.

📜

Certificates in RAG
Our own certs in the knowledge graph — Lya can reference them.

💬 Spectre Impact posted on PR #5

⚠️ HIGH SEVERITY 💥 5 SERVICES 🔄 ROLLBACK READY

Blast Radius: checkout_journey → 5 downstream services
Evidence: Terraform graph → BFS → 5 affected
Rollback: 3 steps, validated, ready to execute
Validation: ✅ Whitelist check passed
🔗 Open in Lya Chat →

Feature 3: One Source of Truth

From GitHub, back to GitHub, and back to you.

🔄 Transition 3: Back to Presentation (Ahmed)

⚙️ UNDER THE HOOD

Engineering Depth

BLOCKED Prompt injection attempts — guarded at every input

REDACTED Secrets in output — filtered before response

CHAINED Multi-provider: if one goes down, we chain three

LOCAL Embeddings run locally — no API key for retrieval

WHITELIST Every rollback command validated before execution

AUDIT Every attempt logged with UTC timestamp

Groq

→

OpenAI

→

Anthropic

→

Fallback

120

Real Documents

Data Stored on Our Side

99.99%

Uptime Target

∞

Audit Trail Depth

If Lya doesn't know, she says so.

📊 THE RECAP + BUSINESS CASE

What You Actually Saw

🔮

Predict

Before you merge, you know what breaks. Deterministic BFS. Not a guess — a computation.

⚖️

Prioritize

Not everything that breaks matters equally. We tell you who pays. One score.

🛡️

Protect

Rollback plan is a checklist. Human-approved. Every action logged. Every decision auditable.

Lya has four modes:

😊

Friend

🔧

Engineer

🎓

Coach

🚨

Emergency

$15K

Downtime cost / minute (enterprise)

82%

Orgs with AI-code production failures

$50–200K

Saved per prevented outage

Datadog

Tells you what broke

Spectre Impact

Tells you what will break

Copilot helps you write code faster.

We help you ship it safer.

حبيبة

🚀 THAT'S TODAY. HERE'S TOMORROW.

The Roadmap

CLI on PyPI

pip install spectre-impact — any developer, local install

GitHub App

Install once per organization, not per repo

Predictive Failure Detection

Learn from every incident to flag risky changes

Slack + Jira Integrations

Native integrations with your workflow tools

Enterprise: SOC 2, SSO, Multi-Dialect Arabic

Sell to enterprises across the Gulf, Levant, and North Africa

Students

450

Hours

∞

Ambition

NilePay isn't real. But the problem is.

Every company has a 2:47 AM story.

Scan to install. It's live. It's open source.

pip install spectre-impact

We built the fix. It's yours.

Everything we said about the CTO firing people? That was a joke. We respect everyone. Especially our DevOps instructor. 😄