Skip to content

A Day in the Life: Champion Personas

Personas: RCHM (Research Crafter Champion), BCHM (Blueprint Crafter Champion), UGCH (User Guide Crafter Champion), RBCH (Runbook Crafter Champion)

Morning: RCHM Orchestrates the Find Phase

RCHM receives a new project brief and decomposes it into parallel research tasks. RC is assigned primary source investigation, CIA handles catalog indexing of existing artifacts, STE begins taxonomy construction for the domain, and RIC starts automated inventory generation. RCHM monitors progress through the event bus, receiving TASK_STARTED and TASK_COMPLETED events from each orchestrated persona.

When RC finishes a capability matrix draft, RCHM reviews it for completeness before allowing CIA to index it. RCHM ensures that no research artifact moves downstream until all quality checks pass. By late morning, RCHM assembles the unified research package and hands it off to BCHM with a PHASE_TRANSITION event.

Midday: BCHM Orchestrates the Create Phase

BCHM picks up the research package and distributes design tasks. BC receives the core blueprint assignment, BV is put on standby for validation, and UMC begins mockup work for any UI-facing components. RIC provides supplementary research data as BC requests it.

BCHM coordinates the validation loop: as BC produces blueprint sections, BV validates each one against quality gates. Failures are routed back to BC with specific remediation guidance. Once all blueprint sections pass validation, BCHM assembles the complete design package and emits two handoff events -- one to DE for critique and one to RBCH for operational documentation.

Afternoon: UGCH and RBCH Complete the Cycle

After DE approves the design package, UGCH takes over user-facing content orchestration. UG drafts user guides, SCP prepares distribution channels, and EC creates executive summaries for stakeholder communication. UGCH ensures that all content is consistent in tone, formatting, and terminology.

Concurrently, RBCH coordinates operational documentation. RB writes runbooks and deployment guides, GCA validates compliance, and TS verifies traceability from requirements through to operational procedures. RBCH ensures that every runbook entry traces back to a validated blueprint section.

Tools Used

  • EventBus for orchestration event flow
  • ProgressTracker for monitoring sub-task completion
  • CrossReferenceMatrix for verifying handoff integrity
  • ConstitutionRegistry for quality gate enforcement
  • Champion orchestrates field for team composition

Key Outputs

  • Unified research packages (RCHM)
  • Validated design packages (BCHM)
  • Published user documentation (UGCH)
  • Compliant operational documentation (RBCH)