{
  "schemaVersion": "1.0",
  "product": "JIG—ME",
  "representation": "public site demonstration",
  "status": "Published presentation; owner approval of canonical facts pending",
  "entryPoints": [
    {
      "id": "home",
      "url": "index.html",
      "decision": "Understand the process or request an assessment",
      "dependsOn": [
        "how-it-works.html",
        "services.html",
        "case-studies.html"
      ]
    },
    {
      "id": "service",
      "url": "services.html",
      "decision": "Discuss the initial engagement and scope",
      "dependsOn": [
        "how-it-works.html",
        "contact.html"
      ]
    }
  ],
  "facts": [
    {
      "id": "J01",
      "statement": "An initial engagement maps the priority product entry points and buyer decisions.",
      "source": "services.html",
      "status": "published; approval pending"
    },
    {
      "id": "J02",
      "statement": "The supporting pages and audit boundary are agreed during the initial assessment.",
      "source": "services.html",
      "status": "published; approval pending"
    },
    {
      "id": "J03",
      "statement": "The assessment establishes a proposed scope and fee for the initial engagement.",
      "source": "services.html",
      "status": "published; approval pending"
    },
    {
      "id": "J04",
      "statement": "Several connected entry points may be reviewed in one engagement.",
      "source": "services.html",
      "status": "published; approval pending"
    },
    {
      "id": "J05",
      "statement": "The canonical fact list and page relationships are handed off as one JSON project with selected formats as needed.",
      "source": "how-it-works.html",
      "status": "published; approval pending"
    },
    {
      "id": "J06",
      "statement": "The client approves consequential product facts and qualifications before final output.",
      "source": "how-it-works.html",
      "status": "published; approval pending"
    }
  ],
  "audienceModes": [
    {
      "id": "product",
      "label": "Product / marketing",
      "question": "What do our pages actually promise?",
      "headline": "See where product meaning breaks across pages.",
      "description": "Trace what buyers encounter from the entry page to pricing, policy, and support. See conflicting claims, missing conditions, and the decisions your team needs to own.",
      "steps": [
        "Start with one buyer decision and its entry URL.",
        "Inspect source-linked claims across dependent pages.",
        "Approve the facts and map the corrections."
      ],
      "cta": "See the method",
      "href": "how-it-works.html",
      "factIds": [
        "J01",
        "J02",
        "J06"
      ]
    },
    {
      "id": "technical",
      "label": "Technical",
      "question": "What do we implement and maintain?",
      "headline": "One reviewed model, usable across destinations.",
      "description": "See the canonical facts, evidence, page dependencies, and audience applications in a single JSON project. Generate only the formats your site and systems need.",
      "steps": [
        "Identify the page and data consumers.",
        "Review the JSON record and source evidence.",
        "Validate the published output and define update owners."
      ],
      "cta": "See the examples",
      "href": "case-studies.html",
      "factIds": [
        "J05",
        "J06"
      ]
    },
    {
      "id": "owner",
      "label": "Founder / owner",
      "question": "What will I get, and what does it cost?",
      "headline": "Start with one product decision that matters.",
      "description": "A typical first engagement maps the priority product paths, audits source evidence, and guides your team through decisions in Product Atlas. The assessment sets a useful scope and fee for implementation and verification.",
      "steps": [
        "Choose a product and the decision a buyer must make.",
        "Review the evidence and settle the open questions.",
        "Receive the JSON project and selected implementation files."
      ],
      "cta": "See the service",
      "href": "services.html",
      "factIds": [
        "J01",
        "J02",
        "J03",
        "J05"
      ]
    }
  ]
}