Adoption Paths (Human + Agent)

EEP is designed so organizations and coding agents can adopt the protocol with the same source of truth. The fastest path is: clone, bootstrap, validate locally, then run compliance against your own platform. For greenfield/brownfield artifact generation, start with Quick Setup CLI and the post-setup integration guide ↗.

1) Clone and bootstrap

Repository Setup

git clone https://github.com/eep-dev/EEP.git
cd EEP
bash scripts/bootstrap.sh

# run full repo checks
bash test.sh

2) Pick your minimum conformance target

Target	When to choose it	Minimum capabilities
Core	You need discovery + push stream quickly	Layer 1 REST + SSE + CloudEvents
Standard	You need production webhook integrations	Core + Webhooks + HMAC verification + payment/credential gates
Full	You need live negotiation and autonomous commerce	Standard + WebSocket pulse + commerce/session controls

3) Enforce zero-trust defaults from day one

Use semantic verifier registries for gate proofs, not structural checks alone.
Keep resolver mode fail-closed (default) unless you explicitly document an exception.
Validate webhook signatures with timing-safe compare and 60-second timestamp tolerance.
Apply SSRF protections before outbound webhook delivery, including IPv6 private/link-local ranges.

4) Production references

5) Narrated demo (optional)

For a side-by-side terminal story contrasting legacy HTML scraping with gate-based JSON (deterministic, no LLM calls), see the realworld simulation guide ↗ and run npm run demo from realworld-simulation/ in the EEP repo.