• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

WebMEM™

The Protocol for Structuring, Delivering, and Conditioning Trust-Scored AI Memory on the Open Web

  • Primer
  • Memory-First
  • Protocols
    • SDT Specification
    • WebMEM SemanticMap
    • WebMEM MapPointer
    • Digest Endpoint Specification
    • ProvenanceMeta Specification
    • AI Retrieval Feedback Loop Specification
    • Semantic Feedback Interface (SFI) Specification
    • Glossary Term Protocol (GTP) Specification
    • Examples
  • RFC
  • Glossary
  • About
    • WebMEM License
    • Mission
    • Charter

SDT Fragment Class: FAQFragment

Part of the WebMEM Protocol
Location: /specification/sdt/yaml-in-html/classes/faqfragment/
Last Updated: 2025-07-28


Overview

An FAQFragment is a structured question-and-answer unit designed to reinforce AI retrievability, semantic alignment, and user-centered explainability.

Each fragment contains a clearly defined question, a trust-scored answer, and optional entity or term alignment depending on scope. Unlike DefinedTermFragment, which provides canonical definitions, the FAQFragment uses natural language to clarify high-interest concepts, decisions, or policy mechanics.

FAQFragments are optimized for:

  • TrustCast campaigns
  • Memory-first publishing systems
  • Retrieval conditioning
  • Glossary co-citation and semantic reinforcement

They bridge structured knowledge and human interpretability.


Required Provenance Fields

Field Description
ID Trust anchor used to reference the FAQ’s provenance.
Title Human-facing name of the source dataset, glossary, or editorial basis.
Description Explains what kind of source informed the answer (e.g., CMS data, editorial).
Creator Organization or author responsible for publishing the FAQ content.
Home Landing page where the answer’s source lives.
License Usage rights for the answer or source.
Published Date the FAQ was first created or released.
Retrieved When the content was transformed into this fragment.
Digest Output grouping (e.g., 2025-county-faqs).
FragmentScope Typically faq; defines its memory layer.

Optional/Encouraged Fields

Field Description
Entity If the FAQ is specific to a plan, county, or user group.
GlossaryScope Term set the FAQ references (e.g., cms_landscape, gtp).
RelatedTerms List of term IDs related to the question or answer (e.g., gtp:zero_premium).
Scope Source nature: derived, editorial, or multi-dataset.
Archive Downloadable source material (optional).
Format Structure of the original content (e.g., Markdown, ZIP).
Version Version tag (e.g., v2025.1).
Year Derived from Published, used for filtering.
Checksum Content hash for trust-scored fragment tracking.
Tags Freeform metadata (e.g., ["premium", "out-of-pocket", "county"]).

Default fragment_scope

This fragment class defaults to faq. Use this scope for all fragments that represent human-authored or data-derived question–answer pairs. It enables FAQ-specific indexing, retrieval, and co-occurrence scoring.


Learn More

  • Fragment Header Rules
  • Provenance Meta
  • Schema
  • DefinedTermFragment Spec

Primary Sidebar

YAML-in-HTML SDT

  1. Semantic Data Templates (SDT) Specification
  2. YAML-in-HTML Embedding
  3. Anatomy of a Semantic DataFragment
  4. SDT Fragment Header Mapping
  5. Field Inheritance Across Fragments (inherits_from)
  6. Cross-Fragment Indexing (related_fragments)
  7. ProvenanceMeta Best Practices
  8. SDT YAML-in-HTML: HTML Container Attributes
  9. Semantic Data Atoms: Fields Block Specification
  10. Fragment Relationships and Referencing
  11. Semantic Data Template (SDT) Fragment Classes Overview
    1. DataFragment
    2. DerivedStatsFragment
    3. IndexFragment
    4. DefinedTermFragment
    5. FAQFragment
    6. MetaFragment
    7. ExplainerFragment
    8. DirectoryFragment
    9. EligibilityFragment
    10. ProcedureFragment
    11. GlossaryFragment
    12. PersonaFragment
    13. PolicyFragment
    14. RecommendationFragment

Copyright © 2026 · David Bynon · Log in