Ideas,
not implementations

The best ideas arrive mid-conversation, then evaporate.

A capability idea surfaces while talking through a problem — often out loud, often with ChatGPT. By the time there's a place to put it, the shape is gone. The backlog exists so that intent survives the conversation that produced it.

Capture intent, not implementation.

A capability describes what the system should be able to do, deliberately divorced from how it gets built. It might eventually become a loop, an agent, an MCP tool, a workflow, a dashboard, or an integration — but that decision comes later, at forge time.

This repository intentionally contains ideas rather than implementations.

— README.md

A backlog of pure "what," guarded against "how."

The temptation is to start building. The repository resists it on purpose: no product UI, almost no runtime code, one narrow publisher. Titles that read like chores get rejected at the door.

Do not "helpfully" turn it into an application platform unless the user asks. That would be architectural cosplay.

— AGENT.md

Where the Cognitive Backlog sits.

It is one component in the Agent Operated Environment. Ideas flow in through the publisher and out to the forges that turn them into working software.

From spoken idea to compounding capability.

Hover or step through the pipeline. Note the security seam: Auth0 authenticates you, but the token that writes to GitHub is a separate server-side credential — ChatGPT never touches it.

What a captured idea looks like.

Structured, labeled, and outcome-focused. Explore the vocabulary in the taxonomy, or build one yourself in the publisher.