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_continuum-admission-family-cutover.md
Original lane: up-next
Original legend: PLATFORM
Original backlog card
PLATFORM - Continuum admission family cutover
Echo now has enough doctrine to stop hand-waving about admission at the shared
boundary. The next platform cut is to choose a small admission-facing family
slice and move it toward the Continuum/Wesley proof path.
This cycle should connect:
BoundedSite- admission outcome family
- shell versus witness layering
- policy identity where it affects published causal meaning
to the existing PLATFORM_continuum-proof-family-runtime-cutover work, without
trying to move the whole runtime across the boundary at once.
The current runtime now has enough truthful mapping to drive that platform cut:
TickReceiptDisposition::Applied => DerivedTickReceiptDisposition::Rejected(FootprintConflict) => ObstructionNeighborhoodSite::Singleton => DerivedNeighborhoodSite::Braided => PluralSettlementDecision::ImportCandidate => DerivedSettlementDecision::ConflictArtifact => Conflict
The next step is not inventing more local nouns. It is selecting one generated
Continuum family slice that can carry this same outcome algebra and shell /
witness layering across the Echo boundary.
The first concrete target for that cut is now:
- Continuum packet:
docs/design/0022-neighborhood-core-and-admission-outcome-family/README.md
- authored family:
schemas/continuum-neighborhood-core-family.graphql
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_continuum-admission-family-cutover.mdOriginal lane:
up-nextOriginal legend:
PLATFORMOriginal backlog card
PLATFORM - Continuum admission family cutover
Echo now has enough doctrine to stop hand-waving about admission at the shared
boundary. The next platform cut is to choose a small admission-facing family
slice and move it toward the Continuum/Wesley proof path.
This cycle should connect:
BoundedSiteto the existing
PLATFORM_continuum-proof-family-runtime-cutoverwork, withouttrying to move the whole runtime across the boundary at once.
The current runtime now has enough truthful mapping to drive that platform cut:
TickReceiptDisposition::Applied=>DerivedTickReceiptDisposition::Rejected(FootprintConflict)=>ObstructionNeighborhoodSite::Singleton=>DerivedNeighborhoodSite::Braided=>PluralSettlementDecision::ImportCandidate=>DerivedSettlementDecision::ConflictArtifact=>ConflictThe next step is not inventing more local nouns. It is selecting one generated
Continuum family slice that can carry this same outcome algebra and shell /
witness layering across the Echo boundary.
The first concrete target for that cut is now:
docs/design/0022-neighborhood-core-and-admission-outcome-family/README.mdschemas/continuum-neighborhood-core-family.graphql