Evidence the run may read
- Verified renewal and notice attributes
- Approved spend and utilization evidence
- Performance, risk, and owner context
Combine notice dates, utilization, spend, performance, and approved business needs into a reviewer-controlled renewal packet.
Search intent: AI agent for vendor contract renewal review
A supplier agreement enters its approved renewal review window.
procurement owner
Business, procurement, finance, and legal owners approve the renewal or termination position.
renewals decided before notice date (percent). Measure reviewed renewals with an approved decision before the verified notice deadline.
Each stage produces an artifact another stage can inspect. The final node is a person, not an autonomous write to an external system.
Validate and normalize the commercial renewal review inputs.
Produce the renewal evidence scorecard.
Produce the commercial option comparison.
Challenge the commercial renewal review result and prepare an approval packet.
Business, procurement, finance, and legal owners approve the renewal or termination position.
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.
workspace/procurement/commercial-renewal-review/inputs/**Read only the evidence attached to this workflow instance.
workspace/procurement/commercial-renewal-review/outputs/**Write drafts and evidence artifacts without modifying source records.
procurement:commercial-renewal-review:read-or-proposeInvoke only tools explicitly granted for this run; external writes remain gated.
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.
name: procurement-commercial-renewal-review
version: 0.1.0
entrypoint: agent:BlueprintAgent
expose:
public: false
composition:
planning: deterministic_dag
max_nodes: 6
max_parallel: 1
max_replans: 0Every material conclusion cites an input artifact or a scoped tool result from this run.
Options use approved assumptions and preserve legal interpretation and supplier commitment decisions for authorized owners.
The run stops at a proposal and records the human decision before any external side effect.
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.
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.
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.
{
"receipt_id": "rcpt_01J...",
"schema_version": 1,
"agent_name": "procurement-commercial-renewal-review",
"caller": "user:workflow-owner",
"task_id": "case_commercial_renewal_review",
"skill_name": "commercial_renewal_review",
"input_hash": "4d7c...9a2f",
"grant_ids": [
"grt_case_inputs",
"grt_tool_propose"
],
"status": "ok",
"result_preview": "Output prepared: Renewal evidence scorecard. Human decision remains separate.",
"elapsed_ms": 4218
}Normalize a purchase request, identify missing business and approval context, and route it under the approved buying policy.
Translate an approved sourcing need into neutral requirements, research questions, and a reviewer-controlled supplier discovery plan.
Compare supplier responses against approved requirements and produce an evidence-linked matrix without choosing the winner.
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.