Evidence the run may read
- Vendor requirement list
- Received evidence and expiry data
- Risk and follow-up policy
production blueprint · compliance & audit
Vendor compliance evidence follow-up agent blueprint.
Track required vendor artifacts, expiry, gaps, and approved follow-ups without asserting control coverage prematurely.
Search intent: AI agent for vendor compliance evidence
Published by a2a cloudProduct-source methodology →
01 · the contract
Start from a bounded job, not a blank chat box.
trigger
A vendor evidence review reaches a due date or detects a gap.
owner
compliance owner
agent stops at
The vendor risk owner approves outreach, exception, or risk disposition.
KPI · decrease
overdue vendor evidence (items). Count required artifacts past due without approved disposition.
outputs
Artifacts the run must produce
- Evidence completeness table
- Gap and expiry queue
- Follow-up draft
02 · topology
Small specialists. Named handoffs. One accountable decision.
Each stage produces an artifact another stage can inspect. The final node is a person, not an autonomous write to an external system.
- 01
intake
Validate and normalize the vendor compliance evidence follow-up inputs.
- 02
evidence inventory analyst
Produce the evidence completeness table.
- 03
expiry and gap reviewer
Produce the gap and expiry queue.
- 04
vendor risk reviewer
Challenge the vendor compliance evidence follow-up result and prepare an approval packet.
- 05
compliance owner
The vendor risk owner approves outreach, exception, or risk disposition.
intake→ validated input packet →evidence-inventory-analyst
evidence-inventory-analyst→ Evidence completeness table →expiry-and-gap-reviewer
expiry-and-gap-reviewer→ Gap and expiry queue →vendor-risk-reviewer
vendor-risk-reviewer→ approval packet with evidence references →human-approver
03 · authority
Grant the run only what this case needs.
Source material is read-only. Drafts land in a case-specific output path. Tools may read or propose; the human gate owns the external write.
case inputs
workspace/compliance/vendor-evidence-follow-up/inputs/**Read only the evidence attached to this workflow instance.
case outputs
workspace/compliance/vendor-evidence-follow-up/outputs/**Write drafts and evidence artifacts without modifying source records.
approved tools
compliance:vendor-evidence-follow-up:read-or-proposeInvoke only tools explicitly granted for this run; external writes remain gated.
04 · implementation
A private, bounded starting manifest.
The blueprint starts private, caps its DAG, disables replanning, and exposes no public endpoint. Add only the tools and data adapters this workflow has approved.
a2a.yamlsafe starting point
name: compliance-vendor-evidence-follow-up
version: 0.1.0
entrypoint: agent:BlueprintAgent
expose:
public: false
composition:
planning: deterministic_dag
max_nodes: 6
max_parallel: 1
max_replans: 005 · acceptance test
Pass only with evidence.
- 01
Evidence traceability
Every material conclusion cites an input artifact or a scoped tool result from this run.
- 02
Coverage is marked only when evidence is current, applicable, and reviewed; missing items remain explicit.
Coverage is marked only when evidence is current, applicable, and reviewed; missing items remain explicit.
- 03
Approval boundary
The run stops at a proposal and records the human decision before any external side effect.
failure containment
Stop small. Preserve the evidence.
Vendor documents cannot be tied to the contracted entity, service, or review period.
Containment: Return a partial result with unresolved items; do not broaden scope or perform an external write.
Operator: Attach the missing evidence, narrow the brief, or explicitly approve a new scoped run.
A required input or tool grant is unavailable.
Containment: Stop the affected branch and preserve completed artifacts in the case output workspace.
Operator: Grant only the missing resource or continue with that branch marked out of scope.
06 · proof
Sign the run facts. Keep money in the billing ledger.
Current platform receipts sign caller identity or classification, skill, bounded input evidence, verified grant IDs when present, outcome or result preview, and timing. Optional file, tool, artifact, handoff, evaluation, and review fields require separate instrumentation and are not populated by default. Price, fees, payouts, and later human approvals remain separate platform records.
The example uses only fields populated by the current platform sealing paths. It is illustrative, not a record of a real customer run.
ExecutionReceipt · selected fieldsEd25519 token
{
"receipt_id": "rcpt_01J...",
"schema_version": 1,
"agent_name": "compliance-vendor-evidence-follow-up",
"caller": "user:workflow-owner",
"task_id": "case_vendor_evidence_follow_up",
"skill_name": "vendor_evidence_follow_up",
"input_hash": "4d7c...9a2f",
"grant_ids": [
"grt_case_inputs",
"grt_tool_propose"
],
"status": "ok",
"result_preview": "Output prepared: Evidence completeness table. Human decision remains separate.",
"elapsed_ms": 4218
}related blueprints
Keep the operating model consistent.
Compliance & Audit
Control evidence collection
Map a control request to approved sources, collect a bounded evidence packet, and flag missing attestations.
Compliance & Audit
Audit request response
Translate an audit request into attributes, sources, owners, and an approved response packet without over-answering scope.
Compliance & Audit
Policy-to-control mapping
Map approved policy statements to controls and evidence expectations, highlighting unsupported or orphaned requirements.
put the pattern to work
Start private. Scope the authority. Require the decision.
Deploy the workflow as a bounded internal agent, verify its outputs and the receipt fields actually emitted, then expand only the scopes your acceptance test proves it needs.