Memkith does not maintain a second permission model beside your repository's. Locally, Git and branch scope define the boundary: a memory written on a branch is visible to that branch. In teams, Memkith respects repository permissions, so memory reaches the people who can already read the code it is attached to.

Memory has an address. Each one stays mapped to the files, functions, and lines it concerns, which is also what makes its scope checkable rather than asserted.

A formal security overview, subprocessor list, and disclosure process will be published here. Memkith holds no compliance certifications today and claims none.