Authoritative data exchange — sealed, timestamped bundles ★ Live
Export knowledge for exchange as a qualified-sealed, timestamped, archived bundle — authorization-driven, never anonymized.
When knowledge is exported for exchange — including an OKF bundle — the authoritative path renders it MD→PDF, applies the qualified GLG seal and a qualified RFC-3161 timestamp (PostSignum), and files it under a real client and project (project permissions apply, every read and download audited) with an NSESSS retention schedule and a hash-chained audit. Exchange is authorization-driven and never anonymized: personal data (e.g. patient records doctor→doctor) leaves only under recorded, verified authorization — an active sharing window or per-subject consent — stamped into the bundle manifest; the default export excludes personal rows entirely, and the anonymization-token map is never shared. OKF defines the file; amemor-ai adds the legal basis, the qualified seal and timestamp, and the audited archive — the accountability layer OKF lacks. A live sample is viewable in the records office.