eforge 1.0.0

Renderer-agnostic project runtime and manifest interpreter for the Forge ecosystem

Your AI agent doesn't know what you meant to build. Forge compiles your architectural intent into a verified, queryable graph — so your agents work with structure, not guesswork.

The Solution

forge start --project-path ~/Projects/my-app

The Demo

Forge managing itself (forge):

{
  "graph_health": 100,
  "sync_health": 100,
  "infra_health": 100,
  "adi_score": 0,
  "brc_score": 100,
  "idr_score": 100,
  "overall": 100,
  "healthy": true
}

Quickstart

git clone https://github.com/[your-username]/forge
cd forge && pip install -e .
forge start --project-path ~/Projects/my-app

How It Works

Three primitives: node, edge, event.

The Protocol Layer

• GloveProtocol — source analysis for any stack
• CheckerProtocol — infrastructure health checking
• RendererProtocol — graph output formatting
• SubscriberProtocol — event bus subscription

The Metrics

• ADI — Architectural Debt Index from ghost nodes, dark matter, stale annotations
• BRC — Blast Radius Coverage percentage of nodes with edge connectivity
• IDR — Intent Decay Rate of nodes lacking recent annotations
• POS — Predictive Obsolescence Score from implementation status and age
• HealthVector — unified six-dimensional health vector

Status

Current epoch: 6 (External Surface) Test count: 1005+ Roadmap: https://github.com/[your-username]/forge/issues

Planning and handoff notes live in _context/. Root docs/ may lag; treat _context as the primary narrative for this repo.