The hand-off round-trip
One record, two people. The engineer forwards a draft from the command line; the compliance team fills and signs it in the browser; then the engineer pulls the filled cells and the finished seal back home. This is that full round-trip, so the sealed evidence ends up next to the systems it describes.
“Forward my Regixo draft record to our compliance team. Show me what would be uploaded before you send it.”
Show the commandHide the commandShow the sentenceHide the sentence
$ regixo inviteIt previews what leaves the machine and waits. 22 dataset names and types, 14 personal-data flags, the drafted record — and no row values.
Check it worked: a DRAFT PDF you can email and a claim link. Your agent must show you the
preview and get your word — off a terminal regixo invite needs
--yes, and the playbook tells it to get that agreement in words first, never to assume
it.
Show what it prints in the terminalHide the terminal outputShow what your agent reportsHide what your agent reports
▸ what leaves: metadata only — 22 dataset names/types + 14 personal-data flags
+ the drafted record (activity titles, suggested legal fields)
your row values ✗ never
? Send this snapshot? [y/N] y
✓ RoPA_DRAFT.pdf written
This forwards a copy of your one compliance record — forward it to your
compliance team (no account needed from you):
DRAFT PDF: .regixo/invite/RoPA_DRAFT.pdf (forward it today — it carries the claim link)
claim link: https://app.regixo.com/claim/clm_7Q… (uploaded — this link now works;
your compliance team opens it and unlocks there)
coverage: 6/6 sourcesregixo invite).--dry-run first to preview.“Pull the answers our compliance team filled in on the forwarded link back into my local Regixo catalog.”
Show the commandHide the commandShow the sentenceHide the sentence
$ regixo dora pull clm_7Q…
Their answers, merged into your local draft. A field they confirmed stays confirmed — it is carried, never re-derived.
Check it worked: it reports how many merged and how many were skipped (already
merged, or your local copy is newer). If it says anything else, check for yourself with
regixo dora status.
Show what it prints in the terminalHide the terminal outputShow what your agent reportsHide what your agent reports
B_05.01/stripe/lei: “” → “5493001KJTIIGC8Y1R12” (claim-side 2026-07-04 09:12) B_02.01/contract-88/expiryDate: “” → “2027-03-31” (claim-side 2026-07-04 09:15) ✓ merged 2 fills from claim clm_7Q… · 3 skipped (already merged or local is newer). ↳ see them: regixo dora status · regixo annotate list
regixo seal pull
<claim-token>. It fetches the signed artifacts — the sealed PDF, the record JSON, the
attestation, and the offline verifier — into your local data directory.“Pull our signed, sealed record from the portal onto this machine.”
Show the commandHide the commandShow the sentenceHide the sentence
$ regixo seal pull clm_7Q…
The sealed record comes home — the official PDF, the record and the attestation, next to the source they describe.
Check it worked: it names who signed and when. Not signed yet? It says so and changes nothing.
Show what it prints in the terminalHide the terminal outputShow what your agent reportsHide what your agent reports
✓ pulled 4/4 sealed artifact(s) → .regixo/remote-seal signed & sealed by Dana Kessler (Data Protection Officer, Acme Europe BV) on 2026-07-05 · plan ropa verify offline: node .regixo/remote-seal/verify-attestation.mjs
RoPA_OFFICIAL.pdf, RoPA_OFFICIAL.json, attestation.json and
verify-attestation.mjs. You can check the seal with no Regixo server in the loop.regixo open, look at the Record screen — the same GDPR Article 30
record you forwarded, still derived from the map, still stamped DRAFT until a person signs it.
The screen below is that record before the round-trip closes: the coverage line, the four counts,
and legal calls still blank — for your compliance team. Once regixo seal pull has
brought the signature home, this same screen carries the seal and the hand-off card reports it was
signed, rather than merely forwarded.Record of Processing Activities
DRAFT↓ Download the sealed PDF serves it right
from the host.--dry-run to preview. And the DORA
official export always stays on the engineer's host — the machine that holds the source — never
on the claim.