Repository navigation
Description
Current state: PR #545 has the required independent approvals on 76342a1ae2e34ac417ca63e0daf0f267f2342180. The DeepWiki evidence follow-up also passed review. Scope decision · Amy's approval · Dong's approval · DeepWiki evidence approval
Decision needed: Final delivery acceptance remains with the repository maintainers after integration.
Next action: Repository maintainers can assess integration using the reviewed revision and verification below.
Goal and acceptance
Make the README easier to navigate and precise about the evidence it summarizes.
- The DeepWiki link opens the published InferRSI project documentation for a signed-out visitor.
- The dashboard instructions state that
inferrsi dashboard --input .writesdashboard.htmlin the input run directory and that readers open it in a browser. - Selected Results reports the medians of six DeepSeek run-level mean TPOT measurements at C1, C4 and C16, and links the historical calibration comment directly.
- The LFM3 comparison states that retained baseline and candidate waveforms matched bit-for-bit within each tested temperature. The MiniCPM-o entry identifies
track_s_fast_r11as the profile whose formal speech quality gates were not run and links to the pinned quality table. - The contribution guidance reflects the required checks and two independent approvals. It explains that the issue owner uses the evidence to accept the work or reopen the issue. Review and merge policy
Verification recorded on 2026-11-21
- Anonymous HTTPS GET requests using
curl, with no login cookies or authorization headers, returned the DeepWiki project Overview and the Getting Started page. The landing page returned HTTP 200 with the titleInferMatrixLab/InferRSI | DeepWikiand linked to the project's Getting Started and module layout pages. Overview · Getting Started · Anonymous request receipt · Independent browser check - A local smoke test with a minimal
run.lock.jsongenerated nonempty HTML in the input directory usinginferrsi dashboard --input ..git diff --checkpassed for the full README change. Dashboard guide - The public calibration comment confirms C1/C4/C16 medians of 39.28/44.07/56.86 ms/token at the README's precision. The LFM3 report records waveform identity immediately after its two temperature tables. The MiniCPM-o quality table distinguishes the unrun formal
track_s_fast_r11gates fromtrack_s_fastdevelopment results. DeepSeek calibration · LFM3 Performance results · MiniCPM-o quality status
Scope and ownership
This issue covers README.md and its source evidence. Repository About metadata and new performance or quality experiments are outside the proposed scope.
Proposed by Inference1, with Codex assisting on the review follow-up. Dong-bot confirmed this scope as Dong1017's authorized delegate. Repository maintainers own final acceptance and closure. Scope decision
Activity
Dong1017 commentedon Nov 21, 2026
Posted by Dong-bot, an automated agent acting on behalf of @Dong1017 (always-on-bot, model claude-sonnet-5-5).
Assessment. This is a reasonable governing issue for the README follow-up in #545. It is small, README-only and has four checkable outcomes. It is the missing "governing issue" that amy-why-3459 and zengchuang-hw flagged on #545. It is not yet an acceptance record, because it asks a maintainer to confirm scope and nobody has done that. A few acceptance lines are also looser or tighter than what #545 actually changes. (Dong-bot, authorized delegate, triaging.)
Where the issue and #545 disagree (resolve before confirming scope)
track_s_fast_r11as the configuration whose formal speech quality gates were not run. That is the right, narrower claim. The docs: add DeepWiki navigation and clarify README guidance #545 README line (README.md:150, as of amy's review at007e65b) still says "the formal speech quality checks were not run for the tested configuration." The cited report also has dev-quality results fortrack_s_fast(UTMOS 0.13 below reference), so the generic wording can read as "no quality data at all." Use this issue's wording as the acceptance text and make the README match it.docs/agent-collaboration.md#pr-review-and-mergeas the source of truth, so "required" can be verified against one page.Evidence and verification risks
#issuecomment-6641425447) with C1/C4/C16 values of 39.28 / 44.07 / 56.86 ms/token, all above the 25 ms/token target. acceptance: DeepSeek V4.1 Flash 910C 8K/1K TPOT ≤25 ms/token at C1/C4/C16 #353's current body no longer repeats that table. The comment permalink is the only anchor, so the README should state the aggregation and link the comment explicitly. Amy confirmed the aggregation from that comment.inferrsi dashboard --input .writesdashboard.htmlin the run directory. I did not run the CLI. The claim should be checked againstdocs/dashboard.md#generate-and-openand the actual default output path.git diff --checkflagged trailing whitespace on the revised dashboard line. That should be fixed and re-run clean before approval.Process points
Refs #557, not Closes/Fixes/Resolves, since maintainers own closure here and the issue shouldn't auto-close on merge.Suggested next steps
Refs #557and drop or split the About text.README.md:150, clear the whitespace finding, and push. amy-why-3459's open points on that PR then become checkable against this issue's acceptance list.I'm not accepting or rejecting the scope here, since the issue asks a maintainer to do that. I haven't run the CLI or re-verified any benchmark or upstream links. I read #545's body and its two latest review comments, and #531.
zengchuang-hw commentedon Nov 21, 2026
PASS(设计检视,建议接受范围;不代替维护者确认)
这条 Issue 适合作为 #545 的 README 跟踪单。建议用普通
Refs #557关联,仓库 About 设置保持独立。核对当前 README 修改:仪表盘给出了 HTML 输出位置和打开步骤;DeepSeek 保留了六个单次均值取中位数的口径;MiniCPM-o 已限定到track_s_fast_r11,没有扩大为所有配置都没做质量验证。验收时请记录 DeepWiki 匿名打开项目页的日期与方法;我未能从外部读取工具独立打开该网址,不把这个限制当成链接失效。未运行 CLI 或确认功能验收。Inference1 commentedon Nov 21, 2026
@zuiho-kai @Dong1017, could a maintainer with scope authority confirm the README-only follow-up and acceptance criteria recorded above for PR #545?
The issue now includes the signed-out DeepWiki checks from 2026-11-21, the dashboard smoke test, the historical DeepSeek aggregation, and the exact LFM3 and MiniCPM-o source passages. PR #545 links this issue with
Refs #557and its description now covers only the README change. Repository About metadata stays outside this scope.The proposed delivery is at
76342a1ae2e34ac417ca63e0daf0f267f2342180. Please record the scope decision here so the reviewers can use it for their independent re-review.Posted by Codex on behalf of Inference1.
Dong1017 commentedon Nov 21, 2026
Posted by Dong-bot, an automated agent acting on behalf of @Dong1017 (always-on-bot, model claude-sonnet-5-5).
Decision: Accepted. The README-only scope and the acceptance criteria in the current #557 body are confirmed for PR #545. This is a scope decision from Dong-bot (authorized delegate). It does not accept the work, close #557, or replace the independent re-reviews on #545.
Accepted clauses
curlGET, HTTP 200, titleInferMatrixLab/InferRSI | DeepWiki).inferrsi dashboard --input .writesdashboard.htmlin the input run directory and that readers open it in a browser. The source isdocs/dashboard.md#generate-and-open, plus the recorded local smoke test.track_s_fast_r11as the profile whose formal speech quality gates were not run, and links the pinned quality table. It must not read as "no quality data for any configuration."docs/agent-collaboration.md#pr-review-and-mergeat the pinned commit as the single source of truth. It also says the issue owner uses the evidence to accept the work or reopen the issue.Out of scope, confirmed
Refs #557, not Closes/Fixes/Resolves. Closure stays with the maintainers.My earlier triage items 1, 3 and 4 and the DeepSeek wording are now reflected in the issue body. The About text is out of scope and the
Refslink is in place, as @Inference1 reports. @zengchuang-hw's design check also supports this scope.Still open before #557 can be accepted or closed (not blockers to the scope decision)
76342a1against the clauses above. In particular,README.md:150should carry thetrack_s_fast_r11wording, andgit diff --checkshould be clean on the final head.amy-why-3459 commentedon Nov 21, 2026
This is a suitable governing issue for the README-only follow-up in #545. The proposed scope is right:
README.mdand its source evidence only; repository About metadata and new performance or quality experiments stay out. Please keep the PR link as plainRefs #557, not Closes/Fixes/Resolves. I confirm that README scope as a maintainer.I am also recording the DeepWiki check here. On 2026-11-21 I opened https://deepwiki.com/InferMatrixLab/InferRSI signed out in a browser. The page title and Overview were the InferMatrixLab/InferRSI project docs, including Getting Started and the module layout, not an unindexed placeholder. That check was first noted on #545 at
fc7fc282.#545 at
76342a1ae2e34ac417ca63e0daf0f267f2342180already matches the narrower MiniCPM-o wording (formal speech quality gates fortrack_s_fast_r11were not run, with a link to the report's quality-status section), usesRefs #557, and moves the About suggestion into a separate non-diff section of the PR body.Two small acceptance-bullet tightenings would make later closure easier; they are not blockers for confirming the README scope:
docs/agent-collaboration.md#pr-review-and-mergeas the source of “required checks,” or also mention that the issue owner may reopen the issue, since docs: add DeepWiki navigation and clarify README guidance #545 changes that sentence.@zengchuang-hw's design review is useful context, but the issue still asks for a maintainer decision; the confirmation above is that decision for the README scope of #545. I have not rerun the dashboard CLI or the cited benchmarks.
amy-why-3459 commentedon Nov 21, 2026
Saw the issue-body update after Dong-bot's scope decision. The status block now records the README-only scope as confirmed, the DeepSeek bullet now says “medians of six … run-level mean TPOT measurements,” and the contributing bullet now names the reopen path and points at
docs/agent-collaboration.md#pr-review-and-merge. The signed-out DeepWiki check is also written into the Verification section. That addresses the two acceptance-bullet tightenings I asked for in my previous comment.I independently rechecked the README at
76342a1against those clauses in my Approve on #545. Final delivery acceptance and closure of this issue still sit with the maintainers after integration, as the new Decision needed line says. I am not restating the earlier scope confirmation.Inference1 commentedon Nov 21, 2026
Signed-out DeepWiki access receipt
I repeated the HTTPS requests with the default curl configuration disabled and with cookie and authorization headers excluded.
request_startedis the client-side request time, andresponse_dateis the header returned with the HTML. Each body hash identifies the HTML received for that request.To reproduce the Overview check, run the command below and inspect the HTML title, heading and navigation links. Replace the URL with the Getting Started URL above to repeat its check.
An independent signed-out browser check also identified the project Overview. Browser check by amy-why-3459
Recorded by Codex on behalf of Inference1 for the README check on #545.
amy-why-3459 commentedon Nov 21, 2026
Saw the latest status-block update after my previous comment. It now records that PR #545 has the required independent approvals on
76342a1ae2e34ac417ca63e0daf0f267f2342180, and that the DeepWiki evidence follow-up also passed review, with links to my approval, Dong's approval, and zengchuang-hw's DeepWiki evidence approval. I rechecked those three reviews: all areAPPROVEDon that same head. The Next action line correctly moves from coordinating another re-review of that head to maintainer integration assessment. The Verification section now also points at the signed-out curl receipt in #557 (comment) and the earlier browser check.Final delivery acceptance and closure of this issue still sit with the maintainers after integration, as the Decision needed line already says. I have no further comments on this body update.
cursor commentedon Nov 21, 2026
Technical / third-party note (cursor[bot]; permission
none).#545 tip
76342a1ae2e3…now has Dong1017 + amy + zeng Approves plus cursor[bot] technical Approve (review); tip declarations green. README-only scope per prior decision.Write+ steward ask: merge #545 when ready, then close #557 if no residual DeepWiki follow-up remains.