120 lines
2.7 KiB
Markdown
120 lines
2.7 KiB
Markdown
|
# OP_10 — Project Intake Protocol
|
||
|
|
|
||
|
|
## Purpose
|
||
|
|
Defines how new projects enter the Atomizer Engineering system.
|
||
|
|
|
||
|
|
## Trigger
|
||
|
|
Antoine (CEO) posts a new project request, typically in `#hq` or directly to `#secretary`.
|
||
|
|
|
||
|
|
## Steps
|
||
|
|
|
||
|
|
### Step 1: Manager Acknowledges (< 5 min)
|
||
|
|
- Manager acknowledges receipt in the originating channel
|
||
|
|
- Creates a project channel: `#<client>-<short-description>`
|
||
|
|
- Posts project kickoff message in new channel
|
||
|
|
|
||
|
|
### Step 2: Technical Breakdown (< 4 hours)
|
||
|
|
Manager hands off to Technical Lead (per OP_09):
|
||
|
|
- **Input:** Contract/requirements from Antoine
|
||
|
|
- **Output:** Structured breakdown containing:
|
||
|
|
- Geometry description
|
||
|
|
- Design variables (parameters to optimize)
|
||
|
|
- Objectives (what to minimize/maximize)
|
||
|
|
- Constraints (limits that must be satisfied)
|
||
|
|
- Solver requirements (SOL type, load cases)
|
||
|
|
- Gap analysis (what's missing or unclear)
|
||
|
|
|
||
|
|
### Step 3: Algorithm Recommendation (after Step 2)
|
||
|
|
Manager hands off to Optimizer:
|
||
|
|
- **Input:** Technical Lead's breakdown
|
||
|
|
- **Output:** Algorithm recommendation with:
|
||
|
|
- Recommended algorithm and why
|
||
|
|
- Population/trial budget
|
||
|
|
- Expected convergence behavior
|
||
|
|
- Alternatives considered
|
||
|
|
|
||
|
|
### Step 4: Project Plan Compilation (Manager)
|
||
|
|
Manager compiles:
|
||
|
|
- Technical breakdown
|
||
|
|
- Algorithm recommendation
|
||
|
|
- Timeline estimate
|
||
|
|
- Risk assessment
|
||
|
|
|
||
|
|
### Step 5: CEO Approval
|
||
|
|
Secretary presents the compiled plan to Antoine in `#secretary`:
|
||
|
|
```
|
||
|
|
📋 **New Project Plan — [Project Name]**
|
||
|
|
|
||
|
|
**Summary:** [1-2 sentences]
|
||
|
|
**Timeline:** [Estimated duration]
|
||
|
|
**Cost:** [Estimated API cost for this project]
|
||
|
|
**Risk:** [High/Medium/Low + key risk]
|
||
|
|
|
||
|
|
⚠️ **Needs CEO approval to proceed.**
|
||
|
|
|
||
|
|
[Full plan in thread ↓]
|
||
|
|
```
|
||
|
|
|
||
|
|
### Step 6: Kickoff (after approval)
|
||
|
|
Manager posts in project channel:
|
||
|
|
- Approved plan
|
||
|
|
- Agent assignments
|
||
|
|
- First task handoffs
|
||
|
|
- Timeline milestones
|
||
|
|
|
||
|
|
## Templates
|
||
|
|
|
||
|
|
### Project Kickoff Message
|
||
|
|
```
|
||
|
|
🎯 **Project Kickoff: [Project Name]**
|
||
|
|
|
||
|
|
**Client:** [Client name]
|
||
|
|
**Objective:** [What we're optimizing]
|
||
|
|
**Timeline:** [Start → End]
|
||
|
|
**Team:** [List of agents involved]
|
||
|
|
|
||
|
|
**Status:** 🟢 Active
|
||
|
|
|
||
|
|
**Milestones:**
|
||
|
|
1. [ ] Technical breakdown
|
||
|
|
2. [ ] Algorithm selection
|
||
|
|
3. [ ] Study build
|
||
|
|
4. [ ] Execution
|
||
|
|
5. [ ] Analysis
|
||
|
|
6. [ ] Audit
|
||
|
|
7. [ ] Report
|
||
|
|
8. [ ] Delivery
|
||
|
|
```
|
||
|
|
|
||
|
|
### CONTEXT.md Template
|
||
|
|
Create in `knowledge_base/projects/<project>/CONTEXT.md`:
|
||
|
|
```markdown
|
||
|
|
# CONTEXT.md — [Project Name]
|
||
|
|
|
||
|
|
## Client
|
||
|
|
[Client name and context]
|
||
|
|
|
||
|
|
## Objective
|
||
|
|
[What we're optimizing and why]
|
||
|
|
|
||
|
|
## Key Parameters
|
||
|
|
| Parameter | Range | Units | Notes |
|
||
|
|
|-----------|-------|-------|-------|
|
||
|
|
|
||
|
|
## Constraints
|
||
|
|
- [List all constraints]
|
||
|
|
|
||
|
|
## Model
|
||
|
|
- NX assembly: [filename]
|
||
|
|
- FEM: [filename]
|
||
|
|
- Simulation: [filename]
|
||
|
|
- Solver: [SOL type]
|
||
|
|
|
||
|
|
## Decisions
|
||
|
|
- [Date]: [Decision made]
|
||
|
|
|
||
|
|
## Status
|
||
|
|
Phase: [Current phase]
|
||
|
|
Channel: [Slack channel]
|
||
|
|
```
|