Evidence the run may read
- Approved matter activity and notes
- Deadline and decision register
- Audience and privilege instructions
production blueprint · legal
Legal matter status summary agent blueprint.
Consolidate approved matter activity, deadlines, decisions, and open questions into a counsel-reviewed status packet.
Search intent: AI agent for legal matter summaries
Published by a2a cloudProduct-source methodology →
01 · the contract
Start from a bounded job, not a blank chat box.
trigger
A matter reaches a scheduled status or reporting checkpoint.
owner
qualified legal reviewer
agent stops at
Responsible counsel approves audience, privilege treatment, and distribution.
KPI · decrease
matter status preparation time (minutes). Measure reporting checkpoint to counsel-approved status packet.
outputs
Artifacts the run must produce
- Chronological status summary
- Deadline and owner table
- Decisions and unresolved questions
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 legal matter status summary inputs.
- 02
matter historian
Produce the chronological status summary.
- 03
deadline compiler
Produce the deadline and owner table.
- 04
responsible counsel reviewer
Challenge the legal matter status summary result and prepare an approval packet.
- 05
qualified legal reviewer
Responsible counsel approves audience, privilege treatment, and distribution.
intake→ validated input packet →matter-historian
matter-historian→ Chronological status summary →deadline-compiler
deadline-compiler→ Deadline and owner table →responsible-counsel-reviewer
responsible-counsel-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/legal/matter-status-summary/inputs/**Read only the evidence attached to this workflow instance.
case outputs
workspace/legal/matter-status-summary/outputs/**Write drafts and evidence artifacts without modifying source records.
approved tools
legal:matter-status-summary: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: legal-matter-status-summary
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
The summary cites matter sources, keeps legal advice attributed, and follows audience restrictions.
The summary cites matter sources, keeps legal advice attributed, and follows audience restrictions.
- 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.
Matter records conflict or privilege and distribution boundaries are not specified.
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": "legal-matter-status-summary",
"caller": "user:workflow-owner",
"task_id": "case_matter_status_summary",
"skill_name": "matter_status_summary",
"input_hash": "4d7c...9a2f",
"grant_ids": [
"grt_case_inputs",
"grt_tool_propose"
],
"status": "ok",
"result_preview": "Output prepared: Chronological status summary. Human decision remains separate.",
"elapsed_ms": 4218
}related blueprints
Keep the operating model consistent.
Legal
Contract intake triage
Normalize a contract request, identify document and owner gaps, and route it under the approved legal intake policy.
Legal
NDA deviation review
Compare an NDA with an approved template and prepare a clause-level deviation packet for counsel.
Legal
Contract clause extraction
Extract specified clauses and attributes with source locations and confidence for a legal reviewer to verify.
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.