Repository navigation
docs(development): move the streaming construction plan out of the repo into issue #1478 - #1479
Conversation
…po into issue #1478 (rev 12) The plan of record for #1387 / #1456 is a living document that was revised eleven times in two days. Holding it as a repository file meant a pull request per revision. The maintainer ruled that it moves into the tracker instead: rev 12 is issue #1478 (milestone M5), and a revision is now an edit to that body plus a comment saying what changed. This removes docs/development/streaming-construction-plan.md (rev 11, PR #1475) and its row in docs/engineering/README.md. Rev 11's content is superseded by #1478 section 0, which records each withdrawn claim and what replaced it; the file stays in history at 7b0113d. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository: CurateLabs/graphforge/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Warning Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Why
The streaming construction plan — the plan of record for #1387 (the ingest throughput floor) and #1456 (the construction foundation) — went through eleven revisions in two days. As a repository file every revision needed a pull request. The maintainer's instruction: "we should move it out of the repo and move it into the issues or milestone body so we are not dealing with PRs."
What
docs/development/streaming-construction-plan.md(rev 11, landed by docs(development): streaming construction plan rev 11 — the #1387 floor, per resource (#1387, #1456) #1475).docs/engineering/README.md.Nothing else references the file (checked across
*.md,*.yml,*.toml,*.py).Where the plan lives now
#1478 —
plan: streaming construction plan (rev 12) — the #1387 floor, per resource, in milestone M5. It is the plan of record and the closing issue for the ingest-throughput workstream (#1387 sits under it as a sub-issue; #1456 sits under #1387). It is not M5's closing tracker; that remains #735.Rev 12 is not a copy of rev 11. Its section 0 records every claim rev 11 made that the F1 device measurement, the
perf stat/ N-way scaling measurement and the external review refuted, and what replaced each. Rev 11's text stays in history at7b0113dd.The status headers on #1387 and #1456, the M5 description, and the local pointer files are repointed to #1478 alongside this PR.
Gates
scripts/ci/adr-index.py check— ok, 35 active and 3 superseded records agreescripts/source_size_policy.py— 693 files checked, 0 violationsscripts/ci/test-text-checkout-policy.py— 3,603 tracked paths resolve to LFmake pre-push-fast— passed🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.