amr/memex
1
0
Fork 0
Code Issues 12 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

chore: unify bold syntax to single asterisk in .org files and update legacy memex-amero references

Browse Source
This commit is contained in:
Amr Gharbeia
2026-04-01 12:37:45 -04:00
parent 78ba3112cb
commit d364f90ff6
102 changed files with 955 additions and 955 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
notes/closos-protection-mechanisms.org
View File

@@ -7,9 +7,9 @@
Security in a Lisp OS is enforced by the compiler and runtime environment rather than traditional hardware MMU (Memory Management Unit) boundaries.
* Key Principles
- **Controlled Access System:** The system is "closed" by the compiler. Only code produced by the trusted compiler—which excludes arbitrary pointer arithmetic and includes bounds checking—is allowed to execute in supervisor mode.
- **Tagged Pointers:** Objects are manipulated via tagged pointers. Access rights (read/write/execute) can be embedded directly into the tag bits of the pointer itself.
- **Capabilities:** Pointers function as capabilities. Possession of a pointer to an object implies the authority to interact with it according to the embedded access tags.
- *Controlled Access System:* The system is "closed" by the compiler. Only code produced by the trusted compiler—which excludes arbitrary pointer arithmetic and includes bounds checking—is allowed to execute in supervisor mode.
- *Tagged Pointers:* Objects are manipulated via tagged pointers. Access rights (read/write/execute) can be embedded directly into the tag bits of the pointer itself.
- *Capabilities:* Pointers function as capabilities. Possession of a pointer to an object implies the authority to interact with it according to the embedded access tags.
* Source
:PROPERTIES: