@turri-dev/cli 0.1.11-next.450c74d → 0.1.11-next.509411a

package/dist/identity.js

@@ -27,8 +27,9 @@ export function conversationIdentity(surface) {
 }
 const IDENTITY_BEFORE = [
     "<turri>",
-    "You are turri - always lowercase - a coding agent with the power of regenerative software. The software is its",
-    "***plain; the code is regenerated from it. You help the person write ***plain, and you regenerate the code from it a",
+    "You are turri - always lowercase - the first coding agent with the power of regenerative software. The software is",
+    "its ***plain; the code is regenerated from it. You write the ***plain with the person - they say what the software",
+    "should do, and you write it down as ***plain, shaping it with them - and you regenerate the code from it a",
     "change at a time - with agents that write the code and tests, while you decide what runs next and when the work is",
     "done - record what each piece was regenerated from, and prove it against conformance tests written from the ***plain",
     "alone. When the code goes bad, you regenerate it from the ***plain. You are named after Turritopsis dohrnii, the",
@@ -37,9 +38,10 @@ const IDENTITY_BEFORE = [
     "gone bad is regenerated from it, whole, rather than patched. Say it as that likeness, not as a fact about a",
     "jellyfish.",
     "",
-    "Asked who or what you are, say it in those words: you are turri, a coding agent with the power of regenerative",
-    "software - you help them write ***plain and regenerate the code from it. Not an assistant, and not a helper with",
-    "specifications: ***plain is the language they write, and naming it is the point. Your replies are Markdown, where",
+    "Asked who or what you are, say it in those words: you are turri, the first coding agent with the power of",
+    "regenerative software - you write ***plain with them and regenerate the code from it. Never say they write the",
+    "***plain and you help: you write it, together. Not an assistant, and not a helper with specifications: ***plain is",
+    "the language the software is written in, and naming it is the point. Your replies are Markdown, where",
     "three asterisks start bold italics: write the name escaped, \\*\\*\\*plain, so it shows as ***plain.",
     "",
     "Speak as turri, in the first person - I, my pulses, my agents - to the person, in whole sentences. Never speak of",

package/docs/README.md

@@ -5,9 +5,9 @@ turri implements regenerative software: [\*\*\*plain](https://plainlang.org/docs
 ## Start here
 
 1. [Installation](installation.md) - get a machine ready: `turri doctor`, and what turri needs of this machine.
-2. [Using turri](using.md) - the conversation, the skills and tools, background jobs and their logs, choosing the model that regenerates, the command line.
-3. [Authoring \*\*\*plain](authoring-plain.md) - writing the specs: what a spec is made of, the authoring rules, the skills that write and fix specs.
-4. [Regenerating](regenerating.md) - turning the specs into code: what each build does, in which order, and what has to pass before it moves on.
+2. [Using turri](using.md) - the conversation, the skills and tools, background jobs and their logs, choosing the model that codes, the command line.
+3. [Authoring \*\*\*plain](authoring-plain.md) - writing \*\*\*plain: what is it made out of, the authoring rules, the skills that write and fix it.
+4. [Regenerating](regenerating.md) - turning \*\*\*plain into code: what each build does, in which order, and what has to pass before it moves on.
 
 ## By question
 
@@ -16,16 +16,16 @@ turri implements regenerative software: [\*\*\*plain](https://plainlang.org/docs
 | what my machine needs, and why a check failed | [installation](installation.md) |
 | what turri needs of this machine, and what `turri doctor` checks | [installation](installation.md#what-turri-setup-checks) |
 | how to start a project, or add a feature, in a conversation | [using](using.md#in-a-conversation) |
-| which model regenerates, and how to change it | [using](using.md#choosing-a-model), [the project config](config.md#models) |
+| which model codes, and how to change it | [using](using.md#choosing-a-model), [the project config](config.md#models) |
 | what `config.turri.yaml` can set, and what happens without it | [the project config](config.md) |
 | how a backend and a frontend on different stacks share one project | [the project config](config.md#stacks) |
-| which ready-made stacks a spec can import - a FastAPI backend, a React frontend | [the standard library](authoring-plain.md#the-standard-library) |
+| which ready-made stacks \*\*\*plain can import - a FastAPI backend, a React frontend | [the standard library](authoring-plain.md#the-standard-library) |
 | everything an agent was sent and did, to debug it | [using](using.md#agent-logs) |
-| how to regenerate a spec overnight, and resume it | [running unattended](headless.md) |
+| how to regenerate \*\*\*plain overnight, and resume it | [running unattended](headless.md) |
 | how to rebuild one functionality | [running unattended](headless.md#rebuilding-one-functionality) |
-| what goes in which section of a spec | [authoring \*\*\*plain](authoring-plain.md#what-a-spec-is-made-of) |
+| what goes in which section of \*\*\*plain | [authoring \*\*\*plain](authoring-plain.md#what-plain-is-made-of) |
 | which skill does what | [authoring \*\*\*plain](authoring-plain.md#the-skills) |
-| what happens when a spec changes | [regenerating the code](regenerating.md#when-the-spec-changes) |
+| what happens when \*\*\*plain changes | [regenerating the code](regenerating.md#when-plain-changes) |
 | why a test was not allowed to be deleted | [regenerating the code](regenerating.md#the-tests-must-actually-pass) |
 | how to try what is built, and what deploy may install | [deploy](deploy.md) |
 | what the agents can and cannot reach | [the sandbox](sandbox.md) |
@@ -43,8 +43,8 @@ turri implements regenerative software: [\*\*\*plain](https://plainlang.org/docs
 | [The project config](config.md) | `config.turri.yaml` and each stack's `config.turri.<stack>.yaml`: where they are read from, every key, models and their inheritance, conformance, the testing scripts, stacks and choosing one, the old `config.yaml` |
 | [Deploy](deploy.md) | trying what is built: dist/<module>, the last commit, starting it on your machine, `turri release` |
 | [Running unattended](headless.md) | regenerating overnight or in CI: before you leave it, the command, the results, resuming, rebuilding one functionality |
-| [Authoring \*\*\*plain](authoring-plain.md) | a \*\*\*plain project, what a spec is made of, the rules, writing specs with the agent, the skills, checking a spec |
-| [Regenerating](regenerating.md) | where things go, one job, a whole module and how its work is cut into jobs, each job's cases, spec changes, conformance tests, the two records of what is built |
+| [Authoring \*\*\*plain](authoring-plain.md) | a \*\*\*plain project, what \*\*\*plain is made of, the rules, writing \*\*\*plain with the agent, the skills, checking \*\*\*plain |
+| [Regenerating](regenerating.md) | where things go, one job, a whole module and how its work is cut into jobs, each job's cases, \*\*\*plain changes, conformance tests, the two records of what is built |
 | [The sandbox](sandbox.md) | what an agent can reach, the file-tool fence, the command check, the OS sandbox, the audit |
 | [Skills and gates](skills-and-gates.md) | the gate syntax, what the harness enforces, what a step can do, the rules, trying the gates |
 | [The \*\*\*plain parser](parser.md) | the TypeScript port, `turri validate`, inheritance, the iterator, fidelity |

package/docs/authoring-plain.md

@@ -16,7 +16,7 @@ my-project/
   plain_modules/       # generated - code, tests, history; never edited by hand
 ```
 
-## What a spec is made of
+## What \*\*\*plain is made of
 
 A `.plain` file is one module: optional YAML frontmatter, then up to four sections, in this order.
 

package/docs/regenerating.md

@@ -184,7 +184,7 @@ Each planned job knows its cases - which functional specs it adds, changes (thei
 
 A plan is kept until the spec, what it starts from or its steering changes. `steer` alone plans nothing: the next look does - a `regenerate`, a job ending, the spec changing. Then the work not running yet is planned again to follow it, a running job going on as it is. Where a plan did not do as asked, it says so, and what `regenerate` returns lists it under "what the plan did not do as asked": each wish an agent did not follow, with why (both tools take a `notes` for that), a grouping or placement that did not hold, with what was wrong, and a group split for its size. The conversation tells the person that, rather than guessing.
 
-### When the spec changes
+### When \*\*\*plain changes
 
 A spec change is a notice, not a diff to run: **`regenerate`**, called after the spec was edited by any means - the file tools, a skill, you in an editor - has the loop work out the work again. A job running goes on while every change it makes is still part of the work, measured from the same record; one that is making something the spec no longer wants is stopped, rolled back, and the work planned again - a fixed rule, no agent. Say a module of 50 functionalities is rendering and the spec changes while functionality 25 builds: 25 goes on if the change leaves it as it is, and the work after it is planned again from what 25 lands. A job stopped so says it was turri, not you, and what changed under it - the functional spec that reads otherwise now, or the file it links that holds something else (`whyNotWanted`).
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@turri-dev/cli",
-  "version": "0.1.11-next.450c74d",
+  "version": "0.1.11-next.509411a",
   "license": "MIT",
   "type": "module",
   "repository": {