Deliver complete Evidence directly through MCP with required nullable analysis profiles and immutable per-server delivery settings. Bind selected environments at construction and require typed cleanup outcomes with retained retry ownership. Remove test-only routing, duplicate session and snapshot metadata, producer-field repairs, and ambiguous provider arguments. Separate artifact byte identity from occurrence classification and retain typed source-map and partial native facts across CLI, MCP, and verifier consumers. BREAKING CHANGE: obsolete Evidence envelopes, session aliases, incomplete snapshots, and missing normalized producer facts are no longer accepted.
41 lines
2.2 KiB
Markdown
41 lines
2.2 KiB
Markdown
# Evidence, comparison, and verification workflows
|
|
|
|
Evidence-producing tools return the complete Evidence record directly in MCP
|
|
`structuredContent` and CLI JSON. Read `normalized_result` for operation data,
|
|
and cite `evidence_id` when another tool or your explanation needs a stable
|
|
reference. Preserve authority, limitations, coverage, and residual unknowns. If a result
|
|
is incomplete or paginated, continue only when the remaining data matters to
|
|
the task; do not fetch a bundle or resource merely to read a result already
|
|
returned inline. When complete `inspect_binary_layout` or
|
|
`analyze_javascript_application` Evidence is already retained, call
|
|
`inspect_analysis_view` for a summary, one section/symbol/module, or a stable
|
|
page instead of repeating the producer.
|
|
|
|
Use `record_unknown` to track unresolved questions in the user's investigation
|
|
and name the authority or environment still required. Supply supporting and
|
|
contradicting evidence IDs. It updates the session registry directly.
|
|
Use `update_unknown` with the current revision; reread after a stale revision
|
|
instead of retrying blindly. Only qualifying observed evidence can verify a
|
|
resolution.
|
|
|
|
Use comparisons with complete, compatible page sets when claiming equivalence
|
|
or absence:
|
|
|
|
- `compare_artifacts` compares inventory pages by occurrence path, content,
|
|
metadata, and graph relations.
|
|
- `compare_functions` compares explicit function Evidence, not fuzzy
|
|
whole-binary matches.
|
|
- `compare_bundles` compares canonical bundle membership and unknown history.
|
|
- `find_changed_behavior` combines existing comparisons; static differences
|
|
remain candidates, not causal proof.
|
|
- `build_call_path` needs explicit function dossiers from one artifact/provider;
|
|
an incomplete frontier makes absence unknown.
|
|
- `correlate_static_and_runtime` uses explicit mappings; matching patterns are
|
|
hypotheses, not causality.
|
|
- `verify_reconstruction` evaluates a finite typed specification. A pass covers
|
|
only declared comparable claims, not global equivalence.
|
|
|
|
Process captures are opt-in behavioral evidence, not a security sandbox. V3
|
|
captures cannot be upgraded to V4; rerun the original scenario. Distinguish root
|
|
exit from descendant settlement and require freshness when the task needs it.
|