Evidence the run may read
- Candidate-provided application
- Role-specific required fields
- Consent, retention, and accommodation workflow
production blueprint · people operations
Candidate intake completeness agent blueprint.
Validate application completeness and scheduling prerequisites without ranking candidates or inferring suitability.
Search intent: AI agent for recruiting application intake
Published by a2a cloudProduct-source methodology →
01 · the contract
Start from a bounded job, not a blank chat box.
trigger
A candidate submits an application for an approved role.
owner
people operations owner
agent stops at
A recruiting professional approves communication and all progression or rejection decisions.
KPI · increase
applications ready for human review (percent). Measure consented applications reaching recruiters with required administrative fields complete.
outputs
Artifacts the run must produce
- Completeness checklist
- Candidate clarification draft
- Restricted-data and accommodation routing flags
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 candidate intake completeness inputs.
- 02
application validator
Produce the completeness checklist.
- 03
consent and routing checker
Produce the candidate clarification draft.
- 04
recruiting operations reviewer
Challenge the candidate intake completeness result and prepare an approval packet.
- 05
people operations owner
A recruiting professional approves communication and all progression or rejection decisions.
intake→ validated input packet →application-validator
application-validator→ Completeness checklist →consent-and-routing-checker
consent-and-routing-checker→ Candidate clarification draft →recruiting-operations-reviewer
recruiting-operations-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/people-ops/candidate-intake-completeness/inputs/**Read only the evidence attached to this workflow instance.
case outputs
workspace/people-ops/candidate-intake-completeness/outputs/**Write drafts and evidence artifacts without modifying source records.
approved tools
people-ops:candidate-intake-completeness: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: people-ops-candidate-intake-completeness
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 workflow checks only administrative completeness and never scores, ranks, or infers protected or job-fit attributes.
The workflow checks only administrative completeness and never scores, ranks, or infers protected or job-fit attributes.
- 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.
Consent, role identity, required application elements, or accommodation routing cannot be established.
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": "people-ops-candidate-intake-completeness",
"caller": "user:workflow-owner",
"task_id": "case_candidate_intake_completeness",
"skill_name": "candidate_intake_completeness",
"input_hash": "4d7c...9a2f",
"grant_ids": [
"grt_case_inputs",
"grt_tool_propose"
],
"status": "ok",
"result_preview": "Output prepared: Completeness checklist. Human decision remains separate.",
"elapsed_ms": 4218
}related blueprints
Keep the operating model consistent.
People Operations
Role description review
Check a proposed role description for clarity, internal consistency, approved requirements, and accessible language before publication.
People Operations
Interview loop packet
Assemble an approved competency plan, interviewer assignments, and structured evidence forms for a recruiting coordinator.
People Operations
Interview evidence summary
Organize submitted interviewer evidence by approved competency and surface missing or contradictory observations without recommending a hire.
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.