Synthetic examples
Start with a business decision, inspect the evidence, then try the policy locally.
Worked business examples
Each walkthrough includes a one-page PDF, a runnable pack, saved expectations, source fixtures and a pilot worksheet. These companion-tool examples are separate from the document-conformance examples below. All policies, records and thresholds are fictional.
Worked example · Synthetic
Deal evidence readiness
Reconcile CRM, quote, security and finance records before an owner reviews a deal. Includes 40 project test cases.
Worked example · Synthetic
Data release readiness
Check that pipeline, quality, schema and owner records cover the same data batch. Includes 18 project test cases.
Worked example · Synthetic
Fleet maintenance review
Connect a diagnostic recommendation to the right vehicle, inspection and work-order check. Includes 18 project test cases.
Worked example · Synthetic
Location campaign readiness
Review location, offer, brand and channel records for one campaign revision. Includes 18 project test cases.
Worked example · Synthetic
Contractor order readiness
Reconcile quote, stock, credit and delivery records before a branch makes a commitment. Includes 18 project test cases.
Worked example · Synthetic
Customer recovery readiness
Check feedback, service findings, remedy approval and account ownership before reviewing a customer remedy. Includes 18 project test cases.
Document-conformance examples
These are synthetic, structurally and semantically conforming JPS documents for inspecting and testing the document format. Unrelated domains exercise the same portable shape without claiming that the examples are complete, authoritative, or safe for operational use.
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.
The document examples below are about document conformance. JPS 0.2.0-draft also defines portable evaluation semantics, but an evaluator-conformance claim is made against the evaluation corpus, never against an example. 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
Synthetic data request intake triage
Invented intake-triage policy for a fictional data platform team: route an incoming data request to proceed, clarify/return, or decline/redirect once completeness and appropriateness have been assessed. Synthetic content for specification testing; it authorizes nothing.
Focus: A three-way triage decision over summarized assessment facts.
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.
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.
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.
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.