You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Real Amazon Bedrock wiring: Titan Text Embeddings V2 (1024-dim, matching VECTOR(1024) schema) in the Correlation Agent; Claude-on-Bedrock reasoning with deterministic precedent-replay fallback in the Remediation Agent
Genuinely interruptible remediation loop: each invocation drives one step through proposed → executing → executed with a simulated execution window; a kill mid-step leaves executing durably in CockroachDB and the next cold invocation re-runs that exact step
Cross-platform chaos_kill.py (psutil) + scripts/chaos_demo.ps1 for Windows; fixed make chaos-demo to actually kill the process doing the work
Seeded historical incidents now include their remediation step history, so precedent replay has real precedent
agents/query_agent.py — a real client of the CockroachDB Cloud Managed MCP Server (official mcp SDK, streamable HTTP), called by the running app itself via GET /api/v1/incidents/open and the Gradio UI's "Ask via MCP" panel, not only by Claude Code during development (ADR 003 amended). This and Distributed Vector Indexing are Continuum's two CockroachDB tools; ccloud CLI was evaluated and cut (ADR 004 resolution, ADR 006)
Real integration test (tests/integration/test_recovery_e2e.py) exercising the actual kill-and-recover cycle against a live CockroachDB instance — previously a stub that always skipped itself
CI now provisions an ephemeral single-node CockroachDB container so the integration suite runs on every push, not only when a developer happens to have a cluster handy
Unit test suite grew from 5 to 42 tests (one file per agent/module: memory, correlation, remediation, query agent, API, observability) — coverage 60% → 100%; CI gate raised 60% → 90%
.github/workflows/release.yml — tags matching v*.*.* cut a GitHub Release with notes pulled from this file
docs/adr/007-eu-central-1-region.md — documents the deployment region and cross-region inference profile choice
AWS region us-east-1 → eu-central-1; Bedrock reasoning model to eu.anthropic.claude-sonnet-4-5-20250929-v1:0 (EU cross-region inference profile) — kept in sync across .env.example, config.py, infra/template.yaml (ADR 007)
infra/template.yaml Lambda runtime python3.12 → python3.14, matching the rest of the codebase
CLAUDE.md expanded (Key Commands, Architecture, Testing Strategy, Deployment, Judging Criteria) to match sibling-repo conventions
Fixed
config.Settings crashed at import — and thus the whole app failed to start — for anyone with ordinary AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEY in their environment (pydantic-settings defaults to extra="forbid", and those two vars were never declared fields). Now extra="ignore"
infra/template.yaml targeted a Lambda runtime (3.12) that couldn't run this codebase's 3.14-only dependencies
Removed
docs/continuum-DEPLOY.md — an exact duplicate of docs/DEPLOY.md
Hugging Face Spaces deployment: README frontmatter, .github/workflows/sync-to-hf-space.yml, docs/DEPLOY.md — free, cardless public hosting for the Gradio demo UI, replacing the Railway/Vercel/Next.js stack considered and rejected for this project (no frontend framework needed, judged surface is the CockroachDB memory layer)
Planned (before submission)
Demo video recording per docs/DEMO_RUNBOOK.md
Deploy orchestrator to AWS Lambda (SAM) and confirm the Hugging Face Space is live
Complete the docs/SUBMISSION.md checklist end to end