id8Labs

Internal Framework

The system that builds systems.

A self-improving development framework that captures patterns, decisions, and failures across projects. Every build makes the next one faster.

In production at ID8Labs~/.claude/pipeline/ locationClaude Code integrated with

The philosophy

“Like mycelium — the visible output (shipped code) is just the fruiting body. The real intelligence is the network underneath.”

Every project that passes through the Foundry:

  • →Benefits from patterns learned in previous projects
  • →Contributes new patterns back to the system
  • →Compounds your ability to ship faster and cleaner

How it works

ID8Pipeline

The 11-stage build process. Concept Lock → Ship → Listen & Iterate.

Defines what stages a project goes through.

ID8Foundry

The accumulated knowledge. Patterns, decisions, failures, learnings.

Provides the knowledge accumulated from all projects.

The structure

Filesystem
~/.claude/pipeline/
├── SYSTEM.md           # Operating instructions
├── CONTEXT.md          # Who you are, current priorities
├── HANDOFF.md          # Session continuity
├── STACK.md            # Default tech choices
├── frameworks/
│   ├── DECISIONS.md    # Decision framework
│   ├── SCOPING.md      # Scoping discipline
│   └── FAILURE_PATTERNS.md
├── patterns/
│   ├── ARCHITECTURE.md
│   ├── COMPONENTS.md
│   └── ANTI_PATTERNS.md
├── projects/
│   ├── _TEMPLATE.md
│   └── [project].md    # Active project files
└── logs/
    └── LEARNINGS.md    # Captured insights

Core Files

SYSTEM.mdSr Dev operating instructions, decision frameworks
CONTEXT.mdWho you are, how you work, current priorities
HANDOFF.mdSession continuity — where we left off
STACK.mdDefault technology choices (Next.js, Supabase, Vercel)
LEARNINGS.mdCaptured insights from every project

Frameworks

DECISIONS.mdHow to make technical decisions with tradeoffs
SCOPING.mdRuthless scoping discipline — cut to ship
FAILURE_PATTERNS.mdWhat breaks and why — so you never fail the same way twice

Patterns

ARCHITECTURE.mdReusable structural patterns
COMPONENTS.mdCode patterns that work
ANTI_PATTERNS.mdWhat to avoid

Session startup

Every session, before diving into work:

  1. 01Read HANDOFF.md — Where we left off
  2. 02Check active project file — Current phase, blockers, decisions
  3. 03Ask: "What's the highest-leverage thing we can do today?"

Commands

6 verbs
pipeline statusReport current project, phase, and next checkpoint
new project [name]Create fresh project file from template
sync project [name]Import existing repo into Foundry
log learningAdd entry to LEARNINGS.md
extract patternMove learning → pattern file
update handoffUpdate session state
In production at ID8Labs~/.claude/pipeline/ locationClaude Code + ID8Pipeline stages