The remote service is the main point of passage.
Core operation first depends on remote infrastructure availability.
OFFLINE FIRST · LOCAL WHEN POSSIBLE
Gankpo prioritises local execution for suitable operations, then uses the network when transport, issuance or the trust model requires it.
01
Core operation first depends on remote infrastructure availability.
The network completes the journey for transport, synchronisation or required external evidence.
02
No network is required merely to store the file on chosen media.
When the application supports the relevant format version.
From the available bytes, fingerprint and public key.
Requires the right secret or access key; support varies by application.
Local when useful anchors and evidence are available; otherwise an update may be required.
Cached or embedded evidence may be checked locally; freshness may require synchronisation.
An existing token may be validated locally; obtaining it relies on a TSA.
Transport through a relay, messaging or another channel remains separate.
Issuer, Connect, OID4VCI and OID4VP exchanges depend on the journey and remote service.
This matrix describes architectural behaviour and its conditions. Exact availability depends on the application, platform, format and qualified version.
LOCAL-FIRST · SEPARATE TRANSPORT
03
Continue locally when connectivity is missing.
Limit systematic transmission.
Reduce the impact of central outages.
Choose storage media.
Move the file through available mechanisms.
Separate local access from trust services.