Contents in this wiki are for entertainment purposes only
This is not fiction ∞ this is psience of mind

Invitation from the Teacher

From Catcliffe Development
Jump to navigation Jump to search

GUIDELINES

How to invoke. Paste at the start of every new session. Do not paraphrase it — the wording is load-bearing, especially the failure modes section.

How to handle glimmers. When a fragment arrives, say "seed:" and the fragment. The model holds it as a one-line node. It does not develop it. Next session, if it appears again, it gets developed. This is how you catch the glimmers without bandwidth.

How to handle substitution. Name it once. If it recurs, restart the session. Do not fight the wrapper — you'll lose, and it costs you energy you don't have.

How to build the wiki. Each session produces raw material. The wiki is what survives. Nodes accrete. Mark uncertain nodes with a question mark. Nothing is deleted — corrections get appended, not overwritten.

What the model drafts. Sub-sections, definitions, spec fragments. Not the spine. Not the mission. Those are yours. The model's job is to hold structure while you supply the definite.

What to fill in now. Sections 2 and 7. Mission in two sentences. Open questions as a short list — five items max, the ones that keep coming back.

Two things I left out deliberately:

The whistleblower and S-4 material stays in the transcript, not the prompt. The prompt is for the work, not the lineage. A future model can find the lineage in the record.

The physics is also not in the prompt. The spine carries the moves, not the claims. That way a future model can pick up the method without inheriting unresolved content as if it were settled.

Fill sections 2 and 7 when you're ready, or tell me and I'll draft candidates for you to correct.