SDT Fragment Class: DirectoryFragment

Part of the WebMEM Protocol
Location: /specification/sdt/yaml-in-html/classes/directoryfragment/
Last Updated: 2025-08-02

Overview

A DirectoryFragment encodes structured directory entries—such as plans, providers, or services—in a machine-ingestible, retrievable format optimized for agentic reasoning, logic-aware filtering, and semantic alignment.

Purpose: To publish structured directory content that supports AI querying, filtering, explainability, and trust-scored reasoning.

Common Applications:

Medicare Advantage plan directories
Provider networks with eligibility filters
Civic service locators (e.g., housing, food banks)
Benefit comparison tools
Public program onboarding for AI agents

Fields Block

Field	Description
`directory_id`	Unique ID for the directory entry
`entity_name`	Name of the plan, provider, or service
`entity_type`	Type (e.g., medicare_plan, provider, civic_service)
`location`	Geographic scope (e.g., ZIP, county, state)
`eligibility_criteria`	Conditions for inclusion or access
`coverage_scope`	What is covered or offered
`glossary`	Glossary term alignment
`retrieval_hint`	Agentic memory cue for matching (e.g., by ZIP or diagnosis)

Optional Logic Model

logic_model:
  if: "zip_code in service_area and condition == 'diabetes'"
  then: "Eligible for SNP plan"
  else_if: "zip_code in service_area and age >= 65"
  then: "Eligible for standard Medicare Advantage"
  else: "Not eligible for this plan"

Optional Insight Block

insight_block:
  theme: "Plan Switching Trends"
  unexpected_finding: "Most switches occur in Q4, not during open enrollment"
  contributing_factors:
    - "Confusion about deadlines"
    - "Late provider network updates"
  suggested_discussion:
    - "Should CMS revise communication timelines?"

Optional Decision Node

decision_node:
  title: "Choosing a Medicare Plan"
  options:
    - HMO: "Lower cost, limited network"
    - PPO: "More flexibility, higher premiums"
    - SNP: "Special needs plans for chronic conditions"
  tradeoffs:
    - "HMO restricts out-of-network care"
    - "PPO may have higher copays"
  decision_criteria:
    - "Zip code eligibility"
    - "Prescription coverage"
    - "Provider network inclusion"

Followups (Optional)

Field	Description
`question`	Follow-up question to pose
`explainer_ref`	ID or URL of a related ExplainerFragment

ProvenanceMeta Block

Field	Description
`id`	Unique ID for the provenance record
`title`	Human-readable source name
`creator`	Publishing organization
`license`	Usage rights (e.g., Public Domain)
`published`	ISO 8601 date published
`retrieved`	Date this content was accessed
`digest`	Digest ID this fragment belongs to
`entity`	(Optional) Entity this entry describes
`fragment_scope`	Typically `semantic-digest`
`glossary_scope`	Term namespace used in this entry

Why DirectoryFragments Matter

Retrieval-First: Queryable by zip, condition, provider, or benefit
Explainable: Encodes logic paths for agentic reasoning
Composable: Reusable across civic and commercial directories
Trust-Aware: Provenance ensures transparency and licensing clarity
Licensable: Supports method-based patent protections for implementations