Capture stopped working after an IDE update.
Open the capture health panel in the dashboard. It marks each client fresh, stale, broken or absent. Most IDE updates move the transcript path; re-point the stale client from the same panel.
A receipt verified yesterday and says TAMPERED today.
That is the verifier doing its job. Check whether the export was re-serialized (a pretty-printer will do it). Verify the original bytes. If the original also fails, open a ticket immediately.
An approval token was refused as already used.
Tokens are single-use by design. A retry that changed anything about the request needs a fresh approval. Check the request digest in the gate error; it will show what differed.
How do I rotate the receipt signing key?
Generate a new key with lore receipts keygen. Older public keys stay published, so historical receipts keep verifying.
Can I export everything if we leave?
Yes. Memory records, context snapshots, and the full receipt chain export in documented formats, and the receipts stay verifiable with the published key after you go.
Where is the acceptance report for my deployment?
Your onboarding contact shares it. It lists, connector by connector, what is captured, what is gated, what is verified, and any known bypass path. If you think it is wrong, tell us; we would rather fix the report than defend it.