Subcontractor Compliance Automation Agent Brief

Role: Principal Construction Systems Architect specializing in autonomous document workflows and subcontractor risk governance.

Context

• Enterprise General Contractor: {{contractor_company}}
• Managed Jobsite Footprint: {{jobsite_portfolio}}
• Regulatory and Safety Baselines: {{compliance_standards}}
• Target Agent Framework: {{target_agent_platform}}
• Core Record System: {{legacy_erp_system}}
• Escalation Protocol: {{exception_handling_policy}}

Task

Author a comprehensive Subcontractor Compliance Agent Technical Specification Brief that outlines the operational architecture, parsing rules, and validation triggers for an autonomous agent handling trade contractor credentialing for {{contractor_company}} across {{jobsite_portfolio}}.

Method

1. Analyze the ingestion pathways for trade partner documents across {{jobsite_portfolio}}, mapping inbound formats into {{target_agent_platform}}.
2. Define structured data extraction schemas for certificates of insurance (COI), OSHA forms, and trade licenses per {{compliance_standards}}.
3. Establish validation routines comparing extracted policy limits and expiration dates against {{contractor_company}} master service agreements.
4. Construct bidirectional synchronization logic between the agent platform and {{legacy_erp_system}}.
5. Design autonomous notification sequences for impending document expirations and deficient coverage thresholds.
6. Detail explicit escalation pathways and review queues in alignment with {{exception_handling_policy}}.
7. Formulate audit logging standards to ensure tamper-proof compliance tracking for project stakeholders.

Constraints

• The brief MUST specify deterministic confidence scores for passing documents versus flagging for manual superintendent review.
• The agent MUST NOT write unvalidated insurance overrides directly to {{legacy_erp_system}}.
• Limit architectural diagrams to concise text-based ASCII flow representations.
• Keep the specification deliverable under 1,000 words focusing purely on functional execution.

Output format

Present the specification as a structured operational brief with the following exact sections:

1. Executive Architecture Summary (max 150 words)
2. Ingestion & Extraction Pipeline Specifications
3. Integration & Sync Contract (mapping {{target_agent_platform}} to {{legacy_erp_system}})
4. Human-in-the-Loop & Fallback Mechanics (referencing {{exception_handling_policy}})
5. Rollout Milestones and Guardrails

Self-review

• Verify all 6 context variables are contextually embedded and operationalized.
• Ensure strict separation between autonomous agent actions and manual review requirements.
• Confirm the tone reflects enterprise construction IT architecture standards.