blitzstrike 1.0.52 → 1.0.57

package/docs/AUTONOMY.md

@@ -0,0 +1,147 @@
+# Blitz Strike — Autonomous Security Research & Verification Engine
+
+Blitz Strike's autonomous layer turns the three-tier methodology (BLITZ →
+EAGLE-EYE → STRIKE) into a **self-driving security research engine**. Give it a
+target and a scope; it plans, executes, verifies, reviews, and reports — without
+babysitting.
+
+This document describes the autonomous engine added on top of the existing
+deterministic core. The core (`blitz_scan`, `eagle_eye2`, `strike_verify`, the
+taint engine, live recon) is unchanged and always available.
+
+---
+
+## 1. Design principles
+
+- **Detection is not proof.** A scan hit is a hypothesis; only live verification
+  (or an adversarial review) turns it into a finding.
+- **A hypothesis is not a finding.** They are separate states that never conflate.
+- **AI reasoning is not evidence.** Every finding carries deterministic evidence
+  (marker reflection, negative control, source→sink trace).
+- **The LLM never controls policy.** Routing is
+  `LLM → Planner → Policy engine → Task executor → Tool`, never an arbitrary
+  shell call. The policy engine enforces scope, risk, and budgets.
+- **Deterministic by default.** No model is called unless a provider is
+  explicitly configured (§Model routing).
+
+---
+
+## 2. Components
+
+| Component | Module | Role |
+|---|---|---|
+| Mission State | `src/mission/state.ts` | Persistent, resumable missions (`~/.blitzstrike/missions/<id>.json`) |
+| Task Graph | `src/mission/taskgraph.ts` | Dependency-aware, parallel scheduler |
+| Mission Control | `src/mission/control.ts` | The autonomous loop (observe → act → replan → terminate) |
+| Specialized Agents | `src/agents.ts` | 13 deterministic agents (recon, source, auth, validator, reviewer, browser, …) |
+| Security Graph | `src/mission/graph.ts` | Shared world model (targets, sinks, endpoints, chains) |
+| Hypothesis Engine | `src/mission/hypothesis.ts` | observation → hypothesis → validated finding / rejected |
+| Adaptive Planner | `src/mission/planner.ts` | Evidence-driven next actions (SSRF → metadata, LFI → logs, …) |
+| Escalation Graph | `src/mission/planner.ts` | The 57 chains integrated into the world model |
+| Coverage Scheduler | `src/mission/coverage.ts` | Auto-generates tasks for under-explored dimensions |
+| Failure Recovery | `src/mission/recovery.ts` | Diagnose → retry / alternative / record — never repeat a mistake |
+| Adversarial Reviewer | `src/mission/reviewer.ts` | Ten §questions → CONFIRMED / REJECTED / NEEDS_MORE_EVIDENCE |
+| Browser Agent | `src/browser-agent.ts` | Session-based real browser (login flows, DOM issues) |
+| Model Router | `src/mission/router.ts` | Task → model tier (pure routing, deterministic default) |
+| Budget Controller | `src/mission/budget.ts` | time / tasks / requests / tokens / cost + per-task budget |
+| Termination Engine | `src/mission/termination.ts` | Seven traceable termination reasons |
+| Cross-agent Memory | `src/mission/memory.ts` | Persist findings + failed approaches (with `future_policy`) |
+| Benchmark | `src/mission/benchmark.ts` | Full-engine precision / recall / F1 against a labelled corpus |
+
+---
+
+## 3. Mission lifecycle
+
+```
+           ┌──────────────────────────────────────────────┐
+           │                 Mission Control              │
+ target ─▶ │  OBSERVE → schedule → execute → collect      │
+  scope  ─▶ │     ↓                                       │
+           │  REPLAN (validator → reviewer → reporter,    │
+           │          coverage gaps)                      │
+           │     ↓                                       │
+           │  terminate (traceable reason)                │
+           └──────────────────────────────────────────────┘
+                        │            │
+            Security Graph (world model)  ←→  Hypothesis Engine
+                        │
+            Cross-agent Memory (findings + failed approaches)
+```
+
+A mission is a state machine persisted to disk after every step, so it survives
+a process restart and can be resumed with `blitz mission resume <id>`.
+
+### Termination reasons (§Termination)
+
+`objective_complete` · `no_progress` · `max_iterations` · `budget_exhausted` ·
+`user_interrupted` · `safety_violation` · `scope_violation`. Each is recorded in
+the mission's `decision_log` with a detail string.
+
+---
+
+## 4. Safety invariants (never bypassed)
+
+- **Scope gate** — a URL target requires an authorized scope before any agent
+  runs; local source paths are always allowed.
+- **No raw secrets persisted** — `redactSecrets` runs before anything is written.
+- **Negative controls** — a finding is only confirmed when the control stays inert.
+- **No destructive actions** — the engine is read-only / probe-only.
+- **Deterministic by default** — no model call unless configured.
+
+---
+
+## 5. CLI
+
+```bash
+# Run an autonomous mission against a source tree
+blitzstrike mission ./path/to/source --mode source
+
+# Run an autonomous mission against a live URL (requires --scope)
+blitzstrike mission https://example.com --mode web --scope example.com
+
+# Resume / inspect a mission
+blitzstrike mission resume <mission-id>
+blitzstrike mission status <mission-id>
+blitzstrike mission list
+
+# Run the autonomous benchmark (--full for the whole 101-fixture corpus)
+blitzstrike benchmark --full
+```
+
+---
+
+## 6. MCP (autonomous mission mode)
+
+The autonomous layer is exposed alongside the low-level tools:
+
+| Tool | Purpose |
+|---|---|
+| `mission_start` | Start an autonomous mission (target + mode + scope) |
+| `mission_status` | Full mission state (tasks, hypotheses, graph, coverage) |
+| `mission_resume` | Resume an interrupted mission |
+| `mission_stop` | Stop a running mission |
+| `mission_list` | List persisted missions |
+| `browser_agent` | Session-based browser ops (open/click/type/evaluate/…) |
+
+Low-level tools (`blitz_scan`, `eagle_eye2`, `strike_verify`, `run_engagement`,
+…) remain available for manual, step-by-step engagements.
+
+---
+
+## 7. No-babysitting
+
+The autonomous mission handles its own recovery, strategy changes, delegation,
+new-task creation, surface discovery, verification, false-positive rejection,
+and coverage gaps. Human input is only needed for: initial authorization/scope,
+high-risk approval when policy requires it, and (optional) final review.
+
+---
+
+## 8. Examples
+
+See `examples/` for runnable scripts. The shortest path:
+
+```bash
+npx blitzstrike benchmark --full     # measure the engine
+npx blitzstrike mission ./src --mode source   # autonomous source audit
+```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "blitzstrike",
-  "version": "1.0.52",
+  "version": "1.0.57",
   "description": "Blitz Strike — a universal MCP security-audit toolbelt. BLITZ sweeps the attack surface, EAGLE-EYE traces source-to-sink, STRIKE verifies live. 57 attack chains, 130-tool catalog, intelligence data layer. One server, every agent.",
   "type": "module",
   "bin": {