NAME

kb-export — write a portable JSON-L snapshot of the database

SYNOPSIS

kb export [-project NAME] [-out PATH]

DESCRIPTION

export writes the knowledge base (or, with -project, just one project and everything reachable from it — its concepts, sources, observations and decision records) as newline-delimited JSON to -out, or to stdout when -out is omitted. Every line is self-describing via a “type” field (project, concept, source, observation, observation_concept, observation_relation, project_concept, observation_source, record, record_relation), in dependency order.

A -project export carries only that project’s decision records — a workspace-tier record belongs to no project, so it has no principled claim on a scoped export, and appears only in an unscoped one. A record relation crossing out of the scoped project (to another project, or to the workspace tier) is likewise excluded along with the record on the far side of it.

Unlike merge, export never touches a second database file — the resulting file can be pasted, emailed, or committed to git, then applied elsewhere with import. This is the no-file-access alternative to merge; when both databases are reachable as files, merge is the more thorough tool (it also detects and can reconcile name collisions).

Exit status: 73 when -out cannot be created (it names a directory, or its directory is missing), 77 when the OS refuses, 74 if a write fails part way, 1 for a -project that does not exist.

With –json, a text confirmation is only meaningful once -out is given (the JSON-L stream itself has already gone to stdout otherwise): it becomes a {“lines_written”: N, “path”: “…”} object instead of the plain text line.

SEE ALSO

kb(1), kb-import(1), kb-merge(1)