AI made summary of 0RWX Framework, Namtao Productions. Not written or verified by the author.

Takeaways: 0RWX Framework

2026-11-12 · Source: https://0rwx.com/ · Namtao Productions, a one-page site, CC0. Tagline: "A simple model of AI usage, inspired by unix permissions." The page names no person. The GitHub repo it links (github.com/NamtaoProductions/0rwx.com) was not read.

Gist

Four labels for how much AI touched a piece of work, named after unix permission bits: ZER0, READ, WRITE, EXECUTE. The author's claim: "We need new language to talk about large language models." What separates the levels is "not necessarily about what TOOL you use, but your ability to scrutinise the generated work." The author says the labels let them discuss their own and others' work "with less judgement and confusion." Free logos for each level, released to the public domain.

A proposed vocabulary, no data. The claim that it reduces judgement and confusion is the author's own experience, not tested.

Takeaways

The four levels

Each level has a rule, a label, three examples (code, visual art, music), and a verb for what the human does.

• ZER0. "AI can't read or write to your work." Label HAND MADE. Examples: "I read the docs", painting with paint, playing music. Verb: "I think".
• READ. "AI has read-only permissions." Label AI INSPIRED. Examples: "I write the code" (links to brainmade.org, not read), reference images, chord inspiration. Verb: "I make".
• WRITE. "AI has read-write permissions." Label AI COLLABORATION. Examples: "I read the code" (links to a Mitchell Hashimoto post on X, not read), generated collages, loop generation. Verb: "I fix".
• EXECUTE. "YOU can no longer read your work." Label AI MADE. Examples: "I vibe code", image generation, song generation. Verb: "I curate".

How the levels relate

• The permission is the AI's on levels 0 to W, but on X it flips to the human: you lose the ability to read your own work.
• The verbs fall as AI rises: think, make, fix, curate. The human role shifts from author to editor to selector.
• The boundary between levels is scrutiny, not tool choice. The same tool can sit at R or X depending on whether you can still check what it produced.
• Epigraph: Dijkstra, EWD667, "machines to be programmed in our native tongues" would be "as damned difficult to make as they would be to use." The page doesn't explain how it connects to the levels.

Patterns

• label work by who can still inspect it, not by the tool used ← "your ability to scrutinise the generated work"
• a shared label replaces moral judgement with plain description ← "with less judgement and confusion"
• borrow a familiar technical model to name a new problem ← "inspired by unix permissions"
• the last level is losing the ability to inspect your own output ← "YOU can no longer read your work"
• more delegation turns the maker into a selector ← "I curate"
• new tools need new words before people can discuss them ← "We need new language"