Concept — EGGF
# EGGF
## Definition
**EGGF** ("Entity Gravity Graph Framework") is a portable framework for organizing intellectual work around a central Entity (a person, organization, or coherent concept) that exhibits *gravity* — the pull that keeps related Bodies, Concepts, Clusters, and collaborators aligned with the source authority.
Five primitives carry the framework: **Entity** (the gravitational center), **Body** (any authored unit at a single canonical URL), **Concept** (a named, reusable intellectual building block), **Cluster** (a topical region of related Bodies), and **Pathway** (a typed link between Bodies). Two more — **Marker** (a deferred Pathway in draft state) and **Claim** (a resolved, addressable assertion) — close the trust loop. Together they describe authorship as a graph that is human-readable, agent-traversable, and federation-ready.
allemaar.com is the reference instance. The framework itself is portable: any Entity can stand up its own EGGF instance, publish a graph manifest at `/.well-known/egg`, and become discoverable by AI assistants and search systems alike.
## Coined by
Alexandru Mares (allemaar)
## First published
2026 (framework formalized in vault; v0.3-draft locked 2026-05-03).
## Canonical artifact
- Spec: framework vault at `alm-os/Projects/Entity Gravity Graph Framework/` (private; portable spec to be published)
- Reference instance: [allemaar.com](https://allemaar.com)
- Manifest endpoints: [/.well-known/egg](https://allemaar.com/.well-known/egg) · [/graph.jsonld](https://allemaar.com/graph.jsonld)
- Version: `v0.3-draft`
## Related concepts
- [[textual-kinematics|Textual Kinematics]] — sibling work (Tier-1 intellectual program)
- [[elastic-automators|Elastic Automators]] — sibling work
- [[notation-as-alignment|Notation as Alignment]] — adjacent: structure as cognition
- [[the-continuum|The Continuum]] — the long-horizon design discipline EGGF supports
- [[../clusters/eggf|Cluster: EGGF]] — gathering Cluster for posts about the framework
## Why it matters
Most personal publishing is fragile. Posts scatter across platforms, citations point at dead URLs, search engines re-rank yesterday's work, and AI assistants reconstruct an Entity's intellectual graph from whatever HTML they happen to crawl. The lifetime value of a body of work degrades because nothing connects it.
EGGF treats authorship as infrastructure. Every Body has one canonical URL; every Pathway is typed; every Claim is addressable; every Cluster gathers; the manifest exposes the graph to machines without flattening it for humans. The result is intellectual work that *compounds* — agents can ask "what did this Entity originate, what is still current, what was superseded, by whom" and get answers traversable across years and platforms.
EGGF is not a CMS, not a personal-knowledge-management tool, not a static-site generator. It is a **publishing-and-credibility architecture** — a contract between a creator's work and the systems that index it.
## Status
`v0.3-draft` — framework spec stable; reference instance live at allemaar.com; portable instance documentation forthcoming; agent-readable manifests already exposed.
Bodies that mention this term (1)
- The Architecture2026-03-12

