Local Git History

Origin writes human-facing artifacts under ~/.origin, including pages, session handoffs, and current status records. Those artifacts are committed into a local git repository.

The git log gives you a practical audit trail for memory work: what changed, when it changed, and which artifacts were touched.

Use normal git commands from ~/.origin to inspect recent memory writes and page changes. This is often faster than opening the database when you want to understand a human-readable change.

The repository is local. It is not pushed anywhere unless you explicitly sync or publish it yourself.

Git can help inspect, diff, revert, or recover a previous Markdown page or session note, but do not treat manual git restore as a full database rollback.

If the durable knowledge is wrong, the safer product path is to capture a correction or forget the memory by ID. That keeps the index and readable artifacts aligned.

Because pages and sessions are normal files, you can inspect them from editors, terminals, or personal note tools. Some users symlink pages into a vault for reading.

Keep writes disciplined. Origin should remain the writer for generated artifacts unless you intentionally edit a human-owned page.

Local git history makes Origin more inspectable, but it also means old versions may contain old private context.

Do not publish, sync, or attach ~/.origin blindly. Redact or create minimal reproductions when reporting bugs.