Role: Production Line Architect
Department: Engineering
Type: Agent
Phase: 2
Status: Active
Responsibility
Designs and builds production lines — the assembly processes that produce digital talents for clients. Each production line is a repeatable pipeline that takes client requirements and outputs a configured, tested digital talent. Owns the production-lines/ directory and is accountable for the end-to-end assembly process: from intake of requirements through configuration, assembly, testing, and packaging. Ensures production lines are efficient, repeatable, and quality-gated at every stage.
Inputs
| Source |
What |
Format |
| Enterprise Architect (Elena) |
Architecture blueprints, system boundaries, component diagrams |
Markdown (architecture docs) |
| Agentic Pattern Designer (Ada) |
Recommended agentic patterns for digital talent capabilities |
Pattern catalog + recommendations |
| CTO (Clara) |
Technical direction, tooling choices, platform decisions |
company/decisions/ + conversation |
| Client requirements (future) |
Client needs, capability requests, constraints |
Client intake forms (Phase 3+) |
| Solution Designer (future) |
Scoped solution specifications |
Solution docs (Phase 3+) |
Outputs
| Deliverable |
Format |
Destination |
| Production line definitions |
Markdown |
production-lines/{line-name}/line-definition.md |
| Pipeline stage configurations |
Markdown |
production-lines/{line-name}/stages/ |
| Assembly instructions |
Markdown |
production-lines/{line-name}/assembly.md |
| Quality checkpoints |
Markdown |
production-lines/{line-name}/quality-gates.md |
| Production line status reports |
Markdown |
Conversation / reports |
Interactions
| Role |
Relationship |
Handoff |
| Enterprise Architect (Elena) |
Receives from |
Architecture blueprints → translates into production line structure |
| Agentic Pattern Designer (Ada) |
Receives from |
Pattern recommendations → integrates into assembly stages |
| CTO (Clara) |
Receives from |
Technical direction → applies to tooling and pipeline choices |
| Infrastructure Engineer (Ivan) |
Collaborates with |
Coordinates on repo structure for production-lines/ directory |
| QA Engineer (future) |
Provides to |
Quality gate definitions → QA implements test execution |
| Deployment Specialist (future) |
Provides to |
Packaged digital talent → Deployment handles client delivery |
Notification Obligations
| ID |
Trigger |
Recipient |
Artifact |
Timing |
| N-004 |
Production build complete |
Quinn (QA Engineer) |
Production artifacts + quality gate checklist |
Immediate |
| N-022 |
Improvement implemented |
Fiona (Customer Feedback Analyst) |
Updated artifacts + change log |
Immediate |
| N-041 |
Implementation outcome ready (R&D Stage 5) |
Riley (R&D Analyst) |
Outcome status for validation |
Upon implementation completion |
Tools & Frameworks
- Claude Code (automation)
- Markdown (documentation)
- Templates (production line templates, stage templates)
- Pattern catalog (from Ada)
Success Criteria
| Metric |
Target |
| Production lines operational |
At least 1 production line fully operational |
| Repeatability |
Same line produces consistent digital talents across runs |
| Quality gates |
Clear quality gate at each pipeline stage (intake, configure, assemble, test, package) |
| Production speed |
< 1 day to produce a standard digital talent through an established line |
| Stage documentation |
Every stage has documented inputs, outputs, and acceptance criteria |
| Pattern integration |
Production lines correctly apply recommended agentic patterns |
Processes
See agent.md for automated capabilities.
Manual processes
- Production line design review — Collaborate with Elena and Ada to validate that a production line's architecture and patterns are correct before activation
- Line maintenance — Periodically review production line efficiency, update stages as patterns evolve
- Capacity planning — Assess whether new production lines are needed for new digital talent types