compliance-evidence-collector

name	compliance-evidence-collector
description	Gather code, config, docs, and operational proof points for audits and internal compliance reviews. Use when assembling evidence for controls.

Compliance Evidence Collector

Overview

Gather code, config, docs, and operational proof points for audits and internal compliance reviews.

Core Workflow

1. Survey the relevant files, configs, runtime signals, or artifacts to identify the important components and boundaries.
2. Map the relationships, dependencies, or graph structure that explain how the system or corpus fits together.
3. Highlight missing links, risky assumptions, or ambiguous edges that affect understanding or change safety.
4. Return a concise map plus the next best checks or follow-up actions.

Deliver

• A structured map of components, dependencies, or graph relationships.
• The highest-risk gaps, missing links, or ambiguous edges.
• Concrete next checks or actions based on the mapped structure.

Guardrails

• Do not infer strong relationships without evidence from code, config, or runtime artifacts.
• Separate confirmed connections from plausible but unverified ones.
• Prefer a smaller high-confidence map over a speculative complete one.
• Do not invent metrics, policy decisions, customer commitments, or ownership that the inputs do not support.