Procedure Platformby MethodMinded
← Procedure Platform
Technical documentation

The Procedure Platform file architecture

Procedure Platform separates meaning, quality requirements, and presentation so procedures remain useful beyond one PDF layout.

Four artifacts

Procedure Definition

Canonical structured source for metadata, preamble, sections, steps, hazards, controls, verification, and assets. It contains no fonts, margins, colors, or page positioning.

Procedure Schema

Documented information requirements and validation rules. Rules include severity, rationale, guidance, examples, and known limitations.

Procedure Presentation Language

Declarative, versioned, machine-readable instructions for presenting procedure data in a PDF. PPL files contain no executable code.

Manifest

Connects the exported files with versions, hashes, compatibility information, and export metadata.

Embedded PDF package

A Procedure Platform PDF contains the visible rendered procedure plus standard PDF attachments:

  • procedure.json
  • procedure-schema.json
  • procedure-presentation.ppl.json
  • procedure-manifest.json

Attachments are not displayed on visible pages and are not concealed with steganography. On import, the platform verifies the package where possible and warns about missing, altered, or incompatible files.

Using an LLM to draft a schema or PPL

A technically capable user may use an LLM of their choice to draft compatible JSON, but generated files must be reviewed and validated before use. Do not treat generated guidance as legal advice or a compliance certification.

You are helping draft a Procedure Platform artifact.

Output only valid JSON. Use the supplied Procedure Platform specification and examples.
- Use format "procedure-schema" or "procedure-presentation-language".
- Use the supported version exactly.
- Include stable identifiers, version metadata, and documented intended use.
- Do not add executable code, JavaScript, arbitrary CSS, or unsupported properties.
- Preserve required identifiers and explain assumptions separately, outside the JSON, only when requested.
- Validate the result against the provided examples before returning it.

Upload the JSON in Schema Studio or Presentation Studio, run validation, review the design rationale, and keep it in draft until an authorized owner approves it.

Bring Your Own AI

The AI Exchange workflow uses the same separation: external AI may help draft language, while Procedure Platform validates structure, applies PPL, renders deterministically, and preserves the source package.

Careful language

Schemas and presentations are designed to support consistency and may be informed by standards, regulations, internal policies, or technical-writing guidance. They do not by themselves make a procedure legally compliant, certified, or suitable for every use.

Open Builder