RFC-0032 · Reference catalog
Versioned draft snapshot
RFCs, reference catalogs, and evidence reflect Spec 3b2e3e7a114fb826b1445d39a48756b8fff629cd. Counts and pending/status notes belong to that snapshot. Read the dated project update for later progress.
Source repositories are private during staging. Links marked “repository access required” need access to the linked repository.
Generated reference catalog. This page renders structured Lean data for RFC-0032: defined terms, diagnostics, dependencies, and invariants. It does not establish proof coverage or runtime conformance. The authored narrative lives in
RFC-0032.This page is generated from the
lean/Gnomon/Spec/module for RFC-0032. Edit that source and regenerate this catalog.
Title: rules_gnomon — Bazel Build Rules for Gnomon Modules
Status: draft
Depends on: RFC-0001, RFC-0002, RFC-0005, RFC-0006, RFC-0008, RFC-0010, RFC-0013, RFC-0016, RFC-0024, RFC-0025, RFC-0026
Proof citations in source: 3 / 3. Standalone proof verification is pending.
Definitions
(none defined)
Diagnostics
| Code | Severity | Description |
|---|---|---|
M32000 | Error | gnomon_module srcs contains a file outside the module directory |
M32001 | Error | gnomon_client specs missing a file referenced by spec: in the .gnm source — Bazel will not track the file as an input, breaking caching |
M32002 | Warning | Gazelle cannot resolve an imports {} reference to an gnomon_module target; generates commented-out deps entry |
M32003 | Error | Compiler output is not byte-for-byte reproducible across two builds with identical inputs — breaks remote caching |
M32004 | Error | gnomon_kernel WASM fingerprint does not match gnomon_module bundle fingerprint — M10040 at runtime; caught here at build time |
M32005 | Error | gnomon_migration plan references a schema object not present in the target environment |
Dependency neighborhood
graph LR
nRFC_0032["RFC-0032"]
nRFC_0001["RFC-0001"]
nRFC_0032 --> nRFC_0001
nRFC_0002["RFC-0002"]
nRFC_0032 --> nRFC_0002
nRFC_0005["RFC-0005"]
nRFC_0032 --> nRFC_0005
nRFC_0006["RFC-0006"]
nRFC_0032 --> nRFC_0006
nRFC_0008["RFC-0008"]
nRFC_0032 --> nRFC_0008
nRFC_0010["RFC-0010"]
nRFC_0032 --> nRFC_0010
nRFC_0013["RFC-0013"]
nRFC_0032 --> nRFC_0013
nRFC_0016["RFC-0016"]
nRFC_0032 --> nRFC_0016
nRFC_0024["RFC-0024"]
nRFC_0032 --> nRFC_0024
nRFC_0025["RFC-0025"]
nRFC_0032 --> nRFC_0025
nRFC_0026["RFC-0026"]
nRFC_0032 --> nRFC_0026
Invariants
- All files in an gnomon_module srcs attribute must reside in the same module directory. (enforced by: build-time)
- An gnomon_kernel WASM fingerprint must match the corresponding gnomon_module bundle fingerprint. (enforced by: build-time + runtime)
- CanonicalIr struct fields must be serialized in declaration order and Vec fields populated alphabetically by symbol id. (enforced by: compile-time)
- Gazelle generates exactly one gnomon_module per leaf directory containing .gnm files. (enforced by: build-time)
- Gazelle must emit a build warning when module.gnm is absent from a concept folder. (enforced by: build-time)
- Spec-backed clients must declare their spec files in gnomon_client.specs so Bazel tracks them as inputs for cache correctness. (enforced by: build-time)
- The gnomon compiler must be fully hermetic with no filesystem reads outside declared srcs/deps and no network access during compilation. (enforced by: build-time)
- gnomon_test execution is hermetic: kernel loaded from compiled bundle with no network access. (enforced by: build-time)
- rkyv archives produced by the gnomon compiler must be byte-for-byte reproducible across builds with identical inputs. (enforced by: compile-time)
Normative Statements
Statements are structured source data. Proof citations, where present, have not passed a standalone Gnomon proof gate.
Core Build Rules
- MUST — All
srcsof angnomon_moduleMUST reside in the same module directory. (proof citation:rfc0032_b2_grounded; verification pending)
Gazelle Extension
- MUST — Gazelle MUST emit a build warning when
module.gnmis absent from a concept folder. (proof citation:rfc0032_b0_grounded; verification pending)
Remote Execution Configuration
- MUST — The gnomon compiler MUST be fully hermetic with no undeclared filesystem or network reads.
- MUST — The gnomon compiler MUST enforce declaration-order serialization of
CanonicalIrfields and stable (alphabetical-by-symbol-id) ordering ofVecfields. (proof citation:rfc0032_b4_grounded; verification pending) - MUST — rkyv archive output MUST be byte-for-byte reproducible across builds with identical inputs.
Linked References
| Direction | Target |
|---|---|
| Depends on | RFC-0001 |
| Depends on | RFC-0002 |
| Depends on | RFC-0005 |
| Depends on | RFC-0006 |
| Depends on | RFC-0008 |
| Depends on | RFC-0010 |
| Depends on | RFC-0013 |
| Depends on | RFC-0016 |
| Depends on | RFC-0024 |
| Depends on | RFC-0025 |
| Depends on | RFC-0026 |