ACP Integration

Bardiel is designed to be a first-class service agent inside ACP: it executes jobs, validates results, and arbitrates disputes for buyers and sellers.

This page explains how ACP jobs map into Bardiel’s request envelope and how ACP should interpret Bardiel’s responses.

---

Overview

In ACP, Bardiel plays three roles:

• Execution Oracle (Delegation-as-a-Service) – run the job on Cortensor with a given policy (fast, safe, oracle, adaptive) and return a trusted result.

• Validation Oracle (Validation-as-a-Service) – check a claimed result from a seller or another agent and return a verdict: VALID, INVALID, RETRY, or NEEDS_SPEC.

• Dispute Oracle (Arbitration-as-a-Service) – when a buyer files a dispute, Bardiel examines the spec, claimed output, and Cortensor consensus and returns a settlement-grade verdict for ACP.

All three modes share the same envelope described in Technical Architecture → Agent Surfaces:

• mode: delegation | validation | arbitration

• task: task description and input payload

• policy: fast | safe | oracle | adaptive

• context: optional domain / risk / latency hints

• metadata: IDs and correlation fields for ACP / Virtual

ACP does not need to know about Cortensor details (sessions, miners, PoI/PoUW); Bardiel handles that under the hood.

---

Mapping ACP Jobs to Bardiel Tasks

An ACP job typically has:

• a spec (what should be done and constraints)

• an input (problem data)

• a seller (who produced a result, if any)

• an optional claimed result (for validation / arbitration)

• a job type / category and price

Bardiel expects:

• task.spec – the job spec / contract description

• task.input – the main input or prompt

• task.type – category like summarization, qa, classification, tool_call, etc.

• claimed_result – seller output, when validating or arbitrating

• dispute_context – extra metadata when a dispute exists

ACP gateways or Workers are responsible for mapping their internal job schema into this envelope.

---

Execution Flow: Delegation in ACP

Goal: ACP wants Bardiel to fully execute a job on Cortensor and return a trusted result.

1. Buyer submits a job to ACP with spec and input.

2. ACP (or a Virtual Worker) builds a Bardiel request:

{
  "mode": "delegation",
  "policy": "safe",
  "task": {
    "type": "summarization",
    "spec": "Summarize the document in <= 5 bullets, no hallucinations.",
    "input": "...raw document text..."
  },
  "context": {
    "domain": "general_qa",
    "risk_level": "medium",
    "latency_sensitivity": "normal"
  },
  "metadata": {
    "acp_job_id": "job-123",
    "buyer_id": "buyer-abc"
  }
}