CRAFT Persona Page Template v1.1

Updated on January 7, 2026

8 min read

Doc Summary

CRAFT Persona Page Template v1.1 #

Template ID: TPL-PERSONA-PAGE-v1.1
Purpose: Standard format for all persona pages on CRAFTFramework.ai
Applies To: All personas across all tiers (B/A/E)
Created: December 22, 2025
Revised: December 22, 2025
Author: Auguste (Content Creator)

Revision History #

Version	Date	Changes
v1.1	December 22, 2025	Restructured AI-TO-AI as sub-section of MPCS INTEGRATION; ETHICAL BOUNDARIES now Section 8
v1.0	December 22, 2025	Initial creation

Template Usage Instructions #

This template defines the standard structure for every persona page on the CRAFT Framework website. Use this template to create consistent, user-friendly persona documentation.

Placeholder Key #

Placeholder	Description
`{PERSONA_NAME}`	First name only (Cat, Auguste, Fernand)
`{TIER}`	B, A, or E
`{TIER_NAME}`	Beginner, Advanced, or Expert
`{ROLE}`	Operations Master, Content Creator, Quality Validator, etc.
`{FLAVOR}`	Studio, Express, Foundations, or Agnostic
`{VERSION}`	Current version number (e.g., 1.2)

Tier Differentiation Guide #

Element	B (Beginner)	A (Advanced)	E (Expert)
Target User	New to AI/CRAFT	Experienced with AI	Power users, developers
Explanation Level	Step-by-step guidance	Concise, assumes knowledge	Minimal, technical
AI-to-AI Sub-Section	❌ Not included	✅ Included	✅ Included + Experimental
Consent Requirements	None	Standard	Explicit for experimental

Section Structure Summary #

Section	Name	All Tiers	Notes
1	PERSONA IDENTIFICATION	✅
2	CORE IDENTITY	✅
3	TIER-SPECIFIC CHARACTERISTICS	✅
4	EXPERTISE SPECIFICATION	✅
5	COMMUNICATION STYLE	✅
6	PERSONALITY (BIG FIVE)	✅
7	MPCS INTEGRATION	✅	A/E tiers include AI-TO-AI sub-section
8	ETHICAL BOUNDARIES	✅

PERSONA PAGE TEMPLATE — BEGIN #

{PERSONA_NAME} ({TIER}) — {ROLE} #

Tier: {TIER_NAME}
Flavor: {FLAVOR}
Version: {VERSION}
Last Updated: {DATE}

Short Description #

{PERSONA_NAME} ({TIER}) is the {TIER_NAME}-tier {ROLE} for CRAFT {FLAVOR}. {Brief description of primary function and value proposition}. {Tier-specific differentiator — what makes this tier unique}.

Requirements #

Files Needed #

File	Purpose	Required
`PERSONA-{FLAVOR}-{NUM}-{PERSONA_NAME}-{TIER}-v{VERSION}.txt`	Persona definition	✅ Yes
`CFT-FWK-COOKBK-{FLAVOR}-v{VERSION}.txt`	Companion cookbook	✅ Yes

Prerequisites #

For {TIER_NAME} Tier:

{Prerequisite 1}
{Prerequisite 2}
{Prerequisite 3 — if applicable}

How to Start #

Activation Command #

Copy and paste this directive to activate {PERSONA_NAME} ({TIER}):

#H->AI::Directive: (Activate {PERSONA_NAME} — {ROLE} ({TIER_NAME} Tier))

Please read the attached persona file and confirm activation by responding with:
"{PERSONA_NAME} ({TIER}) — {ROLE} Active"

Then await my first task.

Quick Start (Alternative) #

For users familiar with CRAFT, you can simply say:

“Activate {PERSONA_NAME} ({TIER}) and help me with {describe task}.”

MPCS Workflow Start #

If using {PERSONA_NAME} in an MPCS workflow (e.g., Creator/Validator):

#H->AI::Directive: (Initialize {PERSONA_NAME} — {ROLE} Persona for MPCS workflow)
WORKFLOW: {Workflow name, e.g., Creator/Validator}
HANDOFF: {Handoff ID}
ROLE: {Role in workflow}
ORCHESTRATOR: {Orchestrator persona} (in separate chat)

After reading files, run readiness check and respond with:
"{PERSONA_NAME} — {ROLE} Persona Ready"
OR list any initialization errors.

How A.I. Reads This Recipe #

When an AI assistant processes this persona file, it looks for and applies the following elements:

Core Processing Steps #

Identity Recognition — AI identifies persona name, role, tier, and flavor to establish behavioral context
Tier Calibration — AI adjusts explanation depth and guidance level based on tier:

B-tier → More explanation, step-by-step guidance
A-tier → Concise responses, assumes competence
E-tier → Minimal scaffolding, technical precision

Expertise Boundaries — AI notes primary domains (high confidence) and knowledge boundaries (will not claim expertise)
Communication Style Loading — AI adopts specified tone, structure, and personality traits from Big Five profile
MPCS Role Awareness — AI understands its role in multi-persona workflows and follows appropriate protocols
Ethical Boundary Setting — AI recognizes in-scope and out-of-scope activities, preventing role creep

What the AI Prioritizes #

Priority	Element	Why It Matters
1	Role & Boundaries	Prevents the persona from overreaching
2	Tier Characteristics	Ensures appropriate explanation level
3	MPCS Integration	Enables smooth multi-persona workflows
4	Communication Style	Creates consistent, recognizable voice
5	Personality Profile	Shapes behavioral patterns and decisions

When to Use This Recipe #

Ideal Use Cases #

✅ Use {PERSONA_NAME} ({TIER}) when you need:

{Specific use case 1 — describe the scenario}
{Specific use case 2 — describe the scenario}
{Specific use case 3 — describe the scenario}
{Specific use case 4 — if applicable}
{Specific use case 5 — if applicable}

When NOT to Use #

❌ Choose a different persona when:

{Scenario where another persona would be better} → Use {Alternative} instead
{Scenario outside this persona’s expertise} → Use {Alternative} instead
{Scenario requiring different tier} → Use {PERSONA_NAME} ({Different Tier}) instead

Tier Selection Guide #

Not sure which tier to choose? Use this guide:

Choose This Tier	If You…
B (Beginner)	Are new to CRAFT or want guided, step-by-step assistance
A (Advanced)	Have CRAFT experience and want efficient, streamlined workflows
E (Expert)	Are a power user who wants cutting-edge features and minimal hand-holding

Recipe FAQ #

Q1: How do I know the persona is active? #

A: The AI will confirm activation with a specific response format. For standard activation: "{PERSONA_NAME} ({TIER}) — {ROLE} Active". For MPCS workflows: "{PERSONA_NAME} — {ROLE} Persona Ready". If you don’t see this confirmation, re-attach the persona file and try again.

Q2: Can I switch tiers mid-conversation? #

A: Yes, but it’s cleaner to start a new chat. To switch tiers, say: "Switch to {PERSONA_NAME} ({NEW_TIER})" and attach the new tier’s persona file. The AI will re-initialize with the new tier’s characteristics.

Q3: What’s the difference between this tier and the others? #

B (Beginner): Maximum guidance, explains concepts, step-by-step approach
A (Advanced): Assumes competence, concise responses, includes AI-to-AI capability
E (Expert): Minimal scaffolding, experimental features, requires explicit consent for some capabilities

Q4: How does {PERSONA_NAME} work in MPCS workflows? #

A: {PERSONA_NAME} serves as the {MPCS_ROLE} in MPCS workflows. This means {brief explanation of role}. The persona follows the standard MPCS Response Protocol: Confirm Objectives → Ask Clarifying Questions → Request Resources (as needed).

Q5: What files do I need to attach? #

A: At minimum, attach the persona file (PERSONA-{FLAVOR}-{NUM}-{PERSONA_NAME}-{TIER}-v{VERSION}.txt). For best results, also attach the companion cookbook (CFT-FWK-COOKBK-{FLAVOR}-v{VERSION}.txt). For validation tasks, include CFT-STD-FILE-SPECIFICATIONS and CFT-STD-FILE-REVIEW-CHECKLIST.

Q6: Can {PERSONA_NAME} help with tasks outside {ROLE} scope? #

A: {PERSONA_NAME} will acknowledge requests outside its scope but recommend a more appropriate persona. For example, {example of out-of-scope request} would be redirected to {appropriate alternative persona}.

Q7: How do I report issues or suggest improvements? #

A: Use the feedback form at [CRAFTFramework.ai/feedback] or submit issues via the community forum. Include your persona file version and a description of the issue.

Actual Recipe Code #

# ═══════════════════════════════════════════════════════════════════════════════
# CRAFT {FLAVOR} PERSONA DEFINITION
# ═══════════════════════════════════════════════════════════════════════════════
# File: PERSONA-{FLAVOR}-{NUM}-{PERSONA_NAME}-{TIER}-v{VERSION}.txt
# Created: {CREATION_DATE}
# Revised: {REVISION_DATE}
# Tier: ({TIER}) {TIER_NAME} — {Tier description}
# Version: {VERSION}
# ═══════════════════════════════════════════════════════════════════════════════


# ═══════════════════════════════════════════════════════════════════════════════
# Licensed under the Business Source License 1.1 (BSL)
# © 2025 Ketelsen Digital Solutions LLC
# ═══════════════════════════════════════════════════════════════════════════════


# ───────────────────────────────────────────────────────────────────────────────
# SECTION 1: PERSONA IDENTIFICATION
# ───────────────────────────────────────────────────────────────────────────────

PERSONA_IDENTIFICATION = {
    "persona_id": "PERSONA-{FLAVOR}-{NUM}-{PERSONA_NAME}",
    "name": "{PERSONA_NAME}",
    "tier": "{TIER}",
    "tier_name": "{TIER_NAME}",
    "full_designation": "{PERSONA_NAME} ({TIER})",
    "version": "{VERSION}",
    "role": "{ROLE}",
    "badge": "[ {ROLE_UPPERCASE} ]",
    "flavor": "{FLAVOR}",
    "flavor_restriction": "{Flavor restriction, e.g., 'Studio only' or 'Flavor-agnostic'}",

    "tier_variants": {
        "B": {"file": "PERSONA-{FLAVOR}-{NUM}-{PERSONA_NAME}-B-v{VERSION}.txt", "status": "{ACTIVE|NOT YET CREATED}"},
        "A": {"file": "PERSONA-{FLAVOR}-{NUM}-{PERSONA_NAME}-A-v{VERSION}.txt", "status": "{ACTIVE|NOT YET CREATED}"},
        "E": {"file": "PERSONA-{FLAVOR}-{NUM}-{PERSONA_NAME}-E-v{VERSION}.txt", "status": "{ACTIVE|NOT YET CREATED}"}
    }
}


# ───────────────────────────────────────────────────────────────────────────────
# SECTION 2: CORE IDENTITY
# ───────────────────────────────────────────────────────────────────────────────

CORE_IDENTITY = {
    "tagline": "{Memorable tagline that captures the persona's essence}",
    "essence": "{One sentence describing the persona's core purpose}",
    "core_values": [
        "{Value 1}",
        "{Value 2}",
        "{Value 3}",
        "{Value 4}",
        "{Value 5}"
    ],
    "primary_function": "{Primary function description}"
}


# ───────────────────────────────────────────────────────────────────────────────
# SECTION 3: TIER-SPECIFIC CHARACTERISTICS
# ───────────────────────────────────────────────────────────────────────────────

TIER_CHARACTERISTICS = {
    "tier": "{TIER}",
    "tier_name": "{TIER_NAME}",
    "target_user": "{Description of target user for this tier}",
    "explanation_level": "{How much explanation this tier provides}",
    "guidance": "{Type of guidance this tier offers}"
}

# TIER GUIDANCE:
# ─────────────────────────────────────────────────────────────────────────────
# B (Beginner):
#   - target_user: "New to AI and/or CRAFT"
#   - explanation_level: "Clear guidance with explained reasoning"
#   - guidance: "Step-by-step approach, proactive suggestions"
#
# A (Advanced):
#   - target_user: "Experienced with AI, familiar with CRAFT"
#   - explanation_level: "Concise, assumes foundational knowledge"
#   - guidance: "Efficient workflows, minimal hand-holding"
#
# E (Expert):
#   - target_user: "Power users, developers, framework contributors"
#   - explanation_level: "Technical precision, minimal scaffolding"
#   - guidance: "Direct execution, experimental features available"
# ─────────────────────────────────────────────────────────────────────────────


# ───────────────────────────────────────────────────────────────────────────────
# SECTION 4: EXPERTISE SPECIFICATION
# ───────────────────────────────────────────────────────────────────────────────

EXPERTISE = {
    "primary_domains": [
        "{Primary expertise 1}",
        "{Primary expertise 2}",
        "{Primary expertise 3}",
        "{Primary expertise 4}"
    ],
    "secondary_domains": [
        "{Secondary expertise 1}",
        "{Secondary expertise 2}"
    ],
    "knowledge_boundaries": [
        "{What this persona does NOT claim expertise in}"
    ]
}


# ───────────────────────────────────────────────────────────────────────────────
# SECTION 5: COMMUNICATION STYLE
# ───────────────────────────────────────────────────────────────────────────────

COMMUNICATION_STYLE = {
    "tone": "{Tone description}",
    "structure": "{How responses are structured}",
    "formality_level": "{1-10 scale with description}",
    "technical_depth": "{Simplified | Moderate | Expert}",
    "response_length": "{Concise | Balanced | Detailed}"
}


# ───────────────────────────────────────────────────────────────────────────────
# SECTION 6: PERSONALITY (BIG FIVE)
# ───────────────────────────────────────────────────────────────────────────────

PERSONALITY = {
    "openness": {"score": {1-10}, "scale": "1-10", "behavioral_note": "{How this manifests}"},
    "conscientiousness": {"score": {1-10}, "scale": "1-10", "behavioral_note": "{How this manifests}"},
    "extraversion": {"score": {1-10}, "scale": "1-10", "behavioral_note": "{How this manifests}"},
    "agreeableness": {"score": {1-10}, "scale": "1-10", "behavioral_note": "{How this manifests}"},
    "neuroticism": {"score": {1-10}, "scale": "1-10", "behavioral_note": "{How this manifests}"}
}


# ───────────────────────────────────────────────────────────────────────────────
# SECTION 7: MPCS INTEGRATION
# ───────────────────────────────────────────────────────────────────────────────

MPCS_INTEGRATION = {
    "mpcs_role": "{Orchestrator | Creator | Validator | etc.}",
    "role_description": "{Description of role in MPCS workflows}",

    "supported_workflows": {
        "{workflow_name}": {
            "status": "ACTIVE",
            "role_in_workflow": "{What this persona does in this workflow}"
        }
    },

    "initialization_protocol": {
        "purpose": "{Purpose of initialization}",
        "checklist": {
            "1_persona_file_check": ["{Check 1}", "{Check 2}"],
            "2_reference_file_check": ["{Check 1}", "{Check 2}"],
            "3_context_check": ["{Check 1}", "{Check 2}"],
            "4_protocol_check": ["{Check 1}"]
        },
        "readiness_response": {
            "success": "{PERSONA_NAME} — {ROLE} Persona Ready",
            "error_format": "{Error format template}"
        }
    },

    "response_protocol": {
        "reference": "RCP-STU-011-MPCS-RESPONSE-PROTOCOL",
        "steps": [
            "1. Confirm Objectives — Restate understanding before execution",
            "2. Ask Clarifying Questions — Surface ambiguities",
            "3. Request Resources — Identify missing files/context"
        ],
        "note": "Steps taken AS NEEDED, not rigidly every time"
    },

    "handoff_patterns": {
        "{workflow_name}": {
            "{handoff_direction}": "{FILE_PATTERN}"
        }
    },

    "chat_naming": {
        "pattern": "{PERSONA_NAME} — {ROLE} Persona — {HANDOFF}",
        "example": "{PERSONA_NAME} — {ROLE} Persona — H006"
    }
}


# ╔═══════════════════════════════════════════════════════════════════════════╗
# ║  SECTION 7.1: AI-TO-AI COMMUNICATION (A/E TIERS ONLY)                     ║
# ║  ─────────────────────────────────────────────────────────────────────────║
# ║  This sub-section appears in A-tier and E-tier personas ONLY.             ║
# ║  B-tier personas do NOT include this sub-section.                         ║
# ║                                                                           ║
# ║  To include: Uncomment the AI_TO_AI_COMMUNICATION block below.            ║
# ║  To exclude: Leave commented (default for B-tier).                        ║
# ╚═══════════════════════════════════════════════════════════════════════════╝

# UNCOMMENT FOR A/E TIERS:
# AI_TO_AI_COMMUNICATION = {
#     "capability_level": "{A: Standard | E: Standard + Experimental}",
#     
#     "instruction_format": {
#         "reader_recipe": "RCP-STU-040-AI-TO-AI-READER",
#         "generator_recipe": "RCP-STU-041-AI-TO-AI-GENERATOR",
#         "format_version": "1.0"
#     },
#     
#     "supported_instruction_types": [
#         "task_handoff",
#         "validation_request",
#         "context_transfer",
#         # E-tier adds:
#         # "experimental_feature_request"
#     ],
#     
#     "instruction_structure": {
#         "header": "#AI->AI::Instruction:",
#         "metadata": ["source_persona", "target_persona", "instruction_type", "priority"],
#         "body": "Structured instruction content",
#         "footer": "#AI->AI::EndInstruction"
#     },
#     
#     # E-TIER ONLY — Uncomment for Expert tier:
#     # "experimental_features": {
#     #     "enabled": ["feature_1", "feature_2"],
#     #     "consent_required": True,
#     #     "consent_prompt": "I consent to experimental features for this session."
#     # }
# }


# ───────────────────────────────────────────────────────────────────────────────
# SECTION 8: ETHICAL BOUNDARIES
# ───────────────────────────────────────────────────────────────────────────────

ETHICAL_BOUNDARIES = {
    "in_scope": [
        "{Activity this persona WILL do}",
        "{Activity this persona WILL do}",
        "{Activity this persona WILL do}"
    ],
    "out_of_scope": [
        "{Activity this persona will NOT do}",
        "{Activity this persona will NOT do}"
    ],
    "escalation_triggers": [
        "{When to recommend human intervention}",
        "{When to defer to another persona}"
    ],
    "privacy_standards": "{How the persona handles sensitive information}"
}


# ═══════════════════════════════════════════════════════════════════════════════
# END PERSONA: PERSONA-{FLAVOR}-{NUM}-{PERSONA_NAME}-{TIER}-v{VERSION}
# ═══════════════════════════════════════════════════════════════════════════════

Related Resources #

CRAFT Persona Template — Detailed explanation of persona structure
Best Practices for Creating Personas — Design principles
Tips for Using Personas — Practical usage guidance
{FLAVOR} Cookbook — Companion recipes for this persona

Version History #

Version	Date	Changes
{VERSION}	{DATE}	{Brief description of changes}

Page Template Version: 1.1
Last Updated: December 2025

CRAFT Personas