JSON Schemas

These are the stable $id URLs referenced by PtcRunner documents. Point your editor at one to get completion and validation while authoring:

{
  "$schema": "https://ptc-runner.dev/schemas/ptc-project-config.schema.json",
  "kind": "ptc-project",
  "version": 1,
  "application": {"path": "ptc.json"}
}

PtcRunner keeps three roles in three separate files. Credential values and provider declarations do not belong in the project file, and project choices do not become part of application content identity.

ptc-project-config.schema.json

operator or project checkout

ptc-project.json — paths to the other files, local artifact policy, and Viewer preferences. This is the document you hand to ptc run, ptc doctor, ptc repl, and ptc viewer.

https://ptc-runner.dev/schemas/ptc-project-config.schema.json

ptc-application-manifest.schema.json

application author or model

ptc.json — workflow, components, input, provider selections, and narrower limits. Model-authorable application selection; runtime loading remains authoritative.

https://ptc-runner.dev/schemas/ptc-application-manifest.schema.json

ptc-host-config.schema.json

operator

ptc-host.json — installed providers, credential references, commands, endpoints, and outer limits. Operator-owned provider installation; runtime loading remains authoritative.

https://ptc-runner.dev/schemas/ptc-host-config.schema.json

ptc-command-envelope-v2.schema.json

machine integration

The V2 command envelope written by ptc run --envelope FILE. An atomic, no-replace file whose status and exit-code relationship is sealed by the command contract — parse this instead of stdout.

https://ptc-runner.dev/schemas/ptc-command-envelope-v2.schema.json

Each schema is published verbatim from priv/schemas/ in the repository, so the hosted copy and the runtime validator are always the same bytes.