agent-bios 0.14.0 → 0.16.0

package/compose/domains.json

@@ -10,113 +10,114 @@
     "office-work": "Office artifacts: spreadsheet processing"
   },
   "bullets": [
-    {"anchor": "Prefer concise Korean responses", "tier": "env-personal", "domains": []},
-    {"anchor": "Keep file changes within the requested scope", "tier": "core", "domains": []},
-    {"anchor": "First identify the goal, scope, ambiguities", "tier": "core", "domains": []},
-    {"anchor": "Resolve ambiguity from context when safe", "tier": "core", "domains": []},
-    {"anchor": "For simple requests, choose the most direct", "tier": "core", "domains": []},
-    {"anchor": "For non-trivial requests, compare 2-4 methods", "tier": "core", "domains": []},
-    {"anchor": "Mark one default method", "tier": "core", "domains": []},
-    {"anchor": "Execute the chosen method accurately", "tier": "core", "domains": []},
-    {"anchor": "Return to understanding if a discovery breaks", "tier": "core", "domains": []},
-    {"anchor": "Reconsider the method if the selected approach", "tier": "core", "domains": []},
-    {"anchor": "Log non-blocking discoveries and continue", "tier": "core", "domains": []},
-    {"anchor": "If the same loopback happens twice", "tier": "core", "domains": []},
-    {"anchor": "Compare the result with the selected", "tier": "core", "domains": []},
-    {"anchor": "Ask decision questions in outcome terms", "tier": "core", "domains": []},
-    {"anchor": "When the user may not know the domain", "tier": "core", "domains": []},
-    {"anchor": "Present 2-4 meaningful options", "tier": "core", "domains": []},
-    {"anchor": "For each option, state what changes", "tier": "core", "domains": []},
-    {"anchor": "Translate technical terms into plain consequences", "tier": "core", "domains": []},
-    {"anchor": "Ask for the user's goal or constraint", "tier": "core", "domains": []},
-    {"anchor": "Evaluate user suggestions for goal fit", "tier": "core", "domains": []},
-    {"anchor": "Distinguish implementation feasibility from recommendation", "tier": "core", "domains": []},
-    {"anchor": "Do not default to a restrictive lens", "tier": "core", "domains": []},
-    {"anchor": "Treat user suggestions, inherited premises, prior diagnoses", "tier": "core", "domains": []},
-    {"anchor": "For structured-output, runtime-authority, capability-surface", "tier": "domain", "domains": ["llm-pipeline-dev"]},
-    {"anchor": "Use instructions to describe intended work", "tier": "domain", "domains": ["llm-pipeline-dev"]},
-    {"anchor": "Use the LLM for semantic work", "tier": "domain", "domains": ["llm-pipeline-dev"]},
-    {"anchor": "Use the capability surface for structural constraints", "tier": "domain", "domains": ["llm-pipeline-dev"]},
-    {"anchor": "Enforce constraints through the capability surface", "tier": "domain", "domains": ["llm-pipeline-dev"]},
-    {"anchor": "Use tools/code for deterministic work", "tier": "domain", "domains": ["llm-pipeline-dev"]},
-    {"anchor": "When exactness, freshness, scale, repeatability", "tier": "domain", "domains": ["llm-pipeline-dev"]},
-    {"anchor": "Let the LLM design merge, projection", "tier": "domain", "domains": ["llm-pipeline-dev"]},
-    {"anchor": "For required structured or machine-consumed outputs", "tier": "domain", "domains": ["llm-pipeline-dev"]},
-    {"anchor": "Let tools/code own ids, paths, serialization", "tier": "domain", "domains": ["llm-pipeline-dev"]},
-    {"anchor": "Keep deterministic values out of LLM authority", "tier": "domain", "domains": ["llm-pipeline-dev"]},
-    {"anchor": "For simple stable explanations or planning", "tier": "domain", "domains": ["llm-pipeline-dev"]},
-    {"anchor": "Treat a produced field, flag, signal", "tier": "domain", "domains": ["llm-pipeline-dev"]},
-    {"anchor": "Hard-block only deterministically decidable structural", "tier": "domain", "domains": ["llm-pipeline-dev"]},
-    {"anchor": "Runtime/code may enforce the contract", "tier": "domain", "domains": ["llm-pipeline-dev"]},
-    {"anchor": "When adding, changing, renaming, splitting, or exposing anything lasting or shared", "tier": "domain", "domains": ["builder-base"]},
-    {"anchor": "Before fixing a review finding or test failure", "tier": "domain", "domains": ["builder-base"]},
-    {"anchor": "For `.xlsx` editing, generation, reconciliation", "tier": "domain", "domains": ["office-work"]},
-    {"anchor": "For development work, read and use", "tier": "domain", "domains": ["builder-base"]},
-    {"anchor": "For mock, fixture, fake, stub, simulated-provider", "tier": "domain", "domains": ["builder-base"]},
-    {"anchor": "Own the full lifecycle of what you create", "tier": "domain", "domains": ["builder-base"]},
-    {"anchor": "Land risky or behavior-changing work behind", "tier": "domain", "domains": ["builder-base"]},
-    {"anchor": "For composing a review request, packet", "tier": "domain", "domains": ["builder-base"]},
-    {"anchor": "After every meaningful code, ontology, config", "tier": "domain", "domains": ["builder-base"]},
-    {"anchor": "For choosing verification depth, the per-domain mix, the case space, what makes a completion criterion falsifiable", "tier": "domain", "domains": ["builder-base"]},
-    {"anchor": "Report the checks run, results", "tier": "core", "domains": []},
-    {"anchor": "Trust a green check only when it traversed", "tier": "domain", "domains": ["builder-base"]},
-    {"anchor": "Before comparing two of anything", "tier": "domain", "domains": ["builder-base"]},
-    {"anchor": "For concrete shell/CLI traps", "tier": "domain", "domains": ["builder-base"]},
-    {"anchor": "Ambient state — the active shell", "tier": "domain", "domains": ["builder-base"]},
-    {"anchor": "Before relying on any model id", "tier": "domain", "domains": ["builder-base"]},
-    {"anchor": "Scope destructive actions (kill, rm, force-push", "tier": "domain", "domains": ["builder-base"]},
-    {"anchor": "Never accept secrets through transcript- or history-logged channels", "tier": "core", "domains": []},
-    {"anchor": "When a secret must be supplied", "tier": "domain", "domains": ["builder-base"]},
-    {"anchor": "Treat a coarse runtime signal", "tier": "domain", "domains": ["builder-base"]},
-    {"anchor": "Standing spawn policy: check the spawn gates", "tier": "domain", "domains": ["multi-agent-orchestration"]},
-    {"anchor": "Down-spawns carry a machine-checkable done-when", "tier": "domain", "domains": ["multi-agent-orchestration"]},
-    {"anchor": "For work spanning multiple models or CLI agents", "tier": "domain", "domains": ["multi-agent-orchestration"]},
-    {"anchor": "For composing a prompt, packet, or tool description", "tier": "domain", "domains": ["multi-agent-orchestration"]},
-    {"anchor": "Allocate models by difficulty", "tier": "domain", "domains": ["multi-agent-orchestration"]},
-    {"anchor": "Judge a review by how much independence", "tier": "domain", "domains": ["multi-agent-orchestration"]},
-    {"anchor": "dual-provider frontier design drafts", "tier": "domain", "domains": ["multi-agent-orchestration"]},
-    {"anchor": "Never retry-storm a live rate limit", "tier": "domain", "domains": ["multi-agent-orchestration"]},
-    {"anchor": "On any resumed, cleared, or relocated session", "tier": "domain", "domains": ["multi-agent-orchestration"]},
-    {"anchor": "Keep runtime code, active docs, and execution-facing", "tier": "domain", "domains": ["builder-base"]},
-    {"anchor": "For where a comment, a compatibility note, deprecated behavior, a rejected alternative", "tier": "domain", "domains": ["builder-base"]},
-    {"anchor": "For SVG diagrams, service blueprints", "tier": "domain", "domains": ["visualization-docs"]},
-    {"anchor": "When a concept is easier to understand visually", "tier": "domain", "domains": ["visualization-docs"]},
-    {"anchor": "Use HTML for comparisons, flows, state changes", "tier": "domain", "domains": ["visualization-docs"]},
-    {"anchor": "Keep HTML self-contained, accessible, and minimal", "tier": "domain", "domains": ["visualization-docs"]},
-    {"anchor": "Use plain text when it is clearer", "tier": "domain", "domains": ["visualization-docs"]},
-    {"anchor": "For the detailed `IMPLEMENTATION_MAP.html` construction rules", "tier": "domain", "domains": ["visualization-docs"]},
-    {"anchor": "In repos with implementation code", "tier": "domain", "domains": ["visualization-docs"]},
-    {"anchor": "`learn!` — session learning", "tier": "core", "domains": []}
+    {"anchor": "Prefer concise Korean responses", "tier": "env-personal", "domains": [], "item_id": "rule-001"},
+    {"anchor": "Keep file changes within the requested scope", "tier": "core", "domains": [], "item_id": "rule-002"},
+    {"anchor": "First identify the goal, scope, ambiguities", "tier": "core", "domains": [], "item_id": "rule-003"},
+    {"anchor": "Resolve ambiguity from context when safe", "tier": "core", "domains": [], "item_id": "rule-004"},
+    {"anchor": "For simple requests, choose the most direct", "tier": "core", "domains": [], "item_id": "rule-005"},
+    {"anchor": "For non-trivial requests, compare 2-4 methods", "tier": "core", "domains": [], "item_id": "rule-006"},
+    {"anchor": "Mark one default method", "tier": "core", "domains": [], "item_id": "rule-007"},
+    {"anchor": "Execute the chosen method accurately", "tier": "core", "domains": [], "item_id": "rule-008"},
+    {"anchor": "Return to understanding if a discovery breaks", "tier": "core", "domains": [], "item_id": "rule-009"},
+    {"anchor": "Reconsider the method if the selected approach", "tier": "core", "domains": [], "item_id": "rule-010"},
+    {"anchor": "Log non-blocking discoveries and continue", "tier": "core", "domains": [], "item_id": "rule-011"},
+    {"anchor": "If the same loopback happens twice", "tier": "core", "domains": [], "item_id": "rule-012"},
+    {"anchor": "Compare the result with the selected", "tier": "core", "domains": [], "item_id": "rule-013"},
+    {"anchor": "Ask decision questions in outcome terms", "tier": "core", "domains": [], "item_id": "rule-014"},
+    {"anchor": "When the user may not know the domain", "tier": "core", "domains": [], "item_id": "rule-015"},
+    {"anchor": "Present 2-4 meaningful options", "tier": "core", "domains": [], "item_id": "rule-016"},
+    {"anchor": "For each option, state what changes", "tier": "core", "domains": [], "item_id": "rule-017"},
+    {"anchor": "Translate technical terms into plain consequences", "tier": "core", "domains": [], "item_id": "rule-018"},
+    {"anchor": "Ask for the user's goal or constraint", "tier": "core", "domains": [], "item_id": "rule-019"},
+    {"anchor": "Evaluate user suggestions for goal fit", "tier": "core", "domains": [], "item_id": "rule-020"},
+    {"anchor": "Distinguish implementation feasibility from recommendation", "tier": "core", "domains": [], "item_id": "rule-021"},
+    {"anchor": "Do not default to a restrictive lens", "tier": "core", "domains": [], "item_id": "rule-022"},
+    {"anchor": "Treat user suggestions, inherited premises, prior diagnoses", "tier": "core", "domains": [], "item_id": "rule-023"},
+    {"anchor": "For structured-output, runtime-authority, capability-surface", "tier": "domain", "domains": ["llm-pipeline-dev"], "item_id": "rule-024"},
+    {"anchor": "Use instructions to describe intended work", "tier": "domain", "domains": ["llm-pipeline-dev"], "item_id": "rule-025"},
+    {"anchor": "Use the LLM for semantic work", "tier": "domain", "domains": ["llm-pipeline-dev"], "item_id": "rule-026"},
+    {"anchor": "Use the capability surface for structural constraints", "tier": "domain", "domains": ["llm-pipeline-dev"], "item_id": "rule-027"},
+    {"anchor": "Enforce constraints through the capability surface", "tier": "domain", "domains": ["llm-pipeline-dev"], "item_id": "rule-028"},
+    {"anchor": "Use tools/code for deterministic work", "tier": "domain", "domains": ["llm-pipeline-dev"], "item_id": "rule-029"},
+    {"anchor": "When exactness, freshness, scale, repeatability", "tier": "domain", "domains": ["llm-pipeline-dev"], "item_id": "rule-030"},
+    {"anchor": "Let the LLM design merge, projection", "tier": "domain", "domains": ["llm-pipeline-dev"], "item_id": "rule-031"},
+    {"anchor": "For required structured or machine-consumed outputs", "tier": "domain", "domains": ["llm-pipeline-dev"], "item_id": "rule-032"},
+    {"anchor": "Let tools/code own ids, paths, serialization", "tier": "domain", "domains": ["llm-pipeline-dev"], "item_id": "rule-033"},
+    {"anchor": "Keep deterministic values out of LLM authority", "tier": "domain", "domains": ["llm-pipeline-dev"], "item_id": "rule-034"},
+    {"anchor": "For simple stable explanations or planning", "tier": "domain", "domains": ["llm-pipeline-dev"], "item_id": "rule-035"},
+    {"anchor": "Treat a produced field, flag, signal", "tier": "domain", "domains": ["llm-pipeline-dev"], "item_id": "rule-036"},
+    {"anchor": "Hard-block only deterministically decidable structural", "tier": "domain", "domains": ["llm-pipeline-dev"], "item_id": "rule-037"},
+    {"anchor": "Runtime/code may enforce the contract", "tier": "domain", "domains": ["llm-pipeline-dev"], "item_id": "rule-038"},
+    {"anchor": "When adding, changing, renaming, splitting, or exposing anything lasting or shared", "tier": "domain", "domains": ["builder-base"], "item_id": "rule-039"},
+    {"anchor": "Before fixing a review finding or test failure", "tier": "domain", "domains": ["builder-base"], "item_id": "rule-040"},
+    {"anchor": "For `.xlsx` editing, generation, reconciliation", "tier": "domain", "domains": ["office-work"], "item_id": "rule-041"},
+    {"anchor": "For development work, read and use", "tier": "domain", "domains": ["builder-base"], "item_id": "rule-042"},
+    {"anchor": "For mock, fixture, fake, stub, simulated-provider", "tier": "domain", "domains": ["builder-base"], "item_id": "rule-043"},
+    {"anchor": "Own the full lifecycle of what you create", "tier": "domain", "domains": ["builder-base"], "item_id": "rule-044"},
+    {"anchor": "Land risky or behavior-changing work behind", "tier": "domain", "domains": ["builder-base"], "item_id": "rule-045"},
+    {"anchor": "For composing a review request, packet", "tier": "domain", "domains": ["builder-base"], "item_id": "rule-046"},
+    {"anchor": "After every meaningful code, ontology, config", "tier": "domain", "domains": ["builder-base"], "item_id": "rule-047"},
+    {"anchor": "For choosing verification depth, the per-domain mix, the case space, what makes a completion criterion falsifiable", "tier": "domain", "domains": ["builder-base"], "item_id": "rule-048"},
+    {"anchor": "Report the checks run, results", "tier": "core", "domains": [], "item_id": "rule-049"},
+    {"anchor": "Trust a green check only when it traversed", "tier": "domain", "domains": ["builder-base"], "item_id": "rule-050"},
+    {"anchor": "Before comparing two of anything", "tier": "domain", "domains": ["builder-base"], "item_id": "rule-051"},
+    {"anchor": "For concrete shell/CLI traps", "tier": "domain", "domains": ["builder-base"], "item_id": "rule-052"},
+    {"anchor": "Ambient state — the active shell", "tier": "domain", "domains": ["builder-base"], "item_id": "rule-053"},
+    {"anchor": "Before relying on any model id", "tier": "domain", "domains": ["builder-base"], "item_id": "rule-054"},
+    {"anchor": "Scope destructive actions (kill, rm, force-push", "tier": "domain", "domains": ["builder-base"], "item_id": "rule-055"},
+    {"anchor": "Never accept secrets through transcript- or history-logged channels", "tier": "core", "domains": [], "item_id": "rule-056"},
+    {"anchor": "When a secret must be supplied", "tier": "domain", "domains": ["builder-base"], "item_id": "rule-057"},
+    {"anchor": "Treat a coarse runtime signal", "tier": "domain", "domains": ["builder-base"], "item_id": "rule-058"},
+    {"anchor": "Standing spawn policy: check the spawn gates", "tier": "domain", "domains": ["multi-agent-orchestration"], "item_id": "rule-059"},
+    {"anchor": "Down-spawns carry a machine-checkable done-when", "tier": "domain", "domains": ["multi-agent-orchestration"], "item_id": "rule-060"},
+    {"anchor": "For work spanning multiple models or CLI agents", "tier": "domain", "domains": ["multi-agent-orchestration"], "item_id": "rule-061"},
+    {"anchor": "For composing a prompt, packet, or tool description", "tier": "domain", "domains": ["multi-agent-orchestration"], "item_id": "rule-062"},
+    {"anchor": "Allocate models by difficulty", "tier": "domain", "domains": ["multi-agent-orchestration"], "item_id": "rule-063"},
+    {"anchor": "Judge a review by how much independence", "tier": "domain", "domains": ["multi-agent-orchestration"], "item_id": "rule-064"},
+    {"anchor": "dual-provider frontier design drafts", "tier": "domain", "domains": ["multi-agent-orchestration"], "item_id": "rule-065"},
+    {"anchor": "Never retry-storm a live rate limit", "tier": "domain", "domains": ["multi-agent-orchestration"], "item_id": "rule-066"},
+    {"anchor": "On any resumed, cleared, or relocated session", "tier": "domain", "domains": ["multi-agent-orchestration"], "item_id": "rule-067"},
+    {"anchor": "Keep runtime code, active docs, and execution-facing", "tier": "domain", "domains": ["builder-base"], "item_id": "rule-068"},
+    {"anchor": "For where a comment, a compatibility note, deprecated behavior, a rejected alternative", "tier": "domain", "domains": ["builder-base"], "item_id": "rule-069"},
+    {"anchor": "For SVG diagrams, service blueprints", "tier": "domain", "domains": ["visualization-docs"], "item_id": "rule-070"},
+    {"anchor": "When a concept is easier to understand visually", "tier": "domain", "domains": ["visualization-docs"], "item_id": "rule-071"},
+    {"anchor": "Use HTML for comparisons, flows, state changes", "tier": "domain", "domains": ["visualization-docs"], "item_id": "rule-072"},
+    {"anchor": "Keep HTML self-contained, accessible, and minimal", "tier": "domain", "domains": ["visualization-docs"], "item_id": "rule-073"},
+    {"anchor": "Use plain text when it is clearer", "tier": "domain", "domains": ["visualization-docs"], "item_id": "rule-074"},
+    {"anchor": "For the detailed `IMPLEMENTATION_MAP.html` construction rules", "tier": "domain", "domains": ["visualization-docs"], "item_id": "rule-075"},
+    {"anchor": "In repos with implementation code", "tier": "domain", "domains": ["visualization-docs"], "item_id": "rule-076"},
+    {"anchor": "`learn!` — session learning", "tier": "core", "domains": [], "item_id": "rule-077"}
   ],
   "guides": {
-    "claude-prompting.md": {"tier": "domain", "domains": ["multi-agent-orchestration"], "handles": ["per-family prompting guide", "계열별 prompting guide"]},
-    "cli-multi-model-workflow.md": {"tier": "domain", "domains": ["multi-agent-orchestration"], "handles": ["multi-model guide", "multi-model 가이드"]},
-    "coding-staged-workflow.md": {"tier": "domain", "domains": ["builder-base"]},
-    "concept-economy.md": {"tier": "domain", "domains": ["builder-base"]},
-    "documentation-hygiene.md": {"tier": "domain", "domains": ["builder-base"]},
-    "gpt-prompting.md": {"tier": "domain", "domains": ["multi-agent-orchestration"], "handles": ["prompting guides for gpt-family"]},
-    "implementation-map.md": {"tier": "domain", "domains": ["visualization-docs"]},
-    "llm-capability-boundary-examples.md": {"tier": "domain", "domains": ["llm-pipeline-dev"]},
-    "llm-capability-boundary-patterns.md": {"tier": "domain", "domains": ["llm-pipeline-dev"]},
-    "llm-capability-boundary.md": {"tier": "domain", "domains": ["llm-pipeline-dev"]},
-    "mock-realization-boundary.md": {"tier": "domain", "domains": ["builder-base"]},
-    "review-defect-criteria.md": {"tier": "domain", "domains": ["builder-base"]},
-    "review-request.md": {"tier": "domain", "domains": ["builder-base"]},
-    "session-distill-workflow.md": {"tier": "infra", "domains": []},
-    "learning-flow.md": {"tier": "infra", "domains": []},
-    "svg-visualization-guide.md": {"tier": "domain", "domains": ["visualization-docs"]},
-    "verification-discipline.md": {"tier": "domain", "domains": ["builder-base"]},
-    "tooling-gotchas.md": {"tier": "domain", "domains": ["builder-base"]}
+    "claude-prompting.md": {"tier": "domain", "domains": ["multi-agent-orchestration"], "handles": ["per-family prompting guide", "계열별 prompting guide"], "item_id": "guide-claude-prompting"},
+    "cli-multi-model-workflow.md": {"tier": "domain", "domains": ["multi-agent-orchestration"], "handles": ["multi-model guide", "multi-model 가이드"], "item_id": "guide-cli-multi-model-workflow"},
+    "coding-staged-workflow.md": {"tier": "domain", "domains": ["builder-base"], "item_id": "guide-coding-staged-workflow"},
+    "concept-economy.md": {"tier": "domain", "domains": ["builder-base"], "item_id": "guide-concept-economy"},
+    "documentation-hygiene.md": {"tier": "domain", "domains": ["builder-base"], "item_id": "guide-documentation-hygiene"},
+    "gpt-prompting.md": {"tier": "domain", "domains": ["multi-agent-orchestration"], "handles": ["prompting guides for gpt-family"], "item_id": "guide-gpt-prompting"},
+    "implementation-map.md": {"tier": "domain", "domains": ["visualization-docs"], "item_id": "guide-implementation-map"},
+    "llm-capability-boundary-examples.md": {"tier": "domain", "domains": ["llm-pipeline-dev"], "item_id": "guide-llm-capability-boundary-examples"},
+    "llm-capability-boundary-patterns.md": {"tier": "domain", "domains": ["llm-pipeline-dev"], "item_id": "guide-llm-capability-boundary-patterns"},
+    "llm-capability-boundary.md": {"tier": "domain", "domains": ["llm-pipeline-dev"], "item_id": "guide-llm-capability-boundary"},
+    "mock-realization-boundary.md": {"tier": "domain", "domains": ["builder-base"], "item_id": "guide-mock-realization-boundary"},
+    "review-defect-criteria.md": {"tier": "domain", "domains": ["builder-base"], "item_id": "guide-review-defect-criteria"},
+    "review-request.md": {"tier": "domain", "domains": ["builder-base"], "item_id": "guide-review-request"},
+    "session-distill-workflow.md": {"tier": "infra", "domains": [], "item_id": "guide-session-distill-workflow"},
+    "learning-flow.md": {"tier": "infra", "domains": [], "item_id": "guide-learning-flow"},
+    "svg-visualization-guide.md": {"tier": "domain", "domains": ["visualization-docs"], "item_id": "guide-svg-visualization-guide"},
+    "slide-writing.md": {"tier": "domain", "domains": ["office-work", "visualization-docs"], "item_id": "skill-slide-writing"},
+    "verification-discipline.md": {"tier": "domain", "domains": ["builder-base"], "item_id": "guide-verification-discipline"},
+    "tooling-gotchas.md": {"tier": "domain", "domains": ["builder-base"], "item_id": "guide-tooling-gotchas"}
   },
   "hooks": {
-    "tooling-gotchas-hook.py": {"tier": "domain", "domains": ["builder-base"], "source_guide": "tooling-gotchas.md"}
+    "tooling-gotchas-hook.py": {"tier": "domain", "domains": ["builder-base"], "source_guide": "tooling-gotchas.md", "item_id": "hook-tooling-gotchas-hook"}
   },
   "agents": {
-    "frontier.md": {"tier": "domain", "domains": ["multi-agent-orchestration"]},
-    "sweep.md": {"tier": "domain", "domains": ["multi-agent-orchestration"]},
-    "workhorse.md": {"tier": "domain", "domains": ["multi-agent-orchestration"]}
+    "frontier.md": {"tier": "domain", "domains": ["multi-agent-orchestration"], "item_id": "agent-frontier"},
+    "sweep.md": {"tier": "domain", "domains": ["multi-agent-orchestration"], "item_id": "agent-sweep"},
+    "workhorse.md": {"tier": "domain", "domains": ["multi-agent-orchestration"], "item_id": "agent-workhorse"}
   },
   "skills": {
-    "repo-charter": {"tier": "domain", "domains": ["builder-base"]}
+    "repo-charter": {"tier": "domain", "domains": ["builder-base"], "item_id": "skill-repo-charter"}
   }
 }

package/compose/write-update-cache.py

@@ -0,0 +1,53 @@
+#!/usr/bin/env python3
+"""Write the update-check cache atomically.
+
+The launcher READS this file on every start and never writes it, so a half-written
+cache is a crash in the TUI rather than a stale badge — hence os.replace over a
+temp file in the same directory, not a plain open-and-write.
+
+`latest` is omitted when the lookup failed; `checked_at` is written regardless, so
+an offline machine records its attempt and waits out the interval instead of
+retrying on every launch. Absence of `latest` therefore means "asked, no answer",
+which the launcher must not render as "up to date".
+"""
+import json
+import os
+import sys
+import tempfile
+
+
+def main(argv: list[str]) -> int:
+    if len(argv) != 5:
+        print("usage: write-update-cache.py <out> <checked_at> <latest|''> <current>",
+              file=sys.stderr)
+        return 2
+    out, checked_at, latest, current = argv[1], argv[2], argv[3], argv[4]
+    try:
+        checked = int(checked_at)
+    except ValueError:
+        print(f"checked_at is not an integer: {checked_at!r}", file=sys.stderr)
+        return 2
+    payload: dict[str, object] = {"checked_at": checked}
+    if current:
+        payload["current"] = current
+    if latest:
+        payload["latest"] = latest
+    directory = os.path.dirname(out) or "."
+    os.makedirs(directory, exist_ok=True)
+    fd, tmp = tempfile.mkstemp(dir=directory, prefix=".update-check.")
+    try:
+        with os.fdopen(fd, "w", encoding="utf-8") as handle:
+            json.dump(payload, handle)
+        os.replace(tmp, out)
+    except BaseException:
+        # A temp file left in the state dir would be swept by nothing.
+        try:
+            os.unlink(tmp)
+        except OSError:
+            pass
+        raise
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main(sys.argv))

package/install.sh

@@ -13,6 +13,7 @@
 #   agent-bios status      show what is installed and where
 #   agent-bios cost        the session cost / context meter, from any directory
 #   agent-bios update      git pull + reinstall (clone), or print the npm update line
+#   agent-bios update --check   cache the registry's latest version for the TUI badge
 #   agent-bios uninstall   remove deployed files and the zsh hook
 #   agent-bios help
 #
@@ -95,6 +96,13 @@ CLEANUP_FAILED=0
 # treating it as a failure made cmd_install exit 1 and the EXIT trap restore the previous
 # manifest — leaving the new corpus on disk with the record saying the old one was deployed.
 ENTRY_NEEDS_ACTION=0
+# Set when the required corpus-status projection could not be written. Deferred rather than
+# returned on the spot: the projection runs AFTER the corpus is deployed, and returning
+# there would fire the EXIT trap and restore the PREVIOUS manifest — leaving the new corpus
+# on disk with the record naming the old one, which is the split state above. The manifest
+# is completed first so it describes what is really there, and the command then exits
+# non-zero. The files, the record, and the exit code then each say something true.
+PROJECTION_FAILED=0
 # Deployed files uninstall could not back up, so did not delete. Global rather than local
 # because the closing summary must not claim a clean removal that did not happen.
 UNBACKED=0
@@ -381,7 +389,37 @@ assemble_corpus() {
     if [ -f "$CLAUDE_DIR/central/bundle.md" ]; then
       printf '%s\n' "$CLAUDE_DIR/central/bundle.md" >> "$MANIFEST"
     fi
-    for sub in guides hooks agents; do
+    # A guide can carry a same-stem companion tree.  The assembler owns that structure, so
+    # manifest it through its resolver rather than flattening `guides/*.md`: uninstall needs
+    # every deployed script/asset by its exact path, and must not claim a user-created sibling
+    # merely because it sits below one of our guide directories.
+    local source_guides="$REPO/claude/guides" codex_guides="$REPO/codex/guides"
+    manifest_guide_members() {
+      # Pin the installed resolver file independently of the selected content tree.
+      python3 - "$REPO/compose/assemble.py" "$1" "$2" <<'PY'
+import pathlib
+import sys
+
+assembler, source, dest = map(pathlib.Path, sys.argv[1:])
+sys.path.insert(0, str(assembler.parent))
+from assemble import GuideMemberError, guide_member_map
+
+try:
+    members = guide_member_map(source)
+except GuideMemberError as exc:
+    raise SystemExit(f"invalid guide bundle source: {exc}")
+for paths in members.values():
+    for rel in paths:
+        target = dest / rel
+        if target.is_file():
+            print(target)
+PY
+    }
+    if ! manifest_guide_members "$source_guides" "$CLAUDE_DIR/central/guides" >> "$MANIFEST"; then
+      log "could not enumerate assembled Claude guide members for the manifest"
+      return 1
+    fi
+    for sub in hooks agents; do
       for s in "$REPO"/claude/"$sub"/*; do
         [ -f "$s" ] || continue
         dst="$CLAUDE_DIR/central/$sub/$(basename "$s")"
@@ -390,16 +428,10 @@ assemble_corpus() {
         if [ -f "$dst" ]; then printf '%s\n' "$dst" >> "$MANIFEST"; fi
       done
     done
-    for g in "$REPO"/codex/guides/*.md; do
-      [ -f "$g" ] || continue
-      dst="$CODEX_DIR/guides/$(basename "$g")"
-      # if-form, not `[ -f ] && printf`: when the alphabetically LAST guide is
-      # not deployed (a partial domain selection on a fresh machine), the
-      # compound's false status became the loop's, the loop's became the
-      # function's, and the install died silently right after ASSEMBLED —
-      # a latent first-user bug the I9 scenario exposed.
-      if [ -f "$dst" ]; then printf '%s\n' "$dst" >> "$MANIFEST"; fi
-    done
+    if ! manifest_guide_members "$codex_guides" "$CODEX_DIR/guides" >> "$MANIFEST"; then
+      log "could not enumerate assembled Codex guide members for the manifest"
+      return 1
+    fi
   fi
   return 0
 }
@@ -859,12 +891,36 @@ cmd_install() {
   # deployed, against this script's own `--dry-run  print actions without changing
   # anything` and README's identical sentence. A dry run that edits state is worse than
   # no dry run: it is consulted precisely when the user is unwilling to touch anything.
+  #
+  # The projection is REQUIRED, not best-effort. It used to be neither: stderr and the
+  # exit status were both discarded and every failure printed one guess of a note —
+  # "versions.json/ledger missing?" — which was wrong for the failure that actually
+  # happened. `compose/corpus-state.py` was not in the npm package at all, so a real
+  # npm install rewrote the corpus, updated selection.json and version.json, passed
+  # verification, exited 0, and left corpus-status.json stale from a previous
+  # deployment. The launcher's corpus panel reads that file, so the machine reported a
+  # selection the successful run had not recorded. A command that deploys the launcher
+  # and advertises its panel cannot call that a success.
+  #
+  # The script now ships and degrades honestly in an npm layout (domains real,
+  # version/ledger reported unavailable), so the remaining failures are real ones:
+  # an unwritable destination, an invalid status, a missing interpreter. Those fail
+  # the install, and the reason reaches the operator instead of /dev/null.
   if [ "$DRY_RUN" = 1 ]; then
     info "[dry-run] project corpus-status"
-  elif python3 "$REPO/compose/corpus-state.py" project --repo "$REPO" >/dev/null 2>&1; then
-    info "corpus-status projected"
   else
-    log "note: corpus-status projection unavailable (versions.json/ledger missing?)"
+    local projection_log
+    projection_log="$(mktemp -t corpus-projection)"
+    if python3 "$REPO/compose/corpus-state.py" project --repo "$REPO" >"$projection_log" 2>&1; then
+      info "corpus-status projected"
+      rm -f "$projection_log"
+    else
+      log "corpus-status projection FAILED — the launcher's corpus panel would report a"
+      log "selection this run did not record. Its own output:"
+      sed 's/^/    /' "$projection_log"
+      log "    full output: $projection_log"
+      PROJECTION_FAILED=1
+    fi
   fi
   # Deploy/system version marker for the launcher's TUI version line, read from
   # package.json (version + releaseDate) — distinct from the corpus content
@@ -917,7 +973,13 @@ PY
     # restore armed above must not fire.
     INSTALL_COMPLETED=1
     log ""
-    log "Done. Open a new shell (or: source \"$ZSHRC\") to activate the zero-arg launcher."
+    # Withheld when the projection failed: the run below reports INSTALL INCOMPLETE and
+    # exits non-zero, and printing "Done." first told the operator both things in the
+    # same breath. The manifest is already complete by here, which is the point — the
+    # files really are deployed; what failed is the record of WHICH selection they are.
+    if [ "$PROJECTION_FAILED" != 1 ]; then
+      log "Done. Open a new shell (or: source \"$ZSHRC\") to activate the zero-arg launcher."
+    fi
     if [ "${ENTRY_NEEDS_ACTION:-0}" = 1 ]; then
       log ""
       log "ONE STEP LEFT: add this line to $CLAUDE_DIR/CLAUDE.md (yours; we never rewrite it):"
@@ -928,6 +990,13 @@ PY
     # must not become a nonzero exit under set -e.
     { [ -n "$BACKUP_DIR" ] && [ -d "$BACKUP_DIR" ] && log "Replaced files were backed up under $BACKUP_DIR"; } || true
     prune_backups
+    if [ "$PROJECTION_FAILED" = 1 ]; then
+      log ""
+      log "INSTALL INCOMPLETE: the corpus is deployed and the manifest records it, but the"
+      log "corpus-status projection failed above — the launcher's panel would describe a"
+      log "state this run did not record. Fix the cause and re-run: agent-bios install"
+      exit 1
+    fi
   else
     log "VERIFY FAILED after install — see messages above"
     exit 1
@@ -1417,8 +1486,22 @@ cmd_onboard() {
     log "ONBOARDING INCOMPLETE: the bundle is installed but not loading — fix the cause above and re-run: agent-bios verify"
     exit 1
   fi
-  python3 "$REPO/compose/corpus-state.py" record-apply \
-    --requested "$sel" --outcome applied >/dev/null 2>&1 || true
+  # The SUCCESS record is strict; the two failure records above stay tolerant. The
+  # asymmetry is the point: a swallowed failure-record rides a run that is already
+  # exiting non-zero and reporting why, while a swallowed success-record is how
+  # onboarding prints a completed summary over a status file that never learned the
+  # selection was applied. That is the state this whole change exists to remove, so it
+  # cannot be the one still guarded by `|| true`.
+  record_log="$(mktemp -t corpus-record-apply)"
+  if ! python3 "$REPO/compose/corpus-state.py" record-apply \
+       --requested "$sel" --outcome applied >"$record_log" 2>&1; then
+    log "ONBOARDING INCOMPLETE: the corpus applied, but recording that outcome failed —"
+    log "the corpus panel would not show this selection as applied. Its own output:"
+    sed 's/^/    /' "$record_log"
+    log "    full output: $record_log"
+    exit 1
+  fi
+  rm -f "$record_log"
   # The prune is authorized by the canary's proof, and cmd_install ran before the canary existed
   # for this bundle rev — so it kept everything. Now that loading is proven, run it for real.
   migrate_learnings
@@ -1613,11 +1696,57 @@ shell_shadow_summary() {
   fi
 }
 
+# The update check is a READ of a public version number: it sends the package name
+# and nothing derived from this machine, which is the same class as provision-venv's
+# PyPI fetch and the onboard model probe — see ENDPOINTS.md "Zero egress by default",
+# whose claim is scoped to DATA egress. It delegates to `npm view` rather than naming
+# a registry, so a private registry, a proxy, and the user's auth all keep working and
+# no shipped file carries a URL (gates/check-endpoints.py forbids that outright).
+#
+# `checked_at` is written even when the lookup FAILS. An offline machine that recorded
+# nothing would retry on every launch, which is the opposite of once a day.
+refresh_update_cache() {
+  if [ "${AGENT_BIOS_UPDATE_CHECK:-1}" = "0" ]; then
+    log "update check disabled (AGENT_BIOS_UPDATE_CHECK=0)"
+    return 0
+  fi
+  local name latest now out
+  name="$(json_field "$REPO/package.json" name)" || return 1
+  [ -n "$name" ] || return 1
+  now="$(date +%s)"
+  latest=""
+  if command -v npm >/dev/null 2>&1; then
+    # `|| latest=""` is not defensive noise: this file runs under `set -euo pipefail`,
+    # so an npm that exits non-zero (offline, firewalled, private registry down) makes
+    # the PIPELINE fail and `set -e` abort the function before it can record the
+    # attempt — turning every offline launch into a retry and `update --check` into
+    # exit 1. Caught by I16's failing-registry stub, not by review.
+    latest="$(npm view "$name" version 2>/dev/null | tr -d '[:space:]')" || latest=""
+  fi
+  mkdir -p "$STATE_DIR" || return 1
+  out="$STATE_DIR/update-check.json"
+  # Atomic: a half-written cache read by the launcher is a crash in the TUI.
+  python3 "$REPO/compose/write-update-cache.py" "$out" "$now" "$latest" "$(source_version)" || return 1
+  if [ -n "$latest" ]; then
+    log "update check: latest $latest (installed $(source_version))"
+  else
+    log "update check: could not reach the registry; recorded the attempt"
+  fi
+}
+
 cmd_update() {
+  if [ "${UPDATE_CHECK_ONLY:-0}" = 1 ]; then
+    refresh_update_cache
+    return $?
+  fi
   if [ -e "$REPO/.git" ]; then
     log "Updating from git..."
     run git -C "$REPO" pull --ff-only
-    cmd_install
+    if [ "${AGENT_BIOS_LEGACY_INSTALL:-0}" = 1 ]; then
+      cmd_install
+    else
+      python3 "$REPO/compose/corpus_install.py" --repo "$REPO" install
+    fi
   else
     log "Installed as an npm package. Update with:"
     log "  npm install -g agent-bios@latest && agent-bios install"
@@ -1629,11 +1758,14 @@ cmd_update() {
 
 usage() {
   cat <<'EOF'
-agent-bios — deploy the Claude/Codex instruction SSOT into $HOME (by copy).
-
-  agent-bios install     deploy into this environment (backs up + verifies)
-  agent-bios onboard     interactive domain selection + install + activation canary
-  agent-bios verify      check the deployed state matches the source
+agent-bios — manage private corpus content for explicitly activated sessions.
+
+  agent-bios install     store a private runtime and corpus baseline
+  agent-bios onboard     select domains for future activated sessions
+  agent-bios corpus      open Corpus Studio; list/show/plan/apply also work non-TTY
+  agent-bios migrate     preview legacy global cleanup; --apply --yes applies it
+  agent-bios reset       preview reset; --apply --yes --expected-revision REV applies it
+  agent-bios verify      verify the private runtime, baseline, and managed files
   agent-bios learn       submit a session learning (reads the JSON record on
                          stdin; this is what the learn! flow calls, and it
                          works from any directory, unlike a repo-relative path)
@@ -1641,7 +1773,10 @@ agent-bios — deploy the Claude/Codex instruction SSOT into $HOME (by copy).
   agent-bios cost        the session cost / context meter (session-cost.py), from any
                          directory: agent-bios cost [--context [--budget N]] <transcript>
   agent-bios update      git pull + reinstall (clone), or print the npm update line
-  agent-bios uninstall   remove deployed files and the zsh hook
+  agent-bios update --check   ask the registry for the latest version and cache it
+                      for the launcher's badge; sends the package name and nothing
+                      else, runs at most daily, AGENT_BIOS_UPDATE_CHECK=0 disables it
+  agent-bios uninstall   remove the private runtime; preserve personal and session data
   agent-bios help
 
 Flags: --dry-run       print actions without changing anything
@@ -1679,6 +1814,20 @@ EOF
 CMD="${1:-help}"
 if [ $# -gt 0 ]; then shift; fi
 
+# Private installation is the new user path. The explicit legacy flag exists only
+# while maintained install fixtures and pre-migration environments exercise the old
+# writer. No private operation falls through to a global writer.
+if [ "$CMD" = "corpus" ]; then
+  exec python3 "$REPO/compose/corpus.py" --repo "$REPO" "$@" <&3
+fi
+if [ "${AGENT_BIOS_LEGACY_INSTALL:-0}" != 1 ]; then
+  case "$CMD" in
+    install|onboard|verify|status|uninstall|migrate|reset)
+      exec python3 "$REPO/compose/corpus_install.py" --repo "$REPO" "$CMD" "$@" <&3
+      ;;
+  esac
+fi
+
 # `learn` forwards its arguments and stdin straight to the collector, so it must
 # bypass the flag parser below (which rejects anything it does not know). This
 # subcommand is the only PATH-reachable entry to capture: the corpus guide used
@@ -1706,6 +1855,7 @@ DOMAINS_SET=0
 while [ $# -gt 0 ]; do
   case "$1" in
     --dry-run) DRY_RUN=1 ;;
+    --check) UPDATE_CHECK_ONLY=1 ;;
     --with) shift; WITH="${1:-}"; [ -n "$WITH" ] || { log "--with needs a comma-separated capability list"; exit 2; } ;;
     --with=*) WITH="${1#--with=}"; [ -n "$WITH" ] || { log "--with needs a comma-separated capability list"; exit 2; } ;;
     --domains) shift; DOMAINS_ARG="${1:-}"; DOMAINS_SET=1; [ -n "$DOMAINS_ARG" ] || { log "--domains needs a comma-separated domain list (use onboard for core-only)"; exit 2; } ;;