Conductor org map model¶
Canonical meta-model for Conductor.
Mechanic: left→right workflows (zoomable stages) × top→down inventories inside stages.
Pack = current cell(s) + bindings + standards + active role.
Hector is President (sole human decision-maker). Agents are staff with designated roles; Hector switches hats by role context. No governance boards or multi-approver ship gates. Corpus changes still use the existing proposal issue → approval → PR path.
Organization¶
text
President (Hector)
└── Portfolio Office # cross-line attention
├── Product Evaluation # venture + bootstrap
├── Software # build / promote / deploy
├── Editorial # newsroom / writing
├── Services # consulting / freelance
└── Operate # shared runtime / platform
+ Project Control Strip (GitHub work contract)
+ Standards (always on)
Career / job-search is out of scope (archive only) until explicitly promoted.
Shared skeleton (every line)¶
| Layer | Meaning |
|---|---|
| Portfolio | Intake, classify, prioritize, WIP/capacity, review |
| Line Product/Define | Why this work exists / success criteria (name varies) |
| Delivery / Production | Make the artifact |
| Operate / Publish-run | Keep it live, change it, retire it |
| Project strip | GitHub issue: outcome, DoD, next action, review date |
| Standards | Secrets, GitHub-first, tone, privacy |
| Roles | Who is acting; which tools that function uses |
Estate (Prototype / Lab / Portfolio-org) lives under Software + Portfolio classify, not as a Deploy inventory.
View A — Horizontal: workflows¶
Same idea at every line: ordered stages; specialize via inventories, not a new ladder per artifact type.
text
ZOOM OUT Portfolio position / line routing
ZOOM MID Line track stages (Delivery, Production, Engagement, …)
ZOOM IN Micro-steps inside a stage (expand only when needed)
View B — Vertical: inventories¶
Inventories are owned by a stage. Top→down: category → option → implies (units, templates, L2 tweaks).
View C — Together¶
text
Line + track stage → inventory picks → role tooling → pack
Assembly:
- Portfolio: line routing, priority, capacity OK?
- Line track + stage (+ L2 if zoomed)
- Resolve inventories (ask if unbound and required)
- Apply bindings from earlier stages / other lines
- Resolve active_role → tooling matrix
- Mix standards + project strip
- Emit pack: plan, units, template_refs, handoffs, gaps, prohibitions
Business lines (summary)¶
| Line | Enterprise analog | Primary workflow |
|---|---|---|
| Portfolio | PMO + strategy | Intake → Classify → Prioritize → Capacity → Review |
| Product | Innovation funnel | Discover → Explore → Score → Build-gate → Ship → Archive |
| Software | Engineering delivery | Frame → Design → Implement → Verify → Promote → Deploy → Document |
| Editorial | Newsroom | Assign → Report → Draft → Edit → Fact-check → Localize → Stage → Publish → Update |
| Services | Consulting firm | Offer → Lead → Propose → Contract → Deliver → Invoice → Complete → Archive |
| Operate | Platform / SRE | Run → Observe → Change → Incident → Retire |
Detail: docs/lines/, docs/roles-and-tooling.md, Software appendix docs/software-map-model.md.
Cross-line handoffs¶
| From | To | When |
|---|---|---|
| Services insight | Product inbox | Client work reveals a product idea |
| Product score pass | Software Prototype | Build gate + WIP slot |
| Software Lab live | Editorial Releases | Ship narrative |
| Services billable code | Software Delivery | Engagement binding (privacy, client brand) |
| Editorial Research | Software Prototype | Analysis tooling needed |
| Bootstrap ship | Venture explore | Optional $1B+ graduation |
Packs must name handoff artifacts (issue, folder, pack fragment) when recommending a crossing.
Corpus authority¶
Runtime truth lives under corpus/ (org, standards, portfolio, lines/*, project-strip, packs/examples).
archive/workspace-instructions/ is recovery only — not live policy.
Workspace folder layouts are described here; migrating live Workspace AGENTS is a later pass.
One-line summary¶
Left→right through zoomable stages on a business line; top→down inventory options inside a stage; pack includes role tooling and cross-line handoffs.