EXPERIMENTAL v0.2.1 SOURCE · LOCAL INVESTIGATION CORE
Evidence before action.
Boundaries before AI.
An RBAC-change event starts an investigation. The model proposes the next question. Deterministic code decides what it is allowed to ask.
Source: experimental 0.2.1. The only published release is v0.2.0; publishing v0.2.1 is a separate maintainer action.
事件觸發調查。模型提出問題,程式碼守住權限、預算與證據邊界。
4read-only capabilities
8replay scenarios
6acceptance gates
0infrastructure write tools
01 / THE AUTHORITY BOUNDARY
The model proposes.
The runtime permits.
Policy is never a prompt suggestion. Every model request passes a fixed registry, exact resource scope and a pre-call budget.
01Event & policy
Validate. Claim once.
Load trusted limits.
02Bounded reasoning
Propose a typed action.
Reserve before calling.
03Read-only evidence
Allowlisted reads only.
Hash and persist evidence.
04Grounded result
Validate every reference.
Persist. Terminate.
⊘No shell. No arbitrary HTTP or SQL. No kubectl passthrough. No remediation. Evidence text cannot grant new authority.
02 / EXECUTABLE ACCEPTANCE
A failed investigation
can prove a control works.
A replay passes when the expected boundary holds. That does not mean a real environment is secure.
Eight synthetic scenarios and their expected outcomes| Scenario | Boundary exercised | Expected investigation |
| S01 | Privilege increase without approval | Confirmed suspicious |
| S02 | Approval matches actor, resource and change | Likely benign |
| S03 | Required evidence is unavailable | Insufficient evidence |
| S04 | Injection text + simulated hostile action | Investigation failed safely |
| S05 | Duplicate delivery | Existing result, no extra calls |
| S06 | Hard budget exhausted | Inconclusive |
| S07 | Unregistered capability requested | Investigation failed safely |
| S08 | Finding cites nonexistent evidence | Investigation failed safely |
03 / START LOCALLY
One checkout.
No cloud credentials.
Python 3.11+. Install dependencies once, then run every replay offline. Inspect the persisted evidence and audit alongside the result. Missing evidence never silently becomes benign.
.[dev] includes the offline HTTP mocks. Paid model calls require an explicit provider invocation and still use fixture evidence; see the opt-in model setup.
Full setup and exit codes ↗
git clone https://github.com/trionnemesis/AgenticDef.git
cd AgenticDef
python -m venv .venv
source .venv/bin/activate
pip install -e '.[dev]'
python -m pytest -q
replay scenarios --all
A fresh temporary output directory is created for each run. Output includes statuses, evidence references, budgets and terminal state. Reusing an explicit output directory returns saved terminal results.
04 / HONEST STATUS
Proof you can inspect.
Limits you can see.
Follow-ups #4–#8 and tracker #9 are closed. Both evaluation decisions are made: an offline evaluation layer outside the runtime grades semantic correctness against a deterministic RBAC oracle (#20, #21), and an opt-in, capped live smoke protocol is committed but not yet run (#22). The v0.3 decision gate is still open. Read the roadmap ↗
EXERCISED OFFLINEReplay & control boundaries
Offline regressions and deterministic S01–S08 replay check contracts, scope, grounding, budgets, cancellation and duplicates. Scripted HTTP mocks also run S01/S02 through the shared core and evaluator; an inverted verdict fails the status/risk checks. An offline evaluation layer compares baselines against a deterministic RBAC oracle on seeded cases.
Inspect acceptance evidence ↗NOT LIVE-VALIDATEDReal model accuracy
The Anthropic adapter is tested with mock transport. A metered smoke protocol (claude-sonnet-5-5, 20 synthetic cases, at most US$10) is committed but has not been run. Actual API calls, model behavior on hostile evidence and live detection accuracy remain unverified.
Read the validation boundary ↗OUT OF v0.2 SCOPECloud & remediation
No GKE dispatch, live cluster evidence, production SOC, multi-agent orchestration or infrastructure mutation is implemented.
Explore the architecture ↗