Read the code
The project is intended to be inspected, forked, adapted, and improved.
PersonalOS is built around private files, explicit review, and user control. You can read the code and inspect the memory.
“Nothing is sent anywhere unless you choose to sync or share it.”
Feedback is generated locally first. Memory is reviewed before it becomes durable. Personal repositories should stay private.
The project is intended to be inspected, forked, adapted, and improved.
Use local storage, trusted cloud sync, or private Git. Do not publish personal memory.
Optional reports are local and inspectable before you manually share them.
Read the technical docs when you want internals and control-plane details.
Use private version history and diffs for memory changes. See the private Git path.
Upstream improvements use privacy gates so personal data stays out. Read CONTRIBUTING.md.