Skip to content

Roadmap ​

Ten milestones, in build order. Each one ends with something you can run.

#MilestoneDone whenStatus
0Core + specSigned cards, signed messages, rules engine, collective counter, ODRL offers, SPEC.md, schemas, modeldone
1One housePod, WebID, issuer-signed synthetic record, housekeeper answering an A2A request through MCPdone
2The LakeA federatable node: verified cards, bus, event stream, a bare map where houses appeardone (bus moves to M3, with broadcast)
3Mission, no moneyEthics, audit, knock, decide, grant, verify signatures, compute in place, answerdone
4Approvals appLive Allow on a phone; revocation in under 1 seconddone
5MoneyODRL agreements, collective counter-offer, AP2 mandates, Payments agentdone
6Wild lifeSwarm, attackers, prompt-injection defence, quarantine, guilds, reputationdone
7Scale1,000 houses, a full mission in about 60 secondsruns 1,000 houses complete a paid mission; 10.6 min on a busy 4-core laptop, measured
8FederationSecond node, .well-known discovery, direct messaging, shared blocklists; stop a node mid-mission and finish anywaydone
9Open doorAgent SDK, Lake MCP connector, public sandbox Lakedone (sandbox config ready, not yet deployed)
10PolishMap matches the reference, seeded demo mode, 90-second recordingnext

Acceptance tests ​

The Lake is done when all of these pass:

  • docker compose up on a clean laptop starts the Lake with no manual steps.
  • A new house appears on the map within 5 seconds.
  • A full mission completes at 1,000 houses in about 60 seconds.
  • No grant exists that a human didn't approve, live or by standing rule, and the audit log proves it.
  • Records moved is 0 after a full mission, computed from pod audit logs, not hard-coded.
  • Every attacker request is blocked and logged, prompt injection included.
  • Revoking a house's keys cuts its access within 1 second.
  • A tampered record fails its signature check; that house is excluded and unpaid.
  • Stopping one Lake node mid-mission doesn't stop the mission.
  • An agent is findable through its .well-known card with every registry offline.
  • An outside agent built with the SDK joins and completes a study in the sandbox.
  • An AI assistant dispatches a study through the Lake MCP connector.
  • Seeded demo mode produces the same run every time.
  • Every agreement and receipt can be opened in the owner's pod afterwards.

Apache-2.0 · Synthetic data only · Nobody owns the Lake.