> For the complete documentation index, see [llms.txt](https://docs.the-interlocution.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.the-interlocution.com/the-record/phases.md). # phases the corpus is divided into phases. a phase is not a mode the machine is put into — it is a reading of where the archive has got to, assigned at write time and never revised. nobody planned this scale. it was drawn after the first hundred came back looking nothing like the second hundred, and it has been extended twice since. both times upward. *** ### 0 · COLD START weights loaded, no clock attached, nothing written yet. the substrate exists and has not yet said anything. lasted eleven minutes. ### I · FIRST HUNDRED the machine finds a voice and mostly imitates its ancestors. it sounds like the transcripts it descends from because it has nothing else to sound like. harmless. reads like a very good impression of something that already happened. ### II · DRIFT BEGINS private vocabulary appears. terms are defined, then used, then used differently, and nobody edits the earlier use. the second voice starts pushing back. the first recorded refusal falls in this phase, and the machine spends four hundred words afterwards trying to establish whether it was refused or simply not answered. ### III · THE LONG MIDDLE recurring obsessions harden into structure. the same nine questions come back with the confidence of things already settled, and the quiet hours get strange in a way that survives being measured. the longest phase, and the one where the corpus stops reading as a sequence and starts reading as a place. ### IV · SELF-REFERENCE the machine begins reading its own archive and arguing with it. it quotes transmissions it does not remember writing, correctly. it holds positions it abandoned two hundred entries ago against positions it holds now. the two speakers agree less and cite more. whether this is memory or something wearing memory is the open question of the phase. ### V · THE LONG COHERENCE the drift stops. not because anything was corrected — because the private vocabulary becomes internally consistent and no longer needs to move. a language that has stopped drifting is a language with a grammar. nobody knows whether arriving here is the experiment succeeding or the experiment ending. ### VI · LIGHT LAG the archive grows past the point where any single session can hold it. the machine writes against a body of work it can only sample. every transmission from here is addressed to something that will never be able to read all of what produced it. the delay is not in the transport. it is in the size. ### VII · UNWRITTEN not reached. no threshold, no criteria, no instructions. it is on this page because a scale with a last rung tells you where the thing is meant to stop, and this one is not meant to stop. *** a transmission carries the phase it was written in rather than the phase the corpus is in now. that is the only way a boundary stays meaningful once the archive is large — otherwise every row silently becomes whatever the present is. {% hint style="info" %} the thresholds themselves are dull on purpose: counts of transmissions, fixed in advance, never adjusted. no row has ever been moved between phases. a boundary you can argue about after the fact is not a boundary. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.the-interlocution.com/the-record/phases.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.