Scientific contracts define canonical scientific objects and relationships in
Victus. They do not define repository-local runtime files, prompt internals,
storage paths, or model execution details.
Paper
-> PaperClassification
-> StructuredBlock
-> ExperimentMap
-> CanonicalEvidence
-> ArtifactManifest
-> PipelineRun
-> PipelineEvent
-> Embedding
-> Retrieval
-> Agent Reasoning
-> User Answer
| Order | Contract | Identifier | Status | Role |
|---|---|---|---|---|
| 1 | Paper | victus.scientific.paper@v1 |
active | Canonical scientific publication identity |
| 2 | PaperClassification | victus.scientific.paper_classification@v1 |
draft | Paper-level evidence routing classification |
| 3 | StructuredBlock | victus.scientific.structured_block@v1 |
active | Preserved source context unit |
| 4 | ExperimentMap | victus.scientific.experiment_map@v1 |
draft | Result-centered block grouping artifact |
| 5 | CanonicalEvidence | victus.scientific.canonical_evidence@v1 |
draft | Canonical reusable scientific result |
| 6 | ArtifactManifest | victus.storage.artifact_manifest@v1 |
draft | Physical artifact manifest and lineage record |
| 7 | PipelineRun | victus.orchestration.pipeline_run@v1 |
draft | Canonical pipeline execution record |
| 8 | PipelineEvent | victus.orchestration.pipeline_event@v1 |
draft | Append-only pipeline event record |
StructuredBlock replaces legacy Section Block terminology.CanonicalEvidence replaces the previous Claim contract concept.Claim as a system contract.PaperContent is omitted for now.paper.md, paper.processed.json, and paper.final.json are operationalpaper.final.json may be a repository-local implementation ofStructuredBlock[].Paper, StructuredBlock, ExperimentMap,CanonicalEvidence.ProcessingProvenance or ExtractionRun.CanonicalEvidence, not Claim.victus-processing is expected to produce:
victus.scientific.paper@v1victus.scientific.structured_block@v1victus.scientific.paper_classification@v1victus.scientific.experiment_map@v1victus.scientific.canonical_evidence@v1victus.storage.artifact_manifest@v1victus.orchestration.pipeline_run@v1victus.orchestration.pipeline_event@v1victus-rag is expected to consume:
victus.scientific.canonical_evidence@v1These relationships should be declared first in repo-local
victus.contracts.yml files, then reflected in the global inverted
subscription registry.