What is planned, what is deliberately not, and a one-paragraph summary of what already exists. Status of shipped work lives in the code and the per-topic docs, not here.
The runtime: the slot/binding schema with graph constraints, PostgreSQL
storage over recursive CTEs, versioned storage with branches, merge and
review, the compile-at-startup executor with delta recompilation and
cross-process invalidation, the full base-fn set (arithmetic, logic, HOFs,
collections, strings, system, HTTP server and client, HTML, CRUD), the type
system with refinements, records, unions and rich types, :fix recursion
(RECURSION.md), secrets as a taint type
(SECRETS.md), services with a reconciler, a Postgres queue
and service-to-service endpoints (SERVICES.md), org
sharding, quotas and a BYO executor (SCALING.md).
The surfaces: the visual editor with a server-computed layout, compare
mode as the diff surface, Explorer filters and views (kinds, namespaces, uses, effects, unused; views saved in the graph), chips for failed runs, type errors
and graph lint, an inspector with run history, path traces and a
step-through call tree; the REST API; the /mcp endpoint that lets an AI
client author graphs (MCP_CLIENTS.md); the package
registry and marketplace with themes and keymaps
(PACKAGE_DISTRIBUTION.md,
MARKETPLACE.md); in-graph tests with auto-run on write
(TESTS.md); the accounts module (ACCOUNTS.md);
the editor’s own assets editable in place as versioned overrides; the
tutorial (tutorial/) and the developer tour
(devtour/). The multi-tenant cloud policy ships from
the private graphden-tenancy repo over the seams in
TENANCY_SEAM.md.
Numbers are rough effort for one developer. Order is by value to the first external users; anything not listed under a block is not scheduled.
telegram-bot, postgres-client,
openai-client, discord webhook, bluesky; a social-post fan-out
fn-def over them so the project’s own announcements run through a
graph. ~1 week each.:python-call / :go-call base-fns for
cross-language reach at coarse granularity. Deferred until an
integration needs it; the launch packages are pure HTTP. ~1.5 weeks.The /mcp server and the graphden://ai-context resource are shipped;
users co-edit through their own MCP client (Claude Code, Cursor) at zero
model cost to the project. What remains:
ai/<slug>), an AI session against the user’s own model and key
through the same MCP tools, then the existing compare mode for accept /
reject. Bring-your-own-model: per-user key stored through the vault
surface on the cloud, client-side when self-hosted. ~2 weeks.Sharding, invalidation, quotas, service-to-service and the BYO executor
are shipped (SCALING.md). Open: a load-balancer rule that
routes by subdomain so the 421 misdirect stays a backstop, and a BYO
executor proven on a second physical machine end to end.
Changing a defbase body needs bb rebuild. An nREPL channel into each
executor plus a per-file re-sync would let the author push an impl into a
running executor. Risks: classloader hygiene, in-flight requests during
the swap, auth on the channel. ~2 weeks; blocks nothing.
editor-graph-view.js / editor-edges-svg.js.:exports fn-def per namespace
whose list items name the fns the author promises to keep across
versions: an update can warn “you depend on internals of P”, and the
install browser can show the public few. Enforced privacy is a
permanent non-goal (install materialises every fn; inherit-override
needs the internals), so any implementation stays visual-only. Trigger:
the first real package update that breaks a ref into internals.Research threads with a design but no schedule.
Automatic parallelisation across executors. The graph already names every dependency, so independent subgraphs are identifiable. Phases: local parallelism of independent args in one JVM; a worker pool on one machine; remote executors with network transport; cost-based partitioning. Open decisions: data transfer between executors, granularity, side-effect ordering, retry. See ARCHITECTURE.md § Distributed Execution.
Function types, rank-1 parametric polymorphism ([:list a],
[:map k v]), composition inference and typed HOF signatures are
implemented; see TYPES.md. Further type-system research
has no scheduled project here. Before proposing an extension, read
TYPE_SYSTEM_DECISIONS.md for the accepted
limits and rejected alternatives.
Shipped as VersionedStorage, branches, merge, review and per-branch routing; the design and known gaps are in VERSIONING.md.