Back to the Playbook
Product BrainPB-05
Maintain architecture context
Keep an accurate map of components, dependencies, owners and constraints derived from the actual code, so product decisions rest on the real system.
Product statusAvailable now
Context in3 required inputsRepository and current code · Existing architecture notes and ADRs · Jira epics touching shared components
TransformationArchitect + Architecture AgentCode Analysis · Find Code Owners · Local Files
OutcomeCurrent architecture context: component map, dependency graph, owners and constraints.Artifact: Architecture context
Owner
Architect
Agent-led
Participants · Agents
EngineerProduct ManagerArchitecture Agent
Trigger
A scheduled review, a merged change in shared components, or a new initiative that touches the architecture.
Required context
CodeRepository and current codeArchitectureExisting architecture notes and ADRsJiraJira epics touching shared components
Optional context
FilesCODEOWNERS and team mapFilesOperational constraints
Skills
Code AnalysisFind Code OwnersLocal Files
Activity steps
- 1Map components, interfaces and dependencies from the code.
- 2Compare with existing diagrams and notes and flag drift.
- 3Record owners and constraints per area.
- 4Publish the updated context and notify affected epics.
Output
Current architecture context: component map, dependency graph, owners and constraints.
Artifacts
Updates: Architecture context, Product Brain
What good looks like
- Derived from current code, not from memory.
- Drift between diagram and code is explicit.
- Every area has a named owner.
- Constraints are stated in product terms.
Quality gate
An architect confirms changes to authoritative architecture context.
Destination
Product BrainConfluence
Usually next
People and agents work from the same Product Brain. The owner stays accountable. Assigned agents prepare and check. A named person approves at the gate.
Show us exactly how product work happens today.
Thirty minutes with a founder. We compare your process with the Playbook and pick the first Activity to run on your Jira and your repo.