take root
Permissionless innovation. Don't ask a system for permission to inspect it, extend it, or reinterpret it — elevate and find out.
$ sudo science
# permissionless innovation — science with privileges
An industrial research lab for experimental interfaces, protocols, environments, and artifacts. We design, implement, and evaluate systems that make complex work more inspectable, augmentable, replayable, and evolvable — then ship them where they can be stressed, forked, and used.
sudo science does not try to be right first. It tries to make the right conversations possible.
show your work
Inspectable systems, inspectable lab. Every claim carries its status; every page carries its provenance; structure stays visible.
everything is a graph
Projects, problems, and artifacts are nodes with visible edges. Navigation is traversal, and the edges are part of the work.
build to find out
Design exposes the interaction, implementation exposes the constraints, evaluation turns use into evidence. Prototypes over position papers.
investigations
eight systems under inspection
Each project is a node with edges into the others: ledgers, manifests, permissions, provenance, and graphs keep reappearing because they are the same problem wearing different clothes.
Layers
prototypeuser-controlled meta-apps over the web
Layers are independent apps that run on top of existing websites, with their own domains, permissions, identity, data, UI, communities, and economic models.
/projects/layersno site yet
instagrate-me
prototypemachine-readable domain observability
A governed surface for seeing what machines try to discover about an organization, then publishing and monitoring the metadata they need.
/projects/instagrate-meinstagrate-me.sudoscience.dev
EZAF
prototypeuser-owned effect routing for agentic work
Websites may request agentic work, but users control review, execution, routing, and result release.
/projects/ezafezaf.sudoscience.dev
DESH
prototypethe terminal, with the amnesia removed
Twenty-plus years of daily terminal use, and the verdict is in: terminals and shells both suck — not at the edges, at the defaults. Warp, Fig, and nushell each fixed a symptom; the model survived them all.
/projects/deshdesh.sudoscience.dev
Avoidant
prototypestructured attachments — portable artifacts with affordances
Attachments that carry data, schema, behavior, provenance, and executable handles across email, decentralized social protocols, documents, WASM, MCP, GraphQL, and other introspectable systems.
/projects/avoidantno site yet
Webpoke
prototypea poke with a hint, then a ranged pull
Webhooks should not deliver truth in flight. A signed, content-free poke plus a cursor-owned ranged pull turns every delivery failure into latency instead of corruption.
/projects/webpokewebpoke.sudoscience.dev
Unfiled
prototypecode is a graph, not a filesystem
The current disruption is a forcing function: to delegate work you must say what you mean, declaratively and intentionally — and once you do, API boundaries move to where they should have been all along.
/projects/unfiledunfiled.sudoscience.dev
Rhett
sketchfield agents on every page — rhetoric, operationalized
Page-local research agents that continuously map the living field around each investigation on this site: prior art, credible actors, felt pain, counterexamples, and translations for whoever just arrived.
/projects/rhettno site yet
method
design → implement → evaluate
We study systems by building them.
design
Design shapes the interaction. The sketch is a hypothesis about how a system should feel to inspect.
implement
Implementation exposes the constraints. If it can't be built, the idea wasn't finished.
evaluate
Evaluation turns use into evidence. Deployed prototypes are the lab's instruments.
orientation
three lenses, three questions
Every problem gets looked at through all three lenses before the lab commits to a build. The distance between the answers is where the accidental complexity lives — and accidental complexity is the lab's standing quarry.
the comfortable lens
How would we achieve this with the stack the team already trusts — and what does that cost?
the state-of-the-art lens
How would we achieve it (or reformulate it, or avoid it entirely) with the best available tools — and what does that cost?
the first-principles lens
How would we achieve it if nothing existed yet — and what does that cost? The gap between the three answers is the accidental complexity.
idea → product
What is the shortest path from an idea to a working product?
accidental complexity
How much of our work is the problem, and how much is the packaging? What can we do about the packaging?
zero → creator
What is the shortest path from not knowing how to program to being able to make something?
The flywheel: better tools make teaching and learning faster, which makes the next tool better. Exhaust becomes tutorials; sessions become examples; learners become teachers. The lab optimizes the loop, not the lap.
faq
the questions are real. the framings are negotiable.
“How do I sandbox a coding agent?” “Why didn't my webhook fire?” “Feature folders or layer folders?” — real questions, answered by showing why the framing can't produce a good answer, and which investigation it routes to.
limbo
the small plates menu
Not everything here has collapsed into a project yet. The uncommitted ideas live in superposition on a tasting menu, served by the house — order one enough times and it graduates.
collaboration
making ecosystems sustainable.
Collaborating with builders, labs, standards groups, institutions, and communities working near interfaces, protocols, environments, provenance, evaluation, and machine-readable surfaces.