Ledger, sync, offline and hardware requirements
Server-to-server transfer, three streams
Secret-shared, decoy-padded transfer.
How to read status labels: In the pilot (v0.2.0, synthetic data) Simulated in the pilot Coming (Wave 2, rolling out) Designed, not yet built Open decision Not offered / no claim made Planned partner integration
C0965How would server-to-server clinical transfers be protected?
The server-to-server transfer, three streams part of the specification (REQ-3401) says server-to-server clinical data transfer must use three simultaneous streams with interleaved decoy traffic and secret sharing so no single stream carries decryptable content. No. The specification describes it, but the pilot does not include it. Acceptance check: capturing any one stream yields no plaintext; test decrypt from one or two streams fails.
C0966Which encryption would transfers use?
How would it be tested? The specification says handshake test shows hybrid group negotiated. That is the check for REQ-3402: the transfer must use AES-256-GCM or ChaCha20-Poly1305 for data and hybrid X25519 + ML-KEM for key exchange. Not yet. It is designed in the specification and not built in the pilot.
C0967Does AuroraMed document that decoys provide traffic-analysis resistance and not confidentiality or quantum resistance?
Designed, not built: there is no code for this in the pilot. For reference, REQ-3403 (a top-priority requirement, all three tiers) says the system must document that decoys provide traffic-analysis resistance and not confidentiality or quantum resistance. Check: doc statement exists in security spec.
C0968Who authorizes a transfer before data leaves?
Transfer must be authorized by an authority record and ledger transaction before any data leaves; the package commitment is recorded on both sides. That is REQ-3404, a top-priority requirement for the medium and large tiers. This is on the design side of the line. Nothing in v0.2.0 does it. Test in the specification: transfer attempt without authority is blocked.
C0969What happens if a transfer behaves oddly?
No. The specification describes it, but the pilot does not include it. REQ-3405 says transfer anomalies (stall, rate deviation, decoy ratio mismatch) must abort the transfer and alert. Its acceptance check: fault injection aborts.