Working Principles
The editorial and system rules for keeping this site useful instead of adding more filler to the web.
The site is intentionally smaller now. The previous shape had many pages saying nearly the same thing: systems, experiments, logs, notes, and catalog placeholders all pointing at the same handful of ideas. That is not useful. It creates the feeling of activity without adding understanding.
Publication rule
A new page has to do at least one of these:
- Explain an operating system. What it reads, what it writes, who reviews it, and how it fails.
- Expose a useful artifact. A diagram, workflow, benchmark, trail, or decision record that is better public than private.
- Teach a reusable lesson. Something another builder could apply without knowing the private context.
If it only restates the homepage, it should not be a page.
Agent workflow rule
Agent work is worth documenting when it has a narrow job, a clear contract, and a visible failure mode. “Help me with my work” is not a workflow. “Summarize pending drops, propose tags, and wait for confirmation” is.
The point is not to show that agents were used. The point is to make the work inspectable: what the agent was allowed to decide, what it had to hand back, and where the human review entered the loop.
Catalog rule
A catalog is not a pile of saved links. It is a selected record with reasons attached. The same rule applies to the website: fewer entries, stronger reasons, easier reading.
The site should add value by leaving a coherent map behind, not by generating a page for every internal moving part.