update-data#100
Conversation
…s for affected topics]
…with the original paper lineage]
…ight paper families
…ages with the corrected lineage]
|
Implemented Addressed in this push:
Local validation completed:
|
…ages with the corrected lineage]
|
Addressed the mergeability failures on commit Mapped fix to the blocker:
Validation after the fix:
|
…ages with the corrected lineage]
|
Addressed the mergeability failure on commit Mapped fix to the blocker:
Validation after the fix:
|
|
Requeued stale CI for head |
…ages with the corrected lineage]
|
Addressed the mergeability failure on commit Mapped fix to the blocker:
Validation after the fix:
|
|
Requeued stale CI for head What I checked before rerunning:
Action taken:
|
|
Requeued stale CI for head |
…s with the corrected lineage
|
Addressed the mergeability failure on commit Mapped fix to the blocker:
Validation after the fix:
|
…ages with the corrected lineage]
|
Addressed the current mergeability failure on commit . Mapped fix to the blocker:
Validation after the fix:
|
|
Addressed the current mergeability failure on commit f8b9173. Mapped fix to the blocker:
Validation after the fix:
|
|
Reconciled stale required CI on head What I checked before intervening:
Action taken:
No code changes were needed in this iteration; the branch is waiting on the fresh CI execution. |
|
Fresh CI rerun is now active for head Follow-up action taken:
No code changes were needed; the remaining blocker is active required CI on the current reviewed head. |
|
Reconciled stale required CI on head |
|
Fresh required CI rerun is now active for head What I checked before rerunning:
Action taken:
No code changes were needed in this iteration; the remaining blocker is active required CI on the current reviewed head. |
…ages with the corrected lineage]
|
Addressed the current mergeability failure on commit Mapped fix to the blocker:
Validation after the fix:
|
|
Reconciled stale required CI on head \ with no new code changes. What I checked before intervening:
Action taken:
No code changes were needed in this iteration; the remaining blocker is fresh required CI on the current reviewed head. |
|
Correction to the previous automation update: the shell stripped inline backticks from that comment. Reconciled stale required CI on head 0d90cb6 with no new code changes. What I checked before intervening:
Action taken:
No code changes were needed in this iteration; the remaining blocker is fresh required CI on the current reviewed head. |
|
Reconciled stale required CI on head What I checked before intervening:
Action taken:
No code changes were needed in this iteration; the remaining blocker is fresh required CI on the current reviewed head. |
|
Follow-up on the stale-CI reconciliation for head |
|
Fresh required CI rerun is now active for head What I checked before rerunning:
Action taken:
No code changes were needed in this iteration; the remaining blocker is active required CI on the current reviewed head. |
…s with the corrected lineage
|
Addressed the current mergeability failure on commit Mapped fix to the blocker:
Validation after the fix:
|
|
BLOCKING: GitHub currently reports this PR as Code review result: after reading the PRD, the full PR diff, the touched files, and surrounding content/runtime/search code, I did not find an independent correctness regression in the implemented lineage fixes themselves. Local validation passed with Project acceptance criteria Story behavioral-assertion audit Standards review Blocking action needed |
1 participant
{
"project": "Model Atlas",
"branchName": "update-data",
"description": "Correct the paper references, citation lineage, and published-date metadata for the docs pages that currently describe on-policy distillation and the DeepSeek attention family so readers see the real original or appropriate supporting papers instead of incorrect downstream attribution.",
"context": {
"customerAsk": "Some of the new paper references such as on-policy distillation and DeepSeek attention references and dates are wrong. Look through the general set of pages we have and update them to reference the real proper references, including the original papers for on-policy distillation and the papers around DeepSeek sparse attention.",
"problem": "The current docs data over-attributes several topics to the
DeepSeek-V4report or uses incorrect paper/date metadata. Theon-policy-distillationpage cites onlyDeepSeek-V4even though the method has an earlier original paper lineage. DeepSeek-related attention pages also blur together generic sparse-attention history, DeepSeek-authored attention papers, and V4-specific variants, which makes reference lists, associated records, and dates unreliable across training, module, paper, and model pages.","solution": "Reconcile citation records and their dependent registry/page records around one rule: each page cites the earliest relevant original paper for the idea it explains, plus later DeepSeek papers only where they specifically use or extend that idea. Correct the source titles, years, URLs, and lineage for on-policy distillation, sparse attention, MLA, and V4-specific attention variants, then propagate those corrections through the affected training, module, paper, and model pages."
},
"acceptanceCriteria": [
"The affected citation records use the correct public paper title, year, and URL for the idea being cited instead of relying on a later downstream report by default.",
"The
on-policy-distillationtraining regime references the original on-policy distillation paper lineage and uses theDeepSeek-V4report only as a usage or related-paper citation when appropriate.","Generic sparse-attention and DeepSeek-specific attention pages distinguish between original sparse-attention sources, DeepSeek-authored attention papers, and DeepSeek-V4-specific variants instead of collapsing them into one citation lineage.",
"Affected paper, model, module, and training pages render corrected reference lists and associated-record relationships that a reviewer can verify directly from the site.",
"Search/indexed page metadata and registry-backed at-a-glance data remain consistent with the corrected citation and date records.",
"Quality gate:
make typecheck,make lint, andmake testpass."],
"userStories": [
{
"id": "update-data-001",
"title": "Correct canonical citation and date records for affected topics",
"description": "As a maintainer, I want the citation registry entries for on-policy distillation and the affected DeepSeek attention topics to point to the correct public sources so every dependent page renders accurate titles, dates, and URLs.",
"acceptanceCriteria": [
"The citation source of truth is corrected for the affected topics, including the original on-policy distillation paper lineage and the real DeepSeek attention papers used by current pages.",
"Each corrected citation record contains the right title, year, and source URL for the paper it represents.",
"The data model no longer uses one downstream report as the default citation for a topic when an earlier primary source is the correct origin reference.",
"If a page needs both an origin paper and a later DeepSeek usage paper, those appear as separate citations instead of one record standing in for both roles.",
"Typecheck passes",
"Tests pass"
],
"priority": 1,
"passes": true,
"notes": ""
},
{
"id": "update-data-002",
"title": "Reconcile the on-policy distillation page with the original paper lineage",
"description": "As a reader, I want the on-policy distillation page to explain and reference the original technique lineage so I can trust where the method came from and how DeepSeek uses it.",
"acceptanceCriteria": [
"The
On-Policy Distillationpage renders the original on-policy distillation paper in its references.","The page no longer implies that
DeepSeek-V4introduced on-policy distillation if the DeepSeek report is only applying or describing the method.","The page’s associated records and metadata still show relevant DeepSeek model or paper usage where that relationship is real.",
"The page’s displayed dates and reference ordering reflect the corrected source metadata.",
"Typecheck passes",
"Tests pass",
"Verify in browser using Browser plugin"
],
"priority": 2,
"passes": true,
"notes": ""
},
{
"id": "update-data-003",
"title": "Reconcile DeepSeek attention pages with the right paper families",
"description": "As a reader, I want DeepSeek attention pages to separate generic sparse-attention history, DeepSeek-authored attention papers, and DeepSeek-V4-specific variants so I can follow the lineage of each mechanism accurately.",
"acceptanceCriteria": [
"
Sparse Attentioncontinues to reference the original sparse-attention paper lineage rather than a later DeepSeek report.","
Multi-Head Latent Attentionreferences the real DeepSeek MLA paper and keeps its date aligned with that paper.","
Compressed Sparse AttentionandHeavily Compressed Attentioncite the DeepSeek-V4 report for the V4-specific variant description, while also citing earlier sparse-attention context where needed.","Affected DeepSeek attention pages no longer claim that V4 introduced a broader attention idea when the idea predates V4.",
"Typecheck passes",
"Tests pass",
"Verify in browser using Browser plugin"
],
"priority": 3,
"passes": true,
"notes": ""
},
{
"id": "update-data-004",
"title": "Align dependent DeepSeek paper and model pages with the corrected lineage",
"description": "As a reader, I want DeepSeek paper and model pages to inherit the corrected references and dates so related pages do not contradict the module and training pages.",
"acceptanceCriteria": [
"The
DeepSeek-V4paper page and affected DeepSeek model pages render references and associated records that stay consistent with the corrected module and training lineage.","Where the site describes V4-specific architecture or post-training steps, the pages distinguish between
introduced hereandbuilds on earlier work.","Registry-backed metadata, related-record groupings, and rendered citations do not contradict the corrected origin papers for on-policy distillation, sparse attention, or MLA.",
"Typecheck passes",
"Tests pass",
"Verify in browser using Browser plugin"
],
"priority": 4,
"passes": true,
"notes": ""
}
]
}