gnomonlearn
Docs/Learn/Gnomon

Gnomon

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.

Gnomon describes how modules define data, behavior, and services over a graph substrate. Its 57 RFCs are the design source for the language, runtime, and contracts. Implementation and proof coverage vary by feature.

What Gnomon does

In the RFC design, module authors describe entities, operations, and interfaces. The compiler turns those descriptions into runtime artifacts, and the graph substrate stores and authorizes the resulting data. Start with module authoring, compiled bundles, and the graph data model; check repository tests for implemented behavior.

Seven pillars

The kernel groups the framework's central claims into seven pillars. The source distinguishes axioms from proved results; a pillar name alone is not a proof of an implementation.

Start here

  1. Read how to read the spec and its maturity notes.
  2. Browse RFC-0000 for terminology, then RFC-0001 for the module format.
  3. Use the RFC navigation to find a specific contract. Check the implementation repository and tests before relying on a draft feature.

Architecture and repositories

The intended dependency direction is specification → expression and graph → framework and applications. Brand assets feed this site and product interfaces.

  • spec: RFCs, Lean sources, and knowledge graph claims.
  • expression: a shared language used by graph and module authoring.
  • graph: data plane, contracts, and operator. Its wire package remains savvifi.graph.v1 for compatibility.
  • gnomon: compiler, runtime, integration build, and current applications.
  • brand and site: visual source and public learning surface.

Maturity

Gnomon is being reorganized from the Aion codebase. The RFCs are drafts, and the normative spec release gate remains blocked by a known inconsistency in pinned formal inputs, deferred proofs, two prose-only RFCs, reviewed RDF mismatches, and unresolved language and contract decisions. Cross-repository releases and the full integration build remain unverified. This site is a preview of the public information architecture. Check package availability and production readiness per repository and release.