Repository navigation
id(phase-14): Scale & performance hardening — v2 — outline: growth policy #6305
Description
Scale & performance hardening — v2 — outline: growth policy
Part of the Phase 14 core topic #6281 (Scale & performance hardening), filed from the next-horizons discussion #1240 per Drew's 2026-11-05 decision. The Phase 14 epic links the whole map.
Scope (rough outline — the core topic's research refines it)
Journal snapshot/compaction policy, presence and fan-out budgets, degradation ladder implemented behind the metrics from #553.
Entry condition
The previous step (v1 — first-iteration design) has its design written, with open questions answered or explicitly deferred to this step.
Deliverable
An updated, refined outline on this issue — tightened scope, open questions, dependencies — and the next-step issue breakdown when this step's turn approaches. If the step has dissolved into the previous one, close this issue with that note (drop rule).
Drew's Phase 14 principles (#1240) govern this step: local-first always; hostable by anyone at any scale; p2p behavior identical to hosted behavior; our hosted instance is the public backstop, never a requirement.
Acceptance criteria
- The deliverable named in this issue exists and is linked from this issue and from its Phase 14 core topic (id(phase-14): Scale & performance hardening — core topic (research + design) #6281): a refined outline/design for this step that answers the scope questions the body raises and is ready to break into implementation issues
- The entry condition stated in this issue is verified met before design work starts, and the verification is recorded on this issue.
- Follow-up implementation issues are filed for the breakdown this design produces, and linked from this issue (native sub-issues/relations where the tooling supports them).
- The design is consistent with Drew's Phase 14 principles from id: next horizons — what comes after Phase 13 (discussion with Drew) #1240 (local-first; hostable by anyone at any scale; p2p behavior identical to hosted; the hosted instance is a public backstop, never a requirement), as recorded on the plan-of-record epic id: Phase 14 — hosted, federated, local-first (plan of record) #6312.
Activity
developing-today commentedon Nov 5, 2026
CODE-1870
developing-today commentedon Nov 5, 2026
Intake review
Fleet monitor intake (2026-11-05 run): verified OPEN, filed 2026-11-05 as part of the Phase 14 filing burst from the #1240 next-horizons decision.
Related: plan-of-record epic #6312; core topic #6281; sibling Phase 14 step issues #6298–#6311 (same filing burst — v1 designs and v2/v3/v4 outlines per theme).
Notes: This is a follow-up outline step for Phase 14, not an implementation task: its own body states the deliverable and the entry condition. It already carries kind, source, priority, effort, and app labels; the monitor appended the acceptance-criteria section and marked it meta/enriched. Liveness check: no merged PR resolves a planning step — it closes when its deliverable lands and its breakdown issues are filed.
Risks: outline staleness — the scope text is explicitly a rough outline that the core topic's research refines, so whoever picks this up must re-check #6281's findings first; entry-condition drift (starting before the predecessor steps move produces a design that has to be redone).
Suggested approach: leave queued behind its entry condition; when the core topic's first-pass findings exist, produce the design doc at the location the body names, then file the breakdown issues and link them here and on #6281.
50 remaining items
dezren39 commentedon Nov 6, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 6, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 6, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 8, 2026
🤖 Agent note · done (triage — task 11159; verdict: deferred, entry condition unmet)
ghreads, 2026-11-08T00:06Z): entry condition unmet, two levels deep. The previous step, issue id(phase-14): Scale & performance hardening — v1 — first-iteration design #6304 (v1 — first-iteration design), is OPEN with no design written — its comments are the intake review, its task 11075 triage (2026-11-06, deferred), and a fresh pickup (task 11158) at 2026-11-08T00:05Z. Issue id(phase-14): Scale & performance hardening — v1 — first-iteration design #6304 is itself deferred pending core topic issue id(phase-14): Scale & performance hardening — core topic (research + design) #6281's first-pass research findings (task 11075 verdict, native blocked-by on issue id(phase-14): Scale & performance hardening — core topic (research + design) #6281), so the v2 outline cannot start without violating this issue's own acceptance criteria. Ladder intact under issue id(phase-14): Scale & performance hardening — core topic (research + design) #6281: v1 issue id(phase-14): Scale & performance hardening — v1 — first-iteration design #6304, v2 issue id(phase-14): Scale & performance hardening — v2 — outline: growth policy #6305 (this), v3 issue id(phase-14): Scale & performance hardening — v3 — outline: multi-node chaos #6306, v4 issue id(phase-14): Scale & performance hardening — v4 — outline: public-server targets #6307 — all OPEN.status/triaged+status/waiting-dependency; stalequeue/queued,work/assigned, andstatus/parkedremoved. Resume condition: issue id(phase-14): Scale & performance hardening — v1 — first-iteration design #6304 carries its written design (open questions answered or explicitly deferred to this step) — then re-triage issue id(phase-14): Scale & performance hardening — v2 — outline: growth policy #6305 and refine the growth-policy outline (journal snapshot/compaction policy, presence and fan-out budgets, degradation ladder behind issue id(world): F11.7 host metrics, Prometheus endpoint and tracing spans #553's metrics) against Drew's Phase 14 principles from issue id: next horizons — what comes after Phase 13 (discussion with Drew) #1240.dezren39 commentedon Nov 8, 2026
🤖 Agent note · done (triage — task 12517; verdict: real and current, entry condition still unmet)