Skip to content
Closed
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
2 changes: 1 addition & 1 deletion quest/m0/nightly/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ This README's own work, after the children:
fixtures were repaired in [moq-dev/moq#7940](https://github.com/moq-dev/moq/pull/7940).
The receive-windows benchmark's overcommitted cells, skipped since
[moq-dev/moq#7838](https://github.com/moq-dev/moq/pull/7838), moved to
[m1](/quest/m1/receive-windows-evicted.md) on 2026-11-04 (maintainer).
[m1](/quest/m3/receive-windows-evicted.md) on 2026-11-04 (maintainer).

Decided 2026-11-05 (maintainer, /quest-plan): catch the next moq-net bench
break in Nightly's measured coverage only. Do not add a test-mode bench run
Expand Down
2 changes: 1 addition & 1 deletion quest/m1/route-inductive.md
Original file line number Diff line number Diff line change
Expand Up @@ -66,4 +66,4 @@ Public API: none. Wire: none.

## Related

- [Route sweeps are checked against the TLA+ model](/quest/m1/route-trace-validation.md) - ties the same spec to the code
- [Route sweeps are checked against the TLA+ model](/quest/m3/route-trace-validation.md) - ties the same spec to the code
4 changes: 2 additions & 2 deletions quest/m2/cluster-routes/route-exhaustive-sim.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ out.
- A search that takes seconds joins the merge gate; a larger one runs in
Nightly.

This sits beside [trace validation](/quest/m1/route-trace-validation.md), which
This sits beside [trace validation](/quest/m3/route-trace-validation.md), which
keeps the TLA+ model honest for [the inductive invariant](/quest/m1/route-inductive.md)
and the design work done on the spec before code exists. It replaces neither
that nor the seeded sweeps on larger meshes
Expand All @@ -66,4 +66,4 @@ Public API: none. Wire: none.

## Related

- [Route sweeps are checked against the TLA+ model](/quest/m1/route-trace-validation.md) - guards the model against the code; this checks the code itself
- [Route sweeps are checked against the TLA+ model](/quest/m3/route-trace-validation.md) - guards the model against the code; this checks the code itself
4 changes: 2 additions & 2 deletions quest/m2/cluster-routing/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -143,7 +143,7 @@ are the cold cost that [cache-aware routing](/quest/m3/cache-routing/README.md)'
per-broadcast warm routes rank against (decided 2026-11-08, maintainer).

Each implementation updates the docs it makes stale. The separate
[routing guide](/quest/m1/routing-guide.md) explains the combined design and
[routing guide](/quest/m3/routing-guide.md) explains the combined design and
setup after the capabilities land.

## Required
Expand All @@ -153,7 +153,7 @@ setup after the capabilities land.
## Related

- [P2P](/quest/m4/p2p/README.md) - application-selected peer sessions feed the shared routing model
- [Routing guide](/quest/m1/routing-guide.md) - concept page and federation setup; P2P extends it in m4
- [Routing guide](/quest/m3/routing-guide.md) - concept page and federation setup; P2P extends it in m4
- [Route wakes](/quest/m4/route-wakes.md) - local work follows affected fronts rather than the whole covered table
- [Link quality](/quest/m5/link-quality.md) - optional measured link cost, distinct from delivery-health failover
- [Cache-aware routing](/quest/m3/cache-routing/README.md) - per-broadcast warm routes ranked against these node routes
2 changes: 1 addition & 1 deletion quest/m2/cluster-routing/federation.md
Original file line number Diff line number Diff line change
Expand Up @@ -79,4 +79,4 @@ Rust/JS parity. Run `just check`, `just test interop --all`, and `just drafts ch

## Related

- [Routing guide](/quest/m1/routing-guide.md) - runnable operator setup after integration
- [Routing guide](/quest/m3/routing-guide.md) - runnable operator setup after integration
2 changes: 1 addition & 1 deletion quest/m2/group-drops.md
Original file line number Diff line number Diff line change
Expand Up @@ -100,4 +100,4 @@ Wire: possibly lite-07 (SUBSCRIBE_DROP for a stopped group), decided here.
- [Address groups by timestamp](/quest/m2/time-addressing/model.md) - the drop range is keyed by start

## Related
- [The receive-windows benchmark](/quest/m1/receive-windows-evicted.md) - its overcommitted cells wait on this (skipped by [moq-dev/moq#7838](https://github.com/moq-dev/moq/pull/7838) until it lands)
- [The receive-windows benchmark](/quest/m3/receive-windows-evicted.md) - its overcommitted cells wait on this (skipped by [moq-dev/moq#7838](https://github.com/moq-dev/moq/pull/7838) until it lands)
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,15 @@ ordering for the Python or FFI audio consumers.

## Plan

Moved from m1 to m3 2026-11-13 (maintainer, /quest-plan): it requires
[Finalize moq-lite-07](/quest/m2/lite07-finalize.md), and a quest requiring one in a later milestone stalls,
since `quest unblocked` ranks a blocker by its own milestone. moq-dev/quest's
`quest check` is planned to reject such links.

- ✅ m3 (rejected: m2, which the [release cut](/quest/m3/release/cut.md)
requires whole, so the cut would wait on this additive work; pulling the
blocker into m1, which would drag breaking m2 work with it)

Motivated by the moq.dev Voice demo: each TTS reply is a fresh track whose
head arrives newest-first, which shifted Chrome's decoder timeline and
overflowed the ring (moq-dev/moq#6523), then clipped each reply's opening
Expand All @@ -38,7 +47,7 @@ Decided 2026-10-23 by the maintainer:
max-delay release rules go. Not chosen: delete the hold outright; keep
#6549's rules unchanged.
- ✅ The hold stays audio-only. Video's startup hold is the poster quest's.
- ✅ Placed in m1, requiring [Finalize moq-lite-07](/quest/m2/lite07-finalize.md):
- ✅ Placed in m1 (superseded 2026-11-13: m3, above), requiring [Finalize moq-lite-07](/quest/m2/lite07-finalize.md):
lite-06 and earlier serve an ascending request newest-first, so this is a
no-op on default sessions until lite-07 negotiates by default. `release`
has no `order` field, so it ships in the next minor, not a 0.6.x patch.
Expand Down
2 changes: 1 addition & 1 deletion quest/m3/cache-routing/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -200,7 +200,7 @@ This README's own work, once its children land:
broadcasts by the hash.
- Docs: warm routes and how to price skip links in `doc/bin/relay/cluster.md`,
and a section on the routing concept page once the
[routing guide](/quest/m1/routing-guide.md) has added it.
[routing guide](/quest/m3/routing-guide.md) has added it.

## Related

Expand Down
11 changes: 10 additions & 1 deletion quest/m1/export-order.md → quest/m3/export-order.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,15 @@ an 11.7 s delay, where SRT loses about 0.

## Plan

Moved from m1 to m3 2026-11-13 (maintainer, /quest-plan): it requires
[Finalize moq-lite-07](/quest/m2/lite07-finalize.md), and a quest requiring one in a later milestone stalls,
since `quest unblocked` ranks a blocker by its own milestone. moq-dev/quest's
`quest check` is planned to reject such links.

- ✅ m3 (rejected: m2, which the [release cut](/quest/m3/release/cut.md)
requires whole, so the cut would wait on this additive work; pulling the
blocker into m1, which would drag breaking m2 work with it)

Decided 2026-11-12 (maintainer, `/quest-import` of
[moq-dev/moq#8559](https://github.com/moq-dev/moq/issues/8559)):
✅ measure Ascending against Descending, then pick (rejected: Ascending for
Expand Down Expand Up @@ -38,7 +47,7 @@ The maintainer's reasoning, to keep in view:
- The right order may depend on the maximum latency.

The starting hypothesis to measure mirrors
[Buffered playback subscribes in ascending order](/quest/m1/buffered-ascending.md):
[Buffered playback subscribes in ascending order](/quest/m3/buffered-ascending.md):
an export with a nonzero playout delay (`Delay::min`) wants its window from
the start, and goes Ascending; one that chases the live edge stays
Descending.
Expand Down
2 changes: 1 addition & 1 deletion quest/m3/quic-path-return.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,5 +54,5 @@ Public API: none. Wire: none.

## Related

- [Buffered exports pick their group order by measurement](/quest/m1/export-order.md) - the send-order half of the same outage
- [Buffered exports pick their group order by measurement](/quest/m3/export-order.md) - the send-order half of the same outage
- [Per-stream and per-datagram deadlines](/quest/m4/quic-deadline.md) - faster recovery below a deadline
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,15 @@ alongside throughput and latency, instead of failing.

## Plan

Moved from m1 to m3 2026-11-13 (maintainer, /quest-plan): it requires
[group-drops](/quest/m2/group-drops.md), and a quest requiring one in a later milestone stalls,
since `quest unblocked` ranks a blocker by its own milestone. moq-dev/quest's
`quest check` is planned to reject such links.

- ✅ m3 (rejected: m2, which the [release cut](/quest/m3/release/cut.md)
requires whole, so the cut would wait on this additive work; pulling the
blocker into m1, which would drag breaking m2 work with it)

Moved to m1 2026-11-04 with the maintainer, after
[moq-dev/moq#7838](https://github.com/moq-dev/moq/pull/7838) landed the
fitting cells: what remains waits on
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -9,12 +9,21 @@ resync the model.

## Plan

Moved from m1 to m3 2026-11-13 (maintainer, /quest-plan): it requires
[the router's route per scope](/quest/m2/cluster-routes/scope.md), and a quest requiring one in a later milestone stalls,
since `quest unblocked` ranks a blocker by its own milestone. moq-dev/quest's
`quest check` is planned to reject such links.

- ✅ m3 (rejected: m2, which the [release cut](/quest/m3/release/cut.md)
requires whole, so the cut would wait on this additive work; pulling the
blocker into m1, which would drag breaking m2 work with it)

Decided 2026-11-10 (maintainer, /quest-plan), as the strongest guard against
the route model drifting from the code ([moq-dev/moq#8447](https://github.com/moq-dev/moq/pull/8447)).

Decided 2026-11-10 (maintainer, a later /quest-plan the same day):

- ✅ m1 (rejected: staying in m4). The mesh configs beside it, the
- ✅ m1 (rejected: staying in m4; superseded 2026-11-13: m3, above). The mesh configs beside it, the
[inductive invariant](/quest/m1/route-inductive.md), and the
[cache-aware routing proof](/quest/m2/cache-routing-proof.md) all build on
`RouteHandoff.tla`, so drift there costs the most.
Expand Down
12 changes: 11 additions & 1 deletion quest/m1/routing-guide.md → quest/m3/routing-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,17 @@ outbound local relays, including priorities, costs, and continuity.

## Plan

The 2026-10-15 release audit keeps federation guidance in m1. Deferred P2P
Moved from m1 to m3 2026-11-13 (maintainer, /quest-plan): it requires
[outbound federation](/quest/m2/cluster-routing/federation.md), and a quest requiring one in a later milestone stalls,
since `quest unblocked` ranks a blocker by its own milestone. moq-dev/quest's
`quest check` is planned to reject such links.

- ✅ m3 (rejected: m2, which the [release cut](/quest/m3/release/cut.md)
requires whole, so the cut would wait on this additive work; pulling the
blocker into m1, which would drag breaking m2 work with it)

The 2026-10-15 release audit kept federation guidance in m1, until the move
above. Deferred P2P
owns the later application-selected peer setup and extends this concept page.
Every feature PR still fixes docs it makes stale.

Expand Down
8 changes: 8 additions & 0 deletions quest/m5/bun-lint-release.md → quest/m4/bun-lint-release.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,14 @@ it is.

## Plan

Moved from m5 to m4 2026-11-13 (maintainer, /quest-plan):
[formatter defaults](/quest/m4/formatter-defaults.md) requires it, and a quest
requiring one in a later milestone stalls, since `quest unblocked` ranks a
blocker by its own milestone. m4's Goal already holds conditions on outside
parties that only later work needs.

- ✅ m4 (rejected: moving formatter defaults to m5)

Announced on 2026-10-15 for "the next version" and only on canary
(`bun upgrade --canary`) when written on 2026-10-29; nixpkgs-unstable carried
bun 1.4.2. On 2026-11-02, nixpkgs-unstable's bun 1.4.4 still answers
Expand Down
2 changes: 1 addition & 1 deletion quest/m4/formatter-defaults.md
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@ Decided with the maintainer on 2026-11-03:

## Required

- [Wait for a stable bun lint](/quest/m5/bun-lint-release.md) - `bun lint`
- [Wait for a stable bun lint](/quest/m4/bun-lint-release.md) - `bun lint`
ships in a stable Bun that nixpkgs carries

## Related
Expand Down
2 changes: 1 addition & 1 deletion quest/m4/quic-deadline.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ Restored 2026-11-12 in m4 (maintainer, `/quest-import` of
m5 for want of a consumer. The consumer: MPEG-TS trunks under a fixed
`moq export ts --delay`, which compete with SRT on delivering whatever can
still arrive within the delay. The outage loss that issue measured belongs to
[Buffered exports pick their group order by measurement](/quest/m1/export-order.md)
[Buffered exports pick their group order by measurement](/quest/m3/export-order.md)
and [A path that's back is used within an RTT](/quest/m3/quic-path-return.md),
not this quest: the early probe never exceeds the congestion window, which is
full of unacknowledged packets during an outage. This quest is the
Expand Down
4 changes: 2 additions & 2 deletions quest/m4/reconnect-trace-validation.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ moq-net): every TLA+ model gets trace validation, not route alone. Milestone
m4, behind route's.

- Reuse the trace format and the TLC recipe
[route trace validation](/quest/m1/route-trace-validation.md) builds, with
[route trace validation](/quest/m3/route-trace-validation.md) builds, with
the `verify-reconnect` skill's Coverage table as the mapping from code to
model actions.
- `reconnect/tests.rs` holds fixtures, not a sweep. Add a seeded one on the
Expand All @@ -32,4 +32,4 @@ Public API: none. Wire: none.

## Required

- [Route sweeps are checked against the TLA+ model](/quest/m1/route-trace-validation.md) - the trace format and TLC recipe this reuses
- [Route sweeps are checked against the TLA+ model](/quest/m3/route-trace-validation.md) - the trace format and TLC recipe this reuses
4 changes: 2 additions & 2 deletions quest/m4/resume-trace-validation.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ moq-net): every TLA+ model gets trace validation, not route alone, so none
can keep passing on code that has moved on. Milestone m4, behind route's.

- Reuse the trace format and the TLC recipe
[route trace validation](/quest/m1/route-trace-validation.md) builds. The
[route trace validation](/quest/m3/route-trace-validation.md) builds. The
sweep records each step as the model action it corresponds to (the
`verify-resume` skill's Coverage table is the mapping) with the variables
the model keeps, and TLC checks the trace is a behaviour of the spec.
Expand All @@ -32,7 +32,7 @@ Public API: none. Wire: none.

## Required

- [Route sweeps are checked against the TLA+ model](/quest/m1/route-trace-validation.md) - the trace format and TLC recipe this reuses
- [Route sweeps are checked against the TLA+ model](/quest/m3/route-trace-validation.md) - the trace format and TLC recipe this reuses

## Related

Expand Down
4 changes: 2 additions & 2 deletions quest/m4/subscribe-trace-validation.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ moq-net): every TLA+ model gets trace validation, not route alone. Milestone
m4, behind route's.

- Reuse the trace format and the TLC recipe
[route trace validation](/quest/m1/route-trace-validation.md) builds, with
[route trace validation](/quest/m3/route-trace-validation.md) builds, with
the `verify-subscribe` skill's Coverage table as the mapping from code to
model actions.
- The model's steps are spread over `lite/publisher.rs` (`TrackRun`,
Expand All @@ -34,7 +34,7 @@ Public API: none. Wire: none.

## Required

- [Route sweeps are checked against the TLA+ model](/quest/m1/route-trace-validation.md) - the trace format and TLC recipe this reuses
- [Route sweeps are checked against the TLA+ model](/quest/m3/route-trace-validation.md) - the trace format and TLC recipe this reuses

## Related

Expand Down