Learn the boundary
Read current implemented capabilities, claims and the Pack YAML contract.
EIK / SELF-SERVICE / SYNTHETIC REFERENCE
Developers & AI Agents
Understand the contract. Build your own Pack. Contribute only if you choose.
PayGod's EIK entry uses an existing deterministic Kernel and portable evidence. Create private policy Packs, compare native tools, and check bounded results. The GitHub Actions reference is a saved synthetic scan, not a live security-scanner or release-authorization integration.
Build privately
Author and test a private Pack without a PayGod account or mandatory upstream PR.
Run the reference
Reproduce saved-report admission, canonical CLI and no-checkout recipient verification.
Contribute optionally
Send a focused PR only if the improvement belongs in the public repository.
Agent instructions ↗ Machine-readable capability description ↗ Current EIK evidence and unresolved tests ↗ Read verified claims and limits ↗
What this does NOT establish
No authenticated real scanner, no mandatory runtime source admission, no permission to deploy or move funds, no independent organizational adoption, no EIK SDK, MCP/A2A service or Pack marketplace. A valid bundle checks scoped integrity, not source truth or delegated authority.
Next validation required
Request an unfamiliar developer/agent to repeat the example; test an authorized real saved report; compare against GitHub-native controls and direct CLI; ask a genuinely independent recipient to explain the result and its limits.
Back to home ↗