AFFIXIO
Extreme edge
Verifiable decisions for orbital and extreme-edge compute
When links are intermittent, decisions must be locally verifiable. Signed credentials and offline spent-proof patterns fit disconnected and delayed networks. AffixIO describes architectural patterns for those gates, not a mission certification.
Definition
Disconnected verification is local checking of signed eligibility when links to central systems are delayed, intermittent, or unavailable.
Field note. Ground-based verify loops break at orbital latency. Push verify to the node with proofs that sync when links return.
Pattern, not certification
AffixIO is not space-certified. This page describes how signed credentials and offline spent-proof ideas apply to disconnected networks. Mission assurance remains with the programme authority.
The useful transfer: issue proofs before disconnection, verify locally, sync Merkle audit when the link returns.
Shared lessons with terrestrial edge
Venue gates, rural utilities, and maritime systems hit the same constraints at smaller distances. Offline gate verification and QR presentation are the terrestrial analogues.
Start with terrestrial offline patterns, then adapt TTL and key distribution to the link budget you actually have.
Rollout notes for orbital edge verification
For orbital edge verification, provision sandbox circuits that mirror production predicates before you expose live agent traffic. Capture sample allow and deny payloads for regression tests.
Keep identity and rich attributes with the issuer. Verifiers receive outcomes and Merkle metadata only. Sync audit refs to your SIEM or order store after the gate returns.
Field reality
Round trips are not free in extreme environments
Orbital and remote edge systems cannot assume low-latency access to an eligibility API. Gates still need honest allow or deny decisions.
High latency links
Waiting on Earth-side databases can miss time-critical windows.
Partial connectivity
Bursty downlinks favour store-and-forward audit over live identity queries.
Resource constraints
Devices may verify signatures locally but should not host full identity directories.
Certification confusion
Architectural patterns are not the same as flight or mission certification.
Offline pattern
Verifiable gates for orbital and extreme-edge compute
Space and extreme-edge systems cannot rely on terrestrial verify endpoints with seconds of round-trip delay. AffixIO stateless proofs let local nodes decide and retain Merkle evidence for ground audit.
Issue before disconnect
Mint proofs while the link is up.
Verify locally
Gate on signatures and spent-proof without Earth round trips.
Queue audit
Buffer Merkle refs for later sync.
Re-issue on schedule
Align TTL with pass windows or mission phases.
Before you commit
Readiness checks for orbital edge verification
- Separate architectural pattern from certification claims.
- Model worst-case disconnect duration into TTL.
- Provision verify keys for the offline window.
- Plan audit sync after reconnect.
- Reuse terrestrial offline gate tests where applicable.
Quick clarifications
Questions on orbital edge verification
Is AffixIO space-certified?
No. This page describes architectural patterns for disconnected verification, not a mission certification.
Can we use QR in space?
Presentation format is an engineering choice. The invariant is local signature verify and anti-replay.
What algorithm?
ML-DSA-65 for signed outcomes on AffixIO paths.
Where to start on Earth?
Offline gate verification and access-control sector pages.
Protocol notes
Pages that support orbital edge verification
Infrastructure
More infrastructure briefs
Prototype orbital verify circuits
Bench issue and verify on disconnected profiles, then validate Merkle handoff when connectivity resumes.