docs: record ECC Tools fleet evidence consumption

This commit is contained in:
Affaan Mustafa
2026-05-16 01:38:11 -04:00
parent 10b1222fc8
commit a1cf97e3f2
7 changed files with 34 additions and 19 deletions

View File

@@ -95,6 +95,10 @@ AgentShield is already more than a static lint tool:
`agentshield evidence-pack fleet <dirs...> [--json]` aggregates multiple
inspected bundles into ready, security-blocker, policy-review,
baseline-regression, supply-chain-review, and invalid routes.
- ECC-Tools now consumes that fleet primitive in hosted security review:
`agentshield-evidence/fleet-summary.json` routes invalid packs, security
blockers, policy reviews, baseline regressions, and supply-chain reviews into
hosted findings.
May 16 update: AgentShield PR #87 merged as
`26bb44650663816d07180e0d20c1895e431a326c`. It classifies installed Claude
@@ -114,8 +118,9 @@ the inspect path, aggregates finding, policy, baseline, supply-chain, and
remediation totals, and assigns each pack to a deterministic fleet route.
The next iteration after fleet routing should not be "add more regex rules" by
default. The higher leverage move is to wire the new fleet summaries into
ECC-Tools follow-up routing and cross-harness policy integration.
default. ECC-Tools follow-up routing now consumes fleet summaries; the higher
leverage move is cross-harness policy integration plus operator-facing review UX
for routed fleet findings.
## Enterprise Gaps