The Procedure Platform file architecture
Procedure Platform separates meaning, quality requirements, and presentation so procedures remain useful beyond one PDF layout.
Four artifacts
Canonical structured source for metadata, preamble, sections, steps, hazards, controls, verification, and assets. It contains no fonts, margins, colors, or page positioning.
Documented information requirements and validation rules. Rules include severity, rationale, guidance, examples, and known limitations.
Declarative, versioned, machine-readable instructions for presenting procedure data in a PDF. PPL files contain no executable code.
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.jsonprocedure-schema.jsonprocedure-presentation.ppl.jsonprocedure-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.
Connected AI assistance
An approved assistant connects through MCP to read the authoring formats, submit procedure drafts, and propose information requirements or presentation templates. The connection is bound to one user and organization. Procedure Platform validates submissions, renders deterministically, and preserves the editable source. Review every draft before release.
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.