PLATFORM - Neighborhood publication stack documentation

[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_neighborhood-publication-stack.md
Original lane: up-next
Original legend: PLATFORM

Original backlog card

PLATFORM - Neighborhood publication stack documentation

Echo now has enough real neighborhood publication truth that the stack needs a
single durable explanation, not scattered comments and chat archaeology.

This cycle should write down:

• the difference between commit-time emissions and read-time publications
• the role of BoundedSite, ObservationArtifact, NeighborhoodSite, and
  NeighborhoodCore
• the exact host/publication path through echo-wasm-abi and warp-wasm
• what the host should request when it wants raw observation, Echo-native local
  site truth, or the shared Continuum family projection

The goal is not new runtime law. The goal is to stop forcing maintainers and
host authors to reverse-engineer the publication stack from code.

Related:

• docs/design/0005-echo-ttd-witness-surface.md
• docs/design/0007-braid-geometry-and-neighborhood-publication.md
• docs/design/0010-bounded-site-and-admission-policy.md
• docs/spec/SPEC-0009-wasm-abi-v3.md

[coderabbitai]

🔗 Related PRs

#326 - Echo contract hosting roadmap [merged]
#329 - Stack Witness 0001 fixture-backed jedit walking skeleton [merged]
#365 - feat(wesley): emit query observer host helpers [merged]
#371 - feat(core): advance v0.1 contract evidence and retention [merged]
#380 - feat(core): expose retained evidence posture on readings [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!