Government | Modelled case study
Transition cryptographic trust across an interagency API
Which agency owns issuer trust, version negotiation, revocation, and failure response when algorithms change?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the API Platform · Mission Owner · Security Authorization functions. It is grounded in the cited problem context but does not identify a real customer.
Operating environment
A public-sector body operates identity, citizen-service, procurement, records, and interagency platforms across long replacement cycles and multiple authorities.
What is at stake
Cryptographic transition must preserve public-service continuity, sovereign control, accessibility, records obligations, and interoperability across agencies and suppliers.
Situation
An API can be technically upgraded yet remain unusable because partner agencies depend on different certificate authorities, gateways, release cycles, and authorization packages.
Event that forces action
A shared service launch, certificate-authority change, or deprecation of a public-key algorithm.
Concrete system boundary
Systems this case study puts in scope
The model is specific about the operational surfaces that must be discovered, changed, or independently checked.
agency API gateways
service identities
shared certificate authorities
cross-agency compatibility and rollback
Modelled case study walkthrough
How this organisation would use QNSI
The walkthrough connects the real-world problem to a bounded QNSI contribution and an independently reviewable result.
Recognise the operating condition
An API can be technically upgraded yet remain unusable because partner agencies depend on different certificate authorities, gateways, release cycles, and authorization packages.
Frame the decision the owners must make
Which agency owns issuer trust, version negotiation, revocation, and failure response when algorithms change?
Apply QNSI to the controlled boundary
Record trust anchors, service identities, algorithms, owners, test evidence, and transition states through QNSI.
Leave the team with a concrete result
An interagency trust contract with compatibility evidence, failure ownership, sunset dates, and signed acceptance.
Prove the result in the organisation's environment
Every participating authority tests its endpoint and approves security, privacy, operational, and records impacts.
What useful success looks like
A decision artifact plus proof from the real environment
The model stops at a target result. It becomes an actual case study only when a customer produces and independently validates this evidence in production.
Decision artifact
An interagency trust contract with compatibility evidence, failure ownership, sunset dates, and signed acceptance.
Independent validation boundary
Every participating authority tests its endpoint and approves security, privacy, operational, and records impacts.
Real-world problem grounding
Primary sources behind the model
These sources establish the external requirement, failure mode, or risk context used to model this case. They do not endorse HEOSSI or prove that QNSI completed the scenario.
Customer evidence status
This is modelled, not a customer claim
The organisation is a composite and the result is a target state. This page does not prove a deployment, customer outcome, certification, legal conclusion, regulator endorsement, or completed control.