Open Knowledge Format (OKF) interoperability ★ Live

amemor-ai speaks Google's Open Knowledge Format (OKF v0.1 — the markdown + YAML knowledge-bundle standard) as a first-class producer and consumer. okf_import ingests a local directory or a git URL through the full pipeline; okf_export turns any project into a conformant bundle, with a lossless round-trip verified even against Google's own sample bundles. We don't invent a proprietary format — we adopt the standard and sit above it as the governance layer OKF itself lacks. “Works with Google Open Knowledge Format” is low-cost interoperability reach.

Exports can also be signed and authorized, not just open. By default okf_export ships knowledge only — client-linked and personal rows are excluded and no authorization is required. To include personal data (for example records shared doctor→doctor), you pass an authorization (recipient, legal basis, scope, authorized_by, reference) that is verified per subject against an active sharing window or consent — rows the authorization does not cover are excluded rather than shipped — and is stamped into the bundle's okf.yaml for accountability. Such a bundle is qualified-sealed and RFC-3161 timestamped (okf.yaml.sig plus an integrity MANIFEST), never anonymized, and the anonymization-token map is never shared. This is the OKF entry point to the authoritative, audited exchange path — see “Authoritative data exchange” under the records office for the sealed-and-archived flow.