Tooling map

Canonical tool boundaries for Conductor. Tools retain their existing production responsibilities; Conductor selects the instructions and permissions appropriate to one role and stage.

Architecture

text Notion Initiative + workstream context │ ▼ Conductor compiler ├── workflow stage contract ├── inventory bindings ├── standards and units └── role tooling policy │ ▼ One authorized execution pack │ ▼ Authorized role uses the relevant production tool

Conductor may use read adapters to retrieve context and evidence. Write access to Notion and production systems is not part of the compiler's authority. Runtime client access uses authenticate and enforce access; only plan approval uses authorize. See authority model and organization profile.

Systems

System	Responsibility	Not responsible for
Conductor	Discover context; review plans; authorize and compile role-and-stage execution packs	Project management or production mutations
Notion Initiatives	Initiative contract and concurrent workstream state	Source code or production artifacts
Notion Products	Product evidence, scorecards, and gate history	Organization-wide intake
GitHub repositories	Source, branches, PRs, checks, releases, deployments; optional issues	Initiative or portfolio state
Google Calendar	Timed reminders and focus blocks	Initiative or workstream state
Bitwarden	Secrets	Work tracking
Notion CLI (ntn)	Default agent access to Notion (read/write after gates); see notion-access.md	Cursor-only OAuth as shared auth
Editorial tools	Writing and publication artifacts	Initiative state
Services client folders	Private engagement artifacts	Public work tracking
Operate tools	Runtime state, incidents, and runbooks	Application product backlog

By line

Line	Primary production surfaces
Portfolio	Notion Initiatives; Calendar for timed attention
Product	Notion Products and linked research artifacts
Software	Local git, GitHub repository, tests, CI/CD, deployment tools
Editorial	writing-publisher-MCP and site repository
Services	Private client folders, proposals, contracts, deliverables, invoices
Operate	Runbooks, hosts, observability, SSH, and incident tools

Tool permission rules

• An authorized pack grants plan scope only to its one active_role and current stage.
• Read and write permissions must be distinguished.
• Access to a tool does not grant decision authority.
• Secrets are referenced by name from organization profile / adapter configuration and retrieved only at execution time from the secret provider.
• Client-private context is included only when required and permitted.
• A stage or role change requires a new pack.
• Agents may use optional GitHub Issues when useful for repository-local coordination; Conductor never requires one as the work contract.

Forbidden uses

• GitHub Projects or GitHub Issues as the Initiative spine.
• Calendar events as project state.
• A multi-role pack with combined permissions.
• Execution authorization as evidence of Hector's approval for exceptions or policy changes.
• Silent writes to production tools during compilation.
• Duplicate line trackers that compete with the Notion Initiative.

Line details: Portfolio, Product, Software, Editorial, Services, Operate.