The unsigned decision / Working paper NI-07
1. Separate recommendation from action
Administrative software often hides the moment at which a proposed answer becomes binding. Our design gives that transition its own object: a decision packet. The packet contains the inputs used, the instruction proposed and the person allowed to authorise it. Revising a recommendation creates a new version; it never borrows a signature from an earlier version.
2. Measure waiting without treating it as waste
Delay is measured from the packet’s ready timestamp to the signature timestamp for completed decisions. The median uses only observed completed pairs. Pending packets are counted separately and cannot be assigned a fictional completion time. Comparing medians without queue type or coverage dates would mistake a careful identity review for a slow warehouse.
3. Preserve the local exit
An annual subscription needs a practical end procedure. Exported packets include readable evidence, original signatures and unresolved questions. The local office should be able to continue reviewing these records without renewing a proprietary recommendation engine. Compute dependence is still a political constraint; portability reduces its cost but does not make it disappear.
4. Lineage and scope are different evidence
The configuration references lineage node NI-2071-A in SIEvoMap. A parent declaration describes a recorded development relation, not intelligence, consciousness or legal fitness. Scope is evaluated separately in boundary record AB-NI-2150-01. Neither a complete lineage nor an administrative signature replaces that assessment.