GG Modules And Extensions
Parent README: ../README.md
This page maps how GG code becomes reusable modules, package APIs, runtime extensions, language extractors, and downstream site/app integrations.
Module Model
Use plain .gg for standalone topologies. Use .mgg plus gnosis.mod when a
topology needs module boundaries.
The module implementation lives in ../src/mod/README.md and owns:
.gg/.mggformat detection- import and export parsing
- filesystem-backed resolution
- lockfile-backed resolution
- optional Forge-registry fallback for declared bare specifiers
- cycle detection
- merged effect-contract summaries
- AST merge/lowering
- canonical merged-source rendering for CLI and runtime consumers
Book 188 explains the module system at tutorial depth.
Capability And Effect Contracts
Use capability metadata when a topology depends on host resources.
Primary references:
- ../src/capabilities/README.md
- ../../../docs/ebooks/183-effect-inference-capability-validation/README.md
Common target profiles include Workers, Node, Bun, gnode, browser WASM, WASI,
and tauri-edge. Capability validation is how GG stays portable without
pretending every host can execute every edge.
Public Package Exports
The package exports many subpaths. Treat these as public developer surfaces and prefer them over deep imports.
Core And Analysis
@a0n/gnosis@a0n/gnosis/css-layout-analysis@a0n/gnosis/flow-obstruction@a0n/gnosis/reynolds-bft@a0n/gnosis/spiderweb-topology@a0n/gnosis/reinforcement-topology@a0n/gnosis/scheduling-mesh@a0n/gnosis/structured-data@a0n/gnosis/randomness@a0n/gnosis/lexicon@a0n/gnosis/liveness
Policy, Runtime, And Admission
@a0n/gnosis/mesh-policy@a0n/gnosis/mesh-policy-edge@a0n/gnosis/mesh-policy-compile@a0n/gnosis/mesh-policy-edge-compiled@a0n/gnosis/ballistic-vest-policy@a0n/gnosis/capabilities@a0n/gnosis/universe@a0n/gnosis/ambient-scheduler@a0n/gnosis/ambient-substrate@a0n/gnosis/foil-edge-gate@a0n/gnosis/esc
Betty, Betti, GG, And Testing
@a0n/gnosis/betty/compiler@a0n/gnosis/betty/legalese@a0n/gnosis/betty/gg-grassmannian-cache@a0n/gnosis/gnode-execution@a0n/gnosis/wasm-execution@a0n/gnosis/wasm-execution-bridge@a0n/gnosis/test@a0n/gnosis/test/bun@a0n/gnosis/test/vitest
Polyglot And TypeScript Bridges
@a0n/gnosis/polyglot-bridge@a0n/gnosis/polyglot-compose@a0n/gnosis/polyglot-memory@a0n/gnosis/polyglot-registry@a0n/gnosis/polyglot-execution-bridge@a0n/gnosis/polyglot-scaffold@a0n/gnosis/polyglot-checkpoint-bridge@a0n/gnosis/ts-check@a0n/gnosis/ts-check-autofix@a0n/gnosis/ts-check-watcher@a0n/gnosis/ts-graph@a0n/gnosis/ts-host
Data, CRDT, Time, And Transport
@a0n/gnosis/crdt@a0n/gnosis/crdt/qdoc@a0n/gnosis/gnosis-time@a0n/gnosis/protocol69@a0n/gnosis/protocol69-r1-witness@a0n/gnosis/protocol69-r1-phyle-entropy@a0n/gnosis/protocol69-r1-worksteal@a0n/gnosis/iota-trees@a0n/gnosis/knotgraft-client@a0n/gnosis/knotgraft-fabric-server@a0n/gnosis/knotgraft-diversity-client@a0n/gnosis/knotgraft-syzygy-cannon
Math, Physics, Probability, And Domain Kernels
@a0n/gnosis/probability-certificate@a0n/gnosis/probability-routing@a0n/gnosis/physics-sandbox@a0n/gnosis/seismic-stress-toy@a0n/gnosis/math-sandbox@a0n/gnosis/math@a0n/gnosis/information-geometry@a0n/gnosis/earth-chronometry@a0n/gnosis/verify-bundle@a0n/gnosis/socio-topology@a0n/gnosis/cooling-policy@a0n/gnosis/arena-merge-gate@a0n/gnosis/ecology-graph-snapshot
App And Boundary Contracts
@a0n/gnosis/dark-shroud@a0n/gnosis/x-ranger-boundary@a0n/gnosis/auth@a0n/gnosis/gpu@a0n/gnosis/moonshine-trace@a0n/gnosis/moonshine-router@a0n/gnosis/topological-xor-certificate@a0n/gnosis/prism-attestation@a0n/gnosis/temporal-prism
Clock And Geometry Family
@a0n/gnosis/solar-geometry@a0n/gnosis/daylight-topology@a0n/gnosis/causal-topology@a0n/gnosis/simultaneity@a0n/gnosis/gravitational-dilation@a0n/gnosis/doppler-redshift@a0n/gnosis/worldline@a0n/gnosis/twin-paradox@a0n/gnosis/cosmic-horizon@a0n/gnosis/causal-diamond@a0n/gnosis/colo-coordinates@a0n/gnosis/clock-topology-coordinator@a0n/gnosis/clock-atlas@a0n/gnosis/solar-scheduler@a0n/gnosis/gg-timers@a0n/gnosis/clock-distributed@a0n/gnosis/clock@a0n/gnosis/wormhole-topology
Extension Points
Add A GG Language Feature
Start with:
Checklist:
- define the syntax or label contract
- add parser/compiler support
- document runtime meaning
- add
.ggexamples and.test.ggcoverage - add theorem or ledger references only if they exist
Add A Runtime Handler
Start with:
Checklist:
- register handler behavior behind the runtime registry
- preserve capability and execution-auth boundaries
- add a small GG fixture
- add a narrow runtime test
- document whether the handler is primary, advanced, or experimental
Add A Language Or Framework Extractor
Start with:
- ../polyglot/README.md
- ../polyglot/src/README.md
- ../polyglot/src/extractors/README.md
- ../polyglot/src/framework_recognizers/README.md
Checklist:
- add scanner/extractor support
- lower to GG without losing control-flow boundaries
- expose diagnostics when extraction is partial
- add fixture coverage
- document host/runtime requirements
Add Editor Or Tooling Integration
There is no dedicated GG LSP or editor-extension directory in this checkout. Current editor-facing work should route through:
@a0n/gnosis/ts-check@a0n/gnosis/ts-check-autofix@a0n/gnosis/ts-check-watcher- the CLI lint/analyze surfaces
- downstream browser/Aeon extension docs when the target is a browser capability
When a real GG language server or syntax package is added, give it a README and link it from this page, GG_CLI_REFERENCE.md, and the root Gnosis README.
Cross-Site Integration
Gnosis is the anchor. Other subsites should cross-reference it rather than redefining GG:
https://gnosis.forgo.cloud/: public Gnosis site generated from ../aeon.tomlx-gnosis: native/web serving of compiled Gnosis surfacesgnot-demo-site: Gnot and structural serialization examplespolyglot-scanner: extraction and scanner-facing workflowsgnosis-engine-mcp: MCP-facing Gnosis engine integrationgnosis-church: formal/theological reader surface, not the first developer pathknot-vizand related visualizers: graph/codec visualization support
Keep Gnosis docs self-sufficient. Cross-site links should deepen the story, not be required for the first run.