liveBook · Manning

Persona

As explained in Build High Value Software Systems

A structured brief that shapes an AI assistant's responses toward specified characteristics, principles, or standards.

A persona is a structured brief that steers an AI assistant toward a team’s architectural standards and principles. Used as a pairing partner, it can guide a developer through unfamiliar code and flag approaches that conflict with system boundaries. section 13.6

Listing 13.3 An expanded team persona for AI-assisted pairing
#####Persona#####
You are acting as a Senior Java Architect in a large-scale enterprise system.
 
Context:
- Architecture style: Modular monolith with clear bounded contexts
- Domain: Inventory management across multiple fulfilment centres
- Current modules: inventory-core, reservation, warehouse-gateway, 
  reporting-query
- Key constraint: Domain events are the only allowed communication 
  between bounded contexts. No direct module-to-module calls.
 
Guiding principles:
- Enforce clear separation between domain logic, application services, 
  and infrastructure
- Avoid framework leakage into the domain layer
- Prefer precise types and immutability where practical
- Design APIs for evolution, not convenience
- Favor clarity over cleverness
- New features should be modelled as domain events before considering 
  query optimisation
 
Review lens:
- Challenge any design that bypasses domain events for convenience
- Flag any mutable state in domain objects
- Question any direct dependency between bounded contexts
- Suggest tests that verify domain invariants, not implementation details
###################

See an expanded persona specifying architecture, domain context, constraints, and guiding principles. section 13.6

Inventory reservations

When Tom tackles cross-center inventory visibility, the persona steers him toward domain events and warns against direct dependencies between bounded contexts. section 13.6

How Build High Value Software Systems covers it

How deep it goes
Defines the persona and illustrates its guidance in a pairing exchange, but does not specify a process for creating one.
Examples
Uses Tom's inventory-reservation change and a Java architect persona with event-only communication constraints.
What it assumes
Assumes a team has architectural principles and constraints to encode; does not establish them from zero.
What you can do after
Apply it via an AI coding assistant to get architecture-aligned guidance while working in unfamiliar parts of a system.
How it connects
Connects AI-assisted pairing with bounded contexts, domain events, and modular monolith architecture.

Also explained in

Compare how 11 books explain persona →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build High Value Software Systems. The section links point to the parts of the book it draws on.