Is this IG AST still valid for the IG’s current inputs?

Run folio-assistant-core’s compiledValidity on an AST manifest’s inputs: recompute the input digest (the same algorithm as the Java writer, pinned by a shared golden vector) and the source revision, and answer valid, stale-inputs (naming which input), or cannot-tell.

Skills it satisfies

A skill states the capability; this Tool is one way to exercise it. Each skill’s declared input and output contract follows, where it has one.

ig-ast-delta

List and view what changed between two IG ASTs, check whether an AST is still valid for the IG’s current inputs, and render the delta as just-the-docs pages that carry the provisional mark. Read before trusting a cached AST, before reviewing an incremental IG build, and before rendering anything from a cache.

Source: fhir-harness/skills/fhir-ig-base/ig-ast-delta.md.

Also satisfied by: ig-ast-diff, ig-ast-jsonld, ig-ast-list, ig-ast-pages, ig-ast-plan, ig-ast-render, ig-cache.

The skill declares no I/O contract (schemas/skills/ig-ast-delta/{input,output}.schema.json).

Inputs and outputs

Each port names a shared type by IRI, so two Tools for one skill can be checked for interchangeability.

porttyperequireddescriptionconstraint
inastFilesystemPathyesstring · A filesystem path, possibly outside the repository. Not admissible as a command-line argument.
inigFilesystemPathyesstring · A filesystem path, possibly outside the repository. Not admissible as a command-line argument.
intoolchainTextThe Publisher that would run now. Without it the toolchain is ASSUMED unchanged, and the result says so.string · A short single-line human string. Not admissible as a command-line argument.
outverdictTextExit 0 valid, 1 stale-inputs, 2 cannot-tell. Cannot-tell is never a pass.string · A short single-line human string. Not admissible as a command-line argument.

Processes and tasks

Steps this Tool can carry out, because each names a skill it satisfies:

processsteplanevia skill
Is the incremental IG AST what a full build would have produced?Check the base AST against the inputsIncremental build (system)ig-ast-delta
Is the incremental IG AST what a full build would have produced?Diff the two ASTsIncremental build (system)ig-ast-delta
Is the incremental IG AST what a full build would have produced?Read the deltaQC reviewerig-ast-delta
An IG site, built from the AST on its cache branchRestore and judge the cached ASTSite build (agent, stage-local)ig-ast-delta
SMART Guideline end to endReview each L3 asset (before / after if adapted)Human adjudicatorsig-ast-delta

How it is deployed and reached

  • Command line. From the repository root: bun run fhir-harness/scripts/ig-ast.ts validity <ast> --ig <root> [--toolchain <s>].
  • GitHub Actions. 11 workflow line(s) run its command:
workflowline
fhir-harness/.github/workflows/ig-ast-refresh.yml173bun run fhir-harness/scripts/ig-ast.ts validity output-ast --ig . > "$RUNNER_TEMP/ast-validity.json"
fhir-harness/.github/workflows/ig-ast-refresh.yml177bun run fhir-harness/scripts/ig-ast.ts cache-line output-ast --ig . 2>/dev/null \|\| true
fhir-harness/.github/workflows/ig-ast-refresh.yml199kind=$(bun run fhir-harness/scripts/ig-ast.ts build-kind output-ast 2>/dev/null \|\| echo full)
fhir-harness/.github/workflows/ig-ast-refresh.yml427&& bun run fhir-harness/scripts/ig-ast.ts validity output-ast --ig . > /dev/null; then
fhir-harness/.github/workflows/ig-ast-refresh.yml430kind=$(bun run fhir-harness/scripts/ig-ast.ts build-kind output-ast 2>/dev/null \|\| echo incremental)
fhir-harness/.github/workflows/ig-ast-refresh.yml433bun run fhir-harness/scripts/ig-ast.ts cache-line output-ast --ig . --warm 2>/dev/null \|\| true
fhir-harness/.github/workflows/ig-ast-refresh.yml459source_digest=$(bun run fhir-harness/scripts/ig-ast.ts digest --ig .) \\
fhir-harness/.github/workflows/ig-ast-refresh.yml498now=$(bun run fhir-harness/scripts/ig-ast.ts digest --ig .)
fhir-harness/.github/workflows/ig-ast-refresh.yml501bun run fhir-harness/scripts/ig-ast.ts source-inputs output-ast --digest "$source_digest" --pre-export "$PRE_EXPORT"
fhir-harness/.github/workflows/ig-ast-refresh.yml505bun run fhir-harness/scripts/ig-ast.ts validity output-ast --ig . \\
fhir-harness/.github/workflows/ig-release.yml123bun run fhir-harness/scripts/ig-ast.ts build-kind "$IN/output-ast" --require-full

As an API: its operation in the OpenAPI document and the MCP tool list of its layer.

installnone
runtimebun, git
networkno
when to choose it
whenBefore trusting, planning against, or rendering from a cached AST.
limitsValid means built from these inputs, not built correctly.
costReads input/ once to hash it.

What it is made of

Linked data

The Tool is published as its own JSON-LD document at its IRI, https://litlfred.github.io/folio-assistant/fhir-harness/tools/ig-ast-validity.jsonld, partOf its layer’s document. The node below is the definition this page was drawn from, and is embedded in the page as application/ld+json.

{
  "@context": "https://litlfred.github.io/folio-assistant/fhir-harness/fhir-harness.context.jsonld",
  "@id": "https://litlfred.github.io/folio-assistant/fhir-harness/tools/ig-ast-validity.jsonld",
  "@type": "https://litlfred.github.io/cat-harness/v0/ns/Tool",
  "partOf": "https://litlfred.github.io/folio-assistant/fhir-harness/fhir-harness.jsonld",
  "name": "ig-ast-validity",
  "title": "Is this IG AST still valid for the IG's current inputs?",
  "description": "Run folio-assistant-core's `compiledValidity` on an AST manifest's `inputs`: recompute the input digest (the same algorithm as the Java writer, pinned by a shared golden vector) and the source revision, and answer valid, stale-inputs (naming which input), or cannot-tell.",
  "install": {
    "none": true
  },
  "invoke": {
    "shell": "bun run fhir-harness/scripts/ig-ast.ts validity <ast> --ig <root> [--toolchain <s>]"
  },
  "io": {
    "inputs": [
      {
        "name": "ast",
        "schema": "https://litlfred.github.io/folio-assistant/cat-harness/tool-types.schema.json#/$defs/FilesystemPath",
        "required": true
      },
      {
        "name": "ig",
        "schema": "https://litlfred.github.io/folio-assistant/cat-harness/tool-types.schema.json#/$defs/FilesystemPath",
        "required": true
      },
      {
        "name": "toolchain",
        "schema": "https://litlfred.github.io/folio-assistant/cat-harness/tool-types.schema.json#/$defs/Text",
        "description": "The Publisher that would run now. Without it the toolchain is ASSUMED unchanged, and the result says so.",
        "required": false
      }
    ],
    "outputs": [
      {
        "name": "verdict",
        "schema": "https://litlfred.github.io/folio-assistant/cat-harness/tool-types.schema.json#/$defs/Text",
        "description": "Exit 0 valid, 1 stale-inputs, 2 cannot-tell. Cannot-tell is never a pass."
      }
    ]
  },
  "satisfies": [
    "ig-ast-delta"
  ],
  "requirements": {
    "runtime": [
      "bun",
      "git"
    ],
    "network": false
  },
  "selection": {
    "when": "Before trusting, planning against, or rendering from a cached AST.",
    "limits": "Valid means built from these inputs, not built correctly.",
    "cost": "Reads `input/` once to hash it."
  }
}

folio-assistant — code under the Apache License 2.0, documentation under CC BY 3.0. Generated schema and API references are rebuilt from source on every push to main.

deployed dev