Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions quest/m1/announce-takeover.md
Original file line number Diff line number Diff line change
Expand Up @@ -126,8 +126,8 @@ separate from the identity rewrite of this Plan, which landed with
- Reword "takeover" as an event or operation, in terms of identity
continuity, in [moq-bench pins the instances it measures](/quest/m2/bench-epoch-pin.md)
(Goal and Plan), [the HLS server follows each path once](/quest/m2/hls-follow-once.md)
(Goal and Tests), and [routes and announces](/quest/m1/cluster-routing/routes.md)
(around line 37, "the separately proven Takeover operation").
(Goal and Tests), and [lite-07 route wire](/quest/m1/cluster-routing/routes/wire.md)
(the wire sketch, "the separately proven Takeover operation").
- Rewrite the EPOCH references in `drafts/draft-lcurley-moq-cluster.md` and
`drafts/draft-lcurley-moq-epoch.md` in terms of IDENTITY.
- Add a regression test where a publisher restart's new announcement
Expand All @@ -151,4 +151,4 @@ beyond [Instance and epoch](https://github.com/moq-dev/moq/pull/7489)'s fields.
- [Listing and follow](/quest/m1/api-audit/route/events.md) - continuity shows up inside `follow`, not as an event
- [Claim answer epochs](https://github.com/moq-dev/moq/pull/5678) - why a restarted job must never be stitched to its predecessor
- [Retired requests](https://github.com/moq-dev/moq/pull/5294) - replacements never substitute content into held handles
- [Routes and announces](/quest/m1/cluster-routing/routes.md) - the route layer whose ANNOUNCE_START layout carries the instance
- [Routes and announces](/quest/m1/cluster-routing/routes/README.md) - the route layer whose ANNOUNCE_START layout carries the instance
4 changes: 2 additions & 2 deletions quest/m1/api-audit/route/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ kinds. Rust, JS, moq-ffi, moq-c and the wrappers
mirror it.

Non-goals: the route layer's wire messages and federation
([Routes and announces](/quest/m1/cluster-routing/routes.md)), lite-07
([Routes and announces](/quest/m1/cluster-routing/routes/README.md)), lite-07
takeover ([announce takeover](/quest/m1/announce-takeover.md)), and any
moq-transport instance ([moq-transport carries no epoch](https://github.com/moq-dev/moq/pull/7239)).

Expand Down Expand Up @@ -174,4 +174,4 @@ stale, including `doc/concept/identity.md`.
## Related

- [A job's exact route continues its claim's readers](/quest/m1/announce-takeover.md) - a job's route inherits its claim's instance, so lite-07 readers keep the first subscribe
- [Routes and announces](/quest/m1/cluster-routing/routes.md) - the wire route layer; instances take over its epochless deletion
- [Routes and announces](/quest/m1/cluster-routing/routes/README.md) - the wire route layer; instances take over its epochless deletion
2 changes: 1 addition & 1 deletion quest/m1/api-audit/route/handle.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ read-only facts on a received announcement, and `Hop`, `Hops` and
Non-goals: the instance model ([Instance and epoch](https://github.com/moq-dev/moq/pull/7489)),
announce events ([Listing and follow](/quest/m1/api-audit/route/events.md)),
the read side, which instance owns, and the route layer's wire metric
([Routes and announces](/quest/m1/cluster-routing/routes.md)).
([lite-07 route wire](/quest/m1/cluster-routing/routes/wire.md)).

## Plan

Expand Down
10 changes: 5 additions & 5 deletions quest/m1/cluster-routing/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,8 +51,8 @@ Decided with the maintainer, 2026-10-13:
qualified when its publish grant is scoped, and stays bare when it is
unscoped, so a forger only damages routes inside its own scope. (Decided
2026-10-14; own identities included 2026-10-26, since they are no longer
proven.) How a scoped peer's identities are keyed is open in
[Routes and announces](/quest/m1/cluster-routing/routes.md): the
proven.) How a scoped peer's identities are keyed waits on the maintainer in
[Route session integration](/quest/m1/cluster-routing/routes/session.md): the
issuer-qualified subject key was dropped 2026-11-02 (maintainer).
- Matching explicit epochs authorize resume. Epochless changes retain
Restart and fresh resolution; neither node identity nor a healthy
Expand Down Expand Up @@ -86,7 +86,7 @@ Decided with the maintainer, 2026-10-13:

The handoff proof showed a complete neighbor snapshot does not prove its
claims are current; receivers merge origin-versioned views by floor instead.
The routing contract is recorded in [Routes and announces](/quest/m1/cluster-routing/routes.md)
The routing contract is recorded in [Routes and announces](/quest/m1/cluster-routing/routes/README.md)
with deterministic counterexamples: path-only subscriptions that reselect
origins at every hop loop and deadlock, so forwarded requests name their
identity; feasibility makes transit priorities depend on arrival order;
Expand All @@ -109,7 +109,7 @@ The 300 ms update hold alone is no longer the baseline. Keep regression
coverage for announcement churn, idle work, active continuity, and retained
state separately; fewer control bytes does not prove cheaper runtime work.

The earlier simulator estimates remain in [Routes and announces](/quest/m1/cluster-routing/routes.md).
The earlier simulator estimates remain in [Routes and announces](/quest/m1/cluster-routing/routes/README.md).
They do not prove the handoff correct; its fixtures do. Preserve public synthetic
fixtures and controlled-time regressions, including residual stale revival,
not only results from deployment tooling. Do not claim per-origin aggregation
Expand All @@ -126,7 +126,7 @@ setup after the capabilities land.

## Required

- [Routes and announces](/quest/m1/cluster-routing/routes.md) - implement the proven route layer with Rust/JS parity and tiered-cluster acceptance
- [Routes and announces](/quest/m1/cluster-routing/routes/README.md) - implement the proven route layer with Rust/JS parity and tiered-cluster acceptance
- [Outbound federation](/quest/m1/cluster-routing/federation.md) - an outbound-only local relay exchanges authorized broadcasts with the CDN and survives partition/healing

## Related
Expand Down
7 changes: 4 additions & 3 deletions quest/m1/cluster-routing/federation.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,8 +18,9 @@ Use authenticated, namespace-scoped admission: the CDN scopes the local
relay's connection to a path prefix, and identities it sends, its own and its
local publishers', are qualified, so a forger or a misconfigured uplink only
affects its own scope (decided 2026-10-14; see
[Routes and announces](/quest/m1/cluster-routing/routes.md)). Open: how
those identities are keyed, owned by routes. Without a key, a scoped forger
[Routes and announces](/quest/m1/cluster-routing/routes/README.md)). Open: how
those identities are keyed, owned by
[Route session integration](/quest/m1/cluster-routing/routes/session.md). Without a key, a scoped forger
declaring a victim's id captures claims outside its scope
(`forged_identity_hijacks_claims_outside_the_forgers_scope`). The scope
itself (`hash(scope, id)`) was rejected 2026-10-15, and the grant's
Expand Down Expand Up @@ -62,7 +63,7 @@ Rust/JS parity. Run `just check`, `just test interop --all`, and `just drafts ch

## Required

- [Routes and announces](/quest/m1/cluster-routing/routes.md) - identity, scoped claims, reachability, and export policy
- [Routes and announces](/quest/m1/cluster-routing/routes/README.md) - identity, scoped claims, reachability, and export policy

## Related

Expand Down
Loading
Loading