Standard
A process card as a control layer, not a specification to copy
ORPR is 74 processes in 22 areas, each with a stable identifier and a card. The STANDARD card is the default unit of the standard: it describes outcome and boundaries, data, invariants, analyst questions, red flags and regulatory bindings — within a 150–250 line budget, so an analyst and an AI agent can use it rather than rewrite it.
- 74
- 22
- 6
- 68
The identifier does not change when a process moves on the map
Every process has a stable technical identifier and a navigation address. The notation is frozen since release v0.1.0 — changing it requires a new release and an explicit deprecation of the withdrawn identifier.
Technical identifier
ORPR-<KOD DOMENY>-<NN>On the map the ORPR- prefix is dropped: the process appears as SAL-01.
Navigation address
<rodzaj> / <obszar> / <NN> · <od czego do czego> · <ID>NN is the ordinal within the area, not a process step. Execution order follows handoffs and flows, not numbers.
Seven sections, each with a single job
Section 0 is identical in every card and explains how to use it. Sections 1–6 carry the normative content. Budgets are soft — exceeding one does not block a change, but requires a one-sentence justification.
- 0
How to use this card
Fixed text. The card is an external control layer for the analyst and the AI agent. In a specification, cite identifiers (ORPR-…, Nx, Fx); do not transplant content.
Budget: fixed
- 1
Outcome and boundaries
The end state by which the business knows the process has happened. Start, end, alternative outcomes, what the process does NOT cover (with →area/ID pointers), owner.
Budget: 1 paragraph
- 2
Data
Mandatory inputs [D! id], conditional inputs [D: id], outputs: document, state, resulting events.
Budget: lists
- 3
Invariants
What must always be true — testable statements without justifying prose. [N] business invariant, [K] boundary contract: observable semantics only, never a mechanism.
Budget: 5–12
- 4
Analyst questions
Class B — blocking: no specification may be written without an answer. Class W — conditional, with an explicit "If…" trigger. Class D — diagnostic, for examining the legacy system during migration.
Budget: 15–30
- 5
Red flags
Signals of a flawed implementation or a flawed legacy system. Each flag points to the questions that detect it. These are acceptance tests during migration.
Budget: 5–12
- 6
Regulatory bindings
Regulatory Matrix version, legal_as_of date and a list of identifiers. Zero legal text in the card. Missing coverage = an explicit GAP in the register, never silence.
Budget: ID list
Deviating from an invariant [N] or contract [K] is allowed without anyone’s approval, but requires an explicit entry "deviation from ORPR-<ID>/<Nx>: <reason>" flagged as a risk. A statement carrying an [R: …] binding cannot be deviated from at card level — that is a legal question.
Every statement in a card says where it comes from
Source tags preserve provenance. The card in the repository carries tags and status fields (the governance layer); the agent package is derived from it by script — tags removed, normative content kept. One source of truth: the card is edited, the package is generated.
- [AUT-R]
- confirmed knowledge of the standard’s owner
- [PROP+]
- accepted editorial proposal
- [LIT]
- public source with a locator
- [R: ID]
- link to a Regulatory Matrix requirement
- [HIP]
- hypothesis — not to be treated as fact
- [do potwierdzenia]
- content awaiting confirmation
STANDARD for every process. In-depth — on demand.
The minimal-sufficiency experiment (25 Aug 2026, two model families) showed the STANDARD card is enough as a control layer — with margin. The full L1 template remains only for in-depth cards, written at an adopter’s request.
STANDARD card
For every process on the map. ~150–250 lines of core. In the public sample: 6 full cards as a format demonstration and 68 public digests.
In-depth card (L2)
Expands boundaries, inputs and outputs, variants, exceptions, the complete question bank, red flags and full mapping to Regulatory Matrix. Produced only with an adopter.
Outside the card: an extended question bank (optional), an "implementation patterns" annex (informational — mechanisms never enter the card), an APQC / ARTS / GS1 crosswalk (reference) and industry profiles (overlays, never in the core).
What sits inside the 68 reviewed cards
Totals across the 68 STANDARD v2 cards after independent review. This is the scale of the control layer, not a count of "features to build".
- 1768
- 714
- 560
- 494
- 741
- 690
- 2
Five rules that keep the standard honest
- 1
The process core is sector-neutral; sector content goes into profiles.
- 2
Material is produced clean-room, without client or employer data.
- 3
Regulatory Matrix supports analysis but is neither a legal opinion nor a compliance certificate.
- 4
The source language of the current release is Polish.
- 5
Release limitations are published openly so a user can tell what is ready to use from what still needs validation.