BACK TO SELECTED WORK
CASE STUDYDistributed SRE / AIOps Platform

Aegis

Air-Gapped AIOps & Self-Healing Infrastructure

ROLELead Systems Arch...
CORE STACKTypeScript / Python /...
YEAR2026
STATUSActive
EST. READ59 MIN READ

Closed-loop, local-first SRE platform for detecting container failures, diagnosing incidents, and executing policy-controlled remediation.

Core Challenge: Modern containerized systems fail through OOM conditions, timeouts, crash loops, port collisions, memory leaks, and permission errors. SRE teams require a closed-loop platform that detects, diagnoses, evaluates safety, remediates, and audits without external cloud dependencies.

TypeScriptPythonNestJSKafkaDockerMongoDB

THE PROBLEM

Modern containerized systems fail through OOM conditions, timeouts, crash loops, port collisions, memory leaks, and permission errors. Detecting the failure is only the first step — automated systems must safely diagnose, evaluate policy, remediate, and audit without human bottlenecks.

Understand what failed at the container runtime level.

Determine the probable failure cause via local semantic classification.

Determine whether automated remediation is safe under strict policy.

Perform a deterministic, controlled Docker action.

Preserve the complete end-to-end evidence trail in durable storage.

KEY CONSTRAINTS & COORDINATION PROBLEMS5 VECTORS
  • ▸DETECT →: Understand what failed at the container runtime level.
  • ▸DIAGNOSE →: Determine the probable failure cause via local semantic classification.
  • ▸DECIDE →: Determine whether automated remediation is safe under strict policy.
  • ▸REMEDIATE →: Perform a deterministic, controlled Docker action.
  • ▸AUDIT →: Preserve the complete end-to-end evidence trail in durable storage.
CONTAINER FAILURE CATEGORIES
FAILURE
│
├── OOM
├── TIMEOUT
├── CRASH LOOP
├── PORT COLLISION
├── MEMORY LEAK
└── PERMISSION ERROR
│
▼
AUTOMATED RESPONSE

Explicit failure classes parsed from stdout/stderr tails and classified by the local AI pipeline.

HORIZONTAL SCROLL ON MOBILE ↔

THE APPROACH

Aegis uses a closed-loop architecture. Rather than passively alerting human operators or granting unbounded shell execution to LLMs, it connects detection to policy-gated remediation.

Watchman catches container death and tails stdout/stderr logs.

Publishes raw incident payloads into decoupled Kafka KRaft topics.

Generates 384-dim log embeddings and runs FAISS + MLP classification.

Validates confidence, risk level, and blast radius against safety gates.

Executes approved enum actions directly through Dockerode API.

Stores full incident context, embeddings, and execution receipts in MongoDB.

CLOSED-LOOP REMEDIATION WORKFLOW
┌─────────────────────┐
│ FAILING CONTAINER │
└──────────┬──────────┘
│
Docker Event
▼
┌─────────────────────┐
│ DOCKER WATCHMAN │
└──────────┬──────────┘
│
Kafka Event
▼
┌─────────────────────┐
│ KAFKA KRAFT │
│ EVENT BACKBONE │
└──────────┬──────────┘
│
▼
┌─────────────────────┐
│ ORCHESTRATOR │
│ NestJS │
└──────────┬──────────┘
│
▼
┌─────────────────────┐
│ AI ENGINE │
│ Diagnose Incident │
└──────────┬──────────┘
│
▼
┌─────────────────────┐
│ SAFETY GATE │
└───────┬───────┬─────┘
│ │
PASS FAIL
│ │
▼ ▼
REMEDIATE REVIEW
│
▼
DOCKER
│
▼
AUDIT

Unidirectional event flow: container death through Kafka KRaft, local AI diagnosis, safety evaluation, and Dockerode execution.

HORIZONTAL SCROLL ON MOBILE ↔

DETECT →

Watchman catches container death and tails stdout/stderr logs.

STREAM →

Publishes raw incident payloads into decoupled Kafka KRaft topics.

DIAGNOSE →

Generates 384-dim log embeddings and runs FAISS + MLP classification.

EVALUATE →

Validates confidence, risk level, and blast radius against safety gates.

REMEDIATE →

Executes approved enum actions directly through Dockerode API.

AUDIT →

Stores full incident context, embeddings, and execution receipts in MongoDB.

ARCHITECTURE & DATA FLOW

Air-gapped distributed topology running entirely within the host environment. Events flow asynchronously through Kafka KRaft into local neural inference and policy-enforced actuation.

Coordinates Docker Watchman events, Kafka producers/consumers, safety policy gates, and actuator calls.

ZooKeeper-free distributed event log for reliable incident streaming, decoupled buffering, and replay.

Local neural network pipeline: all-MiniLM-L6-v2 embeddings, sub-ms FAISS lookup, and PyTorch MLP classifier.

Persistent incident store, raw log history, embedding vectors, remediation plans, and offline RL replay buffers.

Direct Unix socket client executing enum-only container actions (restart, stop, inspect) without shell scripts.

AEGIS DISTRIBUTED SYSTEM TOPOLOGY
┌─────────────────────┐
│ DOCKER HOST │
│ │
│ Failing Container │
└──────────┬──────────┘
│
Docker Events
│
▼
┌─────────────────────┐
│ NESTJS CONTROL │
│ PLANE │
│ │
│ Docker Watchman │
│ Orchestrator │
│ Remediation │
└──────────┬──────────┘
│
▼
┌─────────────────────┐
│ KAFKA KRAFT │
│ EVENT BACKBONE │
└──────────┬──────────┘
│
▼
┌─────────────────────┐
│ AI ENGINE │
│ │
│ Embedding │
│ FAISS │
│ MLP Classifier │
└──────────┬──────────┘
│
Diagnosis
│
▼
┌─────────────────────┐
│ SAFETY GATE │
└──────────┬──────────┘
│
▼
┌─────────────────────┐
│ DOCKERODE │
│ REMEDIATION │
└──────────┬──────────┘
│
▼
┌─────────────────────┐
│ MONGODB │
│ AUDIT / STATE │
└─────────────────────┘

Unidirectional event flow linking Docker daemon events to local AI diagnosis, safety gates, and audited remediation.

HORIZONTAL SCROLL ON MOBILE ↔
SYSTEM SUBSYSTEMS & RESPONSIBILITIES5 SUBSYSTEMS SPECIFIED
01CONTROL PLANE

Coordinates Docker Watchman events, Kafka producers/consumers, safety policy gates, and actuator calls.

02EVENT BACKBONE

ZooKeeper-free distributed event log for reliable incident streaming, decoupled buffering, and replay.

03AI COMPUTE

Local neural network pipeline: all-MiniLM-L6-v2 embeddings, sub-ms FAISS lookup, and PyTorch MLP classifier.

04STATE & AUDIT

Persistent incident store, raw log history, embedding vectors, remediation plans, and offline RL replay buffers.

05EXECUTION

Direct Unix socket client executing enum-only container actions (restart, stop, inspect) without shell scripts.

FROM CRASH TO RECOVERY

Terminal execution trace showing the step-by-step progression of an incident from container death to audited recovery.

Docker daemon emits lifecycle death signal across local Unix socket.

Watchman listener filters out intentional stops and flags unexpected termination.

Recent stdout and stderr streams extracted into raw incident diagnostic context.

Asynchronous incident payload committed into partitioned Kafka event backbone.

NestJS orchestrator consumes event and routes diagnostic payload to local AI engine.

Python service returns classification label, confidence score, and suggested action.

Deterministic safety policy validates diagnosis against blast radius rules.

Orchestrator invokes scoped Dockerode restart call directly on target container.

Complete audit record, diagnosis vector, and actuation receipt stored in MongoDB.

TECHNICAL RIGOR

Concrete systems guarantees enforced through decoupled streaming, immutable persistence, and deterministic safety boundaries.

DISCIPLINEENGINEERING MECHANISMSYSTEM GUARANTEE
EVENT DELIVERYKafka Event BackboneDecouples container watcher death telemetry from downstream AI diagnostic processing.
STATEMongoDB Durable Audit TrailStores immutable incident records, vector embeddings, safety decisions, and receipts.
FAILURE HANDLINGKafka Retry / Outbox StrategyGuarantees reliable message delivery even during transient database or service hiccups.
AILocal Inference PipelineSentenceTransformers (all-MiniLM-L6-v2), FAISS, and PyTorch run 100% locally without cloud dependencies.
SAFETYDeterministic Remediation PolicyEnforces confidence thresholds (>= 0.85) and LOW risk validation before approving any actuation.
SECURITYNo Shell ExecutionEliminates command injection risks by restricting actions to Dockerode API socket calls.
NETWORKPrivate Docker BridgeServices communicate across an isolated host bridge without external egress or cloud telemetry leaks.
TESTINGChaos Simulation EngineBuilt-in failure harness injecting OOM, timeout, crash loop, permission, and port collisions.

AI DIAGNOSIS PIPELINE

Aegis avoids non-deterministic generative LLMs in favor of a fast, local neural pipeline combining semantic embedding, vector similarity, and multi-layer perceptron (MLP) classification.

Preprocesses raw container stderr/stdout logs and converts them into normalized 384-dimensional dense semantic vectors.

Executes sub-millisecond local vector distance search over historical incident embeddings to find nearest prior failures.

Classifies the 384-dim log embedding into supported failure categories (OOM, Timeout, Crash Loop, Port, Perm, Leak).

Emits failure classification, calibrated confidence score, blast radius risk level, and suggested enum remediation action.

LOCAL VECTOR EMBEDDING & CLASSIFICATION PIPELINE
RAW CRASH LOG
│
▼
PREPROCESSING
│
▼
ALL-MINILM-L6-V2
│
▼
384-DIM EMBEDDING
│
├─────────────────────┐
▼ ▼
FAISS MLP
Similarity Search Classification
│ │
└──────────┬──────────┘
▼
DIAGNOSIS RESPONSE

Crash logs pass into local all-MiniLM-L6-v2 embedding, querying FAISS similarity and PyTorch MLP classification in parallel.

HORIZONTAL SCROLL ON MOBILE ↔
all-MiniLM-L6-v2

EMBEDDING

Preprocesses raw container stderr/stdout logs and converts them into normalized 384-dimensional dense semantic vectors.

Facebook AI Similarity Search

FAISS SEARCH

Executes sub-millisecond local vector distance search over historical incident embeddings to find nearest prior failures.

PyTorch Neural Network

MLP CLASSIFIER

Classifies the 384-dim log embedding into supported failure categories (OOM, Timeout, Crash Loop, Port, Perm, Leak).

Structured Schema

DIAGNOSIS OUTPUT

Emits failure classification, calibrated confidence score, blast radius risk level, and suggested enum remediation action.

ENGINEERING CHALLENGES

Key architectural challenges encountered when designing a self-healing SRE platform operating in sensitive, air-gapped container environments.

01 CHALLENGE

AUTOMATED REMEDIATION WITHOUT RCE

SECURITY
PROBLEM

Giving an autonomous system unrestricted shell access creates an unacceptable vulnerability if arbitrary commands enter the execution path.

02 CHALLENGE

AI UNCERTAINTY & FALSE DIAGNOSIS

ACCURACY
PROBLEM

A neural diagnosis can be wrong or low-confidence. Automated remediation on incorrect assumptions can amplify cluster instability.

03 CHALLENGE

EVENT DECOUPLING & LATENCY SKEW

CONCURRENCY
PROBLEM

Docker container death events occur in microsecond bursts, whereas local model inference has completely different latency characteristics.

04 CHALLENGE

ABSOLUTE AUDITABILITY

COMPLIANCE
PROBLEM

Every automated remediation decision, raw diagnostic log tail, vector similarity score, and Docker call must be fully traceable post-mortem.

05 CHALLENGE

AIR-GAPPED OPERATION

ISOLATION
PROBLEM

The entire platform must function without outbound internet access, cloud AI endpoints, or external model hosting infrastructure.

06 CHALLENGE

INDEPENDENT FAILURE RECOVERY

RESILIENCE
PROBLEM

Kafka brokers, consumer orchestrators, target microservices, or MongoDB storage can fail independently without dropping inflight incidents.

ENGINEERING CHALLENGES & SOLUTIONS

Step-by-step engineering reasoning: Problem → Constraint → Engineering Response → Result applied across every critical reliability boundary.

01 CHALLENGE

AI-DRIVEN REMEDIATION WITHOUT RCE

PROBLEM

AI model output should never become arbitrary shell execution on the host container environment.

CONSTRAINT

Automated actions must remain strictly deterministic, scoped, and bounded.

SOLUTION

Used an enum-only action registry (RESTART_CONTAINER, STOP_CONTAINER, IGNORE) mapped directly to explicit Dockerode Unix socket calls.

RESULT

Zero AI-generated shell scripts enter the execution path. Remote code execution is architecturally impossible.

AI-DRIVEN REMEDIATION WITHOUT RCE
AI DIAGNOSIS
│
▼
ENUM-ONLY ACTION REGISTRY
│
├── RESTART_CONTAINER ──► dockerode.getContainer().restart()
├── STOP_CONTAINER ──► dockerode.getContainer().stop()
└── IGNORE ──► no_op()

Formal resolution architecture implemented inside the Aegis runtime.

HORIZONTAL SCROLL ON MOBILE ↔
02 CHALLENGE

LOW-CONFIDENCE DIAGNOSIS & FLAPPING

PROBLEM

Inaccurate or low-confidence diagnosis can trigger unsafe automation loops and container thrashing.

CONSTRAINT

Remediation should execute autonomously only when classification certainty is mathematically high.

SOLUTION

Enforced strict threshold gates: requires confidence >= 0.85 AND risk == LOW AND action == RESTART_CONTAINER. Otherwise, automated action is skipped and flagged for operator review.

RESULT

Unsafe or uncertain actions fail-safe into human oversight rather than causing cascading container failures.

LOW-CONFIDENCE DIAGNOSIS & FLAPPING
EVALUATE DIAGNOSIS
│
├── confidence >= 0.85 ?
├── risk == LOW ?
└── action == RESTART_CONTAINER ?
│
┌───┴───┐
YES NO
│ │
▼ ▼
EXECUTE SKIP + OPERATOR REVIEW

Formal resolution architecture implemented inside the Aegis runtime.

HORIZONTAL SCROLL ON MOBILE ↔
03 CHALLENGE

EVENT DECOUPLING & BURST RESILIENCE

PROBLEM

Docker event capture should not block on AI inference or drop events during container failure storms.

CONSTRAINT

Watcher latency must remain sub-millisecond even when neural networks take longer to compute.

SOLUTION

Kafka KRaft acts as the distributed event backbone between the Docker Watchman and the NestJS orchestrator.

RESULT

High-throughput event ingestion with zero dropped incident signals and decoupled consumer processing.

EVENT DECOUPLING & BURST RESILIENCE
DOCKER WATCHMAN (Events)
│
▼
KAFKA KRAFT (Buffer Queue)
│
▼
NESTJS ORCHESTRATOR (Compute)

Formal resolution architecture implemented inside the Aegis runtime.

HORIZONTAL SCROLL ON MOBILE ↔
04 CHALLENGE

EXPLAINABLE & AUDITABLE POST-MORTEMS

PROBLEM

Automated remediation must remain completely explainable and auditable long after execution.

CONSTRAINT

Every input, neural vector, decision gate, and API execution receipt must be immutably preserved.

SOLUTION

Persisted structured incidents, raw log tails, FAISS vectors, remediation plans, and execution receipts in MongoDB.

RESULT

Complete forensic audit trail for every automated SRE event across the infrastructure.

EXPLAINABLE & AUDITABLE POST-MORTEMS
INCIDENT
│
├── RAW LOG TAIL (stdout/stderr)
├── 384-DIM EMBEDDING (FAISS)
├── SAFETY POLICY VERIFICATION
└── DOCKER ACTUATION RECEIPT
│
▼
MONGODB (Persisted)

Formal resolution architecture implemented inside the Aegis runtime.

HORIZONTAL SCROLL ON MOBILE ↔

TECHNICAL DECISIONS

Compact decision records detailing why each core technology was selected to guarantee air-gapped autonomy, strict isolation, and high performance.

DECISION 01 • EVENT STREAMING

Kafka KRaft

WHY / RATIONALE

Durable event streaming and high-throughput decoupling between container event capture and neural processing.

DECISION 02 • STATE & AUDIT

MongoDB

WHY / RATIONALE

Flexible document persistence perfectly suited for semi-structured incident payloads, raw log arrays, high-dimensional vector embeddings, and offline RL replay buffers.

DECISION 03 • CONTAINER RUNTIME

Dockerode

WHY / RATIONALE

Direct Docker Engine Unix socket communication without spawning shell subprocesses, eliminating shell injection and command interpretation risks.

DECISION 04 • VECTOR SEARCH

FAISS

WHY / RATIONALE

Ultra-fast local nearest-neighbor similarity search over historical incident embeddings without cloud vector database latency or cost.

DECISION 05 • LOCAL EMBEDDINGS

SentenceTransformers

WHY / RATIONALE

Compact, efficient local model (all-MiniLM-L6-v2) generating 384-dimensional dense semantic vectors entirely offline on CPU/GPU.

DECISION 06 • CONTROL PLANE

NestJS

WHY / RATIONALE

Enterprise-grade TypeScript modular architecture with strict dependency injection, separating watchers, event buses, safety policies, and actuators.

AUTOMATION WITH GUARDRAILS

Aegis separates diagnosis from actuation. AI recommends an action, but a deterministic policy engine evaluates safety thresholds before a single container is touched.

Neural classification confidence must be strictly ≥ 0.85. Low-confidence ambiguity defaults to safe inaction.

Risk rating must be strictly LOW. Destructive or stateful services are blocked from autonomous intervention.

Any gate failure aborts automated execution, persists full audit telemetry, and escalates to human on-call engineers.

DETERMINISTIC SAFETY GATE DECISION TREE
AI DIAGNOSIS
│
▼
┌────────────────┐
│ FALLBACK? │
└───────┬────────┘
│ NO
▼
┌────────────────┐
│ CONFIDENCE │
│ >= 0.85 │
└───────┬────────┘
│ YES
▼
┌────────────────┐
│ RISK == LOW │
└───────┬────────┘
│ YES
▼
┌────────────────┐
│ ACTION == │
│ RESTART │
└───────┬────────┘
│ YES
▼
AUTO-REMEDIATE
ANY FAILURE
│
▼
SKIP
│
▼
OPERATOR REVIEW

Strict hierarchical policy gates: any threshold violation or high-risk classification immediately skips actuation and alerts operators.

HORIZONTAL SCROLL ON MOBILE ↔

CONFIDENCE CEILING

Neural classification confidence must be strictly ≥ 0.85. Low-confidence ambiguity defaults to safe inaction.

BLAST RADIUS LIMIT

Risk rating must be strictly LOW. Destructive or stateful services are blocked from autonomous intervention.

FAIL-SAFE OPERATOR ROUTING

Any gate failure aborts automated execution, persists full audit telemetry, and escalates to human on-call engineers.

SECURITY BOUNDARIES

Aegis enforces rigid execution firewalls between the probabilistic AI pipeline, the NestJS control plane, and the Docker container host.

No bash, sh, or exec wrappers. Eliminates command injection vectors completely.

Zero outbound network calls to third-party AI APIs; fully isolated from public internet.

Guaranteed reproducibility with deterministic embeddings and calibrated MLP output.

Hardcoded enum values (RESTART, STOP, IGNORE) bounding actuator scope.

Internal Docker bridge network with no external ports exposed for telemetry.

High-risk, stateful, or uncertain incidents require explicit human sign-off.

RIGID ISOLATION BOUNDARIES
AI
│
│ enum only
▼
ORCHESTRATOR
│
│ safety policy
▼
DOCKERODE
│
│ restricted API
▼
CONTAINER

Unidirectional privilege escalation prevention: AI emits enums only, Orchestrator checks policy, Dockerode executes API only.

HORIZONTAL SCROLL ON MOBILE ↔

NO SHELL EXECUTION

No bash, sh, or exec wrappers. Eliminates command injection vectors completely.

NO CLOUD AI

Zero outbound network calls to third-party AI APIs; fully isolated from public internet.

NO EXTERNAL LLM

Guaranteed reproducibility with deterministic embeddings and calibrated MLP output.

FIXED ACTION REGISTRY

Hardcoded enum values (RESTART, STOP, IGNORE) bounding actuator scope.

PRIVATE SERVICE NETWORK

Internal Docker bridge network with no external ports exposed for telemetry.

OPERATOR REVIEW GATES

High-risk, stateful, or uncertain incidents require explicit human sign-off.

SYSTEM INTERACTION STATES

Deterministic incident state machine tracking every container transition from failure detection to audited recovery. Hover or click any state to inspect its operational invariant.

NestJS Orchestrator tests confidence >= 0.85, risk == LOW, and action == RESTART.

INCIDENT LIFECYCLE STATE MACHINE
HEALTHY
│
│ crash
▼
DETECTED
│
▼
INCIDENT_CREATED
│
▼
LOGS_EXTRACTED
│
▼
DIAGNOSING
│
▼
DIAGNOSIS_READY
│
▼
SAFETY_EVALUATION
│
┌──┴───────┐
▼ ▼
APPROVED SKIPPED
│ │
▼ ▼
REMEDIATED REVIEW
│
▼
AUDITED

Deterministic incident lifecycle: branching at SAFETY_EVALUATION into either automated remediation or human SRE review.

HORIZONTAL SCROLL ON MOBILE ↔

THE AUDIT TRAIL

Aegis is not simply a container restart script. It maintains an immutable, multi-dimensional MongoDB audit history preserving full incident context, neural vectors, and execution logs.

Sequential incident-state-action tuples captured to train offline reinforcement learning policies without production interference.

Point-in-time CPU, RAM, and container network metrics recorded before, during, and after remediation actions.

Transactional outbox pattern guaranteeing that every detected container incident is eventually delivered to Kafka even if brokers temporarily disconnect.

MONGODB ENTITY RELATIONSHIPS
SERVICE
│
▼
INFRASTRUCTURE EVENT
│
├── INCIDENT EMBEDDING
│
└── REMEDIATION PLAN
│
▼
ACTION EXECUTION

Relational structure linking services to raw infrastructure events, high-dimensional embeddings, plans, and execution receipts.

HORIZONTAL SCROLL ON MOBILE ↔
Offline RL Replay Buffer

EPISODES

Sequential incident-state-action tuples captured to train offline reinforcement learning policies without production interference.

Infrastructure Measurements

METRICS SNAPSHOTS

Point-in-time CPU, RAM, and container network metrics recorded before, during, and after remediation actions.

Durable Kafka Event Retry

OUTBOX EVENTS

Transactional outbox pattern guaranteeing that every detected container incident is eventually delivered to Kafka even if brokers temporarily disconnect.

OFFLINE LEARNING LOOP

Aegis incorporates an offline Reinforcement Learning (RL) replay pipeline to analyze historical incident episodes and evaluate future remediation heuristics without live cluster risk.

OFFLINE RL RESEARCH PIPELINE
HISTORICAL INCIDENTS
│
▼
REPLAY DATASET
│
▼
OFFLINE RL TRAINING
│
▼
POLICY EVALUATION
│
▼
RESEARCH / FUTURE POLICY

Historical incident episodes are compiled into offline replay buffers for research and future policy evaluation.

HORIZONTAL SCROLL ON MOBILE ↔

CHAOS TESTING

Aegis ships with a built-in chaos engineering suite to intentionally inject container failure modes and verify closed-loop detection, neural classification, and policy gating.

Spawns a memory-greedy worker allocating unconstrained RAM until Linux kernel OOM-killer fires.

Injects deadlocks and hung HTTP keep-alive loops that exceed service health-check deadlines.

Forces unhandled runtime panics and fatal SIGSEGV exit codes to test immediate recovery.

Revokes host volume filesystem permissions to evaluate permission-denied classification.

Attempts binding already-occupied host TCP ports to test address-in-use detection.

CHAOS INJECTION TO REMEDIATION PIPELINE
CHAOS TRIGGER
│
▼
CONTAINER FAILURE
│
▼
AEGIS DETECTION
│
▼
DIAGNOSIS
│
▼
SAFETY GATE
│
▼
REMEDIATION
│
▼
AUDIT

Controlled failure injection simulating microservice crashes to continuously validate the self-healing loop.

HORIZONTAL SCROLL ON MOBILE ↔
Injects heap exhaustion

EXECUTABLE

OOM

Spawns a memory-greedy worker allocating unconstrained RAM until Linux kernel OOM-killer fires.

MEASURABLE RESULTS

VERIFIED ENGINEERING OUTCOMES

Grounded engineering outcomes built directly into the codebase and validated via chaos testing suites rather than speculative marketing numbers.

01
LOCAL-FIRST

Zero runtime dependency on cloud AI or external endpoints; all model inference executes on host silicon.

02
AIR-GAPPED

All services operate inside an isolated Docker bridge network with zero outbound internet egress.

03
AUDITABLE

Every raw crash log, FAISS vector distance, neural classification, and remediation action is persisted in MongoDB.

04
POLICY-GATED

Autonomous container actions strictly restricted by confidence (>= 0.85) and LOW blast radius risk thresholds.

05
DETERMINISTIC

Fixed enum-only action registry mapping directly to Dockerode calls, eliminating arbitrary command execution.

06
CHAOS-TESTABLE

Built-in failure injection harness actively verifying OOM, timeout, crash loop, and permission scenarios.

THE CLOSED LOOP

The complete autonomous lifecycle: capturing Docker failure signals, streaming through Kafka, computing local neural classifications, verifying safety gates, executing remediations, auditing state, and compiling offline learning buffers.

END-TO-END CLOSED LOOP REMEDIATION PIPELINE
FAILURE
│
▼
DOCKER EVENT
│
▼
EVENT CAPTURE
│
▼
KAFKA
│
▼
ORCHESTRATOR
│
▼
AI DIAGNOSIS
│
▼
SAFETY GATE
/ \
PASS FAIL
│ │
▼ ▼
REMEDIATE REVIEW
│
▼
AUDIT
│
▼
HISTORICAL
DATA
│
▼
OFFLINE LEARNING

Unbroken closed-loop architecture connecting raw failure detection to guarded execution and offline replay datasets.

HORIZONTAL SCROLL ON MOBILE ↔

WHAT I WAS SOLVING

“I designed a closed-loop remediation system where AI can recommend an action, but deterministic policy controls whether that action is allowed to execute.”

Autonomous systems in production cannot rely on probabilistic model outputs alone. True infrastructure safety demands decoupling recommendations from execution, bounding actuators to fixed APIs, and keeping the entire loop air-gapped.

ARCHITECTURAL CORE
“I designed a closed-loop remediation system where AI can recommend an action, but deterministic policy controls whether that action is allowed to execute.”

Autonomous systems in production cannot rely on probabilistic model outputs alone. True infrastructure safety demands decoupling recommendations from execution, bounding actuators to fixed APIs, and keeping the entire loop air-gapped.