Index 01 sync and recovery
The transfer pipeline is designed around one rule: Veura does not acknowledge a ring recording until its durable local state has been committed.
The transfer pipeline
- Discover or reconnectVeura finds a nearby ring or checks the remembered device.
- Stage the recordingIncoming audio is written into local staging before it enters note processing.
- Commit durable stateVeura records enough local state to recover the work after an interruption.
- Acknowledge the ringOnly after the local commit can Veura acknowledge the remote recording.
- Transcribe and enrichThe saved audio is processed by the chosen model, followed by enabled on-device actions.
What resumes automatically
- Pending transfer work after Bluetooth becomes available again.
- Acknowledgements that were not completed before an interruption.
- Queued transcription and enrichment jobs after the app is relaunched.
- The final ready notification after processing completes.
How duplicates are limited
Veura keeps source-device and remote-recording identifiers when they are available. These identities let the ingestion pipeline recognize previously committed work rather than creating a second note for the same remote recording.
Manual recovery actions
- Use Sync Now for a remembered ring when you want an immediate check.
- Once a recording exists on the ring, keep it nearby; no extra press or hold is needed to transfer it.
- Stop an active search before starting another connection attempt.
- Forget the ring in Veura and remove it from iPhone Bluetooth settings before a clean re-pair.
- Use short artifact cleanup only for Index entries shorter than one second.