KERNEL - Braid and Settlement Admission Unification

[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_braid-settlement-admission-unification.md
Original lane: up-next
Original legend: KERNEL

Original backlog card

KERNEL - Braid and Settlement Admission Unification

Strands now obey the one-super_tick() law in doctrine and runtime shape, but
braid and settlement still risk feeling like side corridors instead of further
instances of the same admission architecture.

This cycle should push Echo toward one honest story:

• braid comparison is a plural object over a common basis
• collapse or settlement is an admission act over that plural object
• lawful outcomes remain Derived, Plural, Conflict, or Obstruction
• publication artefacts stay distinct from witness cores

The first cut should narrow the semantic gap, not solve the entire final braid
ontology.

[coderabbitai]

🔗 Related PRs

#323 - Witnessed suffix admission evaluator [merged]
#326 - Echo contract hosting roadmap [merged]
#347 - feat(core): add basis-bound optic admission shell [merged]
#351 - feat(core): add basis resolution v0 boundary [merged]
#358 - feat(core): add admission evidence boundaries [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!