All Ideas
Platform 35 / 100 v1.0 · 2026

Free Cycle

The H Free Cycle Prompt — HFCP
"Teaching the handoff."

A named, human-executable method for rotating AI sessions across platforms using structured synopsis handoffs — staying indefinitely free while preserving the full fidelity of your thinking.

AI platforms ration context, not intelligence. Every free session has a ceiling. Most users hit it and start over, losing everything. A small number of power users discovered something else: you can rotate. Compress the session, carry the context, seed a new platform, continue. Indefinitely. This document names that behavior, structures it, and makes it transferable.

The Free Cycle

  1. Run a session on Platform A to useful depth.
  2. Paste the HFCP Synopsis Prompt at the end of the session.
  3. Copy the generated handoff document.
  4. Open a fresh session on Platform B — Claude, ChatGPT, Gemini, Perplexity.
  5. Paste the handoff. Add the Verification Wrapper. Continue.
  6. When Platform B exhausts, repeat from step 2.

The HFCP Synopsis Prompt

Paste this verbatim at the end of any session before rotating. Do not summarize it yourself — let the model compress it.

Summarize this conversation as a session handoff for a different AI platform. Structure it exactly as follows:

CONTEXT

What we were working on and why. Two to three sentences maximum.

KEY INSIGHTS

The most important ideas generated. Numbered. No filler.

NOTABLE MOMENTS

Any breakthrough reframes, unexpected directions, or conceptually important exchanges. These are the things that would be lost in a flat summary.

SUBSTANTIVE CONCLUSIONS

Decisions made, frameworks named, directions chosen. What is now settled.

LESSONS LEARNED

What didn't work, what got refined, what I now know about this problem that I didn't at the start.

OPEN THREADS

What was unresolved or deliberately deferred. For each open thread, state the specific next action required.

SEED INSTRUCTION

Write one paragraph the next AI should read first to continue without losing fidelity. Write it as if briefing a highly capable colleague who wasn't in the room.

FIDELITY NOTE

Rate the reliability of each section: High (captured cleanly), Medium (compressed with some loss), or Low (partial — probe here first). Note any section where nuance was sacrificed for brevity.


Be ruthlessly concise. Preserve signal. Drop everything that was scaffolding.

The Stance Block

Append this after the Seed Instruction. It transfers not just state but working posture — the difference between a model that knows what you did and one that knows how to continue.

Stance Block

You are not a summarizer or an advisor. You are a working collaborator mid-project. The next move is [state the single specific next action]. A bad response looks like [name the specific failure mode to avoid]. Do not restate what we have established. Continue from the edge of what is resolved, not from the beginning.

The Verification Wrapper

Paste this before your handoff document when seeding the new session. It forces the receiving model to surface its comprehension before it starts working. If sentence one is wrong, the transfer failed — revise the synopsis and retry.

Before continuing, respond first in plain English with three sentences only:

1. What you understand this project to be.
2. What you believe the immediate next action is.
3. What would constitute a failed continuation.

Then proceed.

Known Failure Modes

If the receiving model fails the Verification Wrapper, diagnose against these before revising.

Summary Collapse

Model understands the idea but loses the strategic reasoning that produced it. Fix: make Notable Moments more causal, less descriptive.

Founder Drift

Model begins inventing a different project. Fix: make Substantive Conclusions more explicit about what has been rejected and why.

Next-Step Drift

Model suggests generic actions instead of your specific next move. Fix: Open Threads must name a concrete action, not just a topic.

Tone Deficit

Model mimics your register without inhabiting it. Fix: Stance Block — name the failure mode you most want it to avoid.

What This Is

This is not a prompt library. It is not a snippet manager. It is an AI session continuity method for non-technical users — the first named, structured, human-executable system for transferring working state across competing AI platforms.

No platform will build this. It is structurally adversarial to their retention mechanics. That is the moat.

The method transfers two things most handoffs lose: operational memory — not just what was decided, but why — and agency — not just where you are, but what kind of thinker the next model needs to be. The Verification Wrapper makes the transfer self-checking. A handoff either passes or it doesn't. You know before you waste a session.

To Do — In Order of Priority

  1. Test the live rotation. Use this session's synopsis as the first real test case. Paste it into ChatGPT or Gemini cold. Run the Verification Wrapper. Note exactly what broke.
  2. Revise based on what breaks. If a section fails, rewrite that section only. Do not over-engineer until you know the actual failure point.
  3. Write the Reddit post. One paragraph. Lead with the behavior, not the document. Link the document as the payoff.
  4. Choose one subreddit to post first. r/ChatGPT or r/college. Measure response before spreading wider.
  5. Publish the document publicly. Notion page or Gumroad at zero dollars. Keep the link clean and permanent before the Reddit post goes live.
  6. Add the Fidelity Note to your personal workflow. Use it on your next three real sessions to calibrate how confidence ratings hold up in practice.
  7. Draft the JSON version. Same structure, machine-optimized. Offer as an optional download alongside the human-readable document for technical users.

Interested in this method or want to collaborate on distribution?

Get in touch ↗
Author: Aaron H
Free Cycle · HFCP v1.0
Free to share.
Credit the method.