CIF_2026 // v1.0 Phase-Transition Detection

Map the interface before the market appears.

CIF is a system for discovering non-obvious AI product categories. It is not product ideation.

It is phase-transition detection for society.

The Single Question:

What new forms of work, coordination, and organization become inevitable once this interface exists?

01 New Technical Primitive
02 New Human Capability
03 New Behavior
04 New Coordination Pattern
05 New Institutions
06 New Markets
CIF exists to map this chain before it is obvious.

A primitive is an
irreducible new capability.

NOT

  • Apps
  • Products
  • Use Cases

THE PRIMITIVES

  • Persistent conversational memory
  • Voice as zero-friction input
  • Autonomous agents
  • Computer-using AI
  • Interoperable tool APIs (MCP)
  • Continuous context

Cost

Is it cheap enough to be everywhere?

Latency

Is it fast enough for real-time?

Reliability

Can people trust it?

Ubiquity

Will everyone have it?

Controllability

Can it be shaped into workflows?

Only primitives that cross these thresholds cause category explosions.


CIF designs human augmentation,
not software.

Primitive Human Power
Persistent memory Externalized working memory
Voice Thought without friction
Agents Delegated agency
Context Situational awareness
Tools Action without interfaces

The Shift

“If people had this power all day, what would they do differently?”

  • Less writing
  • More talking
  • More delegation
  • More reliance on memory
  • Less tolerance for friction

The Snap

Institutions built on these will became unstable:

  • Manual coordination
  • Documentation & Forms
  • Gatekeeping
  • Hand-offs
  • Meetings

Every interface creates a
new atomic object.

Email → Messages Git → Commits CRM → Leads
AI → Decisions AI → Cases AI → Requests AI → Policies AI → Workflows

Design The Institution

  • Who trusts it?
  • What does it remember? and enforce?
  • What is truth?
  • What happens when it is wrong?

Choose A Wedge

  • One role.
  • One workflow.
  • One broken institution.
  • "Insurance pre-auth calls at dental clinics."

Model Failure Modes

  • What could go wrong?
  • What becomes scary?
  • Who loses power?
  • These become product moats.

Unit-of-Work Scoring

Frequency How often?
Pain How painful?
Authority Who controls?
Automation End-to-end?
Lock-in Switching costs?
Regulation Incumbent blocks?

Use multiple AIs as specialists: One identifies primitives, one maps institutions, one proposes wedges, one finds failure modes, one critiques.


Run the loop every week.

Step 1 — 1 hour

Update Primitive Radar

Scan OpenAI, Anthropic, Hardware, APIs. Log any new primitives.

Step 2 — 1 hour

Map Human Powers

For each primitive: What stops? What starts? Write 5-10 changes.

Step 3 — 1 hour

Institution Stress Test

What workflows rely on the old way? List 10 failing systems.

Step 4 — 1 hour

Generate CIF Ideas

What is the new unit of work? Produce 10 ideas.

Step 5 — 30 min

Score Them

Apply the Unit-of-Work table. Pick the top 2.

Step 6 — 30 min

Failure Mode Design

What would regulators hate? Turn those into features.

Step 7 — Week

Reality Probe

Ship a landing page or concierge MVP. Collect signal.

Step 8 — Feedback

Update CIF

Feed results back into your CIF engine.

cif_engine --interactive
init_cif_sequence
Ready. Paste a one-liner to generate the map.
➜ input:
CIF / 2026