Update to Frontier Infra

{
  "name": "conductor-pipeline",
  "description": "Design, adapt, implement, or audit a model-driven multi-agent triage and fulfillment pipeline using Conductor's fat-engine/thin-skill, closed-transition, fan-out/fan-in, persistent-workspace, human-gate, and delivery patterns.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 228
    }
  ],
  "skill_md_contents": "---\nname: conductor-pipeline\ndescription: Design, adapt, implement, or audit a model-driven multi-agent triage and fulfillment pipeline using Conductor's fat-engine/thin-skill, closed-transition, fan-out/fan-in, persistent-workspace, human-gate, and delivery patterns.\n---\n\n# Adapt a Conductor-style pipeline\n\nRead `../../references/pattern-catalog.md`, `../../references/system-architecture.md`, and `../../references/threat-model.md`. Treat this as an `orchestrator` shape unless the control loop is genuinely model-free. Current public Conductor material should be described as `Orchestrator-L1 Declared` unless newer executed evidence supports a different shape-stamped claim.\n\n## Workflow\n\n1. Define the item, sources, scoring rubric, threshold, research lanes, route values, deliverables, and the one human approval boundary.\n2. Encode domain differences as validated configuration and templates. Keep dedup, bounds, thresholds, routes, dependency construction, persistence, retries, and legal transitions in a deterministic engine.\n3. Keep model skills thin: detection, bounded scoring judgment, classification, synthesis, and proposal prose.\n4. Use read-only scouts for untrusted sources; minimize each role's tools. Treat source content as prompt-injection input.\n5. Build fan-out research lanes and a dependency-driven fan-in route. Persist the model-selected transition before effects so replay never calls the model again.\n6. Use a shared persistent workspace for chained fulfillment. Put scope rails and a human gate immediately before the high-impact path.\n7. Deliver proposals and results through an explicit channel action; a status change is not delivery.\n8. Add cost gates, idempotency, terminal quarantine, failure alerts, and test cases per rubric boundary and route.\n\n## Output\n\nReturn the configuration map, typed state/transition table, engine-versus-skill responsibility matrix, role/tool matrix, human-gate contract, security boundaries, and validation plan. Never claim `Machine-L*` for this shape.\n"
}