Open-source AI Security Operations Center: alert fusion, LLM-agent triage, MITRE ATT&CK investigation, and a replayable decision ledger for every agent step. Self-hostable, runs with no API keys, MIT licensed. Ships an MCP server for Claude, Cursor and Continue.
Python agentic-aiai-securityalert-triageblue-teamcybersecuritydetection-engineeringincident-responselanggraphllm-agentsmcpmitre-attackmodel-context-protocolpurple-teamsecurity-operationsself-hostedsiemsoarsocthreat-detectionthreat-intelligence
fix(install): a full Docker VM said zookeeper was broken (#1102)
Beenu Arora4d09ab6b5e60
diff --git a/Makefile b/Makefileindex b4362346a..85e51b521 100644--- a/Makefile+++ b/Makefile@@ -282,6 +282,15 @@ _wait:echo ""; \echo "These services are not running: $$broken"; \for s in $$broken; do echo " docker compose logs $$s | tail -30"; done; \+ if $(COMPOSE) logs --tail 80 $$broken 2>/dev/null | grep -qiE "no space left on device|disk quota exceeded"; then \+ echo ""; \+ echo " Those containers died because the Docker VM ran out of disk,"; \+ echo " not because anything is wrong with them. CORE needs ~20GB."; \+ echo ""; \+ echo " docker system prune -af --volumes"; \+ echo ""; \+ echo " then 'make up' again. 'make doctor' reports free space up front."; \+ fi; \echo "Run 'make doctor' for the full picture."; \exit 1; \fi; \diff --git a/PARITY_PROGRESS.md b/PARITY_PROGRESS.mdindex c0b5cbe15..bbad07ae3 100644--- a/PARITY_PROGRESS.md+++ b/PARITY_PROGRESS.md@@ -562,3 +562,31 @@ scanned files changed**. The workflow pins the semgrep binary and not therule packs, so the ratchet compares against a moving target. Ceiling heldat 104/40 with the reasoning written in; pinning is[#1099](https://github.com/beenuar/AiSOC/issues/1099).++## First run, measured on a bare clone (2026-10-02)++Everything below came from a clean-room install: a fresh worktree off+`main`, following the README exactly, on a host that already had a+Postgres on 5432 and an Ollama on 11434.++| Was | Now |+|---|---|+| `make up` **refused to start** on a port conflict and said to edit YAML | Picks a free port, names what held it, moves `AISOC_CONSOLE_URL` with it |+| `make smoke` probed a hardcoded `:3000` and read a connection failure as **"an uncredentialed caller was served"** | Uses the real console URL, and `000` is a skip |+| `make doctor` on a never-started clone showed **22 red failures** | Says nothing is running yet and names `make up` |+| A container dying of a full Docker VM reported as **"zookeeper is not running"** | Names the disk and prints the prune command |+| A new tenant landed on an all-zero dashboard | Lands on a setup wizard derived from its own data |+| No way to see the product work without credentials | Five scenarios through the **real ingest path**, labelled, which do not mark setup complete |++**64 seconds** from `git clone` to a working console with three ports+remapped; `make smoke` 10/10; sample data producing five distinct alerts+from low to critical with differing AI verdicts.++### The through-line++Four of these were diagnostics that named the wrong thing. A port+conflict reported as "edit docker-compose.yml", a dead port reported as+an authentication hole, an unstarted stack reported as eight broken+services, and a full disk reported as a Zookeeper fault. In each case the+information needed was already on the machine and the message did not+carry it.