Skip to content

Document agent-run triage as the evidence-sink phase of 007's Zero Trust roadmap - #34

Closed
PhysShell wants to merge 2 commits into
mainfrom
claude/zero-trust-framework-007-b0vgrw
Closed

PhysShell wants to merge 2 commits into
mainfrom
claude/zero-trust-framework-007-b0vgrw

Conversation

@PhysShell

Copy link
Copy Markdown
Owner

Summary

Adds docs/agent-run-triage.md: the "evidence sink" phase of 007's Zero Trust
roadmap (007/docs/zero-trust-framework.md). 007 orchestrates agent runs and
will (per its own roadmap) emit a structured audit trail — capability-manifest
violations, gate verdicts, a tamper-evident hash chain over each run. Something
has to look at that evidence and separate noise from a real incident; that's
this repo's job, not 007's, for the same reason OwnAudit doesn't run its own
detectors (P-024 in Own.NET: "оркестратор, не анализатор").

Reuses existing machinery instead of building a new pipeline:

  • The confirmed / static-only / runtime-only triage pattern from
    runtime-contract.md maps directly onto policy events (a rule that fires as
    intended → confirmed; an action that succeeded but matched no rule → a
    policy gap, i.e. the manifest's blind spot).
  • The rule → verdict methodology from audit-data-leverage.md (findings
    concentrate in a handful of rules) applies the same way to gate/policy rules.

Explicitly scoped as ingest-and-report only: no enforcement (that's
007 + Sandboy, at the process boundary, before the action happens) and no
automated disposition (containment/rerun/escalate stays a human call, per the
same framework this traces back to).

A follow-up commit adds: verifying 007's run-record provenance hash chain
before trusting any ingested evidence (the same reflex already applied to
runtime.json inputs), and concrete named instances of the
policy-violation-confirmed bucket so the triage model isn't purely abstract —
including flagging an agent editing its own gate config as always requiring
human review, even when the step itself passed.

README.md gets one row in the existing "Where things live" table, matching
the style of the fix-arm.md/leakfix-mine.md entries (status: design).

Trigger to actually build this: once 007's Phase 1 (structured per-run
capability events) lands — this doc is explicit that it's gated on that data
existing, not something to build ahead of it.

Test plan

  • Docs-only change; no build/test surface affected.
  • Reviewer sanity-check on the triage-bucket names and whether they'll
    still make sense once 007 actually emits events in Phase 1.

Generated by Claude Code

claude added 2 commits July 5, 2026 07:12
…ust roadmap

Adds docs/agent-run-triage.md: reuses the existing confirmed/static-only/
runtime-only triage pattern (runtime-contract.md) and rule-to-verdict
methodology (audit-data-leverage.md) for a new evidence source — 007's
structured per-run audit trail — instead of building a separate pipeline.
Scopes it explicitly as ingest-and-report only: enforcement stays with
007+Sandboy, disposition stays human, per the same orchestrator-not-analyzer
charter already codified for the security profile (P-024 in Own.NET).
…un triage

Ingest adapter's first move should be verifying 007's run-record hash chain
before trusting any of it, same reflex already applied to runtime.json inputs.
Names concrete instances of the policy-violation-confirmed bucket so the
triage buckets aren't purely abstract, and flags an agent editing its own
gate config as always requiring human review, even when the step itself passed.
@coderabbitai

coderabbitai Bot commented Jul 5, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@PhysShell, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 36 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 6fdd44cd-6e77-4aef-a4dc-4705c8c22b67

📥 Commits

Reviewing files that changed from the base of the PR and between 540aa06 and 98f11be.

📒 Files selected for processing (2)
  • README.md
  • docs/agent-run-triage.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/zero-trust-framework-007-b0vgrw

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Copy link
Copy Markdown
Owner Author

Консолидировано в #38 (docs/agent-run-triage.md вошёл; поля идентичности run'а корректно отнесены к Phase 1 — сегодняшний RunMeta в 007 их не содержит). Закрываю в пользу единого PR.


Generated by Claude Code

@PhysShell PhysShell closed this Jul 8, 2026
PhysShell added a commit that referenced this pull request Jul 8, 2026
…n-1wat02

docs: consolidated documentation PRs (#34–#37) — validated & corrected
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants