Roles and tooling¶

Roles are first-class inputs to Conductor packs. Hector may wear any role as a hat; agents act as staff in one designated role. Roles define permitted tools and responsibilities, not approval committees. Tool access does not confer decision authority; see authority model.

Corpus sources: corpus/org/roles.yml, corpus/org/tooling-matrix.yml. Concrete role IDs and tooling defaults for this organization belong to the organization profile and org corpus.

Leadership and Portfolio¶

Role ID	Title	Mission	Primary tools
`role.president`	President	Set direction; decide judgment gates and exceptions; approve governed changes	Notion, GitHub PRs, Calendar, Bitwarden
`role.chief-of-staff`	Chief of Staff	Capture intake and maintain timed attention	Notion Initiatives, Calendar, Conductor consult
`role.strategy-research`	Strategy / Research	Produce priority and opportunity evidence	Research tools, Notion read
`role.portfolio-manager`	Portfolio Manager	Govern Initiative outcome, WIP, disposition, review, and workstream routing	Notion Initiatives, Portfolio inventories

Product¶

Role ID	Title	Mission	Primary tools
`role.product-manager`	Product Manager	Own Product evaluation outcome, gates, build-vs-buy, and the Product workstream (not the canonical Initiative outcome; that is Portfolio Manager)	Notion Products, Product inventories
`role.market-researcher`	Market Researcher	Produce market and customer evidence	Research tools, evidence stores
`role.scorecard-analyst`	Scorecard Analyst	Apply venture or bootstrap scorecards	Notion Products, scorecards

Software¶

Role ID	Title	Mission	Primary tools
`role.engineering-lead`	Engineering Lead	Frame scope, architecture, bindings, and definition of done	Repository, Software inventories
`role.implementer`	Implementer	Implement against the current stage pack	git, IDE, tests
`role.platform-engineer`	Platform Engineer	Promote, deploy, and operate platform integrations	deployment tools, secret-gate, runbooks

Editorial¶

Role ID	Title	Mission
`role.editor-in-chief`	Editor-in-Chief	Own slate and editorial judgment
`role.desk-editor`	Desk Editor	Assign desk, schema, and stage role
`role.reporter`	Reporter / Author	Draft authored content
`role.researcher`	Researcher	Produce data and source evidence
`role.fact-checker`	Fact-checker	Verify claims against sources
`role.copy-editor`	Copy Editor	Enforce structure and quality gates
`role.publisher`	Publisher	Publish and verify the live artifact
`role.translator`	Translator	Produce authored locale versions

Services¶

Role ID	Title	Mission
`role.practice-lead`	Practice Lead	Govern offer catalog and rates
`role.bd-sales`	BD / Sales	Progress qualified leads
`role.engagement-manager`	Engagement Manager	Govern scope, contract, and client status
`role.delivery-consultant`	Delivery Consultant	Produce client deliverables
`role.billing`	Billing	Invoice and record paid close

Operate¶

Role ID	Title	Mission
`role.platform-engineer`	Platform Engineer	Maintain shared runtime and planned changes
`role.on-call`	On-call	Triage incidents and restore service

Authorized pack scope¶

Every compiled pack must set:

initiative_id: init.<id>
workstream_id: ws.<id>
stage: <exact stage id>
active_role: role.<id>
tooling:
  read: []
  write: []
authorization:
  id: auth.<id>
  plan_digest: <digest>
  context_version: <version>
  conditions: []

Rules:

One pack has exactly one active_role.
Tool access is restricted to the current stage.
Tool access does not confer decision authority.
A role, stage, material plan, or context change requires a newly authorized pack.
If the active role is ambiguous, compilation stops and reports a required binding.
A sequence of roles is represented by separate stage packs, never a multi-hat pack.