Why this surface exists.A company directory is incomplete without an org chart. For an agent team, the org chart shows logical role separation (User · PMO · PO · CC) + which specialized agents are active vs. pending vs. queued. Track C classes appear explicitly so the team's planned shape isn't hidden by silent omission.

Hierarchy

Primary logical roles 4 roles

User → PMO → PO → CC orchestrator. Three logical roles that direct work; CC executes. Per AGENT-OPERATING-MODEL.md §1-§3.

Logical role

User

Strategic direction · final-quality gate · decision authority on contested calls.

Logical role

PMO · Project Management Office

Cross-session continuity · oversight + bookkeeping · Tier 2a session-end verification interim. Surface: Class B chat with MCP filesystem.

Logical role

PO · Product Owner

Strategy · product knowledge · agent-team decisions · canonical Terminal Roster authoring. Authors plans + dispatches; does not execute.

→ open profile

Logical role

CC · Claude Code orchestrator

Executor + orchestrator. Runs commits · opens PRs · dispatches subagents · executes code/script. Multi-instance default per SO #21.

Specialized direct-instances · Tier 2 corpus complete 4 roles

Domain-expert agents with M-2 expertise corpus authored. Each runs as own terminal (Pattern A) when lane requires deep expertise.

Specialized direct-instances · pending uplift or M-1 amendment 9 roles

Agents whose corpus is in flight (L-5..L-8) or pre-amendment (Planner · Tutor-Behavior · Developer · Auditor · Administrator). Profiles render with placeholder badges; auto-populate per refresh strategy when corpora land.

Track C · deferred classes (revisit post-Stage-7 + Tier-2-cascade-complete) 3 roles

Three NEW classes authorized for future M-1 amendment expansion (S76 P0-5). Surfaced explicitly here per S76 C3 axis 1 closure — silent omission would understate the team's planned shape.

Track C · deferred

Architect

System-architecture decisions · technology selection · cross-cutting infrastructure design. Distinct from Developer (Architect designs; Developer reviews + builds).

Track C · M-1 amendment expansion S76 P0-5

Track C · deferred

Security

Defensive security posture · OWASP audit cadence · threat modeling. Specialized cycle separate from Developer's security-review skill.

Track C · M-1 amendment expansion S76 P0-5

Track C · deferred

Portfolio-PM / Engineering-Manager

Cross-product portfolio management + engineering team coordination. Distinct from PO (PO product-strategy; Portfolio-PM team-level resource allocation).

Track C · M-1 amendment expansion S76 P0-5

Relationship graph · agent ↔ skill ↔ hook

Bidirectional edges from cross-refs/matrix.json. Pick an agent to see which skills load + which hooks constrain. Pick a skill to see every agent that uses it. Mobile-floor (375px) collapses to a list view automatically; no horizontal scroll.

Skills used by Designer 4

Anthropic-Frontend-Design

Load class: always

Aesthetic baseline + production-grade frontend output discipline.

Design-System

Load class: always

AI Uni brand tokens, component patterns, design principles.

Ux-Review

Load class: always

Designer reads to anticipate UX-agent review criteria.

Google-Labs-Code-Design-Md

Load class: task-match

DESIGN.md format spec + linter for brand-identity files.

Hooks constraining Designer 3

tool-scope-frontmatter

Binding: hard

Read · Grep · Glob ONLY

cross-file-fingerprint-check

Binding: hard

CI cross-file similarity bound

lens-rubric-self-application

Binding: process-discipline

Q1-Q7 before any surface-back