| Path | Role |
|---|---|
RFC/Hypercode.md |
The paradigm RFC (concepts, HCS, cascade) |
EBNF/Hypercode_Syntax.md |
Formal .hc syntax (BNF) |
EBNF/Hypercode_Resolution.md |
Formal cascade resolution semantics |
EBNF/ (ANTLR .g4, Java, Makefile, hypercode_tests/) |
Conformance oracle for .hc parsing |
Package.swift, Sources/, Tests/ |
Reference implementation — the root SwiftPM package (Swift + SpecificationCore) |
Schema/ |
Versioned IR schema (hypercode.ir/v1) — the cross-impl contract |
Examples/ |
Runnable .hc / .hcs examples (service, white-label) |
The Swift package at the repo root is the reference implementation: the
canonical grammar-core (as SpecificationCore specifications), the .hcs reader,
the cascade resolver, emit/validate, and the hypercode CLI. It is consumable
as a SwiftPM dependency: .package(url: "https://github.com/0al-spec/Hypercode", from: "…").
The ANTLR/Java setup in EBNF/ predates it and is retained as a conformance
oracle for .hc parsing — both must agree on EBNF/hypercode_tests/*.hc.
New language work happens in Sources/.
Consumers (Ontology, Hyperprompt, …) depend on Hypercode, never the reverse. The
integration contract is the resolved-graph IR (Schema/), not the Swift
API: a consumer reads the emitted IR (or links the library) and projects it to
its own target. See Backends.md and Dialects.md.
How the CLI/library and the VS Code extension get shipped (VSIX, Marketplace, CI automation) is documented in Release.md.