Layers
User-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.
guest@sudoscience.dev:~
$ sudo science
# permissionless innovation
# science with privileges
an industrial research lab
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.
signal field
systems under inspection
The graph is a navigable atmosphere for nearby problems, projects, substrates, and methods. It is meant to be explored, not read as an org chart.
investigations
current lines of work
instagrate-me
Machine-readable domain observability.
A governed surface for seeing what machines try to discover about an organization, then publishing and monitoring the metadata they need.
instagrate-me.sudoscience.dev ->EZAF
User-owned execution across web surfaces.
Websites can request work, but users own review, routing, execution, and release.
ezaf.sudoscience.dev ->DESH
A hypermedia-native developer environment.
DESH treats commands, docs, state, provenance, replay, examples, workflows, artifacts, and system transitions as graph-backed, event-sourced objects.
desh.sudoscience.dev ->Structured 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.
Webpoke
A 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.
webpoke.sudoscience.dev ->Unfiled
Code is a graph, not a filesystem.
The disruption as forcing function: declarative, intentional speech pushes API boundaries to where they always belonged. Functions, tests, scenarios, CQRS/ES, components, event models, and C4 constructs become top-level objects.
unfiled.sudoscience.dev ->method
design -> implement -> evaluate
We study systems by building them.
design
Design shapes the interaction.
implement
Implementation exposes the constraints.
evaluate
Evaluation turns use into evidence.
01websites monopolize interpretation
02domains leak machine-readable truth across many places
03shells are text streams over hidden state
04documents are inert even when they contain structure
05workflows disappear into logs, chats, and tabs
06organizations cannot replay how systems changed
07protocols are hard to evaluate in practice
collaboration
bring a system worth making inspectable.
Collaborating with builders, labs, standards groups, institutions, and communities working near interfaces, protocols, environments, provenance, evaluation, and machine-readable surfaces.
hello@sudoscience.dev