Highlights
- Every figure needs a provenance path.
- Each article points to an external archive record.
- Citation metadata belongs beside the artifact.
Artifact card
| Track | Research artifacts / citation infrastructure |
|---|---|
| Status | Draft |
| Interface/spec | Pending |
| Benchmark schema | Pending |
| Known limitations | Listed in release manifest |
| Version compatibility | Pending |
| External archive | Archive pending |
Abstract
This article defines how public figures and claims map to commits, commands, logs, parsers, checksums, citations, and limitations.
Motivation
This article defines a PCCX research artifact that can be cited, audited, and updated without turning draft evidence into marketing copy.
Evidence snapshot
The article records what is currently known, what remains unresolved, and what artifact must exist before stronger claims are made.
Method outline
The release package should include metadata, source logs, scripts, figures, checksums, citation files, and a plain-English limitation note.
Reproduce this result
- Open the external archive record when published.
- Download the manifest and artifact bundle.
- Run the parser or notebook listed in the manifest.
- Regenerate the figure and compare the checksum.
External archive
| Provider | Zenodo planned |
|---|---|
| Status | Archive pending |
| DOI | Pending |
| Record | Not yet published |
Code availability
Analysis scripts and raw parsers should be released through the project repository or a DOI-backed external archive, then linked here.
Commercial relevance
Creates a technical-diligence format that professors, customers, and investors can audit.
References
- PCCX Research. Article archive record, version 0.1.0-draft.
- PCCX artifact metadata and citation records.