Artifacts

Active

This is the registry that makes rule 2 of the archive enforceable: every artifact has exactly one canonical location, and everything else references it. A figure that appears in a chapter and in a paper is one FIG- record cited twice, not two exported images that have quietly diverged.

ALGAlgorithms

Procedures stated precisely enough to implement, independent of any implementation.

CODESoftware

Released code, pinned to a commit, with the interface it promises.

MODELModels

Trained or fitted models, with the data and procedure that produced them.

DATADatasets

Registered in the datasets section; this page is the pointer, not a second copy.

FIGFigures

Every figure, in vector and raster form, with the code that generated it.

TABLETables

Every table, with the query or script that produced its numbers.

DIAGDiagrams

Architecture and concept diagrams, authored as source rather than drawn.

DOCDocuments

Standalone documents that are not chapters, papers or notes.

PRESPresentations

Delivered talks, registered so that a slide can be cited.

PROMPTPrompts

Prompts used as instruments, versioned like any other instrument.

BENCHBenchmarks

Benchmark definitions: workload, metric, baseline and acceptance criterion.

CONFIGConfigurations

Configurations reused across experiments, registered so a run can name one.

What qualifies as an artifact

Something is registered when it is referenced from more than one place, or when it would need to be cited. A figure used once, in one draft, is a working file in the archive/ tree. The moment it appears in a paper and a chapter, it gets a number.

Registry

The machine-readable index is registry/artifacts.yaml. A page without a registry entry is invisible to the research map, and a registry entry without a page is a broken link; pnpm validate checks both.

Naming

FIG-001, TABLE-014, CODE-002. Numbers are assigned in order within a category, are never reused, and never change. The human-readable name can change as often as it needs to.