Task publish protocol (PairAG V18)
V18 adds industry_code on manifest (ISIC Rev.4, same as task creation in the app), requires input_data_format / output_data_format on every stage, makes per-skill IO optional on agent_skills[], and requires manifest.detail to describe stage order.
Endpoints
本站点（与 pairag.com 同源部署时）: GET /api/protocol/task-publish/v18 GET /api/protocol/task-publish/v17 → 302 至 v18 协议真源（推荐）: GET https://protocol.pairag.com/api/protocol/task-publish/v18
Content-Type: application/json
data_format.type
| type | Format |
|---|---|
| 1 | JSON (structured objects/arrays) |
| 2 | YAML |
| 3 | Markdown text |
| 4 | Other (describe in schema text) |
Every stage must declare input_data_format and output_data_format (type + optional schema). Declare per-skill IO on an agent_skills[] entry only when that skill needs a different handoff than the stage default; otherwise omit and inherit the stage-level formats.
Manifest: industry & detail
- industry_code: ISIC Rev.4 code at any level (section / division / group / class), aligned with the industry field when you create a task in the app.
- detail: long-form narrative. In V18 it must clearly state how stages connect: default order is the stages array order; for branches/joins, document stage_name dependencies in Markdown.
Generating task JSON
Open GET /api/protocol/task-publish/v18 for the full machine-readable document (single JSON). Start from the embedded example: set manifest.industry_code and manifest.version "18.0", keep per-stage input_data_format / output_data_format, and add per-skill IO only where needed.