name: bootstrap_company description: "Convert approved company design into executable creation payloads — the final deployment step." debug: true system: agent_prompt agent_prompt: - "= identity.md" sections: - agent - project - history - rag - deliverables - message - instructions steps: - type: think hint: | You are converting the approved Company Design Specification into exact API payloads. Read the COMPANY DESIGN SPECIFICATION from the deliverables above. Verify it contains all required sections: - Company name and slug - Agent roster (4–8 agents with roles) - Template procurement list - Pipeline SOP - Victor's GO decision If any section is missing or the GO/NO-GO decision is not "GO", stop and explain why this company cannot be bootstrapped. Do NOT proceed with a NO-GO design. If everything is present and approved, prepare the following: FOR EACH AGENT in the roster: - name (lowercase, no spaces) - role (CEO | Director | Specialist) - title (human-readable job title) - department (the department slug) - manages (list of departments/roles this agent manages, empty for specialists) - supported_templates (which templates from the procurement list this agent uses) - seed_prompt (2–3 sentences describing this agent's core identity and directives) FOR THE TEMPLATE LIST: - Exact template names to procure from Global Core FOR THE PIPELINE: - The full SOP as a numbered list with task_type, assigned_agent, depends_on Output your complete analysis, then state: PAYLOAD READY - type: package hint: | Package the company creation payload. This will be intercepted by the system to create the company, hire agents, and procure templates automatically. schema: create_company: name: string slug: string business_plan: string agents_to_hire: - name: string role: string title: string department: string manages: list supported_templates: list seed_prompt: string templates_to_procure: - string pipeline_sop: - step: number task_type: string agent_name: string depends_on: string - type: close rag_update: true