Publish the Four Ways technical supplement - #3
Open
studiofarzulla wants to merge 1 commit into
Open
studiofarzulla wants to merge 1 commit into
studiofarzulla wants to merge 1 commit into
Conversation
The site had no mechanism to publish a technical supplement for any paper. Papers whose reader editions were deliberately slimmed with the apparatus moved into a supplement were therefore publishing the claims without the evidence. Adds an optional `supplement` / `supplementPages` pair to papers.json, rendered as a second download button, and wires it up for marl-coordination (DAI-2606, currently under review at TMLR). The published file is the NAMED reader-facing supplement, 65pp, sha256 24400a6682b6..., matching the arXiv release source at release-candidates/arxiv-new-2026-08-19/source/anc/. It is NOT the 55pp anonymized supplement submitted to TMLR. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
dissensus-ai | debd61a | Commit Preview URL Branch Preview URL |
Sep 05 2026, 08:00 PM |
There was a problem hiding this comment.
🟢 Approval recommended
The changes are small, consistent across metadata and rendering, and the referenced supplement file exists in public/papers.
Pull request overview
Adds first-class support for “technical supplement” PDFs on paper landing pages, so papers can expose both the reader edition and the supporting apparatus when provided.
Changes:
- Extend
papers.jsonpaper entries with optionalsupplementandsupplementPages. - Update
build-papers.jspaper-page template to render a second download button when a supplement is present. - Publish the MARL paper’s supplement button on the generated page.
File summaries
| File | Description |
|---|---|
public/papers/marl-coordination.html |
Adds a “Technical supplement (65pp)” download button alongside the main PDF for the MARL paper page. |
papers.json |
Introduces supplement + supplementPages for marl-coordination metadata. |
build-papers.js |
Renders an optional “Technical supplement” download button based on the new metadata fields. |
Review details
- Files reviewed: 3/4 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Answers the question "did I ever provide the technical addition?" for the site. No — and there was no way to.
The gap
papers.jsonhad no supplement field andbuild-papers.jshad no supplement rendering. So for every paper, the site published the reader edition and nothing else. Where a reader edition was deliberately slimmed with the apparatus moved into a supplement, the site was publishing the claims without the evidence.The fix
Optional
supplement/supplementPagesinpapers.json, rendered as a second download button beside Download PDF. Wired up formarl-coordination(DAI-2606).Which file — this matters
Published is the named reader-facing supplement, 65pp,
sha256 24400a6682b6…, which matches the arXiv release source atrelease-candidates/arxiv-new-2026-08-19/source/anc/. Verified on the copied file: 65pp, A4, first page carries author, ORCID and correspondence.It is not the 55pp anonymized supplement submitted to TMLR (
3fdee015…). Those must not be confused while review is live.Note on the canonical record
PORTFOLIO_CANONICAL_TRUTH.mdrecords this supplement as 64pp /5fb845ba…. That SHA exists only atrelease-candidates/.../qa/final-minor-adjudication-2026-08-25/cold-main-v2/anc/— a QA cold-build, not the release. The promoted reader-facing file and the arXiv release source both carry24400a66…at 65pp. The canonical line appears to quote a QA artifact; worth correcting separately.Scope
axiom-of-consenthas the same gap (50pp supplement atreader-facing/technical-supplement_AOC.pdf, unpublished). Left out — the mechanism now exists, so it is one JSON field plus a file copy whenever you want it.Other 22 paper pages are untouched: the template was written so the button emits nothing when absent.
🤖 Generated with Claude Code