Partnering with sudoscience on platform layers, agentic developer infrastructure, and semantic code search

Developer Experience · AI infrastructure

DESH & EZAF: unbundling the dev environment, rebundling for agents

sudoscienceDESH · EZAF

DESH unbundles the IDE, terminal, and shell, then rebundles them onto scalable primitives: resources, projections, affordances, and a replayable ledger instead of scrollback and forgotten command strings. Its resource-centric, hypermedia model lets agents navigate by following affordances rather than reconstructing POSIX incantations, which saves thinking budget and shrinks context. The same surface is a migration layer off legacy shell constraints and can extend itself at runtime. New recognizers and affordances ship as sandboxed code-on-demand. EZAF decouples the intent of any side effect, including agentic inference calls, from execution. That separation simplifies sandboxing. DESH is where those effects land inspectably.

• Resources replace strings. Commands, outputs, timings, and effects are graph-backed objects, not text that burns on read.
• Affordance traversal instead of flag archaeology. Completion expands what a resource supports and cuts the tokens agents spend guessing syntax.
• Fork, replay, and share links over the ledger. Agent sessions become addressable traces without silent exfiltration.
• Runtime extension via sandboxed recognizers. The environment learns new types the way a browser learns new pages.
• EZAF separates declared intent from execution. Side effects, including model calls, are reviewed and routed before they run.

Code indexing · Review · Agent platforms

Unfiled — semantic code search, agentic coding models, and review at scale

sudoscienceUnfiled

Unfiled treats code as a graph of constructs — functions, tests, scenarios, commands, events — with the folder tree demoted to a projection. Meta's Glean already indexes facts about code at scale with Angle queries and Haskell .hie support; Unfiled asks what changes when diffs are semantic, identity survives motion, and history is a graph query instead of commit-message archaeology.

• Glean-shaped fact stores as prior art; Unfiled construct schemas as an overlay for decisions, scenarios, and semantic change sets.
• Code navigation on diffs — go-to-definition and find-references on changes under review, not only on trunk.
• Agentic coding models that address constructs, not files: agents emit intent over commands and events; review measures meaning changed.
• Scaling code review past line churn — "renamed PlaceOrder's timeout parameter" instead of forty lines because an import moved.
• Model-driven migration at scale — construct schemas and semantic change sets let refactors and platform shifts evolve over time, with replayable transformation history instead of one-shot rewrites.

Applied AI · Knowledge systems

Knowledge work — social annotation and ambient capture

Two surfaces address Meta-scale knowledge work from opposite ends. A social annotation app anchors discussion on PDFs, video, and long documents: select a region and humans and agents share one thread — feedback, translation, links, and tasks pinned to the passage or frame instead of scattered chat. A record-everything companion treats screenshots and screen moments as an append-only store of rich context; every capture lands in an inbox and gets triaged into one or more actionable todos.

• Annotation on documents and media — selection-scoped threads where humans and agents read and write the same anchors.
• Screenshot and screen capture as ledger entries — append-only context routed through triage, not camera-roll archaeology.
• Complements Meta's always-on capture stack — pendant, desktop recorder, keystroke instrumentation — with review surfaces and a backlog.
• Same triage question as large-scale code labeling: ambient signal only scales when something converts it into the next action.

Platforms · Browser · Immersive

Layers — unbundling the browser, rebundling interpretation

sudoscienceLayers

Layers is a model for disrupting the browser itself: unbundle the monolithic tab — rendering, identity, permissions, data, UI, communities, economics — and rebundle capability as installable meta-apps scoped to a host surface. The browser becomes substrate, not destination; users install interpretation the way they install software, without the page owner's cooperation. That same move scales to platform and metaverse surfaces — Horizon-scale worlds and social feeds as hosts, not prisons — but the web browser is where the unbundling story is clearest.

• Unbundle what the browser welded together: one origin owns the only lens; annotation, filtering, audit, automation, and alternate communities shouldn't require host permission.
• Rebundle as layers — independent apps with their own domains, permissions, identity, data, and lifecycle, composed onto static pages or platform surfaces.
• A static site stays static; sign-up, contact, uploads, and commerce arrive as layers instead of summoning a backend the page never wanted.
• Federation links between flat web and immersive surfaces — neither side owns the whole graph.