Braid and settlement Intent paths

[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/PLATFORM_braid-settlement-intent-paths.md
Original lane: up-next
Original legend: PLATFORM

Original backlog card

Braid and settlement Intent paths

Status: planned implementation slice.

Depends on:

• Topology mutation Intent boundary audit
• Strand and support Intent paths

Why now

Braids and settlement decide how plural causal histories are projected,
retained, imported, or collapsed. Those decisions must be causal and replayable,
not direct host mutations.

Goal

Add Intent-level external paths for braid member append/collapse/settlement and
strand settlement execution, while keeping compare/plan/read surfaces
side-effect free.

Likely files touched

• crates/echo-wasm-abi/src/kernel_port.rs
• crates/warp-core/src/settlement.rs
• crates/warp-core/src/neighborhood.rs
• crates/warp-core/src/optic.rs
• crates/warp-core/src/cmd.rs
• crates/warp-wasm/src/lib.rs
• crates/warp-wasm/src/warp_kernel.rs
• crates/warp-core/tests/**

Acceptance criteria

• Compare/plan settlement remain read-only publication surfaces.
• Executing settlement has an Intent equivalent and records causal receipt
  evidence.
• Appending a braid member, settling/collapsing a braid, or admitting a braid
  projection is represented as an Intent when exposed externally.
• Preserved plurality remains typed; it is not hidden as success/no-op.
• Direct settlement execution ABI surfaces, if retained temporarily, are marked
  compatibility/debug and are not required by jedit-style or Continuum-style
  flows.

Non-goals

• Do not add jedit text operations.
• Do not flatten support pins into imports.
• Do not implement network transport.
• Do not make braid projection cached text canonical.

Test expectations

• Settlement execution through Intent emits receipt/witness evidence.
• Direct settlement execution is not required by the public flow test.
• Plural and conflict outcomes remain visible.
• Braid member append requires explicit basis and does not mutate stale
  projection silently.

[coderabbitai]

🔗 Related PRs

#247 - M2.1: DPO concurrency litmus (spec + tests) [merged]
#323 - Witnessed suffix admission evaluator [merged]
#353 - Fix WASM application intent authority boundary [merged]
#358 - feat(core): add admission evidence boundaries [merged]
#368 - feat(core): connect installed contract intent pipeline [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!