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, in order.

Access is provisioned from this list, in order. One email when yours is ready — one, not a drip campaign; no newsletter, no sequence. If we stop working on this, you get one message saying so and your address is deleted. Either way it is one message.

Write-only: one address in, no reply-to-book-time, no scheduling link. The list lives on this origin and goes nowhere else. The row is exactly what you give it — address, timestamp, and the answers you choose to give. Nothing derived: no referrer, no user-agent, no analytics.

We answer in writing. We take at most five conversations a month, only when you ask for one, and only after you already have the written read.

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.