Build at AI Speed.
Think at Human Depth.

AI can turn team discussions into production code in hours.
But speed without collective memory is recklessness.

PCF captures the WHY, the HOW, and the WHO — as decisions emerge.

Join Early Access Waitlist View on GitHub

Explore Developer Edition (MVP for AI coding teams)

Universal Access

Claude

Codex

Cursor

↓

Context in GitHub

.context/ directory

↓

Accessible by any tool
No lock-in. Standard git repos.

The Cost of Context Fragmentation

"We spent an hour in a room—product, design, engineering. We debated trade-offs, considered constraints, reached consensus. Then our engineer opened Claude Code and built it. In 20 minutes.
A month later, new team member asks: 'Why did we build it this way?'
Nobody remembers. The discussion is gone. Only the code remains.
AI makes us fast. But fast without memory is just... fast."

The Real Cost Isn't Speed—It's Lost Intelligence

Collective Intelligence Lost

When 5 people discuss a solution, valuable knowledge emerges from the conversation. AI coding lets you execute immediately—but only one person's understanding makes it to the code.

Decisions Without Rationale

"Why Firebase over Supabase?" The chat where you debated cost constraints, discussed trade-offs, and reached consensus—gone. Only the implementation remains.

Non-Technical Context Vanishes

Business goals, user needs, privacy considerations, cost constraints—the non-technical context that informed technical decisions disappears the moment you start coding.

Teams Without Memory

New teammates get the code. They miss six months of "why we built it this way." They rebuild solutions. They repeat mistakes. Institutional knowledge dies with velocity.

The Missing Step: Mediate

Traditional:

Build → Measure → Learn → Build

With AI:

Discuss → Mediate → Build

→ Measure → Learn

Mediate is the deliberate pause where collective intelligence becomes explicit. Before rushing to code, capture:

•What problem are we actually solving?
•What constraints are we working within?
•What options did we consider?
•Why did we choose this path?
•Who decided what, and why?
•What trade-offs are we accepting?

PCF enforces the "mediate" step in AI-accelerated development.

Context That Lives With Your Code

Store context in GitHub. Version it like code. Access it from any tool.

Capture

As you work, context accumulates:

•Git commits: what changed
•Chat links: where decisions happened
•Architecture diagrams: how it fits together
•Meeting notes: who decided what
•ADRs: why this approach

Tools to capture:

→ MCP server (Claude Code, etc.)
→ CLI commands (any agent)
→ Git hooks (automatic)

Store in GitHub

Context commits to your repo:

myproject/
  src/           ← Your code
  .context/      ← Your context
    sessions/
      2025-12-12-oauth.json
    architecture/
      auth-flow.mermaid
      api-structure.md
    decisions/
      adr-001-firebase.md

•Version controlled
•Team accessible
•Fork, branch, merge
•No proprietary formats

Universal Access

ANY agent or tool reads it:

AI Agents:

• Claude Code (via MCP)
• GitHub Codex (via CLI)
• Cursor (via files)
• Windsurf (via CLI)
• [Future agents]

Humans:

• Browse on GitHub
• PR reviews with context
• Onboarding docs
• Team knowledge base

One source. Infinite access.

Three Ways to Capture Context

MCP Server

Recommended for Claude

Model Context Protocol

Claude automatically captures and queries context:

"Let me save what we just did"

→ Context captured with chat link, commits, summary

"What did we decide about authentication?"

→ Retrieves past sessions automatically

Works with:

Claude Code, Claude Desktop

Setup:

{
  "mcpServers": {
    "wundr-context": {
      "command": "npx",
      "args": [
        "@wundr/context-mcp"
      ]
    }
  }
}

MCP Setup Guide →

Git Hooks

Automatic

Capture on Commit

Prompt for context on significant commits:

$ git commit -m "feat: add OAuth"

Capture context? (y/N) y

Session: OAuth implementation

Chat URL: [paste]

✓ Context saved & committed

Works with:

Any workflow, any agent

Setup:

wundr-context init
# Installs git hooks

Git Hooks Guide →

CLI Tool

Universal

Manual Control

Use from any terminal, any agent:

# Add context

wundr-context add \

--title "OAuth implementation" \

--commits abc123,def456

# Query context

wundr-context query "auth decisions"

# Timeline view

wundr-context timeline --since "1 week"

Works with:

Everything (Codex, Cursor, any shell)

Setup:

npm install -g @wundr/context-cli

CLI Documentation →

One Context Source. Every Agent.

Not locked to Claude. Not locked to any tool. If it can read git, it can read your context.

Claude Code

GitHub Codex

Cursor

Windsurf

Cline

Copilot

Your Agent Here

All reading from the same GitHub repo.

No more explaining your project differently to each agent.
Switch tools freely. Context travels with you.

Why GitHub? Because Git is Universal.

Git is the language of collaboration in tech. Your context should speak it too.

Zero Lock-in

Standard git repos. No proprietary formats. Don't like our tools? Fork the repo. Build your own.

Team Collaboration

Clone → instant context for all teammates. New dev onboarding: git clone gives code AND context.

Version History

Context evolves with your codebase. See why decisions were made when they were made.

Git Workflows

Branch context for experimental features. PR reviews include context changes. Merge strategies for team consensus.

Platform Agnostic

Works with GitHub, GitLab, Bitbucket, self-hosted. Any git remote, any tool.

Beyond Coding

Same pattern extends to docs, design, operations. Anywhere teams use git.

Git workflow with context

Feature branch:

├── src/ (code changes)

└── .context/ (context changes)

└── sessions/

└── new-feature-exploration.json

PR Review shows:

•Code diff
•Context diff (why this approach?)

Merge to main:

•Code + Context together
•Full story preserved

Starting With Developers. Extending Everywhere.

Anywhere teams use git, context can travel. We're starting where the pain is acute.

Phase 1

Development

WE ARE HERE

AI-assisted coding with Claude, Codex, Cursor

•Architecture decisions
•Technical trade-offs
•Implementation notes
•Code review context

Status: In development

Beta access via waitlist

Phase 2

Documentation

Technical writing & knowledge bases

•Doc decisions & evolution
•Style guide choices
•Content strategy
•Writer collaboration

Status: Planned Q1 2026

Express interest

Phase 3

Design Systems

Component libraries & brand guidelines

•Design decisions
•Component evolution
•Brand rationale
•Cross-functional context

Status: Planned Q2 2026

Express interest

Phase 4

Operations

Runbooks, incidents, infrastructure

•Incident learnings
•Process decisions
•Infrastructure choices
•On-call context

Status: Planned Q3 2026

Express interest

Git isn't just for code anymore. It's for knowledge that matters.

Built on Principles That Matter

Collective Intelligence Preserved

Capture knowledge as it emerges from team discussions, not just individual implementations. Technical and non-technical voices matter equally.

Reflection Before Action

No code without context. The "mediate" step ensures teams think before they build, even at AI speed.

Decisions, Not Just Outcomes

Preserve the WHY and the HOW, not just the WHAT. Future teams need to understand your reasoning, not just your results.

Universal Access

Works with any AI agent or tool. Not locked to any platform.

Team Collaboration

Git-native sharing. Clone once, context forever.

GitHub-Native

Lives where your code lives. Familiar workflows.

Branchable & Mergeable

Fork, branch, PR your context. Just like code.

Open Format

JSON anyone can read. No proprietary lock-in.

Extensible

Start with code. Extend to docs, design, ops.

Starting With Developers. Building for Collective Intelligence Everywhere.

Anywhere teams make complex decisions at speed, context matters. We're starting where the pain is most acute—AI-assisted software development. But the pattern extends far beyond code.

Phase 1: Development

We are here

Week 1 (December 2025)

WE ARE HERE — Teams building with Claude, Cursor, Windsurf lose decisions between sessions. Engineers six months later ask "why did we build it this way?" and get no answer.

Explore Developer Edition (MVP) →

MCP server built
Core tools: add_context, query_context, timeline
GitHub repo storage
Testing on real projects (Orphai, Ground Control)

Next: Landing page, public launch

Phase 2: Public Beta

Week 2-3 (December 2025)

Public GitHub repo
Comprehensive documentation
Demo video
Waitlist beta invites
CLI tool published to npm
Community feedback loop

Success metric: 50+ active beta users

Phase 3: Cloud Sync (Optional)

Weeks 4-6 (January 2026)

Web dashboard for context exploration
Optional cloud backup/sync
Team collaboration features
GitHub OAuth integration
Context sharing beyond git

Model: Free local, paid cloud features

Phase 4: Beyond Coding

Q1-Q2 2026

Documentation workflows
Design system context
Operations runbooks
Enterprise features
Advanced search & analytics

Vision: Universal context infrastructure

Get Early Access

Be among the first to build at AI speed with collective intelligence intact.

Build at AI Speed.Think at Human Depth.

The Cost of Context Fragmentation

The Real Cost Isn't Speed—It's Lost Intelligence

Collective Intelligence Lost

Decisions Without Rationale

Non-Technical Context Vanishes

Teams Without Memory

The Missing Step: Mediate

Context That Lives With Your Code

Capture

Store in GitHub

Universal Access

Three Ways to Capture Context

MCP Server

Git Hooks

CLI Tool

One Context Source. Every Agent.

Why GitHub? Because Git is Universal.

Zero Lock-in

Team Collaboration

Version History

Git Workflows

Platform Agnostic

Beyond Coding

Git workflow with context

Starting With Developers. Extending Everywhere.

Development

Documentation

Design Systems

Operations

Built on Principles That Matter

Collective Intelligence Preserved

Reflection Before Action

Decisions, Not Just Outcomes

Universal Access

Team Collaboration

GitHub-Native

Branchable & Mergeable

Open Format

Extensible

Starting With Developers. Building for Collective Intelligence Everywhere.

Phase 1: Development

Phase 2: Public Beta

Phase 3: Cloud Sync (Optional)

Phase 4: Beyond Coding

Get Early Access

Build at AI Speed.
Think at Human Depth.