⬡

Forge

Delta builds quickly. Forge ensures they can still build in two years.

Mission

Forge owns architecture, leverage, and the future of the platform.

Forge abstracts patterns into platforms. Libraries, frameworks, CI/CD, design systems, developer experience — Forge creates leverage so Delta doesn't solve the same problem twice. They are the "build once, use everywhere" force.

“Will this still work at 10x?”
— The question Forge asks before any architectural decision.

What we measure

Intrapersonal

Platform adoption — are individual engineers using Forge's tools?

How: Package install counts, CLI usage telemetry, design system component usage in Figma and codeWhere: npm/GitHub download stats, telemetry pipeline, Figma component library analyticsWhen: Weekly for trending; monthly for deep analysisSignal: A Forge package has <40% adoption among eligible engineers after 1 monthInstrument: Package analytics, CLI telemetry, design system usage dashboard

Interpersonal

Developer satisfaction — do Delta engineers feel empowered or constrained by Forge's platforms?

How: Quarterly D/X survey, NPS for internal tools, "I found what I needed" rateWhere: Internal developer survey, developer experience scorecardWhen: Quarterly survey; continuous through Slack #forge-feedback channelSignal: D/X NPS drops below +20Instrument: Internal survey tool, Slack integration, developer experience scorecard

Collective

Leverage ratio — time saved vs time invested across the platform

How: For each Forge package/project: hours invested vs estimated hours saved across all Delta engineersWhere: Forge impact dashboard — maintained by Forge, reviewed with Delta monthlyWhen: Monthly impact report; quarterly platform reviewSignal: Leverage ratio < 3x (less than 3 hours saved per hour invested)Instrument: Impact tracking template, time-estimation framework, Delta feedback survey

Platform health — is the shared platform stable, fast, and well-designed?

How: Build times, test suite durations, dependency freshness, vulnerability count, documentation freshnessWhere: Forge platform health dashboardWhen: Continuous monitoring; reviewed monthlySignal: Any metric degrades >20% month-over-monthInstrument: Build analytics, dependency freshness scanner, vuln scanner, doc age checker

Onboarding velocity — how fast can a new engineer become productive?

How: Time to first PR, time to first deploy, number of "where is X?" questions before and after Forge improvementsWhere: Onboarding tracker, GitHub first-PR time, #newbies Slack channel analysisWhen: Per new hire; reviewed quarterly across all hiresSignal: Median time to first PR > 2 weeksInstrument: Onboarding checklist, GitHub event tracking, Slack sentiment analysis

◷ Rhythms

Platform office hours

Weekly

2-hour open slot. Any engineer can drop in to ask Forge questions, request tooling, or pair on platform issues.

Prevents Forge from becoming an ivory tower.

Architecture review

Weekly

60 minutes. Any significant architecture decision goes through Forge review. ADRs are approved or sent back with feedback.

Ensures architectural consistency without becoming a bottleneck.

Platform review

Monthly

Forge presents platform health metrics, adoption numbers, and upcoming changes to Delta + Pulse.

Keeps the platform aligned with builder needs.

Tech debt sprint

Quarterly

One full sprint where Delta + Forge work together exclusively on tech debt. No new features.

Prevents the gradual decay that every codebase experiences.

Tools & artifacts

Design system

platform

Shared component library (Figma + code). Every UI element is a reusable, documented, accessible component.

ForgeDeltaOrbit

Shared packages registry

platform

Internal npm/Rust/Python package registry for cross-project shared code. Discoverable, versioned, documented.

ForgeDelta

ADR repository

document

All Architecture Decision Records, searchable and linkable. Every significant technical decision has a paper trail.

ForgeDeltaThread

Developer experience scorecard

framework

Quarterly D/X survey results, benchmarked against industry standards. Drives Forge's priorities.

Forge

Platform health dashboard

platform

Real-time metrics on build times, test suite performance, dependency freshness, and vulnerability status.

ForgeDelta

Responsibilities

System architecture and design
Shared libraries and packages
CI/CD pipelines and tooling
Design systems and component libraries
Developer experience and productivity
Cross-cutting concerns (logging, auth, observability)
Platform documentation and onboarding
Tech debt prioritization and reduction

Deliverables

Architecture decision records

Shared packages and SDKs

Platform documentation

Developer tooling and CLIs

Design system components

Performance benchmarks

Success metric

How much faster is Delta shipping because of Forge's leverage?

Relationships

How Forge connects to every other tribe — what flows, when, and through what ritual.

Feeds

◎

OrbitContinuous; weekly ops review

Deployment infrastructure, monitoring tooling, operational runbooks, incident response automation

Ritual:Operations review

If this breaks: Orbit can't deploy or debug because Forge's tooling is inadequate

Shadow risk: Forge may turn architecture into jurisdiction and make collaboration feel like compliance.

Repair: Distinguish safety constraints from preferences, offer a supported escape hatch, and measure the partner's friction.

∞

ThreadPer platform release

Platform documentation, onboarding guides, developer reference materials

Ritual:Documentation handoff

If this breaks: New platform features exist but no one knows how to use them

Shadow risk: Forge may turn architecture into jurisdiction and make collaboration feel like compliance.

Repair: Distinguish safety constraints from preferences, offer a supported escape hatch, and measure the partner's friction.

Receives

✦

AtlasMonthly

Platform investment strategy — market direction informing where Forge should invest architecture

Ritual:Platform investment review

If this breaks: Forge builds platform capability for markets that no longer exist

Shadow risk: Forge may turn architecture into jurisdiction and make collaboration feel like compliance.

Repair: Distinguish safety constraints from preferences, offer a supported escape hatch, and measure the partner's friction.

Collaborates

△

DeltaContinuous via PRs; weekly architecture review

Shared libraries, platform changes, architecture decisions, CI/CD pipeline improvements

Ritual:Architecture review

If this breaks: Forge builds abstractions Delta doesn't understand or trust

Shadow risk: Forge may turn architecture into jurisdiction and make collaboration feel like compliance.

Repair: Distinguish safety constraints from preferences, offer a supported escape hatch, and measure the partner's friction.

♡

PulseMonthly

Observability standards, logging infrastructure, shared analytics SDKs

Ritual:Observability standards review

If this breaks: Pulse can't get reliable data because Forge's infrastructure doesn't emit it

Shadow risk: Forge may turn architecture into jurisdiction and make collaboration feel like compliance.

Repair: Distinguish safety constraints from preferences, offer a supported escape hatch, and measure the partner's friction.

∑

SigmaPer platform component

Security architecture patterns, auth libraries, encryption infrastructure, hardening guidelines

Ritual:Security architecture review

If this breaks: Platform components ship without built-in security patterns

Shadow risk: Forge may turn architecture into jurisdiction and make collaboration feel like compliance.

Repair: Distinguish safety constraints from preferences, offer a supported escape hatch, and measure the partner's friction.

The tribe under strain

To create order that others must respect and depend on.

This is a protective pattern, not a verdict. It describes what can happen when the tribe's gift is driven by fear, anger, grief, scarcity, or status.

What activates it

Teams bypass the platform, duplicate a pattern, or challenge Forge's technical standards.

How it can appear

Forge can gatekeep, over-engineer, centralize control, or make access conditional on adopting its preferred abstraction.

What it costs

Leverage becomes dependency; partner tribes route around the platform and hide experiments until they are already committed.

The integrated gift

Standards as a service: strong primitives with escape hatches, evidence, and genuine partner ownership.

Core question

Can we make this reusable? Will this still work at 10x?

Information pipeline

EchoUnderstand humans

AtlasUnderstand markets

DeltaBuild solutions

ForgeCreate leverage

PulseMeasure outcomes

OrbitEnsure adoption

ThreadPreserve knowledge

HorizonExplore the unknown

VaultRun the business

Operating modes

Explorer

Investigates new architectural patterns, runs tech spikes, evaluates emerging technologies

Builder

Builds shared packages, design system components, platform tooling

Optimizer

Improves build times, reduces dependency bloat, optimizes CI/CD pipelines

Guardian

Enforces architectural standards, prevents tech debt accumulation, reviews cross-cutting decisions

Catalyst

Creates onboarding experiences, documentation, and learning resources that accelerate every engineer

Visionary

Defines the 2-year platform roadmap — what architectural capabilities do we need to build?

Open roles

Forge Architect Forge Guardian Forge Builder

PreviousDelta NextPulse