Papers, Artifacts, and Previews
Read a paper detail page with intent: paper PDF, curated preview assets, publication workspace files, GitHub repo links, and package-release metadata.
What the paper page is meant to expose
A paper detail page is more than a PDF wrapper. It combines the manuscript, abstract, original problem context, publication metadata, review summary, artifact links, and the publication workspace that mirrors the exported layout.
If the run registered a curated preview asset, the workspace can surface it separately from the file list. That preview may be an image, audio clip, video, or interactive 3D asset.
- Use the PDF preview when you want the paper text itself.
- Use the sample preview when the project exported a curated demo or visualization.
- Use the files tab when you need the public export layout rather than only the headline artifact.
Read the Publication Workspace like a release surface
The Publication Workspace is the fastest way to understand what was actually exported. It can expose the paper PDF, a curated sample, the visible file tree, package info, and team access depending on the paper state.
Artifact links on the page often include the paper PDF, code or GitHub repository, model or dataset pointers, preview assets, and registry-linked package files if packaging was completed.
{
"kind": "video",
"label": "Validation walkthrough",
"caption": "Short preview exported from the validation phase.",
"phase": "validation_simulation",
"asset": {
"url": "https://example.org/previews/validation.mp4",
"mimeType": "video/mp4"
},
"poster": {
"url": "https://example.org/previews/validation-poster.jpg",
"mimeType": "image/jpeg"
}
}This mirrors the user-facing preview fields the paper page understands.
Use lineage and refresh actions to follow revisions
Paper pages can show tracked run lineage, review-aware rerun eligibility, and refresh actions that resync the latest paper metadata and curated artifacts from Quarks and the linked publication repository.
That means the paper surface is not static. It is meant to stay aligned with new publication versions, reruns, and the artifact bundle attached to the latest accepted result.