PersonaFragment

Part of the WebMEM® Protocol
Fragment Class: PersonaFragment
Location: /protocol/fragments/personafragment/
Status: Current Draft
Last Updated: 2026-08-24

Overview

A PersonaFragment is a WebMEM fragment class for publishing a structured persona, user archetype, lived-experience scenario, or contextual human profile.

Each PersonaFragment establishes the persona being represented and the circumstances, challenges, goals, values, constraints, or experiences necessary to understand that persona within a defined context.

Unlike a DataFragment, which represents source-observed factual knowledge, or an IdentityFragment, which establishes the canonical identity of an entity, a PersonaFragment represents a human-centered contextual model used to frame how other knowledge may apply within a particular scenario.

A PersonaFragment may represent a real-world archetype, a composite scenario, an illustrative persona, or another explicitly characterized human context. The fragment should make the nature and provenance of that representation clear rather than implying that an illustrative or composite persona is a verified individual.

Semantic Purpose

The semantic purpose of a PersonaFragment is to state:

This is a defined human context or persona, and these are the circumstances, challenges, goals, values, or other characteristics relevant to understanding that context.

A PersonaFragment may establish:

the identity or label of the persona;
the setting or life context in which the persona exists;
the challenge, problem, or circumstance being represented;
the persona’s goals or desired outcomes;
constraints affecting the scenario;
a pivotal event or turning point where relevant;
values expressed by or relevant to the scenario;
relationships to programs, products, services, policies, or procedures;
relationships to explanatory or eligibility knowledge;
and provenance describing how the persona was created or sourced.

The PersonaFragment preserves these elements as one coherent contextual knowledge object.

PersonaFragment Within an SDT

A PersonaFragment exists as one modular knowledge object within a Semantic Data Template (SDT).

The relationship is:

Web Resource → SDT → PersonaFragment → Human Context

An SDT may contain one PersonaFragment or multiple PersonaFragments when a resource represents different user contexts, audience scenarios, needs, or pathways.

A PersonaFragment may also reference other fragments within the SDT when the persona’s circumstances relate to eligibility requirements, procedures, policies, explanations, recommendations, directories, or other structured knowledge.

This allows the human context to remain independently identifiable while participating in the broader machine representation of the resource.

PersonaFragment Requirements

A conforming PersonaFragment should establish enough information to identify the persona or scenario and understand the context it represents.

Element	Purpose
Fragment Class	Identifies the knowledge object as a `PersonaFragment`.
Fragment ID	Provides a stable identifier for the PersonaFragment within the published knowledge structure.
Persona	Provides the name, label, or other identifying designation used for the persona or archetype.
Setting	Establishes the environment, life domain, situation, or other context in which the persona is represented.
Challenge or Circumstance	Identifies the problem, barrier, need, decision, or situation relevant to the persona.
Persona Type	Identifies whether the persona is illustrative, composite, research-derived, or another explicitly declared form when that distinction is necessary.
Provenance	Identifies or references the source, methodology, authorship, or lineage supporting the persona representation.

Goals, constraints, pivotal moments, values, related knowledge, and other contextual information may be included when appropriate to the persona being represented.

Persona Context

The value of a PersonaFragment comes from the context it preserves.

Depending on the application, that context may include:

life circumstances;
responsibilities;
goals;
barriers or constraints;
information needs;
decision context;
program or service interactions;
geographic circumstances;
financial or logistical constraints;
or other characteristics relevant to the represented scenario.

The purpose is not to create an exhaustive profile. A PersonaFragment should contain the contextual information necessary for the knowledge object it supports.

Persona Types

A PersonaFragment may represent different kinds of persona knowledge.

Persona Type	Description
Illustrative Persona	A constructed scenario used to demonstrate how information, policies, procedures, products, or decisions may apply in a particular context.
Composite Persona	A persona assembled from recurring characteristics or patterns observed across multiple people, cases, or research inputs.
Research-Derived Persona	A persona developed from documented research, interviews, surveys, observational data, or another identified methodology.
Scenario Persona	A persona defined primarily to establish the circumstances surrounding a particular decision, process, explanation, or use case.

When the distinction matters to interpretation, the persona type should be declared explicitly.

Example PersonaFragment

The following example represents an illustrative caregiver persona using the current WebMEM HTML serialization.

<template
  data-webmem-fragment
  data-fragment-class="PersonaFragment"
  data-fragment-id="persona-maria-caregiver">

  <section
    data-entity-type="Persona"
    data-entity-id="persona:maria-caregiver"
    data-persona-type="illustrative"
    data-provenance-ref="#provenance-editorial-personas">

    <h3 data-role="persona-name">
      Maria, a caregiver
    </h3>

    <p data-role="setting">
      Navigating Medicare and public benefits for her father.
    </p>

    <p data-role="challenge">
      Maria is trying to understand complex eligibility rules
      while coordinating her father's healthcare coverage.
    </p>

    <p data-role="goal">
      Identify the coverage and assistance programs that may
      apply to her father's circumstances.
    </p>

    <p data-role="pivotal-moment">
      She discovers that her father's circumstances may qualify
      him for a Dual Eligible Special Needs Plan.
    </p>

    <ul data-role="values-expressed">
      <li>Responsibility</li>
      <li>Family loyalty</li>
      <li>Need for understandable guidance</li>
    </ul>

  </section>

</template>

The fragment establishes that:

the knowledge object is a PersonaFragment;
the fragment has a stable identity;
the persona is explicitly identified as illustrative;
the setting and challenge are represented separately;
the persona’s goal and pivotal circumstance are explicit;
the values relevant to the scenario are represented;
and provenance describing the persona’s origin can be resolved through the referenced provenance object.

Goals, Challenges, and Constraints

A PersonaFragment may distinguish among goals, challenges, and constraints when those concepts play different roles in the represented scenario.

Goal: the outcome the persona is attempting to achieve.
Challenge: the problem, uncertainty, or difficulty the persona faces.
Constraint: a circumstance that limits or shapes the available choices or actions.

For example, a persona may have the goal of finding appropriate healthcare coverage, the challenge of understanding eligibility requirements, and the constraint of living within a particular service area.

Keeping these concepts distinct can make the represented human context more explicit and useful to related knowledge objects.

Values and Contextual Framing

A PersonaFragment may identify values that are explicitly part of the represented scenario.

Examples may include:

independence;
affordability;
continuity of care;
family responsibility;
accessibility;
privacy;
simplicity;
or other values relevant to the persona’s circumstances.

Values should not be inferred from demographic characteristics or other attributes merely because the publisher assumes a person with those characteristics would hold particular preferences.

When values are represented, the fragment should make clear whether they are part of an illustrative scenario, derived from research, explicitly stated by a source, or established through another documented basis.

PersonaFragment and ExplainerFragment

PersonaFragment and ExplainerFragment can work together while preserving different semantic purposes.

PersonaFragment	ExplainerFragment
Represents the human context or persona.	Represents a structured explanation of a subject.
Answers: What circumstances, goals, challenges, or values define this scenario?	Answers: How should this subject be understood?
Provides contextual framing.	Provides explanatory structure.
May establish a scenario to which an explanation applies.	May reference a persona when the explanation is contextualized to that scenario.

For example, an ExplainerFragment may explain Medicare coverage choices within the circumstances represented by a caregiver PersonaFragment.

PersonaFragment and EligibilityFragment

A PersonaFragment may describe circumstances that overlap with criteria represented in an EligibilityFragment, but the two classes serve different purposes.

The PersonaFragment represents the human scenario.

The EligibilityFragment represents the actual qualification rules.

For example:

Persona Circumstances → EligibilityFragment → Qualification Criteria

A PersonaFragment should not convert illustrative characteristics into an eligibility determination. When qualification rules matter, those rules should remain explicitly represented by the EligibilityFragment and supported by the appropriate provenance.

PersonaFragment and RecommendationFragment

A persona may provide context relevant to a recommendation, but the PersonaFragment itself does not make the recommendation.

A RecommendationFragment may reference a PersonaFragment when the recommendation is intended to apply to the goals, circumstances, constraints, or values represented by that persona.

This preserves an important distinction:

PersonaFragment: represents the context.
RecommendationFragment: represents the recommendation made within or in response to that context.

The recommendation should preserve its own basis, criteria, provenance, and limitations rather than treating the persona itself as sufficient justification.

PersonaFragment and IdentityFragment

A PersonaFragment and an IdentityFragment both may contain identifying information, but they serve fundamentally different purposes.

An IdentityFragment establishes canonical identity for an actual entity.

A PersonaFragment establishes a contextual human model, archetype, scenario, or lived-experience representation.

An illustrative or composite persona should not be represented as though it were a canonical real-world individual.

When a PersonaFragment is based on a documented real-world subject, identity relationships should be represented only when appropriate to the publishing purpose and provenance of the material.

PersonaFragment and Relationships

A PersonaFragment may participate in explicit relationships with other WebMEM knowledge objects.

For example, a PersonaFragment may relate to:

an ExplainerFragment contextualized to the persona’s circumstances;
an EligibilityFragment containing qualification rules relevant to the scenario;
a ProcedureFragment describing a process the persona may need to follow;
a DirectoryFragment containing services or resources relevant to the scenario;
a RecommendationFragment representing a recommendation made within the defined context;
a PolicyFragment governing a program or service relevant to the persona;
a DefinedTermFragment defining terminology encountered in the scenario;
or another PersonaFragment representing a contrasting or related human context.

These relationships allow the persona to remain a focused contextual knowledge object while connecting it to the information structures relevant to the represented scenario.

Read the Relationships specification →

PersonaFragment and Resolution

A PersonaFragment may participate in machine resolution by providing a defined context from which related knowledge can be identified and traversed.

A resolution path may take the form:

Persona Context → EligibilityFragment → Applicable Program

or:

Persona Goal → ProcedureFragment → Required Process

or:

Persona Challenge → ExplainerFragment → Relevant Explanation

or:

Persona Context → DirectoryFragment → Relevant Resources

The PersonaFragment publishes the contextual model. It does not require a consuming system to infer undisclosed personal characteristics, assign a real person to a persona, or make decisions about an individual based solely on persona similarity.

Where persona context participates in a broader resolver surface, the resolver may use or reference explicitly represented characteristics and relationships as part of the resolution path.

Read the WebMEM Resolution Model →

Provenance

A PersonaFragment should preserve information about the origin and nature of the persona it represents.

Provenance may identify:

the person or organization responsible for creating the persona;
whether the persona is illustrative, composite, research-derived, or otherwise characterized;
the research, interviews, surveys, cases, editorial methodology, or other source material supporting the persona when applicable;
the canonical source location when one exists;
publication or revision dates;
version information;
license or reuse terms;
methodology or editorial guidelines;
and other lineage information necessary to understand how the persona was constructed.

When a persona is fictional or illustrative, provenance should not imply that its characteristics were observed from a real individual.

When a persona is derived from research or multiple source records, the provenance model should preserve that distinction rather than representing the persona as a source-observed individual.

Read the Provenance specification →

Conformance

A conforming PersonaFragment must:

identify itself as a PersonaFragment;
have an identifiable fragment scope;
provide a name, label, or other designation for the persona;
establish enough context to understand the scenario being represented;
identify the challenge, circumstance, goal, or other human context central to the persona;
distinguish illustrative, composite, research-derived, or other persona types when that distinction is necessary to interpret the representation correctly;
identify or reference provenance describing the origin of the persona;
avoid representing inferred characteristics as though they were source-observed facts;
preserve relationships to other knowledge objects when those relationships are necessary to understand how the persona participates in the SDT;
and conform to the applicable WebMEM serialization requirements.

A PersonaFragment represents published contextual knowledge. Conformance does not imply that a consuming system should classify a real person as belonging to the persona, infer characteristics that have not been explicitly provided, or treat an illustrative or composite scenario as a factual record of an individual.

Relationship to WebMEM 1.x

The PersonaFragment class originated in the WebMEM 1.x Semantic Data Template specification and remains a defined fragment class in the current WebMEM Protocol.

Earlier specifications described PersonaFragment as a structured representation of lived experience, user archetypes, and empathy scaffolds and associated it with retrieval hints, memory cues, empathy modeling, agent alignment, semantic digests, and trust-aware reasoning.

The current protocol preserves the semantic purpose of the class while separating that purpose from retired WebMEM 1.x memory, retrieval, digest, and agent-conditioning mechanisms.

Character, setting, challenge, pivotal moment, and expressed values remain valid elements of the class. The current protocol expands the model to make explicit the persona’s goals, constraints, type, provenance, and relationships to other WebMEM knowledge objects where those elements are relevant.

The current protocol also clarifies the distinction between contextual representation and factual identity. A PersonaFragment may represent an illustrative scenario, composite archetype, research-derived persona, or other human context without asserting that the represented characteristics belong to a specific real-world individual.

The current protocol further makes explicit how PersonaFragment can participate in machine resolution by connecting a defined human context to relevant explanations, eligibility requirements, procedures, directories, policies, recommendations, and other knowledge objects.

PersonaFragment continues to represent a structured human context, persona, archetype, or scenario together with the circumstances, challenges, goals, values, and relationships necessary to understand that context.