Publication pipeline
The site is downstream of query execution. A stored expectation by itself can never become a published passing result.
Validation sequence
- Install the exact npm dependency graph from
package-lock.json. - Build the current Rust canonical CLI used by Rust-owned query families.
- Run the Python runner and generator contract tests.
- Execute all top-level
fixtures/queries/*.jsonqueries against their declared canonical fixtures or governed extensions. - Compare every actual result with its fixture expectation using exact JSON structural equality.
- Execute all top-level
fixtures/reference-cases/*.jsonmanifests and resolve every answer/evidence check against actual query output. - Retain both complete suite reports as exact-commit workflow artifacts.
- Recompute the generated Markdown in memory and fail on missing, extra, or byte-different pages.
- Build Docusaurus with broken-link failures enabled.
Pull requests and pushes to develop or main run that validation sequence.
Pull requests do not publish.
Publication sequence
Pushes to source develop and source main enter the distribution workflow.
It repeats the full validation sequence, writes deterministic source provenance
into the static tree, and retains that exact tree as an artifact before making
the destination repository writable. It then replaces the corresponding branch
of governance-foundation/ontograph-docs: develop maps to develop, and
main maps to main. It never uses a gh-pages branch. Overlapping writes to
the same destination branch are serialized.
| Evidence | Contents | Retention |
|---|---|---|
| Reference-query suite artifact | Fixture, query kind, input, execution engine, status, expected result, actual result, and non-claim boundary for every case | 14 days for validation; 30 days for publication |
| Reference-case suite artifact | Case manifest, external input identities, human questions, structured answers, actual runtime output, resolved evidence checks, and non-claim boundary | 14 days for validation; 30 days for publication |
| Compiled-site artifact | Exact Docusaurus tree plus publication-manifest.json source provenance | 30 days for publication |
| Generated site | Query and proof-case catalogues, one page per executed fixture/case, input and source digests, verified outputs, evidence checks, and source commit | Matching branch of ontograph-docs; Pages serves develop |
The public ontograph-docs repository has GitHub Pages configured to serve the
root of develop. Its destination-scoped deploy key is available only to the
post-build synchronization job. That repository setting and distribution
credential remain separate from semantic or release authority.