RFC-0041 install-domain identity
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.
This is a trace and gap record from the pinned draft specification. It does not establish proof or implementation conformance.
Status: source-bound RDF review, 2026-10-04. Owner: Module Platform, Graph Runtime, and Spec. No Gnomon system is deployed.
The inherited ontology calls a DeclarationKind a top-level Gnomon
language form, a NamedDeclaration a source declaration instance, a
Field a declaration slot, an Operation a Gnomon algebra kind, a Module
a platform/application module, and a DataType a type in the Gnomon
language type model. RFC-0041 instead describes an install engine, graph
Resource kinds, manifest object kinds, build artifacts, runtime components,
transaction boundaries, lifecycle outcomes, hook phases, and runtime
values. Their RDF classes should express those distinct identities.
The source-bound review identifies these class groups:
| Current nodes | Projected class | Intended identity |
|---|---|---|
declaration/core.module | NamedDeclaration | Installed graph Resource kind, shared with RFC-0052. |
Manifest object kinds (data_source, operation, predicate, predicate_policy, resource, resource_type, statement, template, template-call) | DeclarationKind | Typed entries inside the graph module’s objects map, shared with RFC-0040/0042/0043. |
install-hook, install-plan, install-transaction, lifecycle-policy, linker, object-installer | DeclarationKind | Callable hook, build artifact, transaction boundary, and runtime components, respectively. |
core.module.* and install-plan.continueOnError | Field | Graph Resource properties and install-plan field. |
Nine operation/* nodes | Operation | Four lifecycle outcomes, a linker pass, three hook phases, and uninstall action; none is a Gnomon algebra kind. |
module/graph-install-engine | Module | Runtime component/package, not an authored Gnomon module. |
CanonicalVersion, ManifestHash, MigrationStrategy, StableId | DataType | Installer runtime value types, not Gnomon source-language types. |
The existing RuntimeComponent class can represent the linker, object
installer, lifecycle policy, and install engine. The graph module object
kinds should use the proposed ModuleObjectKind from
RFC0040_DOMAIN_IDENTITY_PROPOSAL.md.
Add explicit GraphResourceKind, GraphResourceField, InstallArtifact,
InstallArtifactField, InstallTransaction, LifecycleOutcome,
InstallAction, InstallPhase, and RuntimeValueType classes where the
current ontology has no faithful class. Re-key subjects whose current
declaration/, field/, operation/, or type/ path asserts the wrong
identity, and update every cross-RFC reference and consumer together.
Four inherited invariants also need source reconciliation. The
deterministic-install rule omits ambient clock/ID/graph inputs; idempotent
reinstall says no graph changes while §5.2 records a no-op provenance
entry; lifecycle strategy is said to depend only on version comparison
despite force and hash triggers; and hash-triggered reinstall lacks a
defined same-version lifecycle outcome. The associated decisions are in
RFC0041_INSTALL_SEQUENCING_PROPOSAL.md
and RFC0041_LIFECYCLE_PRIORITY_PROPOSAL.md.
The core.module.installedAt summary says the transaction commit instant,
while RFC-0041 §11.1 specifies only an install instant and the record is
written before commit. Define the timestamp point before publication.
Acceptance
- Reconcile RDF class and IRI identity for the graph resource, manifest
object kinds, installer artifacts, runtime components, phase/action
names, and runtime values. No shared IRI may carry conflicting classes,
FQNs, or declaration
kindClassvalues. - Preserve source and claim provenance while updating narrative, Lean,
protobuf projections, generated Turtle/reference catalogs, and all
invariantOf/claimSubjectlinks that move. - Compare all 16 claim-query results before and after, run domain identity and projection drift gates, compile Lean, test the install engine and published graph closure, and rebuild the pinned site.