Synthetic examples

These are synthetic, structurally and semantically conforming JPS documents for inspecting and testing the document format. Three unrelated domains exercise the same portable shape without claiming that the examples are complete, authoritative, or safe for operational use.

Use synthetic data only. These examples are designed for structural and semantic document testing, not decision execution. Ordinary validation must not fetch their source locators unless explicitly requested.

How to use these examples

Open a detail page to understand the document's focus, boundaries, edges, and useful failure exercises.
Download the exact JSON and validate it locally; the checked-in document should pass all three document-conformance layers.
Edit only a scratch copy to create a carrier, structural, or semantic failure.
Compare what you observe with Test the preview.

JPS 0.1.0-draft defines document conformance, not portable rule evaluation. The edge notes on each page explain illustrative applicability, evidence, unknown, conflict, and fallback situations without claiming an expected runtime decision. Validity never proves truth, authority, safety, or fitness.

For the structural baseline, use an independent Draft 2020-12 implementation and inspect semantic references separately. Conforming tools that check all current JPS document-conformance layers are listed on the Implementations page.

Synthetic · non-operational

Expense approval

Research example for deciding whether an employee expense may be automatically approved.

Focus: Cross-feature authoring and local-reference tracing.

3 outcomes · 3 rules

Synthetic · non-operational

Synthetic records disposition review

A non-operational example using invented training fixtures. It is not records-management or legal guidance and does not authorize retention or deletion.

Focus: A sensitive-domain-shaped example with an explicitly harmless boundary.

3 outcomes · 2 rules

Synthetic · non-operational

Synthetic software change review

A non-operational example for discussing the schema. It labels a fictional training-demo change and does not authorize deployment or represent a production change policy.

Focus: Schema-versus-semantics exercises in a harmless training scenario.

3 outcomes · 2 rules

Synthetic · non-operational

Synthetic supplier invoice approval

A non-operational example for discussing the schema. It labels a fictional training-fixture invoice and does not authorize any payment or represent a real accounts-payable policy.

Focus: A business approve / manual-review / escalate / reject decision gated on evidence.

4 outcomes · 3 rules