{
  "schema": "dkharlanau.dataset.manifest",
  "schema_version": "1.1",
  "generated_at_utc": "2026-04-13T08:37:04+00:00",
  "doi": {
    "concept": "10.5281/zenodo.18862098",
    "version": "10.5281/zenodo.18862097",
    "repository": "https://github.com/dkharlanau/dkharlanau-datasets"
  },
  "license": {
    "name": "Creative Commons Attribution-NonCommercial 4.0 International (CC BY-NC 4.0)",
    "spdx": "CC-BY-NC-4.0",
    "url": "https://creativecommons.org/licenses/by-nc/4.0/"
  },
  "attribution": {
    "attribution_required": true,
    "preferred_citation": "Dzmitryi Kharlanau. Dataset bytes (manifest). CC BY-NC 4.0. DOI: 10.5281/zenodo.18862098. https://dkharlanau.github.io/datasets/manifest.json"
  },
  "creator": {
    "name": "Dzmitryi Kharlanau",
    "role": "SAP Lead",
    "website": "https://dkharlanau.github.io",
    "linkedin": "https://www.linkedin.com/in/dkharlanau"
  },
  "datasets_root": "datasets",
  "count": 150,
  "entries": [
    {
      "dataset": "DAMA",
      "id": "db_governance_decision_rights_v0_1",
      "title": "Decision Rights & RACI for Master Data (Who decides what?)",
      "path": "DAMA/db_governance_decision_rights_v0_1.json",
      "tags": [
        "governance",
        "raci",
        "ownership",
        "accountability",
        "operating_model"
      ],
      "entity_type": "data_governance_byte",
      "summary": "Decision Rights & RACI for Master Data (Who decides what?)"
    },
    {
      "dataset": "DAMA",
      "id": "db_governance_drift_detection_response_v0_1",
      "title": "Governance Drift: How to detect degradation early and respond without panic fixes",
      "path": "DAMA/db_governance_drift_detection_response_v0_1.json",
      "tags": [
        "governance_drift",
        "operating_model",
        "leading_indicators",
        "bypass",
        "exceptions",
        "mdg"
      ],
      "entity_type": "data_governance_byte",
      "summary": "Governance Drift: How to detect degradation early and respond without panic fixes"
    },
    {
      "dataset": "DAMA",
      "id": "db_governance_maturity_model_mdg_v0_1",
      "title": "MDG Governance Maturity Model: assess current level and choose the next upgrade (Level 1–5)",
      "path": "DAMA/db_governance_maturity_model_mdg_v0_1.json",
      "tags": [
        "maturity_model",
        "assessment",
        "roadmap",
        "mdg",
        "governance",
        "continuous_improvement"
      ],
      "entity_type": "data_governance_byte",
      "summary": "MDG Governance Maturity Model: assess current level and choose the next upgrade (Level 1–5)"
    },
    {
      "dataset": "DAMA",
      "id": "mdg_ai_reasoning_prompt_schema_v0_1",
      "title": "Mdg Ai Reasoning Prompt Schema V0 1",
      "path": "DAMA/mdg_ai_reasoning_prompt_schema_v0_1.json",
      "tags": [],
      "entity_type": "mdg_byte",
      "summary": "Mdg Ai Reasoning Prompt Schema V0 1"
    },
    {
      "dataset": "DAMA",
      "id": "mdg_design_patterns_pack_v0_1",
      "title": "Mdg Design Patterns Pack V0 1",
      "path": "DAMA/mdg_design_patterns_pack_v0_1.json",
      "tags": [],
      "entity_type": "mdg_byte",
      "summary": "Architecture patterns for SAP MDG / MDM programs covering Create, Update, Migration/Cutover, and Day-2 operations."
    },
    {
      "dataset": "DAMA",
      "id": "mdg_metric_decision_playbooks_v0_1",
      "title": "Mdg Metric Decision Playbooks V0 1",
      "path": "DAMA/mdg_metric_decision_playbooks_v0_1.json",
      "tags": [],
      "entity_type": "mdg_byte",
      "summary": "Translate breached metrics into deterministic governance actions via linked Decision Blocks."
    },
    {
      "dataset": "DAMA",
      "id": "mdg_metrics_framework_v0_1",
      "title": "Mdg Metrics Framework V0 1",
      "path": "DAMA/mdg_metrics_framework_v0_1.json",
      "tags": [],
      "entity_type": "mdg_byte",
      "summary": "Provide a canonical, AI-readable metrics framework for MDG governance: detect drift, assess decision quality, and trigger the right Decision Blocks."
    },
    {
      "dataset": "DAMA",
      "id": "mdg_migration_data_architecture_v0_1",
      "title": "Mdg Migration Data Architecture V0 1",
      "path": "DAMA/mdg_migration_data_architecture_v0_1.json",
      "tags": [],
      "entity_type": "mdg_byte",
      "summary": "Mdg Migration Data Architecture V0 1"
    },
    {
      "dataset": "DAMA",
      "id": "mdg_migration_sequence_playbook_v0_1",
      "title": "Mdg Migration Sequence Playbook V0 1",
      "path": "DAMA/mdg_migration_sequence_playbook_v0_1.json",
      "tags": [],
      "entity_type": "mdg_byte",
      "summary": "Mdg Migration Sequence Playbook V0 1"
    },
    {
      "dataset": "DAMA",
      "id": "mdg_tool_pack_v0_1",
      "title": "Mdg Tool Pack V0 1",
      "path": "DAMA/mdg_tool_pack_v0_1.json",
      "tags": [],
      "entity_type": "mdg_byte",
      "summary": "A minimal practical toolkit to operationalize the MDG Governance Reasoning Framework (Decision Blocks + Metrics + Playbooks) for real projects and AI/RAG usage."
    },
    {
      "dataset": "LLM-prompts",
      "id": "CE-01",
      "title": "Context Engineering is a Discipline, Not a Prompt Trick",
      "path": "LLM-prompts/CE-01.json",
      "tags": [],
      "entity_type": "llm_prompt_byte",
      "summary": "Context Engineering is a Discipline, Not a Prompt Trick"
    },
    {
      "dataset": "LLM-prompts",
      "id": "CE-02",
      "title": "Positional Strategy: Engineering Around 'Lost in the Middle' in Long Context + RAG",
      "path": "LLM-prompts/CE-02.json",
      "tags": [],
      "entity_type": "llm_prompt_byte",
      "summary": "Positional Strategy: Engineering Around 'Lost in the Middle' in Long Context + RAG"
    },
    {
      "dataset": "LLM-prompts",
      "id": "CE-03",
      "title": "Retrieval as a Product: RAG Refinement, Compression, and Long-Context Noise Control",
      "path": "LLM-prompts/CE-03.json",
      "tags": [],
      "entity_type": "llm_prompt_byte",
      "summary": "Retrieval as a Product: RAG Refinement, Compression, and Long-Context Noise Control"
    },
    {
      "dataset": "LLM-prompts",
      "id": "CE-04",
      "title": "Prompt Optimization as Engineering: From Handcrafted Prompts to Optimized Systems",
      "path": "LLM-prompts/CE-04.json",
      "tags": [],
      "entity_type": "llm_prompt_byte",
      "summary": "Prompt Optimization as Engineering: From Handcrafted Prompts to Optimized Systems"
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-01",
      "title": "Segmentation",
      "path": "TRIZ-bytes/TRIZ-01.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Reduce system rigidity by dividing a problem into independently changeable parts."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-02",
      "title": "Taking Out (Separation)",
      "path": "TRIZ-bytes/TRIZ-02.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Remove or isolate a problematic or volatile part so the rest of the system can stay stable and simple."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-03",
      "title": "Local Quality",
      "path": "TRIZ-bytes/TRIZ-03.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Allow different parts of a system to have different properties instead of forcing uniformity everywhere."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-04",
      "title": "Asymmetry",
      "path": "TRIZ-bytes/TRIZ-04.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Break false symmetry to reduce complexity, cost, or risk by assigning different roles or properties to similar-looking parts."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-05",
      "title": "Merging",
      "path": "TRIZ-bytes/TRIZ-05.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Reduce overhead and latency by combining related elements, activities, or responsibilities when separation creates friction."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-06",
      "title": "Universality",
      "path": "TRIZ-bytes/TRIZ-06.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Reduce system complexity by making one element perform multiple functions instead of introducing new specialized components."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-07",
      "title": "Nested Doll",
      "path": "TRIZ-bytes/TRIZ-07.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Manage complexity by placing systems or components inside others, creating clear containment and layered responsibility."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-08",
      "title": "Anti-Weight (Counterbalance)",
      "path": "TRIZ-bytes/TRIZ-08.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Offset negative forces or constraints by introducing compensating mechanisms instead of fighting them directly."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-09",
      "title": "Preliminary Anti-Action",
      "path": "TRIZ-bytes/TRIZ-09.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Reduce risk and cost by performing preventive actions before a problem fully manifests."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-10",
      "title": "Preliminary Action",
      "path": "TRIZ-bytes/TRIZ-10.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Accelerate execution by preparing critical elements in advance so the main action becomes simple and fast."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-11",
      "title": "Beforehand Cushioning",
      "path": "TRIZ-bytes/TRIZ-11.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Absorb shocks and uncertainty by building safety buffers into the system before failures occur."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-12",
      "title": "Equipotentiality",
      "path": "TRIZ-bytes/TRIZ-12.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Reduce unnecessary effort by aligning conditions so work does not have to fight against artificial differences."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-13",
      "title": "The Other Way Around (Inversion)",
      "path": "TRIZ-bytes/TRIZ-13.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Solve a problem by reversing actions, relationships, or assumptions instead of optimizing the existing direction."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-14",
      "title": "Spheroidality / Curvature",
      "path": "TRIZ-bytes/TRIZ-14.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Increase adaptability and robustness by replacing rigid, linear structures with flexible, curved, or adaptive ones."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-15",
      "title": "Dynamics",
      "path": "TRIZ-bytes/TRIZ-15.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Allow a system to change its structure, behavior, or parameters over time instead of remaining static."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-16",
      "title": "Partial or Excessive Actions",
      "path": "TRIZ-bytes/TRIZ-16.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Achieve better results by deliberately doing less or more than the nominal requirement instead of aiming for exactness."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-17",
      "title": "Another Dimension",
      "path": "TRIZ-bytes/TRIZ-17.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Unlock new solution space by moving the problem into an additional dimension instead of optimizing within the same plane."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-18",
      "title": "Mechanical Vibration",
      "path": "TRIZ-bytes/TRIZ-18.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Improve performance by introducing controlled oscillation, iteration, or repetition instead of static operation."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-19",
      "title": "Periodic Action",
      "path": "TRIZ-bytes/TRIZ-19.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Replace continuous or one-time actions with periodic ones to reduce load, cost, and risk while maintaining effectiveness."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-20",
      "title": "Continuity of Useful Action",
      "path": "TRIZ-bytes/TRIZ-20.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Maximize value creation by ensuring the system is always performing useful work instead of waiting or idling."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-21",
      "title": "Skipping (Rushing Through)",
      "path": "TRIZ-bytes/TRIZ-21.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Reduce negative effects or inefficiencies by executing certain steps very quickly or bypassing them when their duration adds no value."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-22",
      "title": "Blessing in Disguise",
      "path": "TRIZ-bytes/TRIZ-22.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Turn a harmful effect or constraint into a useful feature instead of eliminating it."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-23",
      "title": "Feedback",
      "path": "TRIZ-bytes/TRIZ-23.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Improve control and outcomes by continuously feeding results back into the system to adjust behavior."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-24",
      "title": "Intermediary",
      "path": "TRIZ-bytes/TRIZ-24.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Reduce coupling and conflict by introducing an intermediate element that manages interaction between parts."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-25",
      "title": "Self-Service",
      "path": "TRIZ-bytes/TRIZ-25.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Reduce coordination cost and delays by letting a system or user perform needed actions independently."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-26",
      "title": "Copying",
      "path": "TRIZ-bytes/TRIZ-26.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Reduce cost, risk, or complexity by using copies, templates, or simplified representations instead of originals."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-27",
      "title": "Cheap Short-Living Objects",
      "path": "TRIZ-bytes/TRIZ-27.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Reduce risk and cost by using temporary, disposable, or easily replaceable elements instead of durable ones."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-28",
      "title": "Mechanics Substitution",
      "path": "TRIZ-bytes/TRIZ-28.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Replace rigid, manual, or mechanical approaches with more flexible, informational, or automated ones."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-29",
      "title": "Pneumatics and Hydraulics",
      "path": "TRIZ-bytes/TRIZ-29.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Transmit force, control, or influence indirectly through flexible, buffered media instead of rigid connections."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-30",
      "title": "Flexible Shells and Thin Films",
      "path": "TRIZ-bytes/TRIZ-30.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Protect core elements while keeping the system lightweight and adaptable by adding flexible, minimal protective layers."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-31",
      "title": "Porous Materials",
      "path": "TRIZ-bytes/TRIZ-31.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Increase adaptability and resilience by allowing controlled permeability instead of enforcing total isolation."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-32",
      "title": "Color Changes",
      "path": "TRIZ-bytes/TRIZ-32.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Improve understanding, control, and reaction speed by making system states and risks immediately visible."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-33",
      "title": "Homogeneity",
      "path": "TRIZ-bytes/TRIZ-33.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Reduce friction and complexity by making interacting elements similar in nature, structure, or rules."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-34",
      "title": "Discarding and Recovering",
      "path": "TRIZ-bytes/TRIZ-34.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Improve flow and resilience by intentionally removing elements when they are no longer useful, while keeping the ability to restore them if needed."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-35",
      "title": "Parameter Changes",
      "path": "TRIZ-bytes/TRIZ-35.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Improve outcomes by changing key parameters instead of redesigning the entire system."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-36",
      "title": "Phase Transitions",
      "path": "TRIZ-bytes/TRIZ-36.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Achieve step-change improvements by moving the system into a different operating state instead of incremental optimization."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-37",
      "title": "Thermal Expansion",
      "path": "TRIZ-bytes/TRIZ-37.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Exploit expansion, contraction, or elasticity effects to adapt to changing conditions without redesign."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-38",
      "title": "Strong Oxidants",
      "path": "TRIZ-bytes/TRIZ-38.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Achieve radical improvement by introducing a more powerful, transformative mechanism instead of incremental enhancement."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-39",
      "title": "Inert Atmosphere",
      "path": "TRIZ-bytes/TRIZ-39.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Stabilize sensitive operations by isolating them from disruptive external influences."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-40",
      "title": "Composite Materials",
      "path": "TRIZ-bytes/TRIZ-40.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "Combine different elements to achieve properties that none of them provide alone."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-TECH-01",
      "title": "Contradiction Formulation (Engineering Contradiction)",
      "path": "TRIZ-bytes/TRIZ-TECH-01.json",
      "tags": [],
      "entity_type": "triz_technique",
      "summary": "Turn a messy situation into a solvable TRIZ problem by expressing it as a trade-off between two parameters."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-TECH-02",
      "title": "Physical Contradiction + Separation Principles",
      "path": "TRIZ-bytes/TRIZ-TECH-02.json",
      "tags": [],
      "entity_type": "triz_technique",
      "summary": "Break a deadlock where the same parameter must be simultaneously high and low by separating requirements across conditions."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-TECH-03",
      "title": "System Operator (9 Windows)",
      "path": "TRIZ-bytes/TRIZ-TECH-03.json",
      "tags": [],
      "entity_type": "triz_technique",
      "summary": "Escape tunnel vision by analyzing the problem across time (past/present/future) and hierarchy (subsystem/system/supersystem)."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-TECH-04",
      "title": "X-Operator (Exaggeration / Extremes)",
      "path": "TRIZ-bytes/TRIZ-TECH-04.json",
      "tags": [],
      "entity_type": "triz_technique",
      "summary": "Force breakthrough ideas by pushing a system parameter to an extreme and observing what must change to make it work."
    },
    {
      "dataset": "TRIZ-bytes",
      "id": "TRIZ-XX",
      "title": "TRIZ Byte Template",
      "path": "TRIZ-bytes/TRIZ-XX.json",
      "tags": [],
      "entity_type": "triz_byte",
      "summary": "TRIZ Byte Template"
    },
    {
      "dataset": "agentic-bytes",
      "id": "agentic_dev_001",
      "title": "The Agent Loop: Observe → Plan → Act → Verify",
      "path": "agentic-bytes/agentic_dev_001.json",
      "tags": [
        "agent-loop",
        "react",
        "plan-execute",
        "verification",
        "reliability"
      ],
      "entity_type": "agentic_byte",
      "summary": "Understand the minimal mental model of an AI agent so you can explain it clearly and design it reliably."
    },
    {
      "dataset": "agentic-bytes",
      "id": "agentic_dev_002",
      "title": "Tools vs Chat: When an Agent Must Act, Not Just Talk",
      "path": "agentic-bytes/agentic_dev_002.json",
      "tags": [
        "tool-calling",
        "hallucination-prevention",
        "decision-rule",
        "agent-design"
      ],
      "entity_type": "agentic_byte",
      "summary": "Learn to clearly distinguish between 'thinking in text' and 'acting on the world', and explain why serious agents must use tools."
    },
    {
      "dataset": "agentic-bytes",
      "id": "agentic_dev_003",
      "title": "Output Contracts: Why Agents Must Speak JSON",
      "path": "agentic-bytes/agentic_dev_003.json",
      "tags": [
        "json-schema",
        "output-contracts",
        "agent-reliability",
        "automation"
      ],
      "entity_type": "agentic_byte",
      "summary": "Understand why strict output formats (JSON schemas) are critical for building agents you can trust, debug, and automate."
    },
    {
      "dataset": "agentic-bytes",
      "id": "agentic_dev_004",
      "title": "Chunking: How Knowledge Must Be Cut for RAG",
      "path": "agentic-bytes/agentic_dev_004.json",
      "tags": [
        "rag",
        "chunking",
        "knowledge-design",
        "retrieval-quality"
      ],
      "entity_type": "agentic_byte",
      "summary": "Learn how to structure knowledge so an agent can reliably retrieve and use it without confusion or hallucination."
    },
    {
      "dataset": "agentic-bytes",
      "id": "agentic_dev_005",
      "title": "Metadata: Teaching Agents What a Chunk Is About",
      "path": "agentic-bytes/agentic_dev_005.json",
      "tags": [
        "metadata",
        "rag",
        "knowledge-governance",
        "agent-control"
      ],
      "entity_type": "agentic_byte",
      "summary": "Understand how metadata turns raw text chunks into navigable, filterable, and trustworthy knowledge for agents."
    },
    {
      "dataset": "agentic-bytes",
      "id": "agentic_dev_006",
      "title": "Reranking: Choosing the Right Knowledge After Retrieval",
      "path": "agentic-bytes/agentic_dev_006.json",
      "tags": [
        "reranking",
        "rag",
        "retrieval",
        "answer-selection"
      ],
      "entity_type": "agentic_byte",
      "summary": "Understand why initial retrieval is not enough and how reranking helps an agent select the most relevant and safe knowledge."
    },
    {
      "dataset": "agentic-bytes",
      "id": "agentic_dev_007",
      "title": "Guardrails: What an Agent Is Never Allowed to Do",
      "path": "agentic-bytes/agentic_dev_007.json",
      "tags": [
        "guardrails",
        "agent-safety",
        "control",
        "production-agents"
      ],
      "entity_type": "agentic_byte",
      "summary": "Learn how to define hard boundaries so an agent behaves safely, predictably, and does not overstep its authority."
    },
    {
      "dataset": "agentic-bytes",
      "id": "agentic_dev_008",
      "title": "Self-Check / Critic: Teaching Agents to Verify Themselves",
      "path": "agentic-bytes/agentic_dev_008.json",
      "tags": [
        "self-check",
        "critic",
        "verification",
        "hallucination-control"
      ],
      "entity_type": "agentic_byte",
      "summary": "Understand how to add an explicit self-check step so agents catch their own mistakes before users do."
    },
    {
      "dataset": "agentic-bytes",
      "id": "agentic_dev_009",
      "title": "Plan → Execute: Separating Thinking from Doing",
      "path": "agentic-bytes/agentic_dev_009.json",
      "tags": [
        "plan-execute",
        "agent-control",
        "workflow",
        "reliability"
      ],
      "entity_type": "agentic_byte",
      "summary": "Learn why agents must separate planning from execution to stay controllable, debuggable, and safe."
    },
    {
      "dataset": "agentic-bytes",
      "id": "agentic_dev_010",
      "title": "Human-in-the-Loop: Where Agents Must Stop and Ask",
      "path": "agentic-bytes/agentic_dev_010.json",
      "tags": [
        "human-in-the-loop",
        "governance",
        "agent-autonomy",
        "trust"
      ],
      "entity_type": "agentic_byte",
      "summary": "Understand where and why an agent must defer to a human, and how to design clear handoff points."
    },
    {
      "dataset": "agentic-bytes",
      "id": "agentic_dev_011",
      "title": "Golden Set & Evals: How to Know Your Agent Works",
      "path": "agentic-bytes/agentic_dev_011.json",
      "tags": [
        "evaluation",
        "golden-set",
        "regression",
        "agent-quality"
      ],
      "entity_type": "agentic_byte",
      "summary": "Learn how to evaluate agents systematically so improvements do not break existing behavior."
    },
    {
      "dataset": "agentic-bytes",
      "id": "agentic_dev_012",
      "title": "Tracing & Observability: Making Agent Behavior Explainable",
      "path": "agentic-bytes/agentic_dev_012.json",
      "tags": [
        "tracing",
        "observability",
        "production-agents",
        "explainability"
      ],
      "entity_type": "agentic_byte",
      "summary": "Understand how to trace, inspect, and explain what an agent did, step by step, in production."
    },
    {
      "dataset": "agentic-bytes",
      "id": "agentic_dev_013",
      "title": "Memory: What Agents Should Remember (and Forget)",
      "path": "agentic-bytes/agentic_dev_013.json",
      "tags": [
        "agent-memory",
        "rag",
        "state-management",
        "knowledge-hygiene"
      ],
      "entity_type": "agentic_byte",
      "summary": "Understand different types of agent memory and how to use them without creating confusion, drift, or privacy risks."
    },
    {
      "dataset": "agentic-bytes",
      "id": "agentic_dev_014",
      "title": "Prompt Injection & RAG Defense: How Agents Protect Themselves",
      "path": "agentic-bytes/agentic_dev_014.json",
      "tags": [
        "prompt-injection",
        "rag-security",
        "agent-safety",
        "defense"
      ],
      "entity_type": "agentic_byte",
      "summary": "Learn how to prevent agents from being manipulated by user input or retrieved content, especially in RAG systems."
    },
    {
      "dataset": "agentic-bytes",
      "id": "agentic_dev_015",
      "title": "Cost & Latency Budgeting: Designing Agents That Are Economical",
      "path": "agentic-bytes/agentic_dev_015.json",
      "tags": [
        "cost-control",
        "latency",
        "agent-design",
        "scalability"
      ],
      "entity_type": "agentic_byte",
      "summary": "Understand how to design agents with predictable cost and latency, so they are usable at scale and acceptable for business."
    },
    {
      "dataset": "agentic-bytes",
      "id": "agentic_dev_016",
      "title": "Versioning: How Agents and Knowledge Evolve Safely",
      "path": "agentic-bytes/agentic_dev_016.json",
      "tags": [
        "versioning",
        "agent-lifecycle",
        "knowledge-management",
        "stability"
      ],
      "entity_type": "agentic_byte",
      "summary": "Learn how to change agents, prompts, and knowledge without breaking existing behavior or trust."
    },
    {
      "dataset": "agentic-bytes",
      "id": "agentic_dev_017",
      "title": "Failure Modes & Fallbacks: What Agents Do When Things Go Wrong",
      "path": "agentic-bytes/agentic_dev_017.json",
      "tags": [
        "failure-modes",
        "fallbacks",
        "agent-reliability",
        "production"
      ],
      "entity_type": "agentic_byte",
      "summary": "Understand the most common ways agents fail in production and how to design explicit fallback strategies instead of silent breakdowns."
    },
    {
      "dataset": "agentic-bytes",
      "id": "agentic_dev_018",
      "title": "Single-Agent vs Multi-Agent: When One Brain Is Enough",
      "path": "agentic-bytes/agentic_dev_018.json",
      "tags": [
        "single-agent",
        "multi-agent",
        "architecture",
        "coordination"
      ],
      "entity_type": "agentic_byte",
      "summary": "Understand when a single agent is sufficient and when splitting responsibilities across multiple agents makes systems more reliable and maintainable."
    },
    {
      "dataset": "agentic-bytes",
      "id": "agentic_dev_019",
      "title": "Agent Interfaces & Contracts: How Agents Communicate Safely",
      "path": "agentic-bytes/agentic_dev_019.json",
      "tags": [
        "agent-interfaces",
        "contracts",
        "multi-agent",
        "architecture"
      ],
      "entity_type": "agentic_byte",
      "summary": "Understand how agents should communicate with other agents and systems using strict contracts instead of free text."
    },
    {
      "dataset": "agentic-bytes",
      "id": "agentic_dev_020",
      "title": "Ownership, SLAs & Accountability: Who Is Responsible for the Agent",
      "path": "agentic-bytes/agentic_dev_020.json",
      "tags": [
        "ownership",
        "sla",
        "accountability",
        "operations"
      ],
      "entity_type": "agentic_byte",
      "summary": "Understand how to assign clear ownership and service expectations so agents can be operated like real systems, not experiments."
    },
    {
      "dataset": "agentic-bytes",
      "id": "agentic_dev_021",
      "title": "Business Value: Where Agents Create Real Impact (and Where They Don’t)",
      "path": "agentic-bytes/agentic_dev_021.json",
      "tags": [
        "business-value",
        "roi",
        "agent-use-cases",
        "product-thinking"
      ],
      "entity_type": "agentic_byte",
      "summary": "Learn to identify use cases where agents generate measurable business value, and avoid areas where they add complexity without payoff."
    },
    {
      "dataset": "agentic-bytes",
      "id": "agentic_dev_022",
      "title": "From Bytes to RAG: Assembling an Agent Knowledge Base",
      "path": "agentic-bytes/agentic_dev_022.json",
      "tags": [
        "rag-assembly",
        "knowledge-base",
        "agent-design",
        "scalability"
      ],
      "entity_type": "agentic_byte",
      "summary": "Learn how to turn individual bytes into a coherent RAG knowledge base that agents can reliably use in production."
    },
    {
      "dataset": "agentic-bytes",
      "id": "agentic_dev_023",
      "title": "Owning the Knowledge: Turning Bytes into a Personal Moat",
      "path": "agentic-bytes/agentic_dev_023.json",
      "tags": [
        "knowledge-ownership",
        "personal-moat",
        "agentic-strategy",
        "leverage"
      ],
      "entity_type": "agentic_byte",
      "summary": "Understand how structured agentic bytes become a long-term personal asset you can explain, reuse, sell, and build products on."
    },
    {
      "dataset": "ai-business-signals",
      "id": "aibs-001",
      "title": "Enterprise AI Deployment Is Real, but Data Complexity Still Blocks Scale",
      "path": "ai-business-signals/aibs-001.json",
      "tags": [
        "enterprise-ai",
        "adoption",
        "data-complexity",
        "skills-gap",
        "governance",
        "sap-relevance"
      ],
      "entity_type": "ai_business_signal",
      "summary": "Use current enterprise survey data to anchor conversations about AI rollout, skills gaps, and data readiness in large organizations."
    },
    {
      "dataset": "ai-business-signals",
      "id": "aibs-002",
      "title": "Employees Are Adopting AI Faster Than Company Governance",
      "path": "ai-business-signals/aibs-002.json",
      "tags": [
        "knowledge-work",
        "shadow-ai",
        "enterprise-governance",
        "training",
        "rollout"
      ],
      "entity_type": "ai_business_signal",
      "summary": "Capture the operational gap between employee AI usage and enterprise rollout discipline."
    },
    {
      "dataset": "ai-business-signals",
      "id": "aibs-003",
      "title": "AI Ambition Is Outrunning Workforce Readiness",
      "path": "ai-business-signals/aibs-003.json",
      "tags": [
        "readiness",
        "digital-adoption",
        "training",
        "roi",
        "enterprise-change"
      ],
      "entity_type": "ai_business_signal",
      "summary": "Show that AI investment alone does not create operational value without employee readiness and digital adoption."
    },
    {
      "dataset": "ai-business-signals",
      "id": "aibs-004",
      "title": "Supply Chain AI Strategy Remains Under-Formalized",
      "path": "ai-business-signals/aibs-004.json",
      "tags": [
        "supply-chain",
        "ai-strategy",
        "roi-pressure",
        "scale",
        "enterprise-architecture"
      ],
      "entity_type": "ai_business_signal",
      "summary": "Ground AI strategy discussions in supply chain data rather than generic enthusiasm."
    },
    {
      "dataset": "ai-business-signals",
      "id": "aibs-005",
      "title": "AI Is Already Operating at Scale in SAP Customer Support",
      "path": "ai-business-signals/aibs-005.json",
      "tags": [
        "sap",
        "support",
        "ai-operations",
        "ticketing",
        "knowledge-retrieval"
      ],
      "entity_type": "ai_business_signal",
      "summary": "Show an operational example of AI moving beyond demos into high-volume support workflows."
    },
    {
      "dataset": "ai-business-signals",
      "id": "aibs-006",
      "title": "C-Suites Are Trusting AI in Live Decision-Making",
      "path": "ai-business-signals/aibs-006.json",
      "tags": [
        "executives",
        "decision-making",
        "sap",
        "governance",
        "trust"
      ],
      "entity_type": "ai_business_signal",
      "summary": "Document how AI is entering executive decision loops in large enterprises."
    },
    {
      "dataset": "ai-business-signals",
      "id": "aibs-007",
      "title": "AI-Exposed Industries Are Widening the Productivity Gap",
      "path": "ai-business-signals/aibs-007.json",
      "tags": [
        "productivity",
        "revenue-per-employee",
        "skills",
        "wage-premium",
        "business-case"
      ],
      "entity_type": "ai_business_signal",
      "summary": "Anchor the AI value conversation in productivity, wage, and revenue-per-worker signals rather than generic hype."
    },
    {
      "dataset": "ai-business-signals",
      "id": "aibs-008",
      "title": "AI Value Comes From Workflow Redesign and Governance, Not Tools Alone",
      "path": "ai-business-signals/aibs-008.json",
      "tags": [
        "workflow-redesign",
        "governance",
        "ebit-impact",
        "enterprise-ai",
        "change-management"
      ],
      "entity_type": "ai_business_signal",
      "summary": "Capture the shift from AI experimentation to operating-model rewiring."
    },
    {
      "dataset": "ai-business-signals",
      "id": "aibs-009",
      "title": "Agentic AI Will Be Mainstream in Software, but Many Projects Will Still Fail",
      "path": "ai-business-signals/aibs-009.json",
      "tags": [
        "agents",
        "gartner",
        "project-failure",
        "roi",
        "legacy-integration",
        "enterprise-architecture"
      ],
      "entity_type": "ai_business_signal",
      "summary": "Separate durable agentic AI signals from hype and show where enterprise teams should be selective."
    },
    {
      "dataset": "ai-business-signals",
      "id": "aibs-010",
      "title": "Open Agent Protocols Are Becoming a Direct Anti-Lock-In Strategy",
      "path": "ai-business-signals/aibs-010.json",
      "tags": [
        "a2a",
        "interoperability",
        "vendor-lock-in",
        "linux-foundation",
        "agent-architecture",
        "sap-relevance"
      ],
      "entity_type": "ai_business_signal",
      "summary": "Document the shift toward open agent interoperability standards as a practical response to vendor lock-in."
    },
    {
      "dataset": "ai-business-signals",
      "id": "aibs-011",
      "title": "Open Source AI Is Being Valued for Productivity, Flexibility, and Lower Lock-In",
      "path": "ai-business-signals/aibs-011.json",
      "tags": [
        "open-source",
        "productivity",
        "lock-in",
        "tco",
        "interoperability",
        "digital-sovereignty"
      ],
      "entity_type": "ai_business_signal",
      "summary": "Anchor anti-lock-in and side-by-side architecture arguments in recent organizational research rather than opinion."
    },
    {
      "dataset": "ai-business-signals",
      "id": "aibs-012",
      "title": "SAP Is Publicly Framing Cross-Vendor Agent Collaboration as a Business Requirement",
      "path": "ai-business-signals/aibs-012.json",
      "tags": [
        "sap",
        "a2a",
        "model-choice",
        "side-by-side",
        "clean-core",
        "interoperability"
      ],
      "entity_type": "ai_business_signal",
      "summary": "Capture SAP’s explicit public position that enterprise agents must work across vendors and platforms."
    },
    {
      "dataset": "ai-business-signals",
      "id": "aibs-013",
      "title": "Modular Enterprise AI Stacks Are Being Positioned Against Single-Stack Dependence",
      "path": "ai-business-signals/aibs-013.json",
      "tags": [
        "opea",
        "modularity",
        "composable-ai",
        "vendor-independence",
        "local-deployment",
        "cost-control"
      ],
      "entity_type": "ai_business_signal",
      "summary": "Show that modular AI architecture is emerging as an explicit enterprise design principle, not just an engineering preference."
    },
    {
      "dataset": "ai-business-signals",
      "id": "aibs-014",
      "title": "MCP Is Becoming a Cross-Platform Standard Rather Than a Single-Vendor Connector",
      "path": "ai-business-signals/aibs-014.json",
      "tags": [
        "mcp",
        "agent-protocols",
        "vendor-neutral",
        "interoperability",
        "tooling",
        "architecture"
      ],
      "entity_type": "ai_business_signal",
      "summary": "Anchor agent integration strategy in an open standard that reduces connector rework and vendor dependency."
    },
    {
      "dataset": "ai-business-signals",
      "id": "aibs-015",
      "title": "Open Enterprise AI Is Explicitly Being Framed as Multi-Provider and Composable",
      "path": "ai-business-signals/aibs-015.json",
      "tags": [
        "opea",
        "multi-provider",
        "composable-ai",
        "open-source",
        "enterprise-architecture",
        "business-design"
      ],
      "entity_type": "ai_business_signal",
      "summary": "Support a build-versus-buy strategy centered on composability rather than proprietary platform dependence."
    },
    {
      "dataset": "ai-business-signals",
      "id": "aibs-016",
      "title": "SAP Clean Core Ties Decoupled Extensions Directly to Lower TCO",
      "path": "ai-business-signals/aibs-016.json",
      "tags": [
        "sap",
        "clean-core",
        "technical-debt",
        "tco",
        "side-by-side",
        "ams"
      ],
      "entity_type": "ai_business_signal",
      "summary": "Ground side-by-side modernization and AMS cost reduction in SAP’s own clean-core position."
    },
    {
      "dataset": "ai-business-signals",
      "id": "aibs-017",
      "title": "SAP Is Publicly Endorsing Framework Choice for Pro-Code Agent Development",
      "path": "ai-business-signals/aibs-017.json",
      "tags": [
        "framework-choice",
        "langgraph",
        "crewai",
        "a2a",
        "agent-governance",
        "sap"
      ],
      "entity_type": "ai_business_signal",
      "summary": "Capture the enterprise shift toward agent ecosystems that allow framework choice rather than a single mandated builder."
    },
    {
      "dataset": "ams",
      "id": "ams-001",
      "title": "Chat-First AMS: One Conversation, One Trace",
      "path": "ams/ams-001.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "Stop treating support like email archaeology. Run AMS through structured chats that automatically produce the evidence trail."
    },
    {
      "dataset": "ams",
      "id": "ams-002",
      "title": "Metrics That Hurt (in a Good Way)",
      "path": "ams/ams-002.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "If your metrics don’t change behavior, they are decorative. Modern AMS uses indicators that expose waste, risk, and fake progress."
    },
    {
      "dataset": "ams",
      "id": "ams-003",
      "title": "Stable SAP Core, Free Edges",
      "path": "ams/ams-003.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "The mistake is not SAP itself. The mistake is letting SAP define how expensive, slow, and locked-in your whole landscape becomes."
    },
    {
      "dataset": "ams",
      "id": "ams-004",
      "title": "No Fiori Dependency: AMS Runs on Signals, Not Screens",
      "path": "ams/ams-004.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "User interfaces age fast. Signals, events, and data contracts age slowly. AMS should operate on the latter."
    },
    {
      "dataset": "ams",
      "id": "ams-005",
      "title": "Don’t Carry Problems Forward: SAP AMS as a Load-Killing System",
      "path": "ams/ams-005.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "Old AMS accumulates pain and calls it backlog. Modern SAP AMS deletes load permanently."
    },
    {
      "dataset": "ams",
      "id": "ams-006",
      "title": "Contain Custom Code: Stop Z-Code from Owning AMS",
      "path": "ams/ams-006.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "Most SAP AMS pain is not caused by SAP standard. It’s caused by unmanaged custom code quietly becoming critical infrastructure."
    },
    {
      "dataset": "ams",
      "id": "ams-007",
      "title": "Standard Changes, Automated Execution",
      "path": "ams/ams-007.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "Speed in SAP AMS doesn’t come from shortcuts. It comes from removing choice where choice is unnecessary."
    },
    {
      "dataset": "ams",
      "id": "ams-008",
      "title": "AI-Augmented Diagnosis: Faster Thinking, Fewer Guess Cycles",
      "path": "ams/ams-008.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "SAP incidents are rarely hard because they are complex. They are hard because diagnosis starts blind."
    },
    {
      "dataset": "ams",
      "id": "ams-009",
      "title": "Choose What NOT to Fix: Data-Driven AMS Triage",
      "path": "ams/ams-009.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "If you try to fix everything in SAP, you end up fixing nothing well. Modern AMS is ruthless about priority — using data, not emotion."
    },
    {
      "dataset": "ams",
      "id": "ams-010",
      "title": "AMS Contracts That Don’t Lie: SLAs, SLOs, and Penalties With Teeth",
      "path": "ams/ams-010.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "Classic SAP AMS uses SLAs like makeup. Modern AMS uses measurable reliability targets tied to business flows — and penalties that punish the right behavior."
    },
    {
      "dataset": "ams",
      "id": "ams-011",
      "title": "Team Topology for SAP AMS: Fewer Handovers, Faster Fixes",
      "path": "ams/ams-011.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "Most SAP AMS slowness is not technical. It’s organizational latency: handovers, unclear ownership, and ‘not my module’."
    },
    {
      "dataset": "ams",
      "id": "ams-012",
      "title": "Approval Without Paralysis: Decision Gates That Actually Work",
      "path": "ams/ams-012.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "Approvals are not control. They are latency. Real control comes from clear gates, data, and reversible decisions."
    },
    {
      "dataset": "ams",
      "id": "ams-013",
      "title": "Coordination Without Noise: How SAP AMS Talks Under Pressure",
      "path": "ams/ams-013.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "Most outages get worse because communication collapses. Too many messages, no shared truth, and zero decision rhythm."
    },
    {
      "dataset": "ams",
      "id": "ams-014",
      "title": "Incentives That Shape Behavior: Teams, Bonuses, and Penalties",
      "path": "ams/ams-014.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "You get the AMS you pay for. If incentives reward speed and silence, you’ll get fragile fixes and hidden problems."
    },
    {
      "dataset": "ams",
      "id": "ams-015",
      "title": "Vendor and Internal Team Alignment: One System, Not a Battlefield",
      "path": "ams/ams-015.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "SAP AMS fails fastest when internal IT, vendors, and business optimize against each other instead of the system."
    },
    {
      "dataset": "ams",
      "id": "ams-016",
      "title": "Risk, Audit, and Control Without Slowing the System",
      "path": "ams/ams-016.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "Audit pressure usually makes SAP AMS slower and more defensive. Done right, it actually makes it calmer and cheaper."
    },
    {
      "dataset": "ams",
      "id": "ams-017",
      "title": "Upgrade and Release Insulation: Keep AMS Calm While SAP Changes",
      "path": "ams/ams-017.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "SAP releases don’t kill AMS. What kills AMS is when every upgrade becomes a surprise generator."
    },
    {
      "dataset": "ams",
      "id": "ams-018",
      "title": "Training That Pays Back: SAP AMS Enablement as a Ticket-Killer",
      "path": "ams/ams-018.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "Most AMS training is a one-off slideshow. Modern AMS training is a system that steadily deletes recurring demand."
    },
    {
      "dataset": "ams",
      "id": "ams-019",
      "title": "Handover Without Amnesia: Make Knowledge Survive People",
      "path": "ams/ams-019.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "AMS collapses not when systems change, but when people change. Bad handovers recreate the same incidents with new names."
    },
    {
      "dataset": "ams",
      "id": "ams-020",
      "title": "Knowledge Base as an Engine: Built for RAG, Not for Reading",
      "path": "ams/ams-020.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "A classic SAP KB is dead text. A modern AMS knowledge base is an execution engine for humans, bots, and AI."
    },
    {
      "dataset": "ams",
      "id": "ams-021",
      "title": "Ideas Pipeline: Turning SAP AMS Pain into Improvements",
      "path": "ams/ams-021.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "Good ideas don’t appear in workshops. They leak out of incidents, workarounds, and repeated frustration — if you know how to capture them."
    },
    {
      "dataset": "ams",
      "id": "ams-022",
      "title": "Continuous Learning Loop: AMS That Gets Smarter Every Month",
      "path": "ams/ams-022.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "If AMS knowledge doesn’t compound, you’re paying forever for the same lessons."
    },
    {
      "dataset": "ams",
      "id": "ams-023",
      "title": "Exit Without Shock: AMS as a Controlled SAP Lock-In Reducer",
      "path": "ams/ams-023.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "You don’t escape SAP by rewriting it. You escape SAP by slowly making it less central — without breaking the business."
    },
    {
      "dataset": "ams",
      "id": "ams-024",
      "title": "AMS as a Platform: Agents, Open Stack, and Composable Ops",
      "path": "ams/ams-024.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "When AMS stays a process, it caps its value. When AMS becomes a platform, it compounds."
    },
    {
      "dataset": "ams",
      "id": "ams-025",
      "title": "Security and SoD as a First-Class AMS Flow",
      "path": "ams/ams-025.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "In classic SAP AMS, security is a gate at the end. In modern AMS, security is a continuous flow that prevents incidents instead of reacting to them."
    },
    {
      "dataset": "ams",
      "id": "ams-026",
      "title": "Effort Estimation That Doesn’t Lie: Size, Risk, and Coordination Cost",
      "path": "ams/ams-026.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "In SAP AMS, bad estimates don’t just miss deadlines — they create chaos: wrong priorities, broken approvals, and hidden risk."
    },
    {
      "dataset": "ams",
      "id": "ams-027",
      "title": "Problem vs Change Portfolio: Stop Letting Changes Starve Prevention",
      "path": "ams/ams-027.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "SAP AMS usually drowns not because of too many incidents, but because Problems and Changes fight for the same oxygen — and Problems always lose."
    },
    {
      "dataset": "ams",
      "id": "ams-028",
      "title": "Backlog Hygiene: Keep SAP AMS Clean or It Will Rot",
      "path": "ams/ams-028.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "A dirty backlog is silent technical debt. It consumes attention, hides priorities, and creates fake urgency."
    },
    {
      "dataset": "ams",
      "id": "ams-029",
      "title": "Boards and Scorecards: Executive Visibility Without Theater",
      "path": "ams/ams-029.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "Most AMS reporting is designed to look busy. Modern AMS boards are designed to force decisions."
    },
    {
      "dataset": "ams",
      "id": "ams-030",
      "title": "Handover & Transition at Scale: Zero-Drama AMS Transfers",
      "path": "ams/ams-030.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "Most AMS transitions fail quietly. Not on day one — three months later, when the same incidents return and nobody remembers why."
    },
    {
      "dataset": "ams",
      "id": "ams-031",
      "title": "Crisis Mode (P0): Lead the System, Not the Noise",
      "path": "ams/ams-031.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "In a real SAP P0, technical skill matters less than control of flow, attention, and decisions."
    },
    {
      "dataset": "ams",
      "id": "ams-032",
      "title": "Financial Transparency: Know Where AMS Money Actually Goes",
      "path": "ams/ams-032.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "If you can’t explain why AMS costs what it costs, you can’t reduce it without breaking something important."
    },
    {
      "dataset": "ams",
      "id": "ams-033",
      "title": "Demand Forecasting & Capacity Planning: Stop Scheduling Surprises",
      "path": "ams/ams-033.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "SAP AMS feels ‘overloaded’ when demand is unmanaged and capacity is planned as if tomorrow will be like yesterday."
    },
    {
      "dataset": "ams",
      "id": "ams-034",
      "title": "AMS as a Product: Roadmap, Value Promises, and ‘Stop Doing’ Lists",
      "path": "ams/ams-034.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "If SAP AMS is treated as a service desk, it stays expensive forever. If it’s treated as a product, it becomes predictable, improvable, and cheaper over time."
    },
    {
      "dataset": "ams",
      "id": "ams-035",
      "title": "Master Data in AMS: Treat Data Quality as Production Reliability",
      "path": "ams/ams-035.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "In SAP, master data is not ‘data’. It’s executable configuration. Bad data behaves like bad code — it breaks flows, creates incidents, and burns AMS capacity."
    },
    {
      "dataset": "ams",
      "id": "ams-036",
      "title": "Change Intake & Agreement: Stop Negotiating Chaos",
      "path": "ams/ams-036.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "Most SAP AMS pain starts before any work begins — at intake. Vague requests turn into scope creep, rework, and unsafe changes."
    },
    {
      "dataset": "ams",
      "id": "ams-037",
      "title": "Conflict-Proof AMS: Multi-Vendor Reality Without Blame Games",
      "path": "ams/ams-037.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "Conflicts in SAP AMS don’t come from bad people. They come from unclear boundaries, mixed incentives, and missing evidence."
    },
    {
      "dataset": "ams",
      "id": "ams-038",
      "title": "Verification & Acceptance: Prove the Change Worked (or Don’t Close It)",
      "path": "ams/ams-038.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "Most SAP AMS work fails quietly at the end: changes are ‘done’, but nobody can prove the business is safer or faster."
    },
    {
      "dataset": "ams",
      "id": "ams-039",
      "title": "Knowledge → Automation → Agent Loop: Make Fixes Compound",
      "path": "ams/ams-039.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "If a fix lives only in a human’s head, AMS pays for it forever. Modern AMS turns fixes into reusable assets."
    },
    {
      "dataset": "ams",
      "id": "ams-040",
      "title": "AMS Culture Rules: Behavior That Makes the System Work",
      "path": "ams/ams-040.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "Processes don’t fail first in SAP AMS. Behavior does. Culture is the invisible control plane."
    },
    {
      "dataset": "ams",
      "id": "ams-041",
      "title": "AMS Operating System: How All Pieces Work as One",
      "path": "ams/ams-041.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "Modern SAP AMS fails when parts are optimized in isolation. It succeeds when everything is wired into a single operating system."
    },
    {
      "dataset": "ams",
      "id": "ams-042",
      "title": "Executive One-Pager: Modern SAP AMS in 5 Minutes",
      "path": "ams/ams-042.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "This AMS is designed to reduce risk and cost at the same time — without betting the business on big rewrites."
    },
    {
      "dataset": "ams",
      "id": "ams-043",
      "title": "Anti-Patterns Catalog: What Kills SAP AMS Faster Than Bugs",
      "path": "ams/ams-043.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "Most AMS disasters are not caused by SAP defects. They are caused by repeated bad patterns that everyone quietly tolerates."
    },
    {
      "dataset": "ams",
      "id": "ams-044",
      "title": "From Support to Trusted Advisor: Introducing New Capabilities Without Noise",
      "path": "ams/ams-044.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "New SAP or adjacent capabilities fail not because they are bad, but because AMS introduces them like features — instead of decisions."
    },
    {
      "dataset": "ams",
      "id": "ams-046",
      "title": "Vendor Segmentation & Operating Boundaries: How to Run Multi-Vendor AMS Cleanly",
      "path": "ams/ams-046.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "Multi-vendor AMS only works when boundaries are real: defined surfaces, measurable contracts, controlled access, and a single arbitration layer."
    },
    {
      "dataset": "ams",
      "id": "ams-047",
      "title": "Decision Support Factory: Making Reliable Estimates for Business Choices",
      "path": "ams/ams-047.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "The fastest way to become a trusted AMS provider is to stop answering with opinions — and start delivering decision packs that survive scrutiny."
    },
    {
      "dataset": "ams",
      "id": "ams-048",
      "title": "AMS Maturity Levels: From Firefighting to Decision Platform",
      "path": "ams/ams-048.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "Most SAP AMS teams believe they are mature because systems are running. Real maturity starts when the system improves itself."
    },
    {
      "dataset": "ams",
      "id": "ams-049",
      "title": "AMS Reputation Metrics: Measuring Trust, Not Ticket Volume",
      "path": "ams/ams-049.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "Reputation in AMS is not what people say in meetings. It’s what they do before problems appear."
    },
    {
      "dataset": "ams",
      "id": "ams-050",
      "title": "AMS as Risk Buffer: Absorbing Business Uncertainty Without Breaking SAP",
      "path": "ams/ams-050.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "SAP breaks not because change exists, but because risk is unmanaged. Modern AMS exists to absorb uncertainty — not to pretend it isn’t there."
    },
    {
      "dataset": "ams",
      "id": "ams-051",
      "title": "RAG-First Documentation: From Diagrams to Living Text Structures",
      "path": "ams/ams-051.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "Classic SAP documentation dies the moment reality changes. Diagrams freeze assumptions. Text structures evolve."
    },
    {
      "dataset": "ams",
      "id": "ams-052",
      "title": "TCO & ROI in Modern AMS: Measuring What Actually Matters",
      "path": "ams/ams-052.json",
      "tags": [],
      "entity_type": "ams_byte",
      "summary": "AMS cost is not what you pay the vendor. It’s what the system forces you to repeat."
    }
  ]
}