Aegis Gateway 2.0

Evidence: Aegis 2.0 on stock Apache Knox 3.0.0

This directory retains incomplete historical evidence from an earlier Knox cold-install exercise. Its classification is recorded-unattested, not verified-current or complete verified-historical evidence. The exact capture date, candidate commit/tree, raw request and process logs, jar hashes, and Knox archive SHA-512 value were not retained here.

Files actually retained

No raw K1 to K7 or V1 to V7 request log, VRP log, Knox gateway log, Knox audit excerpt, or Aegis console excerpt is retained in this directory. The prose below records observations but cannot substitute for those missing artifacts.

Historical setup and reported observations

Knox, its providers, and the Aegis jars were reported as real in these runs. The backend behind Aegis was a test MCP server on loopback (engine-mcp in aegis.json), so the exercise concerned the Knox integration path, not a real engine behind it. Automated adopter runs are described separately in examples/adopters.

Provenance: which code this was captured against

The retained files came from jars as they stood before extension-hook work and later changes. The following changes were subsequently recorded in modules that Knox loads from ext/:

Change Module
GovernanceHook rewritten for all four operations, HookRunner, HookBinding aegis-engine
DecisionListener.Event gained a Span component aegis-engine
Built-in remote and sql-readonly hook types aegis-config
tracing.otlp section aegis-config
OtlpSpanExporter, now its own jar that aegis-config links against aegis-observability-otlp (new)
sources[].trust and the state provider SPI aegis-config

Knox integration, packaging, identity, and gateway code have changed further since this cold-install capture. Current tests are executable assertions only; without retained candidate-bound output they do not make this historical directory current evidence.

The current install uses five base jars or the knox-bundle jar; see KNOX-EXTENSION.md. A new cold-install capture must use that layout, record exact commands and versions, and retain request, process, and verification output with a candidate-bound SHA-256 manifest. This capture should be repeated before a release and is tracked in ROADMAP.md.