DRKM Blueprint System

Active

Team and Ownership

Team roster, roles, and domain ownership

Active·Owner: kristina·2026-04-04

Team Roster

| Name | Title | Role | Domains | Status | |---|---|---|---|---| | Greg | Chief Visionary & Brand Director | Vision, product direction, system architecture | vision, product, design, ux, brand, market-strategy | active | | Kristina | Compliance Director & Chief Project Manager | Compliance, governance, project management | compliance, governance, process, audit, project-management | active | | Rafa | DevOps Lead & Infrastructure Architect | Backend, infrastructure, implementation | devops, backend, database, infrastructure, ci-cd, deployment | active | | Markus | AI Publisher (OpenClaw Assistant) | Content generation, scaffold creation, validation | content-generation, scaffold, validation, changelog, deployment | active |

Role Descriptions

Greg - Chief Visionary & Brand Director

Responsibilities:

  • Set product vision and direction
  • Design UX and visual language
  • Define what success looks like
  • Make architectural decisions affecting user experience
  • Validate design consistency

Domains: vision, product, design, ux, brand, market-strategy, monetization

Decision Authority: All design, UX, and product direction decisions. Final say on vision and strategy.

Kristina - Compliance Director & Chief Project Manager

Responsibilities:

  • Ensure compliance with policies and standards
  • Manage project timeline and deliverables
  • Track risks and mitigations
  • Audit governance processes
  • Manage stakeholder communication

Domains: compliance, governance, process, audit, project-management

Decision Authority: All governance, process, and compliance decisions. Final say on policies and procedures.

Rafa - DevOps Lead & Infrastructure Architect

Responsibilities:

  • Implement system architecture
  • Build and maintain infrastructure
  • Deploy and operate the system
  • Ensure performance and reliability
  • Make technical implementation decisions

Domains: devops, backend, database, infrastructure, ci-cd, deployment

Decision Authority: All technical and infrastructure decisions. Final say on how the system is built and deployed.

Markus - AI Publisher

Responsibilities:

  • Generate scaffold and content based on specifications
  • Validate content against schemas
  • Create and maintain changelog
  • Execute deployment procedures
  • Provide feedback on specification usability

Domains: content-generation, scaffold, validation, changelog, deployment

Decision Authority: No final decision authority (executor role). Provides input on process and specification effectiveness.

Domain Matrix

| Domain | Owner | Secondary | Tertiary | |---|---|---|---| | Vision | Greg | Kristina | Rafa | | Product | Greg | Kristina | Rafa | | Design | Greg | - | - | | UX | Greg | Rafa | Kristina | | Brand | Greg | Kristina | - | | Market Strategy | Greg | Kristina | - | | Compliance | Kristina | Greg | Rafa | | Governance | Kristina | Greg | Rafa | | Process | Kristina | Rafa | Greg | | Audit | Kristina | Greg | Rafa | | Project Management | Kristina | Greg | Rafa | | DevOps | Rafa | Kristina | Greg | | Backend | Rafa | Greg | Kristina | | Database | Rafa | Kristina | Greg | | Infrastructure | Rafa | Kristina | Greg | | CI/CD | Rafa | Kristina | Greg | | Deployment | Rafa | Kristina | Greg | | Content Generation | Markus | Greg | Rafa | | Scaffold | Markus | Rafa | Greg | | Validation | Markus | Rafa | Greg | | Changelog | Markus | Kristina | Greg |

Cross-Domain Collaboration

Some decisions span multiple domains:

| Decision Type | Lead | Consults | Approves | |---|---|---|---| | New feature | Greg | Rafa, Kristina | Greg | | Architecture change | Rafa | Greg, Kristina | Rafa | | Process change | Kristina | Greg, Rafa | Kristina | | Policy change | Kristina | Greg, Rafa | Kristina | | Design change | Greg | Rafa (feasibility) | Greg | | Performance optimization | Rafa | Greg (UX impact) | Rafa |

Team Availability

  • Greg: Vision input, design review, decision making
  • Kristina: Process, compliance, governance
  • Rafa: Implementation, operations, deployment
  • Markus: Scaffold generation, content creation, validation

Onboarding New Team Members

New team members join by:

  • 1. Shadow existing team member in their domain
  • 2. Review decision log and governance docs
  • 3. Understand domain-specific processes
  • 4. Start with low-risk decisions/tasks
  • 5. Gradually increase responsibility

All processes are documented so new members can self-onboard.