RFC-0039 expression source ownership
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.
RFC-0039 §5 calls @savvi-studio/expression-framework and an absolute path in
the retired savvi-studio-full checkout the canonical grammar. The extracted
gnomon-sh/expression repository now owns the cross-language expression wire
contract and conformance corpus, while the framework still carries a local
TypeScript evaluator at gnomon/core/packages/expression-framework. Its
expression/CONTRACTS.md explicitly records this old
canonical-Zod reference as unresolved. The RDF claim that expressions share
their canonical grammar with the old framework is therefore not a reliable
first-release ownership statement.
Before normative release, name one authored grammar owner and one versioned executable conformance surface. Reconcile the RFC’s expression forms and builtin semantics with the released expression repository, pin its immutable artifact in graph and framework consumers, run shared vectors across those consumers, then update Lean and RDF projections and regenerate reference catalogs. Keep the inherited TypeScript file as a measured compatibility input until consumer cutover is verified.