[


  {
    "title": "AOI boundary example",
    "url": "/docs/examples/aoi-boundary/",
    "description": "A complete synthetic example of probabilistic AOI membership near a shared boundary.",
    "data": "Synthetic",
    "focus": "Measurement uncertainty",
    "reuse": "Uncertainty workflow",
    "output": "Probabilistic AOI membership and uncertainty-aware summaries",
    "boundary": "Synthetic geometry and error values are not empirical calibration evidence."
  },

  {
    "title": "All structural-QC issues in one synthetic table",
    "url": "/docs/examples/all-structural-qc-issues/",
    "description": "A fully synthetic GazeAudit example exercising all five implemented structural-QC issue families and all ten current diagnostic detail codes, with interpretation, decision, reporting, and limitation guidance.",
    "data": "Synthetic",
    "focus": "Data & QC",
    "reuse": "Complete structural-QC diagnostic and triage pattern",
    "output": "One review report plus row/group diagnostics covering all current issue families and detail-code types",
    "boundary": "Synthetic flags demonstrate software behavior; they are not default repair, retention, exclusion, or quality rules."
  },

  {
    "title": "Analysis-readiness example",
    "url": "/docs/examples/analysis-readiness/",
    "description": "Analysis-readiness example",
    "data": "Synthetic",
    "focus": "Data & QC",
    "reuse": "Readiness workflow",
    "output": "Readiness diagnostics and cohort-impact summary",
    "boundary": "Teaching workflow; readiness rules remain study-owned."
  },

  {
    "title": "Choose the right example",
    "url": "/docs/examples/choose-the-right-example/",
    "description": "A documentation-only walkthrough showing how to choose a GazeAudit example by learning need, data context, and output without treating catalog filtering as scientific method selection.",
    "data": "Documentation-only",
    "focus": "Documentation & API",
    "reuse": "Example-selection pattern",
    "output": "A chosen learning route with an explicit reason and boundary",
    "boundary": "Catalog filtering chooses learning material, not scientific methods or study parameters."
  },

  {
    "title": "Conclusion-rule edge cases",
    "url": "/docs/examples/conclusion-rule-edge-cases/",
    "description": "Deterministic synthetic examples for GazeAudit ConclusionRule covering missing tolerances, invalid thresholds, dual-tolerance conjunction, sign recovery, zero reference effects, threshold equality, circular-reference boundaries, and bounded reporting.",
    "data": "Synthetic",
    "focus": "Interpretation & reporting",
    "reuse": "Reference / tolerance / sign / recovery-threshold edge-case pattern",
    "output": "Deterministic branch-recovery tables and summary classifications",
    "boundary": "Teaching reference effects and tolerances are not recommended empirical thresholds or generic robustness rules."
  },

  {
    "title": "Decision-to-report worked example",
    "url": "/docs/examples/decision-to-report/",
    "description": "Use the deterministic synthetic robustness demo to practice declaring analytical choices, reading the complete 12-specification pattern, and translating it into bounded reporting language.",
    "data": "Synthetic",
    "focus": "Interpretation & reporting",
    "reuse": "Interpretation workflow",
    "output": "Bounded reporting language tied to a complete synthetic audit",
    "boundary": "Synthetic result patterns are not empirical evidence for another study."
  },

  {
    "title": "Declared → valid → successful",
    "url": "/docs/examples/specification-denominator-audit/",
    "description": "A fully synthetic GazeAudit specification-space exercise that separates the Cartesian declaration, pre-execution scientific validity, and technical execution outcomes in an 8 declared → 6 valid → 5 successful audit.",
    "data": "Synthetic",
    "focus": "Robustness & sensitivity",
    "reuse": "Declared → valid → successful denominator and failure-ledger pattern",
    "output": "An eight-combination declaration with six valid specifications, five successful endpoints, two predeclared-invalid combinations, and one preserved valid technical failure",
    "boundary": "The factors, levels, validity rule, failure, and estimates are teaching choices; they are not recommended detector, QC, AOI, or robustness decisions."
  },

  {
    "title": "Diagnostic interpretation walkthrough",
    "url": "/docs/examples/robustness-diagnostic-walkthrough/",
    "description": "A deterministic synthetic robustness example that moves from eight finite specification estimates through specification ordering, effect stability, marginal and pairwise sensitivity, plot routes, bounded interpretation, reporting, and an explicit incomplete-execution contrast.",
    "data": "Synthetic",
    "focus": "Interpretation & reporting",
    "reuse": "Finite-estimate → curve → stability → marginal/pairwise sensitivity → bounded reporting sequence",
    "output": "Eight-specification diagnostic tables, exact descriptive summaries, visual routes, and reporting language",
    "boundary": "The factors, estimates, diagnostic values, and interpretation thresholds are synthetic teaching material rather than empirical validation evidence."
  },

  {
    "title": "Documentation intent routing",
    "url": "/docs/examples/documentation-intent-routing/",
    "description": "A fully synthetic exercise showing how one research question moves through learning, task guidance, exact reference, and explanation without collapsing those purposes together.",
    "data": "Documentation-only",
    "focus": "Documentation & API",
    "reuse": "Navigation pattern",
    "output": "Intent-routed documentation path",
    "boundary": "Navigation routing does not select a scientific method."
  },

  {
    "title": "End-to-end robustness audit",
    "url": "/docs/examples/end-to-end-robustness/",
    "description": "Run a complete synthetic GazeAudit workflow from canonical study construction through specification execution, stability summaries, and sensitivity diagnostics.",
    "data": "Synthetic",
    "focus": "Robustness & sensitivity",
    "reuse": "Complete audit workflow",
    "output": "Specification results, stability summaries, and sensitivity diagnostics",
    "boundary": "Teaching specifications and endpoints must be rebuilt for a real study."
  },

  {
    "title": "Endpoint drift audit",
    "url": "/docs/examples/endpoint-drift-audit/",
    "description": "A fully synthetic worked example distinguishing acceptable specification variation from scientific endpoint drift in GazeAudit, including contrast reversal, unit mismatch, aggregation changes, different outcome families, and non-finite endpoint handling.",
    "data": "Synthetic",
    "focus": "Robustness & sensitivity",
    "reuse": "Common-endpoint invariance and drift-detection pattern",
    "output": "A branch-by-branch endpoint compatibility audit with corrected handoff rules",
    "boundary": "Synthetic endpoint scenarios teach comparability checks; they are not recommended eye-tracking endpoints or effect definitions."
  },

  {
    "title": "Example → study handoff",
    "url": "/docs/examples/example-to-study-handoff/",
    "description": "A fully synthetic walkthrough showing how to reuse the structure of a GazeAudit robustness example while replacing teaching values with explicitly declared study decisions.",
    "data": "Synthetic",
    "focus": "Project lifecycle",
    "reuse": "Example-to-study adaptation pattern",
    "output": "Study-owned decision inventory and handoff record",
    "boundary": "The walkthrough intentionally does not supply replacement scientific values."
  },

  {
    "title": "Failed-audit recovery walkthrough",
    "url": "/docs/examples/failed-audit-recovery/",
    "description": "A fully synthetic break-diagnose-repair example that preserves invalid combinations, valid technical failures, rerun history, and execution denominators.",
    "data": "Synthetic",
    "focus": "Robustness & sensitivity",
    "reuse": "Failure-recovery workflow",
    "output": "Preserved failure record, repaired rerun, and reconciled denominator",
    "boundary": "Technical repair must not change the scientific branch after outcome inspection."
  },

  {
    "title": "Failure → repair → reconciliation",
    "url": "/docs/examples/execution-ledger-reconciliation/",
    "description": "A fully synthetic GazeAudit execution-ledger example that preserves one invalid combination, one valid technical failure, one non-finite endpoint, one valid not-run branch, and successful repair reruns without changing the scientific specification denominator.",
    "data": "Synthetic",
    "focus": "Robustness & sensitivity",
    "reuse": "Branch identity → attempt history → repair lineage → current-state reconciliation pattern",
    "output": "A reconciled execution ledger separating 8 declared branches, 7 valid branches, historical attempt events, and current successful coverage",
    "boundary": "The failure types, repairs, endpoint values, and branch decisions are synthetic teaching material and are not recommended scientific rules."
  },

  {
    "title": "First real audit example",
    "url": "/docs/examples/first-real-audit/",
    "description": "Run one practical GazeAudit script on deterministic demo data or a canonical eye-tracking CSV and save structural-QC provenance plus robustness tables.",
    "data": "Demo or user data",
    "focus": "Data & QC",
    "reuse": "Project template",
    "output": "Structural-QC provenance and robustness tables",
    "boundary": "Demo choices must be replaced or justified before use on a real study."
  },

  {
    "title": "Function to evidence walkthrough",
    "url": "/docs/examples/function-to-evidence/",
    "description": "A fully synthetic navigation exercise that starts from a GazeAudit public symbol and follows its governed path to a guide, runnable example, visual, and evidence boundary.",
    "data": "Documentation-only",
    "focus": "Documentation & API",
    "reuse": "Symbol-to-context navigation pattern",
    "output": "Function-to-guide-example-visual-evidence route",
    "boundary": "Linked validation evidence remains protocol-bound."
  },

  {
    "title": "Generated API call contracts",
    "url": "/docs/examples/api-call-contracts/",
    "description": "A fully synthetic interface-reading exercise for required positional arguments, required keyword-only arguments, all-optional signatures, return annotations, and minimal call shapes.",
    "data": "Documentation-only",
    "focus": "Documentation & API",
    "reuse": "Interface-reading pattern",
    "output": "Interpreted parameter, return, and minimal-call contracts",
    "boundary": "Software-call structure does not choose scientific values."
  },

  {
    "title": "Install, verify, first import",
    "url": "/docs/examples/install-smoke-check/",
    "description": "A software-only GazeAudit smoke check for a fresh virtual environment, optional extras, package identity, public imports, and console commands.",
    "data": "Software-only",
    "focus": "Environment",
    "reuse": "Installation verification workflow",
    "output": "Verified package identity, imports, CLI, and environment record",
    "boundary": "Successful installation does not establish scientific validity."
  },

  {
    "title": "Mapping change audit",
    "url": "/docs/examples/data-mapping-change-audit/",
    "description": "A fully synthetic provenance exercise showing how source-column renames, source-version changes, unit conversions, coordinate transforms, grouping changes, and exclusions affect the data-mapping record.",
    "data": "Synthetic",
    "focus": "Data & QC",
    "reuse": "Mapping-change classification pattern",
    "output": "A before/after mapping comparison with an explicit rerun decision",
    "boundary": "A mapping-provenance record improves reconstruction but does not certify preprocessing or scientific validity."
  },

  {
    "title": "Project lifecycle walkthrough",
    "url": "/docs/examples/project-lifecycle-walkthrough/",
    "description": "A fully synthetic five-stage GazeAudit walkthrough from planning and audit execution through interpretation, peer-review amendment, and final handoff.",
    "data": "Synthetic",
    "focus": "Project lifecycle",
    "reuse": "Project-stage workflow",
    "output": "Five-stage project record from planning through final handoff",
    "boundary": "Synthetic project decisions are teaching choices, not a protocol."
  },

  {
    "title": "Publication and archive handoff example",
    "url": "/docs/examples/publication-archive-handoff/",
    "description": "Walk through an illustrative manuscript and archive handoff that connects a decision record, complete robustness evidence, scoped wording, provenance, and reproducibility metadata.",
    "data": "Synthetic",
    "focus": "Peer review & publication",
    "reuse": "Publication handoff pattern",
    "output": "Manuscript/archive evidence map and reproducibility handoff",
    "boundary": "Archive completeness does not by itself establish scientific validity."
  },

  {
    "title": "Readiness policy design",
    "url": "/docs/examples/readiness-policy-design/",
    "description": "A fully synthetic worked example for declaring a primary and alternative GazeAudit readiness policy, previewing trial- versus participant-scope cohort consequences, interpreting policy-relative status, and writing bounded Methods, Results, and limitations text.",
    "data": "Synthetic",
    "focus": "Data & QC",
    "reuse": "Readiness-policy declaration, comparison, denominator, and reporting pattern",
    "output": "Primary/alternative readiness policies with policy-relative status and trial/participant cohort-impact interpretation",
    "boundary": "All threshold values are teaching choices for this synthetic fixture; they are not recommended eye-tracking cutoffs."
  },

  {
    "title": "Reference lookup walkthrough",
    "url": "/docs/examples/reference-lookup-workflow/",
    "description": "A fully synthetic example showing how to answer exact API, denominator, failure, CLI, and frozen-label questions by moving through the GazeAudit reference layer.",
    "data": "Documentation-only",
    "focus": "Documentation & API",
    "reuse": "Reference lookup pattern",
    "output": "Authoritative API, CLI, denominator, or evidence lookup route",
    "boundary": "Reference lookup states contracts; it does not choose research decisions."
  },

  {
    "title": "Reporting-language rewrite",
    "url": "/docs/examples/reporting-language-rewrite/",
    "description": "A fully synthetic worked exercise that rewrites over-strong GazeAudit manuscript claims into evidence-bounded Methods, Results, and limitation language while preserving runtime status, denominator, execution completeness, and protocol scope.",
    "data": "Synthetic",
    "focus": "Interpretation & reporting",
    "reuse": "Evidence object → denominator → claim boundary → bounded rewrite pattern",
    "output": "Seven repaired manuscript claims with explicit evidence and limitation boundaries",
    "boundary": "The sentences are synthetic teaching material; they are not manuscript claims about any real study."
  },

  {
    "title": "Result-pattern reporting example",
    "url": "/docs/examples/result-patterns/",
    "description": "Compare four synthetic robustness patterns to practise separating execution completeness, direction stability, magnitude sensitivity, and bounded manuscript wording.",
    "data": "Synthetic",
    "focus": "Interpretation & reporting",
    "reuse": "Result-pattern interpretation workflow",
    "output": "Bounded wording for stable, sensitive, sign-changing, and incomplete audits",
    "boundary": "Synthetic patterns teach interpretation; they are not empirical priors."
  },

  {
    "title": "Reviewer reconstruction worked example",
    "url": "/docs/examples/reviewer-reconstruction/",
    "description": "Walk through an illustrative GazeAudit manuscript archive as a reviewer and identify what is reconstructable, what is missing, and what must be repaired before submission.",
    "data": "Synthetic",
    "focus": "Peer review & publication",
    "reuse": "Reviewer reconstruction workflow",
    "output": "Reconstructed claim path plus missing-evidence diagnosis",
    "boundary": "The synthetic archive is for review practice, not empirical validation."
  },

  {
    "title": "Reviewer-requested reanalysis worked example",
    "url": "/docs/examples/reviewer-requested-reanalysis/",
    "description": "Extend a synthetic submitted GazeAudit record with a reviewer-requested sensitivity analysis while preserving the original denominator, decision history, and manuscript provenance.",
    "data": "Synthetic",
    "focus": "Peer review & publication",
    "reuse": "Post-review amendment workflow",
    "output": "Separate submitted and reviewer-requested evidence layers",
    "boundary": "Post-review analyses must not be relabelled as pre-specified."
  },

  {
    "title": "Revision reproducibility package worked example",
    "url": "/docs/examples/reproducibility-package-cli/",
    "description": "A synthetic executable-style example that scaffolds a reviewer-revision package, records separate submitted and post-review evidence, demonstrates a missing-file failure, and validates the repaired structure.",
    "data": "Synthetic",
    "focus": "Reproducibility",
    "reuse": "CLI package workflow",
    "output": "Validated reviewer-revision package with failure-repair history",
    "boundary": "Structural package validity is not scientific validation."
  },

  {
    "title": "Revision response package worked example",
    "url": "/docs/examples/revision-response-package/",
    "description": "A synthetic peer-review response package linking reviewer requests to amendment timing, separate denominators, manuscript edits, and archived revision evidence.",
    "data": "Synthetic",
    "focus": "Peer review & publication",
    "reuse": "Reviewer-response evidence pattern",
    "output": "Linked response, amendment, manuscript-change, and archive records",
    "boundary": "Response structure cannot substitute for justified analysis decisions."
  },

  {
    "title": "Revision-package quickstart",
    "url": "/docs/examples/revision-package-quickstart/",
    "description": "Synthetic end-to-end quickstart for creating, populating, validating, and handing off a reviewer-revision provenance package with the real GazeAudit CLI.",
    "data": "Synthetic",
    "focus": "Peer review & publication",
    "reuse": "Revision-package workflow",
    "output": "Created, populated, and structurally validated revision package",
    "boundary": "Package validity establishes provenance structure, not scientific validity."
  },

  {
    "title": "Revision-round routing scenarios",
    "url": "/docs/examples/revision-round-scenarios/",
    "description": "Synthetic peer-review scenarios showing clarification, correction, sensitivity amendments, incomplete post-review execution, endpoint amendments, response records, and revision-package handoff.",
    "data": "Synthetic",
    "focus": "Peer review & publication",
    "reuse": "Revision routing scenarios",
    "output": "Scenario-specific clarification, correction, amendment, and handoff routes",
    "boundary": "Scenario routes are teaching cases, not editorial rules."
  },

  {
    "title": "Sampling sensitivity example",
    "url": "/docs/examples/sampling-sensitivity/",
    "description": "Downsample a synthetic GazeStudy to controlled target rates and inspect endpoint stability.",
    "data": "Synthetic",
    "focus": "Robustness & sensitivity",
    "reuse": "Sampling sensitivity workflow",
    "output": "Endpoint stability across controlled target sampling rates",
    "boundary": "Synthetic target rates do not define acceptable sampling for another study."
  },

  {
    "title": "Search to contract walkthrough",
    "url": "/docs/examples/search-to-contract/",
    "description": "A fully synthetic example showing how grouped GazeAudit search results lead from an ambiguous query to the correct guide, example, reference, or evidence authority.",
    "data": "Documentation-only",
    "focus": "Documentation & API",
    "reuse": "Search-to-authority navigation pattern",
    "output": "Grouped search path to the relevant documentation authority",
    "boundary": "Search ranking is navigation support, not method ranking."
  },

  {
    "title": "Sensitivity protocol worked example",
    "url": "/docs/examples/sensitivity-protocol/",
    "description": "Build a deterministic synthetic sampling and missingness sensitivity protocol, preserve the declared grid, plot complete curves, and write bounded interpretation.",
    "data": "Synthetic",
    "focus": "Robustness & sensitivity",
    "reuse": "Predeclared perturbation protocol",
    "output": "Sampling and missingness sensitivity tables with reproducible plots and bounded reporting",
    "boundary": "The synthetic ranges and endpoint are teaching values, not recommended thresholds or acquisition standards."
  },

  {
    "title": "Source-level API inspection",
    "url": "/docs/examples/source-api-inspection/",
    "description": "A fully synthetic documentation exercise showing how to verify GazeStudy, run_specs, and aoi_probabilities from generated signatures through source links and governed pathways.",
    "data": "Documentation-only",
    "focus": "Documentation & API",
    "reuse": "Source-inspection workflow",
    "output": "Verified signatures, source links, and pathway context",
    "boundary": "Source inspection describes implementation; it does not justify study choices."
  },

  {
    "title": "Specification curve example",
    "url": "/docs/examples/specification-curve/",
    "description": "Summarise synthetic multiverse results with ordered estimates, sign stability, and factor sensitivity.",
    "data": "Synthetic",
    "focus": "Robustness & sensitivity",
    "reuse": "Specification-curve workflow",
    "output": "Ordered estimates, sign stability, and factor sensitivity summaries",
    "boundary": "Synthetic specifications illustrate mechanics; they are not recommended defaults."
  },

  {
    "title": "Study preflight example",
    "url": "/docs/examples/study-preflight/",
    "description": "Run structural QC, inspect row/group diagnostics, record decisions, and preserve deterministic provenance.",
    "data": "Synthetic",
    "focus": "Data & QC",
    "reuse": "Structural-preflight workflow",
    "output": "Structural QC diagnostics, decision record, and provenance",
    "boundary": "Structural QC flags are not automatic scientific exclusions."
  },

  {
    "title": "Submission-to-accepted-record worked example",
    "url": "/docs/examples/submission-to-accepted-record/",
    "description": "A synthetic end-to-end revision example that preserves submitted evidence, reviewer-requested amendments, response records, version changes, and the final editor-facing archive as separate temporal layers.",
    "data": "Synthetic",
    "focus": "Peer review & publication",
    "reuse": "Submission-to-handoff workflow",
    "output": "Temporally separated submitted, amended, and final editor-facing records",
    "boundary": "Revision chronology preserves provenance; it does not certify scientific correctness."
  },

  {
    "title": "Valid, invalid, and reviewable tables",
    "url": "/docs/examples/data-contract-valid-invalid/",
    "description": "A fully synthetic walkthrough showing which table conditions prevent GazeStudy construction, which construct but require structural review, and which checks belong downstream.",
    "data": "Synthetic",
    "focus": "Data & QC",
    "reuse": "Schema-validation and preflight pattern",
    "output": "A classified set of constructor failures and structural-review conditions",
    "boundary": "Passing the constructor or structural preflight does not establish measurement or scientific validity."
  }

]