KERNEL - Bounded Site and Admission Policy

[flyingrobots]

Migrated from Method backlog

This issue was created from a legacy filesystem backlog card. GitHub Issues are now the live work tracker; repository docs remain Method evidence.

Source backlog: docs/method/backlog/up-next/KERNEL_bounded-site-and-admission-policy.md
Original lane: up-next
Original legend: KERNEL

Original backlog card

KERNEL - Bounded Site and Admission Policy

Echo already has one super_tick() law, several real policy surfaces, and
several partial site vocabularies. What it lacks is one explicit admission-law
packet that ties those pieces together.

This cycle should define Echo's admission-side BoundedSite, freeze the rule
that hosts choose engine-defined deterministic policy by reference rather than
injecting bespoke law, and restate super_tick() as admission over ingress
claims at bounded sites under explicit policy.

[coderabbitai]

🔗 Related PRs

#178 - TT0 (#166) TimeStreams + wormholes spec lock [merged]
#323 - Witnessed suffix admission evaluator [merged]
#326 - Echo contract hosting roadmap [merged]
#358 - feat(core): add admission evidence boundaries [merged]
#360 - feat(core): stage ticketed ingress and outcome observation [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!