Skip to content

A Day in the Life: Core Personas

Personas: RC (Research Crafter), BC (Blueprint Crafter), DE (Documentation Evangelist), RB (Runbook Crafter), UG (User Guide Crafter)

Morning: The Find Phase

The day begins with RC -- the Investigator -- opening a new project brief. The first task is to scan source code repositories, architecture documents, and stakeholder feedback from the previous sprint. RC builds a capability matrix, tagging each entry with a capability ID and cross-referencing it against existing research inventories to avoid duplication. By mid-morning, a draft traceability matrix links every stated requirement to at least one evidence artifact.

RC feeds the completed research package into the event bus, emitting a PHASE_TRANSITION event that signals the end of Find and the start of Create.

Midday: The Create Phase

BC -- the Architect -- picks up the research package and begins translating it into design artifacts. For each capability in the matrix, BC produces a blueprint section: architecture diagrams, API endpoint specifications with schemas and error handling, and data model definitions. BC works closely with UMC (from Integration) on any UI-facing designs, ensuring that mockups align with the API specs.

Meanwhile, RB -- the Operator -- works in parallel on operational runbooks: deployment checklists, rollback procedures, and troubleshooting decision trees. RB consults the capability matrix to ensure every operational concern maps back to a documented capability.

UG -- the Guide -- drafts user-facing documentation: onboarding flows, quick-reference cards, and FAQ entries. UG coordinates with SCP (from Stakeholder) on distribution channels.

Afternoon: The Critique Phase

DE -- the Guardian -- reviews all Create-phase deliverables. DE runs quality gate checks against the configured constitution tiers: Tier 1 hard-stop rules are checked first (any violation halts the workflow), followed by Tier 2 mandatory rules (violations require documented exceptions), and Tier 3 preferred practices (deviations are noted as advisories).

DE provides structured feedback to BC and RB, referencing specific quality gate failures and linking each finding to the relevant constitution rule. Once all gates pass, DE emits a PUBLISH_APPROVED event and hands off to UGCH for final publishing orchestration.

Tools Used

  • PersonaRegistry for loading persona specifications
  • SimulationEngine for running the FCC cycle
  • EventBus for inter-persona communication
  • ConstitutionRegistry for quality gate enforcement
  • ActionEngine for structured task execution

Key Outputs

  • Capability matrix and traceability matrix (RC)
  • Blueprints, API specifications, data models (BC)
  • Operational runbooks and troubleshooting guides (RB)
  • User guides and onboarding materials (UG)
  • Quality review reports and publish decisions (DE)