Expand description
The artifacts module: what majordomus generate writes, read back.
The generator declares every artifact it produces — the document it projects, the
encoding it is written in, the JSON Schema its content satisfies, and where it came
from — and commits that declaration as docs/generated/artifacts.json. This module is
the reading half: it takes the committed manifest and reconciles it with the working
tree, so that a person, an MCP client, an HTTP caller and the Cockpit all learn from
one answer which generated files exist, which encodings a document is committed in,
and which are stale.
It does not regenerate anything and it holds no list of its own: a document added to
the generator appears here on the next majordomus generate, and a file this module
reports as stale is a file majordomus generate --check refuses.
Structs§
- Artifact
Report - The answer of
artifacts.list. - Artifact
Tallies - How many of each, so a caller needs no arithmetic of its own.
- Artifact
View - One generated file, as the manifest declares it and as the tree has it.
- Artifacts
Input - The input of
artifacts.list: the whole manifest, or one slice of it. - Document
View - One document, and the encodings it is committed in.
Enums§
- Artifact
State - Where one generated file stands against the tree it is committed in.
- Artifact
Verdict - Where the generated tree stands as a whole: the one verdict every surface renders, decided here so that no page decides it again from a subset of the tallies.
Constants§
- ARTIFACTS_
URI - The URI under which the manifest is read as an MCP resource.
Functions§
- module
- The module.