GRN timing policies
Govern when a future receipt presents its GRN identity and becomes eligible for one fixed controlled-document issuance, using only four code-owned stages.
Screen orientation
Tenant administrators author and independently publish policies. Receipt readers see only scoped pinned state; issuance remains a separate receipt permission.
The policy editor defines bounded rules over the fixed stage/fact catalogues. Simulation and exact version history show selected rule, checksums and maker-checker decisions.
Field reference
The entries below describe the current screen controls and read-only values. They do not relax server-side validation, site scope, classification handling or required independence in a governed decision.
| Field or value | Control | Required or shown when | How to use or read it | Result |
|---|---|---|---|---|
| Policy key · Policy name · Policy description | Text | Required. | Create the stable policy identity and bounded timing purpose. | Forms the immutable policy register. |
| Rule key · Rule name · Precedence · Rule description | Rule controls | Required per rule. | Create unique ordered rules including exactly one fallback. | Defines deterministic selection. |
| Presentation stage | Fixed select | Required. | Choose RECEIPT_RECORDED, QUARANTINE_POSTED, INSPECTION_DISPOSED or INSPECTION_ACCEPTED. | Controls when the GRN is presented. |
| Document issuance stage | Fixed select | Required and not earlier than presentation. | Choose one code-owned threshold. | Controls eligibility for the fixed issuance contract. |
| Condition field · Operator · Comparison value | Bounded condition builder | Optional for non-fallback rules. | Use only allowed receipt-source/authority/classification/policy/category/criticality/route facts. | Builds deterministic applicability without executable content. |
| Effective from · Change reason | Version fields | Required for publication/replacement. | Set future effectivity and explain the immutable change. | Preserves existing receipt pins. |
| Receipt source · Authority type · Classification · Procurement policy mode | Simulation facts | Required. | Enter an exact safe receipt context. | Tests deterministic rule selection only. |
| Category code · Criticality code · Route code | Simulation facts | Required when governed procurement applies. | Use exact configured codes. | Completes policy applicability context. |
| Simulation note | Long text | Required. | Explain the tested receipt scenario. | Stores attributable simulation evidence. |
| Code-owned stage catalogue | Read-only table | Derived. | Use the fixed stage ordering shown by the server. | Prevents configuration from inventing receipt actions. |
Actions and effects
When to use: After complete rules and fallback.
What it does: Checks catalogue, rule and definition checksums without creating a receipt.
When to use: After a successful current-definition simulation.
What it does: Freezes the version for independent decision.
When to use: By a different Tenant Administrator.
What it does: Applies the version only to future receipts and preserves prior pins.
Lists and states
- GRN timing policy register: use status, exact version and accountable actors to distinguish current work from retained history.
- History and evidence: hashes and source/version references identify the immutable facts used by each decision.
Authority boundary
Timing controls presentation and fixed issuance eligibility only. It cannot create/amend a receipt, ASN, authority, inspection, quarantine, custody, stock/ledger fact, PDF template, print, email or external delivery.