{
  "releaseId": "r-3c7687664372c00d",
  "entries": [
    {
      "id": "mf-agent-developers",
      "slug": "agent-developers",
      "brand": "mirrorfirm",
      "canonicalTopic": "buyer-audiences",
      "audience": [
        "agent-developers"
      ],
      "workflows": [
        "cross-team handover"
      ],
      "question": "How does MirrorFirm help agent developers?",
      "summary": "Connected business tasks, including handovers and dependencies.",
      "claimStatus": "positioning",
      "evidenceStatus": "editorial",
      "url": "https://mirrorfirm.com/knowledge/buyer-audiences",
      "terms": [
        "agent",
        "agents",
        "and",
        "around",
        "build",
        "business",
        "can",
        "connected",
        "dependencies",
        "depends",
        "determine",
        "developers",
        "does",
        "evaluate",
        "finishes",
        "from",
        "given",
        "handovers",
        "happens",
        "help",
        "how",
        "including",
        "mirrorfirm",
        "next",
        "passes",
        "records",
        "scenario",
        "step",
        "tasks",
        "team",
        "tell",
        "that",
        "the",
        "what",
        "whether",
        "work"
      ]
    },
    {
      "id": "mf-approval-limits",
      "slug": "approval-limits",
      "brand": "mirrorfirm",
      "canonicalTopic": "approvals-and-connected-records",
      "audience": [
        "agent-developers",
        "evaluation-teams"
      ],
      "workflows": [
        "delegated approval",
        "credit escalation"
      ],
      "question": "How can an approval limit be turned into an evaluation task?",
      "summary": "Test when an agent should act and when it should escalate.",
      "claimStatus": "positioning",
      "evidenceStatus": "editorial",
      "url": "https://mirrorfirm.com/knowledge/approvals-and-connected-records",
      "terms": [
        "100000",
        "1042",
        "125000",
        "act",
        "action",
        "agent",
        "also",
        "and",
        "app",
        "application",
        "approval",
        "approve",
        "authority",
        "can",
        "escalate",
        "evaluation",
        "expected",
        "fictional",
        "how",
        "illustrative",
        "into",
        "limit",
        "question",
        "rather",
        "requests",
        "reviewer",
        "scenario",
        "should",
        "task",
        "test",
        "than",
        "the",
        "turned",
        "when"
      ]
    },
    {
      "id": "mf-changing-state",
      "slug": "changing-state",
      "brand": "mirrorfirm",
      "canonicalTopic": "state-and-environments",
      "audience": [
        "agent-developers",
        "environment-builders"
      ],
      "workflows": [],
      "question": "How does changing state shape the next task?",
      "summary": "Actions change what comes next, and the consequences can be inspected.",
      "claimStatus": "positioning",
      "evidenceStatus": "editorial",
      "url": "https://mirrorfirm.com/knowledge/state-and-environments",
      "terms": [
        "actions",
        "and",
        "approval",
        "around",
        "because",
        "build",
        "business",
        "can",
        "change",
        "changed",
        "changes",
        "changing",
        "check",
        "comes",
        "consequences",
        "created",
        "does",
        "earlier",
        "fictional",
        "how",
        "inspect",
        "inspected",
        "later",
        "next",
        "once",
        "only",
        "possible",
        "recorded",
        "repayment",
        "scenario",
        "scenarios",
        "schedule",
        "shape",
        "state",
        "step",
        "task",
        "that",
        "the",
        "their",
        "those",
        "what"
      ]
    },
    {
      "id": "mf-connected-records",
      "slug": "connected-records",
      "brand": "mirrorfirm",
      "canonicalTopic": "approvals-and-connected-records",
      "audience": [
        "environment-builders",
        "model-labs"
      ],
      "workflows": [
        "credit escalation"
      ],
      "question": "Why do records need to be connected?",
      "summary": "A decision affects an application, its policy and downstream work.",
      "claimStatus": "positioning",
      "evidenceStatus": "editorial",
      "url": "https://mirrorfirm.com/knowledge/approvals-and-connected-records",
      "terms": [
        "affects",
        "and",
        "application",
        "back",
        "between",
        "can",
        "connected",
        "decision",
        "downstream",
        "evaluation",
        "follow",
        "from",
        "identifiers",
        "its",
        "model",
        "more",
        "need",
        "one",
        "policy",
        "question",
        "record",
        "records",
        "relationships",
        "row",
        "starting",
        "than",
        "the",
        "why",
        "work",
        "you"
      ]
    },
    {
      "id": "mf-core-proposition",
      "slug": "core-proposition",
      "brand": "mirrorfirm",
      "canonicalTopic": "observed-business-foundation",
      "audience": [
        "model-labs",
        "agent-developers",
        "evaluation-teams",
        "environment-builders",
        "licensed-resellers"
      ],
      "workflows": [],
      "question": "What does MirrorFirm provide?",
      "summary": "Generated data and simulated environments for AI training and evaluation, informed by observed business operations.",
      "claimStatus": "positioning",
      "evidenceStatus": "editorial",
      "url": "https://mirrorfirm.com/knowledge/observed-business-foundation",
      "terms": [
        "and",
        "are",
        "ask",
        "available",
        "been",
        "before",
        "business",
        "data",
        "does",
        "environments",
        "evaluation",
        "for",
        "generated",
        "have",
        "informed",
        "into",
        "limitation",
        "mirrorfirm",
        "not",
        "observed",
        "operations",
        "positioning",
        "provide",
        "release",
        "releases",
        "relying",
        "say",
        "scope",
        "simulated",
        "specific",
        "statement",
        "the",
        "this",
        "training",
        "turns",
        "what",
        "which",
        "workflows"
      ]
    },
    {
      "id": "mf-custom-scope",
      "slug": "custom-scope",
      "brand": "mirrorfirm",
      "canonicalTopic": "scoping-and-evaluating-a-release",
      "audience": [
        "model-labs",
        "agent-developers",
        "evaluation-teams",
        "environment-builders",
        "licensed-resellers"
      ],
      "workflows": [],
      "question": "How is a custom scope defined?",
      "summary": "Objective, operating patterns, deliverable and evaluation criteria are scoped together.",
      "claimStatus": "positioning",
      "evidenceStatus": "editorial",
      "url": "https://mirrorfirm.com/knowledge/scoping-and-evaluating-a-release",
      "terms": [
        "and",
        "are",
        "before",
        "bring",
        "conversation",
        "criteria",
        "custom",
        "dataset",
        "decide",
        "defined",
        "deliverable",
        "environment",
        "evaluate",
        "evaluation",
        "form",
        "generated",
        "how",
        "objective",
        "operating",
        "pack",
        "patterns",
        "prefer",
        "relevant",
        "scope",
        "scoped",
        "simulated",
        "start",
        "task",
        "the",
        "together",
        "train",
        "training",
        "want",
        "what",
        "would",
        "you"
      ]
    },
    {
      "id": "mf-dataset-buyers",
      "slug": "dataset-buyers",
      "brand": "mirrorfirm",
      "canonicalTopic": "scoping-and-evaluating-a-release",
      "audience": [
        "licensed-resellers",
        "model-labs"
      ],
      "workflows": [],
      "question": "What should a dataset buyer inspect first?",
      "summary": "A small sample that exposes schema, relationships and business logic.",
      "claimStatus": "positioning",
      "evidenceStatus": "editorial",
      "url": "https://mirrorfirm.com/knowledge/scoping-and-evaluating-a-release",
      "terms": [
        "agreeing",
        "and",
        "aster",
        "before",
        "behind",
        "business",
        "buyer",
        "checklist",
        "dataset",
        "decisions",
        "demonstration",
        "does",
        "each",
        "example",
        "exposes",
        "fictional",
        "financial",
        "first",
        "how",
        "inspect",
        "larger",
        "link",
        "logic",
        "not",
        "other",
        "records",
        "relationships",
        "release",
        "rules",
        "sample",
        "schema",
        "shape",
        "should",
        "show",
        "small",
        "start",
        "that",
        "the",
        "this",
        "validated",
        "what",
        "with"
      ]
    },
    {
      "id": "mf-environment-builders",
      "slug": "environment-builders",
      "brand": "mirrorfirm",
      "canonicalTopic": "buyer-audiences",
      "audience": [
        "environment-builders"
      ],
      "workflows": [],
      "question": "What do environment builders get from MirrorFirm?",
      "summary": "Operating patterns translated into roles, records, tools and changing state.",
      "claimStatus": "positioning",
      "evidenceStatus": "editorial",
      "url": "https://mirrorfirm.com/knowledge/buyer-audiences",
      "terms": [
        "able",
        "agents",
        "and",
        "builders",
        "can",
        "changes",
        "changing",
        "does",
        "environment",
        "expose",
        "from",
        "get",
        "integration",
        "into",
        "later",
        "mirrorfirm",
        "must",
        "need",
        "operating",
        "patterns",
        "question",
        "records",
        "roles",
        "see",
        "state",
        "steps",
        "that",
        "tools",
        "translate",
        "translated",
        "what",
        "which",
        "with",
        "work",
        "your"
      ]
    },
    {
      "id": "mf-evaluation-teams",
      "slug": "evaluation-teams",
      "brand": "mirrorfirm",
      "canonicalTopic": "buyer-audiences",
      "audience": [
        "evaluation-teams"
      ],
      "workflows": [
        "delegated approval"
      ],
      "question": "How can evaluation teams use MirrorFirm?",
      "summary": "Evaluations around business decisions, policy boundaries and explicit outcomes.",
      "claimStatus": "positioning",
      "evidenceStatus": "editorial",
      "url": "https://mirrorfirm.com/knowledge/buyer-audiences",
      "terms": [
        "and",
        "around",
        "boundaries",
        "boundary",
        "business",
        "can",
        "decisions",
        "does",
        "each",
        "evaluation",
        "evaluations",
        "expected",
        "explicit",
        "for",
        "how",
        "informed",
        "mirrorfirm",
        "observed",
        "operations",
        "outcome",
        "outcomes",
        "policy",
        "question",
        "scope",
        "task",
        "teams",
        "test",
        "the",
        "use",
        "what",
        "which"
      ]
    },
    {
      "id": "mf-exceptions",
      "slug": "exceptions",
      "brand": "mirrorfirm",
      "canonicalTopic": "handovers-and-exceptions",
      "audience": [
        "agent-developers",
        "evaluation-teams"
      ],
      "workflows": [
        "credit escalation"
      ],
      "question": "Why build tasks around exceptions?",
      "summary": "The interesting work often begins when the standard path breaks.",
      "claimStatus": "positioning",
      "evidenceStatus": "editorial",
      "url": "https://mirrorfirm.com/knowledge/handovers-and-exceptions",
      "terms": [
        "action",
        "around",
        "before",
        "begins",
        "breaks",
        "build",
        "correct",
        "define",
        "evaluation",
        "exception",
        "exceptions",
        "expected",
        "generated",
        "interesting",
        "its",
        "limitation",
        "observed",
        "often",
        "only",
        "path",
        "patterns",
        "response",
        "shape",
        "standard",
        "stated",
        "task",
        "tasks",
        "the",
        "use",
        "useful",
        "using",
        "what",
        "when",
        "why",
        "work"
      ]
    },
    {
      "id": "mf-first-step",
      "slug": "first-step",
      "brand": "mirrorfirm",
      "canonicalTopic": "scoping-and-evaluating-a-release",
      "audience": [
        "model-labs",
        "agent-developers",
        "evaluation-teams",
        "environment-builders",
        "licensed-resellers"
      ],
      "workflows": [],
      "question": "What is a sensible first step?",
      "summary": "Inspect a sample, discuss the business logic and define what a pilot must demonstrate.",
      "claimStatus": "positioning",
      "evidenceStatus": "editorial",
      "url": "https://mirrorfirm.com/knowledge/scoping-and-evaluating-a-release",
      "terms": [
        "and",
        "business",
        "continuing",
        "define",
        "demonstrate",
        "discuss",
        "evaluation",
        "first",
        "how",
        "inspect",
        "logic",
        "make",
        "measured",
        "must",
        "needs",
        "pilot",
        "question",
        "result",
        "sample",
        "scoped",
        "sensible",
        "step",
        "successful",
        "the",
        "what",
        "will",
        "worth",
        "would"
      ]
    },
    {
      "id": "mf-generated-output",
      "slug": "generated-output",
      "brand": "mirrorfirm",
      "canonicalTopic": "observed-business-foundation",
      "audience": [
        "licensed-resellers",
        "model-labs"
      ],
      "workflows": [],
      "question": "Is MirrorFirm selling observed business data?",
      "summary": "The commercial product is generated data and environments; the observed foundation explains how they are built.",
      "claimStatus": "positioning",
      "evidenceStatus": "editorial",
      "url": "https://mirrorfirm.com/knowledge/observed-business-foundation",
      "terms": [
        "and",
        "are",
        "built",
        "business",
        "commercial",
        "considering",
        "construction",
        "data",
        "environments",
        "evaluation",
        "explains",
        "for",
        "foundation",
        "generated",
        "how",
        "mirrorfirm",
        "modelled",
        "observed",
        "product",
        "question",
        "release",
        "selling",
        "the",
        "their",
        "they",
        "was",
        "what",
        "you"
      ]
    },
    {
      "id": "mf-grounding-evidence",
      "slug": "grounding-evidence",
      "brand": "mirrorfirm",
      "canonicalTopic": "observed-business-foundation",
      "audience": [
        "evaluation-teams",
        "licensed-resellers"
      ],
      "workflows": [],
      "question": "How can a buyer inspect the grounding of a release?",
      "summary": "Separate what was observed, what was modelled and what was generated.",
      "claimStatus": "positioning",
      "evidenceStatus": "editorial",
      "url": "https://mirrorfirm.com/knowledge/observed-business-foundation",
      "terms": [
        "and",
        "apply",
        "ask",
        "behind",
        "boundaries",
        "business",
        "buyer",
        "can",
        "checklist",
        "checks",
        "from",
        "generated",
        "grounding",
        "how",
        "inspect",
        "logic",
        "make",
        "modelled",
        "observation",
        "observed",
        "outcomes",
        "output",
        "release",
        "rights",
        "separate",
        "should",
        "that",
        "the",
        "those",
        "understandable",
        "used",
        "useful",
        "was",
        "what"
      ]
    },
    {
      "id": "mf-handovers",
      "slug": "handovers",
      "brand": "mirrorfirm",
      "canonicalTopic": "handovers-and-exceptions",
      "audience": [
        "agent-developers",
        "environment-builders"
      ],
      "workflows": [
        "cross-team handover"
      ],
      "question": "Why do handovers matter in generated scenarios?",
      "summary": "Context, dependencies and responsibility move with the work.",
      "claimStatus": "positioning",
      "evidenceStatus": "editorial",
      "url": "https://mirrorfirm.com/knowledge/handovers-and-exceptions",
      "terms": [
        "action",
        "and",
        "application",
        "aster",
        "can",
        "changes",
        "check",
        "context",
        "credit",
        "dependencies",
        "example",
        "fictional",
        "financial",
        "from",
        "generated",
        "handovers",
        "hands",
        "holds",
        "identifies",
        "matter",
        "move",
        "moves",
        "next",
        "now",
        "origination",
        "passed",
        "preserve",
        "record",
        "responsibility",
        "scenario",
        "scenarios",
        "that",
        "the",
        "who",
        "why",
        "with",
        "work"
      ]
    },
    {
      "id": "mf-licensed-resellers",
      "slug": "licensed-resellers",
      "brand": "mirrorfirm",
      "canonicalTopic": "buyer-audiences",
      "audience": [
        "licensed-resellers"
      ],
      "workflows": [],
      "question": "What should a licensed reseller look for?",
      "summary": "An inspectable release, documented provenance and clear terms.",
      "claimStatus": "positioning",
      "evidenceStatus": "editorial",
      "url": "https://mirrorfirm.com/knowledge/buyer-audiences",
      "terms": [
        "and",
        "before",
        "buyer",
        "can",
        "checklist",
        "clear",
        "data",
        "documented",
        "for",
        "generated",
        "inspectable",
        "inspected",
        "intended",
        "intends",
        "licensed",
        "look",
        "match",
        "own",
        "provenance",
        "purchase",
        "release",
        "reseller",
        "should",
        "start",
        "terms",
        "the",
        "use",
        "what",
        "with",
        "your"
      ]
    },
    {
      "id": "mf-model-labs",
      "slug": "model-labs",
      "brand": "mirrorfirm",
      "canonicalTopic": "buyer-audiences",
      "audience": [
        "model-labs"
      ],
      "workflows": [],
      "question": "What can a model lab use MirrorFirm for?",
      "summary": "Richer business-operations material for model training.",
      "claimStatus": "positioning",
      "evidenceStatus": "editorial",
      "url": "https://mirrorfirm.com/knowledge/buyer-audiences",
      "terms": [
        "and",
        "business",
        "can",
        "carry",
        "consequences",
        "decision",
        "decisions",
        "downstream",
        "exceptions",
        "followed",
        "for",
        "generated",
        "give",
        "its",
        "lab",
        "material",
        "mirrorfirm",
        "model",
        "observed",
        "operations",
        "picture",
        "policy",
        "question",
        "records",
        "richer",
        "scenario",
        "shaped",
        "the",
        "together",
        "training",
        "use",
        "useful",
        "wants",
        "what",
        "whether",
        "which",
        "with",
        "work",
        "workflows"
      ]
    },
    {
      "id": "mf-multiple-teams",
      "slug": "multiple-teams",
      "brand": "mirrorfirm",
      "canonicalTopic": "handovers-and-exceptions",
      "audience": [
        "model-labs",
        "environment-builders"
      ],
      "workflows": [
        "cross-team handover"
      ],
      "question": "How are workflows that cross departments represented?",
      "summary": "Shared context is retained across departments.",
      "claimStatus": "positioning",
      "evidenceStatus": "editorial",
      "url": "https://mirrorfirm.com/knowledge/handovers-and-exceptions",
      "terms": [
        "across",
        "and",
        "application",
        "are",
        "aster",
        "back",
        "before",
        "business",
        "can",
        "collections",
        "complete",
        "connects",
        "context",
        "creating",
        "credit",
        "cross",
        "departments",
        "fictional",
        "financial",
        "generated",
        "how",
        "later",
        "map",
        "material",
        "original",
        "origination",
        "represented",
        "retain",
        "retained",
        "scenario",
        "servicing",
        "shared",
        "state",
        "team",
        "that",
        "the",
        "through",
        "trace",
        "training",
        "when",
        "workflow",
        "workflows"
      ]
    },
    {
      "id": "mf-origin-of-realism",
      "slug": "origin-of-realism",
      "brand": "mirrorfirm",
      "canonicalTopic": "observed-business-foundation",
      "audience": [
        "model-labs",
        "agent-developers",
        "evaluation-teams",
        "environment-builders",
        "licensed-resellers"
      ],
      "workflows": [],
      "question": "Where does the realism in MirrorFirm output come from?",
      "summary": "Access to real businesses informs what is generated.",
      "claimStatus": "positioning",
      "evidenceStatus": "editorial",
      "url": "https://mirrorfirm.com/knowledge/observed-business-foundation",
      "terms": [
        "access",
        "actually",
        "and",
        "ask",
        "before",
        "businesses",
        "come",
        "does",
        "from",
        "generate",
        "generated",
        "generation",
        "given",
        "how",
        "inform",
        "informed",
        "informs",
        "mirrorfirm",
        "modelled",
        "moves",
        "not",
        "observation",
        "observations",
        "operating",
        "our",
        "output",
        "patterns",
        "point",
        "real",
        "realism",
        "release",
        "starting",
        "the",
        "them",
        "they",
        "those",
        "through",
        "way",
        "were",
        "what",
        "where",
        "which",
        "work"
      ]
    },
    {
      "id": "mf-stateful-environments",
      "slug": "stateful-environments",
      "brand": "mirrorfirm",
      "canonicalTopic": "state-and-environments",
      "audience": [
        "environment-builders",
        "model-labs"
      ],
      "workflows": [],
      "question": "What is a stateful environment?",
      "summary": "Business operations as connected state with actions that affect later outcomes.",
      "claimStatus": "positioning",
      "evidenceStatus": "editorial",
      "url": "https://mirrorfirm.com/knowledge/state-and-environments",
      "terms": [
        "actions",
        "affect",
        "against",
        "agent",
        "and",
        "business",
        "check",
        "connected",
        "decisions",
        "environment",
        "expected",
        "exposed",
        "how",
        "integration",
        "later",
        "operations",
        "outcome",
        "outcomes",
        "question",
        "represent",
        "resulting",
        "state",
        "stateful",
        "that",
        "the",
        "what",
        "will",
        "with",
        "you",
        "your"
      ]
    },
    {
      "id": "mf-task-packs",
      "slug": "task-packs",
      "brand": "mirrorfirm",
      "canonicalTopic": "scoping-and-evaluating-a-release",
      "audience": [
        "agent-developers",
        "evaluation-teams"
      ],
      "workflows": [],
      "question": "What is in a task pack?",
      "summary": "A business objective with the policies, records and starting conditions to work through it.",
      "claimStatus": "positioning",
      "evidenceStatus": "editorial",
      "url": "https://mirrorfirm.com/knowledge/scoping-and-evaluating-a-release",
      "terms": [
        "accompany",
        "agent",
        "and",
        "business",
        "can",
        "checks",
        "conditions",
        "consistently",
        "criteria",
        "evaluation",
        "judged",
        "needs",
        "objective",
        "pack",
        "pair",
        "policies",
        "question",
        "records",
        "run",
        "starting",
        "success",
        "task",
        "the",
        "through",
        "what",
        "with",
        "work"
      ]
    }
  ]
}