003. The build
One useful foundation.
Then the next.
Our first goal is to help first-time builders and business owners understand what their app needs to handle responsibly. Then make those practices easier to implement with open tools.
The website, learning guide, and initial law library are available. OPS Guide and its MCP interface, the consent engine, SDKs, and conformance tests remain planned work.
01 / The plan
Make the promise tangible.
01 — AVAILABLE
Publish the foundations.
The open letter, manifesto, beginner guide, six source-linked law summaries, scope draft, and website source are available to read and adapt.
02 — PLANNED
Build the guidance layer.
Review a narrow rule database, test explanations with first-time builders, and develop OPS Guide with a website and MCP interface.
03 — PLANNED
Define the first contract.
Specify consent events, preference state, purpose definitions, receipts, and decision behavior. Publish examples and discuss the difficult edge cases.
04 — PLANNED
Build a reference implementation.
Create a self-hostable service and TypeScript SDK. Demonstrate a working preference center with grant, refusal, and withdrawal.
05 — PLANNED
Prove the behavior.
Publish conformance tests for state transitions, tenant isolation, repeated events, and enforcement after withdrawal.
06 — PLANNED
Learn from real applications.
Document integrations, review security and privacy behavior, and improve the contract before expanding its scope.
02 / The first release
A deliberately small scope.
| In scope | What it should make possible |
|---|---|
| Consent events | Record and update explicit choices for defined purposes. |
| Preferences | Read effective choices and give people a way to change them. |
| Decisions | Check whether a configured use is permitted and explain why. |
| Receipts | Export the context and evidence behind a choice. |
| Tests | Verify behavior against a published contract. |
Automated legal compliance, enterprise discovery, and a complete security platform are beyond this first release.
03 / How we work
Build in the open.
Study public documentation and authorized product behavior. Write independent specifications and original code. Publish the reasoning behind design decisions.
Progress will be recorded as it happens. Planned work will remain labeled until it is usable.