• 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: DerivedStatsFragment

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


Overview

A DerivedStatsFragment is a semantic fragment class that represents multiple computed values or metrics derived from a known dataset.

It is scoped to a single entity, built from trusted source data, and used to expose calculated summaries such as counts, percentages, averages, or conditional aggregates.

Unlike DataFragment, which exposes single source facts, or IndexFragment, which surfaces listings, the DerivedStatsFragment focuses on transformed insights from structured source data.


Required Provenance Fields

Field Description
ID Unique provenance ID; anchors trust lineage for computed values.
Title Dataset title that the stats are based on (e.g., CMS MA Landscape 2025).
Description Explains how the stats were generated from the source.
Creator The original publisher of the dataset (e.g., CMS).
Home Homepage or documentation site for the dataset.
License Legal reuse terms for the original data (e.g., CC0).
Published Publication date of the dataset (not the derived output).
Retrieved Download date of the original dataset.
Digest Memory set the fragment belongs to (e.g., county-level digest ID).
Entity The subject the stats apply to (e.g., county ID, plan ID).
FragmentScope Declares the semantic purpose (e.g., derived, semantic-digest).

Optional Provenance Fields

Field Description
Scope Source classification (single-dataset, derived, etc.).
Archive Downloadable file used in the derivation process.
Format Structure of the source dataset (e.g., CSV, JSON).
Guidelines Link to official compliance or usage documentation.
GlossaryScope Glossary or namespace for aligning term definitions.
Version Version ID for the dataset or fragment (e.g., v2025.01).
Year Policy year or calendar year scope.
Checksum Cryptographic file hash to verify original data integrity.
Tags Keywords (e.g., county, stats, summary) for filtering or display.

Default fragment_scope

This fragment class defaults to semantic-digest. Use this scope when publishing derived or aggregated statistics tied to a specific entity (e.g., county-level MOOP averages or plan enrollment rankings). It supports trust-scored memory conditioning in structured output layers.


Learn More

  • Fields Block Specification
  • Fragment Header Rules
  • Schema
  • Provenance Meta

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