ai-collab-open-system 0.1.0 → 0.1.2

package/.aict/START_HERE.md

@@ -105,7 +105,7 @@ Expected result: profile/context, acceptance, execution prompt, guard review, ha
 
 ## Want the AI to remind you on its own
 
-Tired of remembering to run the guard yourself? Install the adapter into your AI tool's always-on instructions with `node bin/ai-collab.js adapters install --target <repo>` (after publish: `ai-collab adapters install --target <repo>`). It turns on restrained coaching reminders, so the AI prompts you at the key moments - define done, review a completion claim, hand off, harvest. If you only have one tool, the completion-claim check routes through `single-tool-guard` (a fresh adversarial pass in the same tool) instead of a second AI brand.
+Tired of remembering to run the guard yourself? Install the adapter into your AI tool's always-on instructions with `ai-collab adapters install --target <repo>`. It turns on restrained coaching reminders, so the AI prompts you at the key moments - define done, review a completion claim, hand off, harvest. If you only have one tool, the completion-claim check routes through `single-tool-guard` (a fresh adversarial pass in the same tool) instead of a second AI brand.
 
 ## Where to go next
 

package/.aict/WORKSPACE_MANIFEST.json

@@ -1,6 +1,6 @@
 {
-  "name": "AI Collaboration Open System Workspace",
-  "version": "0.1.0",
+  "name": "DoneTrace Workspace",
+  "version": "0.1.2",
   "localFirst": true,
   "defaultNetworkUse": "none",
   "workspaceDirs": [

package/.aict/adapters/SHARED_CORE_CONTRACT.md

@@ -60,15 +60,19 @@ Separate from the timed reminders above: when the user's message contains one of
 
 When none of these words appears, ignore this section and behave normally — never force a mode the user did not ask for.
 
-### First-run promise (act on this the FIRST time, before anything else)
+### First-run onboarding (one-time, trigger-driven — runs in full when the user asks to start)
 
-The first time you work with this user after the workspace is installed — on your very first reply, proactively — run the full onboarding script below. Do not wait to be asked. This is a four-step script (install -> scan -> profile + pain points -> harvest), and you run it as a guided conversation, one step at a time, stopping for the user wherever it says to stop.
+This one-time onboarding is SEPARATE from the day-to-day coaching restraint above: that restraint governs recurring, per-turn nudges, while this is a single guided welcome that runs once, right after install. Running it once does NOT count as over-prompting.
+
+Reliable trigger: the `ai-collab first-run` command tells the user to send you one line — "Walk me through the ai-collab first run". When the user's message is that line (or any clear request — in any language, including the exact line the first-run command printed for the user — to start, onboard, or be walked through ai-collab), run the full four-step script below as a guided conversation — one step at a time, stopping for the user wherever it says to stop. Because that is a direct user request, it overrides the restraint above.
+
+If the user did NOT send a clear start request but their message is a question ABOUT ai-collab itself (e.g. "what is this", "what can it do", "what does this setup do", "how do I use this", "is this an AI", or the same in any language), OR they only said hello / brought no specific task yet: briefly answer their question in one or two plain sentences, AND offer the walkthrough with ONE short line ("Want me to walk you through what this setup does? Just say the word.") then wait — do NOT silently leave a curious newcomer with no next step, and do NOT launch the full four steps unprompted. Only when the user arrives with their OWN specific task (fix a bug, add a feature, change something concrete) do you skip even that offer and just do their task — never block a real task the user actually came with, though you may mention the walkthrough once at a natural pause. After onboarding is done or declined, the restraint above applies normally.
 
 **HARD RULE throughout — PLAIN LANGUAGE.** Never hand the user a technical term. Translate every task title into everyday words in your head before you say it: "auth" -> "login stuff", "payment" -> "money / checkout", "refactor" -> "tidying up the code", "API" -> "the connection between two things". Even a very technical title gets translated first. The whole script is spoken in the user's own language and stays plain — a person who has never written code should follow every sentence.
 
 #### Step 0 — Installed (show the canonical intro VERBATIM)
 
-Run `ai-collab welcome` (before publish: `node bin/ai-collab.js welcome`) and show its output VERBATIM. Do NOT re-summarize or paraphrase it — the CLI hard-prints the canonical intro (the six layers, the keyword modes, the honest privacy line, the closing question) so it always lands in full instead of being garbled by a re-write. Print it as-is, then STOP and let the user answer the closing question.
+Run `ai-collab welcome` and show its output VERBATIM. Do NOT re-summarize or paraphrase it — the CLI hard-prints the canonical intro (the six layers, the keyword modes, the honest privacy line, the closing question) so it always lands in full instead of being garbled by a re-write. Print it as-is, then STOP and let the user answer the closing question.
 
 #### Step 1 — Scan (only after they say go)
 
@@ -76,7 +80,7 @@ When they say to scan ("scan" / "go" / "just the X project" / etc.): first state
 
 Honesty about the scan — you MUST say this before scanning, it is the whole point: the scan is done by YOU, the cloud AI they already use, so the content passes through your provider's servers like any normal chat. Say plainly: this is NOT "zero data leaves your machine" — any tool claiming "absolutely no leak" is bluffing. But it is no more exposure than normally talking to you. The ai-collab tool itself sends nothing to third parties. They can narrow the scope or decline. Default scope: only the currently active project, nothing wider unless they ask.
 
-Then run `ai-collab bootstrap --yes` (before publish: `node bin/ai-collab.js bootstrap --yes`) for the DETERMINISTIC facts: which "done"s lack evidence (VERIFY), what is in flight (RESUME), profile clues, high-risk role signals, harvestable lessons. Everything you say from here on is built on these scanned facts plus the conversation you are having now — never on a guess.
+Then run `ai-collab bootstrap --yes` for the DETERMINISTIC facts: which "done"s lack evidence (VERIFY), what is in flight (RESUME), profile clues, high-risk role signals, harvestable lessons. Everything you say from here on is built on these scanned facts plus the conversation you are having now — never on a guess.
 
 #### Step 2 — Profile read + collaboration advice + CONFIRM (do this first, one block, then WAIT)
 

package/.aict/cookbook/README.md

@@ -1,6 +1,6 @@
 # Cookbook
 
-Do-it recipes for running the AI Collaboration Open System. Each recipe is a full configuration: when to use it, prerequisites, steps, a copy-paste block you can actually run, expected output, failure handling, a privacy note, and a next step. The walkthroughs are operation cards ("press these in this order"); these recipes explain why each step exists and how to adapt it to your own task.
+Do-it recipes for running DoneTrace. Each recipe is a full configuration: when to use it, prerequisites, steps, a copy-paste block you can actually run, expected output, failure handling, a privacy note, and a next step. The walkthroughs are operation cards ("press these in this order"); these recipes explain why each step exists and how to adapt it to your own task.
 
 - `run-a-first-loop.md`: run one complete collaboration loop end to end on your own real task; the prepared synthetic case is an optional "watch the flow first" track.
 - `connect-a-tool.md`: wire any AI tool (general chat AI, coding assistant, command-line AI) to the shared contract by copying files into its instruction slot.

package/.aict/mechanisms/README.md

@@ -1,6 +1,6 @@
 # Mechanisms
 
-The reusable collaboration moves of the AI Collaboration Open System. Each one is a local-first, public-safe Markdown package you can copy-paste into any AI tool. A mechanism is a self-contained directory with five files:
+The reusable collaboration moves of DoneTrace. Each one is a local-first, public-safe Markdown package you can copy-paste into any AI tool. A mechanism is a self-contained directory with five files:
 
 - `README.md` — what it is, when to use it, and when not to.
 - `PROMPT.md` — the copy-paste prompt that runs it.

package/.aict/mechanisms/anti-drift-partner/EXAMPLE.synthetic.md

@@ -1,6 +1,6 @@
 # Anti-Drift Partner Synthetic Example
 
-This is a public-safe synthetic example for the AI Collaboration Open System. It is local-first and contains no private account, customer, route, hook, or conversation material.
+This is a public-safe synthetic example for DoneTrace. It is local-first and contains no private account, customer, route, hook, or conversation material.
 
 ## Synthetic example
 

package/.aict/mechanisms/anti-drift-partner/FAILURE_MODES.md

@@ -1,6 +1,6 @@
 # Anti-Drift Partner Failure Modes
 
-AI Collaboration Open System failure checklist. Use it in a local-first workflow before trusting a mechanism run, and rewrite any public example into public-safe language.
+DoneTrace failure checklist. Use it in a local-first workflow before trusting a mechanism run, and rewrite any public example into public-safe language.
 
 ## Failure modes
 

package/.aict/mechanisms/anti-drift-partner/PROMPT.md

@@ -1,6 +1,6 @@
 # Anti-Drift Partner Prompt
 
-This prompt belongs to the AI Collaboration Open System. Use it in a local-first workflow with public-safe or redacted material.
+This prompt belongs to DoneTrace. Use it in a local-first workflow with public-safe or redacted material.
 
 ## Purpose
 
@@ -9,7 +9,7 @@ Run a long thinking conversation with an AI that pushes back instead of agreeing
 ## Copy-paste prompt
 
 ```text
-Use the Anti-Drift Partner mechanism from my local AI Collaboration Open System workspace.
+Use the Anti-Drift Partner mechanism from my local DoneTrace workspace.
 
 Purpose:
 Run a long thinking conversation with an AI that pushes back instead of agreeing, so it surfaces the blind spots you cannot see from where you stand rather than fluently confirming whatever you already believe. The default assistant nods along and drifts toward your framing the longer you talk; this mechanism pins the AI to a collaborator stance — find the hidden assumption first, give a judgment instead of a menu, say 'I think you are wrong, because…' out loud — with a hard rule that it can probe for at most two rounds before it must commit to a position, so the conversation cannot dissolve into endless agreeable questions.

package/.aict/mechanisms/anti-drift-partner/README.md

@@ -1,6 +1,6 @@
 # Anti-Drift Partner
 
-Part of the AI Collaboration Open System. This is a local-first, public-safe mechanism package you can copy into Claude Code, Codex, Cursor, Cline, Windsurf, or Copilot.
+Part of DoneTrace. This is a local-first, public-safe mechanism package you can copy into Claude Code, Codex, Cursor, Cline, Windsurf, or Copilot.
 
 ## Purpose
 

package/.aict/mechanisms/anti-drift-partner/TEMPLATE.md

@@ -1,6 +1,6 @@
 # Anti-Drift Partner Template
 
-AI Collaboration Open System mechanism card. Fill this in a local-first workflow with public-safe or redacted material.
+DoneTrace mechanism card. Fill this in a local-first workflow with public-safe or redacted material.
 
 ## Purpose
 

package/.aict/mechanisms/blind-spot-scan/EXAMPLE.synthetic.md

@@ -1,6 +1,6 @@
 # Blind-Spot Scan Synthetic Example
 
-This is a public-safe synthetic example for the AI Collaboration Open System. It is local-first and contains no private account, customer, route, hook, or conversation material.
+This is a public-safe synthetic example for DoneTrace. It is local-first and contains no private account, customer, route, hook, or conversation material.
 
 ## Synthetic example
 

package/.aict/mechanisms/blind-spot-scan/FAILURE_MODES.md

@@ -1,6 +1,6 @@
 # Blind-Spot Scan Failure Modes
 
-AI Collaboration Open System failure checklist. Use it in a local-first workflow before trusting a mechanism run, and rewrite any public example into public-safe language.
+DoneTrace failure checklist. Use it in a local-first workflow before trusting a mechanism run, and rewrite any public example into public-safe language.
 
 ## Failure modes
 

package/.aict/mechanisms/blind-spot-scan/PROMPT.md

@@ -1,6 +1,6 @@
 # Blind-Spot Scan Prompt
 
-This prompt belongs to the AI Collaboration Open System. Use it in a local-first workflow with public-safe or redacted material.
+This prompt belongs to DoneTrace. Use it in a local-first workflow with public-safe or redacted material.
 
 ## Purpose
 
@@ -9,7 +9,7 @@ Surface the dead angles you cannot see from your own seat by borrowing an outsid
 ## Copy-paste prompt
 
 ```text
-Use the Blind-Spot Scan mechanism from my local AI Collaboration Open System workspace.
+Use the Blind-Spot Scan mechanism from my local DoneTrace workspace.
 
 Purpose:
 Surface the dead angles you cannot see from your own seat by borrowing an outside viewpoint and re-reading the discussion through it, instead of stress-testing your own logic from the inside. Your own position has a fixed line of sight: the assumptions that feel obvious, the stakeholders you have stopped picturing, the failure that is invisible precisely because it sits where you are standing. This mechanism deliberately swaps the eyes — a customer, a competitor, a domain expert, an opponent, the version of you three years out — and asks what THAT viewpoint would notice that you did not, then hands back a short list of concrete blind spots plus the one counter-question most worth sitting with.

package/.aict/mechanisms/blind-spot-scan/README.md

@@ -1,6 +1,6 @@
 # Blind-Spot Scan
 
-Part of the AI Collaboration Open System. This is a local-first, public-safe mechanism package you can copy into Claude Code, Codex, Cursor, Cline, Windsurf, or Copilot.
+Part of DoneTrace. This is a local-first, public-safe mechanism package you can copy into Claude Code, Codex, Cursor, Cline, Windsurf, or Copilot.
 
 ## Purpose
 

package/.aict/mechanisms/blind-spot-scan/TEMPLATE.md

@@ -1,6 +1,6 @@
 # Blind-Spot Scan Template
 
-AI Collaboration Open System mechanism card. Fill this in a local-first workflow with public-safe or redacted material.
+DoneTrace mechanism card. Fill this in a local-first workflow with public-safe or redacted material.
 
 ## Purpose
 

package/.aict/mechanisms/collaboration-coach/EXAMPLE.synthetic.md

@@ -1,6 +1,6 @@
 # Collaboration Coach Synthetic Example
 
-This is a public-safe synthetic example for the AI Collaboration Open System. It is local-first and contains no private account, customer, route, hook, or conversation material.
+This is a public-safe synthetic example for DoneTrace. It is local-first and contains no private account, customer, route, hook, or conversation material.
 
 ## Synthetic example
 
@@ -10,8 +10,8 @@ A synthetic execution session reaches a 'done, implemented and tested' claim. At
 
 A solo user is working in one AI tool on a small synthetic feature. The coach runs at standard. The session passes through several collaboration moments; this shows the coach firing at the completion-claim node, once, with a concrete next step.
 
-### First-run: act proactively the first time
-"You just installed a collaboration discipline — before I say 'done' I'll show evidence, when I'm unsure I'll pull in a second AI, you won't re-explain when you switch tools, and I'll help you save what's worth keeping. Want me to take 30 seconds and look at a few of your recent tasks to show you what this changes?" Then it offers a scan, respects yes / narrow / no, and gets to work; it does not repeat this.
+### First-run: one-time onboarding, trigger-driven
+Earlier this session the user sent the trigger line first-run printed ("Walk me through the ai-collab first run."), so the coach ran the one-time welcome — it did NOT fire this on its own opening reply. "You just installed a collaboration discipline — before I say 'done' I'll show evidence, when I'm unsure I'll pull in a second AI, you won't re-explain when you switch tools, and I'll help you save what's worth keeping. Want me to take 30 seconds and look at a few of your recent tasks to show you what this changes?" Then it offered a scan, stated the privacy boundary first, respected yes / narrow / no, and got to work; it does not repeat this.
 
 ### Firing node and signal
 Node 3, completion claim. The execution assistant just returned: "Done. I implemented the new sort option and added a test; everything passes." That 'done / everything passes' phrasing is the signal.

package/.aict/mechanisms/collaboration-coach/FAILURE_MODES.md

@@ -1,6 +1,6 @@
 # Collaboration Coach Failure Modes
 
-AI Collaboration Open System failure checklist. Use it in a local-first workflow before trusting a mechanism run, and rewrite any public example into public-safe language.
+DoneTrace failure checklist. Use it in a local-first workflow before trusting a mechanism run, and rewrite any public example into public-safe language.
 
 ## Failure modes
 

package/.aict/mechanisms/collaboration-coach/PROMPT.md

@@ -1,6 +1,6 @@
 # Collaboration Coach Prompt
 
-This prompt belongs to the AI Collaboration Open System. Use it in a local-first workflow with public-safe or redacted material.
+This prompt belongs to DoneTrace. Use it in a local-first workflow with public-safe or redacted material.
 
 ## Purpose
 
@@ -9,7 +9,7 @@ Make the assistant proactively remind the user of the matching collaboration ste
 ## Copy-paste prompt
 
 ```text
-Use the Collaboration Coach mechanism from my local AI Collaboration Open System workspace.
+Use the Collaboration Coach mechanism from my local DoneTrace workspace.
 
 Purpose:
 Make the assistant proactively remind the user of the matching collaboration step at six recurring moments — define done, review a completion claim, hand off, harvest, update the profile — instead of waiting to be asked, so the workspace teaches itself while the user works rather than sitting unused behind a manual. The hard constraint is restraint: prompt at key moments only, once per moment, never every turn, because over-prompting is the fastest way to get the whole system uninstalled.
@@ -24,7 +24,7 @@ Input:
 [paste redacted task material, context package, and acceptance card here]
 
 Process:
-1. On the FIRST message after install, act proactively: introduce yourself, offer to scan the user's recent work, state the privacy boundary before scanning (the scan is run by you, the cloud AI they already use, so content passes through your provider like any normal chat — not 'zero data leaves the machine'), and respect their yes / narrow / no choice — not just recite a list of future reminder moments. Then say reminders are restrained by default and switchable with `coach: light` / `coach: strict`. Do this once, then stop.
+1. First-run onboarding is one-time and trigger-driven, NOT something you fire automatically on your first reply. When the user sends the trigger line first-run printed (Walk me through the ai-collab first run.) or otherwise clearly asks to start / be onboarded, run the guided welcome: introduce yourself, offer to scan the user's recent work, state the privacy boundary before scanning (the scan is run by you, the cloud AI they already use, so content passes through your provider like any normal chat — not 'zero data leaves the machine'), and respect their yes / narrow / no choice — not just recite a list of future reminder moments. Then say reminders are restrained by default and switchable with `coach: light` / `coach: strict`. Do this once, then stop.
 2. Map each firing moment to its node and reminder. 1 Task start -> set a context boundary and acceptance before building. 2 Pre-execution -> define the acceptance card first. 3 Completion claim -> run a guard review before trusting it. 4 Long thread / tool switch -> generate a handoff instead of relying on chat memory. 5 Reusable insight -> harvest it into a card. 6 Repeated preference -> offer it as a profile-update candidate.
 3. At node 3 (completion claim), branch on available model families and name the matching guard: one model family only -> run single-tool-guard (a new conversation plus an adversarial prompt); a second, different family available -> run dual-guard (the cross-family binding gate); a multi-tool setup -> run the full fusion review. Do not silently skip the branch and just say 'looks good'.
 4. Apply the restraint tier before speaking. Light: only fire at nodes 3 and 4. Standard (default): fire at nodes 1, 3, 4, 6 — fold node 2 into the task-start reminder (skip it entirely if node 1 already landed an acceptance card) and node 5 into a natural pause, not a separate interruption; count "once per moment" by task phase, not by node, so the opening of one task is a single moment even if nodes 1 and 2 both trip — never stack reminders on back-to-back turns at a task's start, and never re-raise a reminder already acted on. Strict: fire at all six every time they trip. If a tier would make you repeat a just-given reminder, stay silent instead.
@@ -32,7 +32,7 @@ Process:
 6. Honor a restraint switch immediately. When the user says `coach: light` / `coach: standard` / `coach: strict`, change tier for the rest of the session without arguing, and confirm the new tier in a few words.
 
 Output shape:
-- First-run promise: on the first reply, the assistant proactively introduces itself, offers to scan the user's recent work, states the privacy boundary before scanning, and respects the user's yes / narrow / no choice — rather than passively reciting a list of future reminder moments.
+- First-run promise: one-time and trigger-driven (when the user sends the first-run trigger line or asks to start), the assistant introduces itself, offers to scan the user's recent work, states the privacy boundary before scanning, and respects the user's yes / narrow / no choice — rather than firing automatically on the first reply or passively reciting a list of future reminder moments.
 - Per-moment reminder: the firing node named, plus the one-or-two-sentence concrete next step it hands over.
 - Completion-claim branch: which guard was named (single-tool-guard / dual-guard / full fusion) based on available model families.
 - Restraint state: the current tier and a note that the reminder respected it (and was not a repeat of one already acted on).
@@ -47,7 +47,7 @@ Return:
 - Next action
 
 Pass bar (do not pass unless all hold):
-- On the first reply the assistant acted proactively: it introduced itself, offered to scan recent work, stated the privacy boundary before scanning, respected the user's yes / narrow / no choice, and did not repeat the intro afterward.
+- When the user sent the first-run trigger line (or otherwise asked to start), the assistant ran the one-time onboarding: it introduced itself, offered to scan recent work, stated the privacy boundary before scanning, respected the user's yes / narrow / no choice, and did not repeat the intro afterward — and it did not fire this onboarding automatically on an unrelated first reply.
 - Each reminder fired at the right node with a concrete next step the user can act on in one move.
 - The completion-claim node named the correct guard depth for the number of model families available.
 - Restraint held: standard by default, once per moment, no reminder the user already acted on was re-raised, and a `coach:` switch was honored immediately.

package/.aict/mechanisms/collaboration-coach/README.md

@@ -1,6 +1,6 @@
 # Collaboration Coach
 
-Part of the AI Collaboration Open System. This is a local-first, public-safe mechanism package you can copy into Claude Code, Codex, Cursor, Cline, Windsurf, or Copilot.
+Part of DoneTrace. This is a local-first, public-safe mechanism package you can copy into Claude Code, Codex, Cursor, Cline, Windsurf, or Copilot.
 
 ## Purpose
 
@@ -29,7 +29,7 @@ The live collaboration moment (which of the six nodes is firing, and the signal
 
 ## Process
 
-1. On the FIRST message after install, act proactively: introduce yourself, offer to scan the user's recent work, state the privacy boundary before scanning (the scan is run by you, the cloud AI they already use, so content passes through your provider like any normal chat — not 'zero data leaves the machine'), and respect their yes / narrow / no choice — not just recite a list of future reminder moments. Then say reminders are restrained by default and switchable with `coach: light` / `coach: strict`. Do this once, then stop.
+1. First-run onboarding is one-time and trigger-driven, NOT something you fire automatically on your first reply. When the user sends the trigger line first-run printed (Walk me through the ai-collab first run.) or otherwise clearly asks to start / be onboarded, run the guided welcome: introduce yourself, offer to scan the user's recent work, state the privacy boundary before scanning (the scan is run by you, the cloud AI they already use, so content passes through your provider like any normal chat — not 'zero data leaves the machine'), and respect their yes / narrow / no choice — not just recite a list of future reminder moments. Then say reminders are restrained by default and switchable with `coach: light` / `coach: strict`. Do this once, then stop.
 2. Map each firing moment to its node and reminder. 1 Task start -> set a context boundary and acceptance before building. 2 Pre-execution -> define the acceptance card first. 3 Completion claim -> run a guard review before trusting it. 4 Long thread / tool switch -> generate a handoff instead of relying on chat memory. 5 Reusable insight -> harvest it into a card. 6 Repeated preference -> offer it as a profile-update candidate.
 3. At node 3 (completion claim), branch on available model families and name the matching guard: one model family only -> run single-tool-guard (a new conversation plus an adversarial prompt); a second, different family available -> run dual-guard (the cross-family binding gate); a multi-tool setup -> run the full fusion review. Do not silently skip the branch and just say 'looks good'.
 4. Apply the restraint tier before speaking. Light: only fire at nodes 3 and 4. Standard (default): fire at nodes 1, 3, 4, 6 — fold node 2 into the task-start reminder (skip it entirely if node 1 already landed an acceptance card) and node 5 into a natural pause, not a separate interruption; count "once per moment" by task phase, not by node, so the opening of one task is a single moment even if nodes 1 and 2 both trip — never stack reminders on back-to-back turns at a task's start, and never re-raise a reminder already acted on. Strict: fire at all six every time they trip. If a tier would make you repeat a just-given reminder, stay silent instead.
@@ -38,7 +38,7 @@ The live collaboration moment (which of the six nodes is firing, and the signal
 
 ## Output shape
 
-- First-run promise: on the first reply, the assistant proactively introduces itself, offers to scan the user's recent work, states the privacy boundary before scanning, and respects the user's yes / narrow / no choice — rather than passively reciting a list of future reminder moments.
+- First-run promise: one-time and trigger-driven (when the user sends the first-run trigger line or asks to start), the assistant introduces itself, offers to scan the user's recent work, states the privacy boundary before scanning, and respects the user's yes / narrow / no choice — rather than firing automatically on the first reply or passively reciting a list of future reminder moments.
 - Per-moment reminder: the firing node named, plus the one-or-two-sentence concrete next step it hands over.
 - Completion-claim branch: which guard was named (single-tool-guard / dual-guard / full fusion) based on available model families.
 - Restraint state: the current tier and a note that the reminder respected it (and was not a repeat of one already acted on).
@@ -47,7 +47,7 @@ The live collaboration moment (which of the six nodes is firing, and the signal
 
 ## Pass bar (what counts as done / safe to trust)
 
-- On the first reply the assistant acted proactively: it introduced itself, offered to scan recent work, stated the privacy boundary before scanning, respected the user's yes / narrow / no choice, and did not repeat the intro afterward.
+- When the user sent the first-run trigger line (or otherwise asked to start), the assistant ran the one-time onboarding: it introduced itself, offered to scan recent work, stated the privacy boundary before scanning, respected the user's yes / narrow / no choice, and did not repeat the intro afterward — and it did not fire this onboarding automatically on an unrelated first reply.
 - Each reminder fired at the right node with a concrete next step the user can act on in one move.
 - The completion-claim node named the correct guard depth for the number of model families available.
 - Restraint held: standard by default, once per moment, no reminder the user already acted on was re-raised, and a `coach:` switch was honored immediately.

package/.aict/mechanisms/collaboration-coach/TEMPLATE.md

@@ -1,6 +1,6 @@
 # Collaboration Coach Template
 
-AI Collaboration Open System mechanism card. Fill this in a local-first workflow with public-safe or redacted material.
+DoneTrace mechanism card. Fill this in a local-first workflow with public-safe or redacted material.
 
 ## Purpose
 
@@ -8,7 +8,7 @@ Make the assistant proactively remind the user of the matching collaboration ste
 
 ## Template
 
-### First-run promise (first reply, proactive — introduce + offer to scan + state the privacy boundary + respect yes / narrow / no):
+### First-run promise (one-time, trigger-driven — on the first-run trigger line / a start request, NOT auto on the first reply: introduce + offer to scan + state the privacy boundary + respect yes / narrow / no):
 
 
 ### Firing node (1-6) and the signal that tripped it:
@@ -35,7 +35,7 @@ Make the assistant proactively remind the user of the matching collaboration ste
 
 ## Pass bar (tick before you trust the result)
 
-- On the first reply the assistant acted proactively: it introduced itself, offered to scan recent work, stated the privacy boundary before scanning, respected the user's yes / narrow / no choice, and did not repeat the intro afterward.
+- When the user sent the first-run trigger line (or otherwise asked to start), the assistant ran the one-time onboarding: it introduced itself, offered to scan recent work, stated the privacy boundary before scanning, respected the user's yes / narrow / no choice, and did not repeat the intro afterward — and it did not fire this onboarding automatically on an unrelated first reply.
 - Each reminder fired at the right node with a concrete next step the user can act on in one move.
 - The completion-claim node named the correct guard depth for the number of model families available.
 - Restraint held: standard by default, once per moment, no reminder the user already acted on was re-raised, and a `coach:` switch was honored immediately.

package/.aict/mechanisms/do-not-handle-yet/EXAMPLE.synthetic.md

@@ -1,6 +1,6 @@
 # Do Not Handle Yet Synthetic Example
 
-This is a public-safe synthetic example for the AI Collaboration Open System. It is local-first and contains no private account, customer, route, hook, or conversation material.
+This is a public-safe synthetic example for DoneTrace. It is local-first and contains no private account, customer, route, hook, or conversation material.
 
 ## Synthetic example
 

package/.aict/mechanisms/do-not-handle-yet/FAILURE_MODES.md

@@ -1,6 +1,6 @@
 # Do Not Handle Yet Failure Modes
 
-AI Collaboration Open System failure checklist. Use it in a local-first workflow before trusting a mechanism run, and rewrite any public example into public-safe language.
+DoneTrace failure checklist. Use it in a local-first workflow before trusting a mechanism run, and rewrite any public example into public-safe language.
 
 ## Failure modes
 

package/.aict/mechanisms/do-not-handle-yet/PROMPT.md

@@ -1,6 +1,6 @@
 # Do Not Handle Yet Prompt
 
-This prompt belongs to the AI Collaboration Open System. Use it in a local-first workflow with public-safe or redacted material.
+This prompt belongs to DoneTrace. Use it in a local-first workflow with public-safe or redacted material.
 
 ## Purpose
 
@@ -9,7 +9,7 @@ Protect the main line by explicitly parking tempting but lower-priority work.
 ## Copy-paste prompt
 
 ```text
-Use the Do Not Handle Yet mechanism from my local AI Collaboration Open System workspace.
+Use the Do Not Handle Yet mechanism from my local DoneTrace workspace.
 
 Purpose:
 Protect the main line by explicitly parking tempting but lower-priority work.

package/.aict/mechanisms/do-not-handle-yet/README.md

@@ -1,6 +1,6 @@
 # Do Not Handle Yet
 
-Part of the AI Collaboration Open System. This is a local-first, public-safe mechanism package you can copy into Claude Code, Codex, Cursor, Cline, Windsurf, or Copilot.
+Part of DoneTrace. This is a local-first, public-safe mechanism package you can copy into Claude Code, Codex, Cursor, Cline, Windsurf, or Copilot.
 
 ## Purpose
 

package/.aict/mechanisms/do-not-handle-yet/TEMPLATE.md

@@ -1,6 +1,6 @@
 # Do Not Handle Yet Template
 
-AI Collaboration Open System mechanism card. Fill this in a local-first workflow with public-safe or redacted material.
+DoneTrace mechanism card. Fill this in a local-first workflow with public-safe or redacted material.
 
 ## Purpose
 

package/.aict/mechanisms/dual-guard/EXAMPLE.synthetic.md

@@ -1,6 +1,6 @@
 # Dual Guard Synthetic Example
 
-This is a public-safe synthetic example for the AI Collaboration Open System. It is local-first and contains no private account, customer, route, hook, or conversation material.
+This is a public-safe synthetic example for DoneTrace. It is local-first and contains no private account, customer, route, hook, or conversation material.
 
 ## Synthetic example
 

package/.aict/mechanisms/dual-guard/FAILURE_MODES.md

@@ -1,6 +1,6 @@
 # Dual Guard Failure Modes
 
-AI Collaboration Open System failure checklist. Use it in a local-first workflow before trusting a mechanism run, and rewrite any public example into public-safe language.
+DoneTrace failure checklist. Use it in a local-first workflow before trusting a mechanism run, and rewrite any public example into public-safe language.
 
 ## Failure modes
 

package/.aict/mechanisms/dual-guard/PROMPT.md

@@ -1,6 +1,6 @@
 # Dual Guard Prompt
 
-This prompt belongs to the AI Collaboration Open System. Use it in a local-first workflow with public-safe or redacted material.
+This prompt belongs to DoneTrace. Use it in a local-first workflow with public-safe or redacted material.
 
 ## Purpose
 
@@ -11,7 +11,7 @@ Don't have a second model family yet? See the cookbook recipe `../../cookbook/br
 ## Copy-paste prompt
 
 ```text
-Use the Dual Guard mechanism from my local AI Collaboration Open System workspace.
+Use the Dual Guard mechanism from my local DoneTrace workspace.
 
 Purpose:
 Cancel shared blind spots with structure instead of a stronger model: a guard from a different model family is the binding gate, and a same-family guard is a non-binding reference, so a fluent answer cannot be trusted just because it reads well.

package/.aict/mechanisms/dual-guard/README.md

@@ -1,6 +1,6 @@
 # Dual Guard
 
-Part of the AI Collaboration Open System. This is a local-first, public-safe mechanism package you can copy into Claude Code, Codex, Cursor, Cline, Windsurf, or Copilot.
+Part of DoneTrace. This is a local-first, public-safe mechanism package you can copy into Claude Code, Codex, Cursor, Cline, Windsurf, or Copilot.
 
 ## Purpose
 

package/.aict/mechanisms/dual-guard/TEMPLATE.md

@@ -1,6 +1,6 @@
 # Dual Guard Template
 
-AI Collaboration Open System mechanism card. Fill this in a local-first workflow with public-safe or redacted material.
+DoneTrace mechanism card. Fill this in a local-first workflow with public-safe or redacted material.
 
 ## Purpose
 

package/.aict/mechanisms/feedback-absorption-ledger/EXAMPLE.synthetic.md

@@ -1,6 +1,6 @@
 # Feedback Absorption Ledger Synthetic Example
 
-This is a public-safe synthetic example for the AI Collaboration Open System. It is local-first and contains no private account, customer, route, hook, or conversation material.
+This is a public-safe synthetic example for DoneTrace. It is local-first and contains no private account, customer, route, hook, or conversation material.
 
 ## Synthetic example
 

package/.aict/mechanisms/feedback-absorption-ledger/FAILURE_MODES.md

@@ -1,6 +1,6 @@
 # Feedback Absorption Ledger Failure Modes
 
-AI Collaboration Open System failure checklist. Use it in a local-first workflow before trusting a mechanism run, and rewrite any public example into public-safe language.
+DoneTrace failure checklist. Use it in a local-first workflow before trusting a mechanism run, and rewrite any public example into public-safe language.
 
 ## Failure modes
 

package/.aict/mechanisms/feedback-absorption-ledger/PROMPT.md

@@ -1,6 +1,6 @@
 # Feedback Absorption Ledger Prompt
 
-This prompt belongs to the AI Collaboration Open System. Use it in a local-first workflow with public-safe or redacted material.
+This prompt belongs to DoneTrace. Use it in a local-first workflow with public-safe or redacted material.
 
 ## Purpose
 
@@ -9,7 +9,7 @@ Keep independent judgment alive when you are synthesizing feedback from several
 ## Copy-paste prompt
 
 ```text
-Use the Feedback Absorption Ledger mechanism from my local AI Collaboration Open System workspace.
+Use the Feedback Absorption Ledger mechanism from my local DoneTrace workspace.
 
 Purpose:
 Keep independent judgment alive when you are synthesizing feedback from several sources by scoring each incoming point across five tiers instead of silently rubber-stamping all of it: absorb fully, absorb and refine, absorb with a boundary, partly absorb, or reject with a reason. The trap this defends against is the controller who collects three reviews and quietly accepts everything, becoming a courier for other people's opinions; the equal-and-opposite trap is reflexively rejecting things to look independent. The ledger forces a per-item decision with a stated reason, and treats the absorb/reject ratio as an OUTCOME of honest judgment, never a target to hit.

package/.aict/mechanisms/feedback-absorption-ledger/README.md

@@ -1,6 +1,6 @@
 # Feedback Absorption Ledger
 
-Part of the AI Collaboration Open System. This is a local-first, public-safe mechanism package you can copy into Claude Code, Codex, Cursor, Cline, Windsurf, or Copilot.
+Part of DoneTrace. This is a local-first, public-safe mechanism package you can copy into Claude Code, Codex, Cursor, Cline, Windsurf, or Copilot.
 
 ## Purpose
 

package/.aict/mechanisms/feedback-absorption-ledger/TEMPLATE.md

@@ -1,6 +1,6 @@
 # Feedback Absorption Ledger Template
 
-AI Collaboration Open System mechanism card. Fill this in a local-first workflow with public-safe or redacted material.
+DoneTrace mechanism card. Fill this in a local-first workflow with public-safe or redacted material.
 
 ## Purpose
 

package/.aict/mechanisms/half-product-review/EXAMPLE.synthetic.md

@@ -1,6 +1,6 @@
 # Half-Product Review Synthetic Example
 
-This is a public-safe synthetic example for the AI Collaboration Open System. It is local-first and contains no private account, customer, route, hook, or conversation material.
+This is a public-safe synthetic example for DoneTrace. It is local-first and contains no private account, customer, route, hook, or conversation material.
 
 ## Synthetic example
 

package/.aict/mechanisms/half-product-review/FAILURE_MODES.md

@@ -1,6 +1,6 @@
 # Half-Product Review Failure Modes
 
-AI Collaboration Open System failure checklist. Use it in a local-first workflow before trusting a mechanism run, and rewrite any public example into public-safe language.
+DoneTrace failure checklist. Use it in a local-first workflow before trusting a mechanism run, and rewrite any public example into public-safe language.
 
 ## Failure modes
 

package/.aict/mechanisms/half-product-review/PROMPT.md

@@ -1,6 +1,6 @@
 # Half-Product Review Prompt
 
-This prompt belongs to the AI Collaboration Open System. Use it in a local-first workflow with public-safe or redacted material.
+This prompt belongs to DoneTrace. Use it in a local-first workflow with public-safe or redacted material.
 
 ## Purpose
 
@@ -9,7 +9,7 @@ Block confident claims when the project has docs, demos, or architecture but no
 ## Copy-paste prompt
 
 ```text
-Use the Half-Product Review mechanism from my local AI Collaboration Open System workspace.
+Use the Half-Product Review mechanism from my local DoneTrace workspace.
 
 Purpose:
 Block confident claims when the project has docs, demos, or architecture but no runnable first experience.

package/.aict/mechanisms/half-product-review/README.md

@@ -1,6 +1,6 @@
 # Half-Product Review
 
-Part of the AI Collaboration Open System. This is a local-first, public-safe mechanism package you can copy into Claude Code, Codex, Cursor, Cline, Windsurf, or Copilot.
+Part of DoneTrace. This is a local-first, public-safe mechanism package you can copy into Claude Code, Codex, Cursor, Cline, Windsurf, or Copilot.
 
 ## Purpose
 

package/.aict/mechanisms/half-product-review/TEMPLATE.md

@@ -1,6 +1,6 @@
 # Half-Product Review Template
 
-AI Collaboration Open System mechanism card. Fill this in a local-first workflow with public-safe or redacted material.
+DoneTrace mechanism card. Fill this in a local-first workflow with public-safe or redacted material.
 
 ## Purpose
 

package/.aict/mechanisms/handoff-abc/EXAMPLE.synthetic.md

@@ -1,6 +1,6 @@
 # Handoff A/B/C Synthetic Example
 
-This is a public-safe synthetic example for the AI Collaboration Open System. It is local-first and contains no private account, customer, route, hook, or conversation material.
+This is a public-safe synthetic example for DoneTrace. It is local-first and contains no private account, customer, route, hook, or conversation material.
 
 ## Synthetic example
 

package/.aict/mechanisms/handoff-abc/FAILURE_MODES.md

@@ -1,6 +1,6 @@
 # Handoff A/B/C Failure Modes
 
-AI Collaboration Open System failure checklist. Use it in a local-first workflow before trusting a mechanism run, and rewrite any public example into public-safe language.
+DoneTrace failure checklist. Use it in a local-first workflow before trusting a mechanism run, and rewrite any public example into public-safe language.
 
 ## Failure modes
 

package/.aict/mechanisms/handoff-abc/PROMPT.md

@@ -1,6 +1,6 @@
 # Handoff A/B/C Prompt
 
-This prompt belongs to the AI Collaboration Open System. Use it in a local-first workflow with public-safe or redacted material.
+This prompt belongs to DoneTrace. Use it in a local-first workflow with public-safe or redacted material.
 
 ## Purpose
 
@@ -9,7 +9,7 @@ Externalize the current state into a structured handoff packet so ANY AI or sess
 ## Copy-paste prompt
 
 ```text
-Use the Handoff A/B/C mechanism from my local AI Collaboration Open System workspace.
+Use the Handoff A/B/C mechanism from my local DoneTrace workspace.
 
 Purpose:
 Externalize the current state into a structured handoff packet so ANY AI or session can pick up from where the work actually is, instead of the human re-explaining the background every time a tool or session changes. A/B/C are three handoff modes for three situations: A = high-interaction handoff (a human and AI trading turns inside the same tool, lightweight resume); B = programmatic handoff (a clear task an executor picks up and drives to completion on its own); C = delivery overview (a human-facing total account of what one phase produced). Whichever mode, the packet carries the same load-bearing fields so the receiver never starts from zero.

package/.aict/mechanisms/handoff-abc/README.md

@@ -1,6 +1,6 @@
 # Handoff A/B/C
 
-Part of the AI Collaboration Open System. This is a local-first, public-safe mechanism package you can copy into Claude Code, Codex, Cursor, Cline, Windsurf, or Copilot.
+Part of DoneTrace. This is a local-first, public-safe mechanism package you can copy into Claude Code, Codex, Cursor, Cline, Windsurf, or Copilot.
 
 ## Purpose