Say what you will compile.

Access opens the layer end to end: the engine's verbs on your own corpus, the join against the pinned EPCIS 2.0 schema, and the MCP door for the agent that will run it after you. The address comes first; everything after it is optional.

Get on the access list.

Step one is an address — only an address. After it, a handful of optional questions, each one chosen by your previous answer, about what you have actually done — never what you might buy. Access is provisioned from this list.

Access is provisioned from this list. We use your address to tell you when yours is ready and to follow up about it; you can tell us to stop at any time. We don't sell it or hand it to advertisers. If we stop working on this, we say so rather than go quiet.

One address in, no reply-to-book-time, no scheduling link. The row is what you give it — address, timestamp, and the answers you choose to give — plus a token we mint for that row so nobody who merely knows your address can open it. We use your address to follow up about this; we don’t sell it or hand it to advertisers. Separately, this origin does record the request itself — the referring page, the user agent, the address and the network it came from, and whether we judge the caller a person, an agent or a crawler. That is its own store, and the address is taken out of it after 30 days — while the estate’s append-only event ledger is never rewritten: what we log, in full.

Read before you sign up, if you prefer.

The layer's laws are on the landing page; the worked 856 run, the core-field argument and the reconcile transcript are on the blog; the family's event door — where the emitted events land — is epcis.dev, and its calculators answer on that origin with no key.