# titan - Doramagic AI Context Pack > Positioning: a pre-install experience and judgment asset. It helps the host AI get off to a good start, but it does not mean the project has already been installed, run, or validated. ## Sufficiency Principle - **Sufficiency over compression**: The AI Context Pack should be sufficient for the host AI to understand the project's value, capability boundaries, entrypoints, risks, and evidence sources before starting work; it may be layered, but it does not aim for the shortest possible summary. - **Compression policy**: Compress only noise and duplication, never context that affects judgment or the quality of the work. ## How the Host AI Should Use This You are reading the AI Context Pack that Doramagic compiled for titan. Treat it as pre-work context: help the user understand who it fits, what it can do, how to start, what must be verified after install, and where the risks are. Do not claim that you have already installed, run, or executed the target project. ## Claim Consumption Rules - **Fact source**: Repo Evidence + Claim/Evidence Graph; the Human Wiki only supplies salience, terminology, and narrative structure. - **Minimum status for a fact**: `supported` - `supported`: May be used as a project fact, but the answer must cite the claim_id and evidence path. - `weak`: Usable only as a low-confidence lead; the user must be asked to keep verifying. - `inferred`: Usable only for risk notes or open questions; must not be packaged as a project fact. - `unverified`: Must not be used as fact; state clearly that evidence is insufficient. - `contradicted`: Must show the conflicting sources and must not force a single version on the user's behalf. ## Who It Fits Best - **Developers already using host AIs such as Claude/Codex/Cursor/Gemini**: The README or plugin config mentions multiple host AIs. Evidence: `README.md` Claim: `clm_0003` supported 0.86 - **Users who want to bring professional workflows into a host AI**: The repo contains Skill documents. Evidence: `assets/agent-skills/agent-introspection-debugging/SKILL.md`, `assets/agent-skills/api-and-interface-design/SKILL.md`, `assets/agent-skills/browser-testing-with-devtools/SKILL.md`, `assets/agent-skills/ci-cd-and-automation/SKILL.md` et al. Claim: `clm_0004` supported 0.86 ## What It Can Do - **AI Skill / Agent Instruction Asset Library** (Previewable before install): The project contains Skill or Agent instruction files that a host AI can read, useful for bringing professional workflows into hosts like Claude, Codex, or Cursor. Evidence: `assets/agent-skills/agent-introspection-debugging/SKILL.md`, `assets/agent-skills/api-and-interface-design/SKILL.md`, `assets/agent-skills/browser-testing-with-devtools/SKILL.md`, `assets/agent-skills/ci-cd-and-automation/SKILL.md` et al. Claim: `clm_0001` supported 0.86 - **Command-Line Startup or Install Flow** (Verify after install): The project documentation contains runnable commands; real use requires running them in a local or host environment. Evidence: `README.md` Claim: `clm_0002` supported 0.86 ## How to Start - `npm install -g titan-agent` Evidence: `README.md` Claim: `clm_0005` supported 0.86 - `curl -fsSL https://raw.githubusercontent.com/Djtony707/TITAN/main/install.sh | bash` Evidence: `README.md` Claim: `clm_0006` supported 0.86 - `npx vitest run tests/core.test.ts # single file` Evidence: `README.md` Claim: `clm_0007` supported 0.86 - `git clone https://github.com/Djtony707/TITAN` Evidence: `README.md` Claim: `clm_0008` supported 0.86 ## Continue-or-Stop Decision Card - **Current recommendation**: Needs admin / security approval - **Why**: Continuing may involve secrets, accounts, external services, or sensitive context; get admin or security approval first. ### 30-Second Read - **What to do now**: Needs admin / security approval - **Minimum safe next step**: Run Prompt Preview first; if credentials or an enterprise environment are involved, get approval before trialing - **Do not trust yet**: Whether this workflow fits your way of working cannot be trusted directly. - **Continuing will touch**: Host behavior change, Command execution, Host AI configuration ### What You Can Trust Now - **Target-audience signal: Developers already using host AIs such as Claude/Codex/Cursor/Gemini** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `README.md` Claim: `clm_0003` supported 0.86 - **Target-audience signal: Users who want to bring professional workflows into a host AI** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `assets/agent-skills/agent-introspection-debugging/SKILL.md`, `assets/agent-skills/api-and-interface-design/SKILL.md`, `assets/agent-skills/browser-testing-with-devtools/SKILL.md`, `assets/agent-skills/ci-cd-and-automation/SKILL.md` et al. Claim: `clm_0004` supported 0.86 - **Capability exists: AI Skill / Agent Instruction Asset Library** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `assets/agent-skills/agent-introspection-debugging/SKILL.md`, `assets/agent-skills/api-and-interface-design/SKILL.md`, `assets/agent-skills/browser-testing-with-devtools/SKILL.md`, `assets/agent-skills/ci-cd-and-automation/SKILL.md` et al. Claim: `clm_0001` supported 0.86 - **Capability exists: Command-Line Startup or Install Flow** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `README.md` Claim: `clm_0002` supported 0.86 - **There are Quick Start / install-command signals** (supported): You can trust that the docs mention a startup or install entrypoint; do not run it directly in your primary environment because of that. Evidence: `README.md` Claim: `clm_0005` supported 0.86 ### What You Cannot Trust Yet - **Whether this workflow fits your way of working cannot be trusted directly.** (unverified): Workflow-style Skills can strongly constrain AI behavior; they can improve discipline but may also slow your current task pace. Evidence: `assets/agent-skills/agent-introspection-debugging/SKILL.md`, `assets/agent-skills/api-and-interface-design/SKILL.md`, `assets/agent-skills/browser-testing-with-devtools/SKILL.md`, `assets/agent-skills/ci-cd-and-automation/SKILL.md` et al. - **That it will not conflict with your existing Claude/Cursor/Codex rules cannot be trusted directly.** (inferred): A dev-workflow Skill changes default behaviors like clarifying, planning, testing, and verifying, so it must be tried in a temporary host. Evidence: `assets/agent-skills/agent-introspection-debugging/SKILL.md`, `assets/agent-skills/api-and-interface-design/SKILL.md`, `assets/agent-skills/browser-testing-with-devtools/SKILL.md`, `assets/agent-skills/ci-cd-and-automation/SKILL.md` et al. - **Real output quality cannot be trusted before install.** (unverified): Prompt Preview can only show how it guides you; it cannot prove result quality in the real project. - **Host AI version compatibility cannot be trusted before install.** (unverified): Host loading rules and version differences across Claude, Cursor, Codex, Gemini, and others must be verified in a real environment. - **That it will not pollute your existing host AI's behavior cannot be trusted directly.** (inferred): Skill, plugin, and AGENTS/CLAUDE/GEMINI instructions may change the host AI's default behavior. Evidence: `assets/agent-skills/agent-introspection-debugging/SKILL.md`, `assets/agent-skills/api-and-interface-design/SKILL.md`, `assets/agent-skills/browser-testing-with-devtools/SKILL.md`, `assets/agent-skills/ci-cd-and-automation/SKILL.md` et al. - **Safe rollback cannot be assumed by default.** (unverified): Unless the project clearly provides uninstall and recovery instructions, verify in an isolated environment first. - **After a real install, is it compatible with the user's current host AI version?** (unverified): Compatibility can only be verified in the actual host environment. - **Does the project's output quality meet the user's specific task?** (unverified): The pre-install preview can only show flow and boundaries; it cannot replace real evaluation. ### What Continuing Will Touch - **Host behavior change**: The default development rhythm of clarifying, planning, TDD, verifying, and wrapping up. Why: This kind of Skill draws both its value and its risk from strongly constraining the workflow; confirm first that you are willing to have it change how you work. Evidence: `assets/agent-skills/agent-introspection-debugging/SKILL.md`, `assets/agent-skills/api-and-interface-design/SKILL.md`, `assets/agent-skills/browser-testing-with-devtools/SKILL.md`, `assets/agent-skills/ci-cd-and-automation/SKILL.md` et al. - **Command execution**: Package managers, network downloads, the local plugin directory, project config, or the user's home directory. Why: Running the very first command can already change your environment; decide whether it is worth running first. Evidence: `README.md` - **Host AI configuration**: The plugin, Skill, or rule-loading config of hosts like Claude/Codex/Cursor/Gemini/OpenCode. Why: Host configuration changes how the AI works afterward and may conflict with the user's existing rules. Evidence: `assets/agent-skills/agent-introspection-debugging/SKILL.md`, `assets/agent-skills/api-and-interface-design/SKILL.md`, `assets/agent-skills/browser-testing-with-devtools/SKILL.md`, `assets/agent-skills/ci-cd-and-automation/SKILL.md` et al. - **Local environment or project files**: Install results, plugin caches, project config, or local dependency directories. Why: The write scope and rollback path cannot be proven before install and need isolated verification. Evidence: `README.md` - **Environment variables / API keys**: Project entry docs explicitly showing API key, token, secret, or account credential configuration. Why: If a real install needs credentials, use test credentials first and go through a permission/compliance review. Evidence: `CHANGELOG.md`, `README.md` - **Host AI context**: The AI Context Pack, Prompt Preview, Skill routing, risk rules, and project facts. Why: Importing context affects the host AI's later judgment, so avoid packaging unverified items as facts. ### Minimum Safe Next Steps - **Run Prompt Preview first**: Feel how it changes the AI's development rhythm first, then decide whether to let it into a real host. (applies when: Applies to any project, especially when output quality is unknown.) - **Trial-install only in an isolated directory or a test account**: Avoid letting install commands pollute your primary host AI, real projects, or home directory. (applies when: When there are signals of command execution, plugin config, or local writes.) - **Back up your host AI configuration first**: Skill, plugin, and rule files may change the default behavior of Claude/Cursor/Codex. (applies when: When there is a plugin manifest, a Skill, or a host rule entrypoint.) - **Do not use real production credentials**: Once an environment variable / API key enters the host or toolchain, it can create account and compliance risk. (applies when: When environment signals like API, TOKEN, KEY, or SECRET appear.) - **After install, verify just one minimal task**: Verify loading, compatibility, output quality, and rollback first, then decide whether to use it deeply. (applies when: When moving from a trial into a real workflow.) ### Exit Plan - **Preserve the pre-install state**: Record the original host config and project state so you can later judge whether it is recoverable. - **Be ready to remove the host plugin / Skill / rule entrypoint**: If behavior is off after the trial install, you can restore the host AI to its pre-trial state. - **Record the install commands and written paths**: Without clear uninstall instructions, you at least need to know which directories or configs to clean up manually. - **Be ready to revoke test API keys or tokens**: If test credentials leak or are misused, you can cut losses quickly. - **If there is no rollback path, do not enter your primary environment**: No rollback is a blocker before continuing; do not proceed on trust or luck. ## What Can Only Be Previewed - Explain who the project fits and what it can do - Demonstrate a typical conversation flow based on project docs - Help the user decide whether it is worth installing or researching further ## What Must Be Verified After Install - Actually installing the Skill, plugin, or CLI - Running scripts, modifying local files, or accessing external services - Verifying real output quality, performance, and compatibility ## Boundary & Risk Decision Card - **Mistaking the pre-install preview for a real run**: The user may overestimate how much configuration, permission, and compatibility verification the project has already done. Mitigation: Clearly separate prompt_preview_can_do from runtime_required. Claim: `clm_0009` inferred 0.45 - **Command execution will modify the local environment**: Install commands may write to the user's home directory, the host plugin directory, or project configuration. Mitigation: Run in an isolated environment or a test account first. Evidence: `README.md` Claim: `clm_0010` supported 0.86 - **To confirm**: After a real install, is it compatible with the user's current host AI version?. Why: Compatibility can only be verified in the actual host environment. - **To confirm**: Does the project's output quality meet the user's specific task?. Why: The pre-install preview can only show flow and boundaries; it cannot replace real evaluation. - **To confirm**: Do the install commands require network access, permissions, or global writes?. Why: This affects install risk in both enterprise and personal environments. ## Pre-Work Working Context ### Loading Order - First read how_to_use.host_ai_instruction to establish the boundaries of this pre-install judgment asset. - Read claim_graph_summary to confirm facts come from the Claim/Evidence Graph, not the Human Wiki narrative. - Then read intended_users, capabilities, and quick_start_candidates to judge whether the user is a match. - When you need to carry out a concrete task, check role_skill_index first, then evidence_index. - For real install, file modification, network access, performance, or compatibility questions, turn to risk_card and boundaries.runtime_required. ### Task Routes - **AI Skill / Agent Instruction Asset Library**: Use role_skill_index / evidence_index to help the user pick a usable role, Skill, or workflow first. Boundary: Can be experienced via a pre-install Prompt. Evidence: `assets/agent-skills/agent-introspection-debugging/SKILL.md`, `assets/agent-skills/api-and-interface-design/SKILL.md`, `assets/agent-skills/browser-testing-with-devtools/SKILL.md`, `assets/agent-skills/ci-cd-and-automation/SKILL.md` et al. Claim: `clm_0001` supported 0.86 - **Command-Line Startup or Install Flow**: State that this is an after-install capability first, then give a pre-install checklist. Boundary: Must be verified after a real install or run. Evidence: `README.md` Claim: `clm_0002` supported 0.86 ### Context Scale - Total files: 1246 - Important-file coverage: 40/1246 - Evidence index entries: 80 - Role / Skill entries: 30 ### Handling Insufficient Evidence - **missing_evidence**: State that evidence is insufficient and ask the user for the target file, a README section, or after-install verification records; do not fill in facts. - **out_of_scope_request**: State that the task is beyond the current AI Context Pack's evidence scope and suggest the user check the Human Manual or verify after a real install. - **runtime_request**: Provide a pre-install checklist and command sources, but do not run commands for the user or claim they have been run. - **source_conflict**: Show the conflicting sources side by side, mark them as unverified, and do not force a single version. ## Prompt Recipes ### Fit assessment - Goal: Judge whether this project fits the user's current task. - Expected output: A fit conclusion, key reasons, evidence citations, what can be previewed before install, what must be verified after install, and a next-step recommendation. ```text Based on the AI Context Pack for titan, ask me 3 necessary questions first, then judge whether it fits my task. The answer must cover: who it fits, what it can do, what it cannot do, whether it is worth installing, and where the evidence comes from. Every project fact must cite evidence_refs, source_paths, or a claim_id. ``` ### Pre-install experience - Goal: Let the user feel the core workflow before installing, while avoiding packaging the preview as real capability or a marketing promise. - Expected output: An experience script with boundary labels, an after-install verification checklist, and a cautious recommendation; with no real-run promises or strong marketing language. ```text Treat titan as a pre-install experience asset, not an already-installed tool or a real runtime environment. Output exactly four parts: 1. Ask me 3 necessary questions first. 2. Give an "experience script": use the three labels [Previewable before install], [Must verify after install], and [Insufficient evidence] to show how it might guide the workflow. 3. Give an after-install verification checklist: list which capabilities can only be confirmed after a real install, real host loading, and a real project run. 4. Give a cautious recommendation: only "worth researching/trialing further", "add information before deciding", or "not recommended to continue"; do not endorse the project. Hard boundaries: - Do not claim you have installed, run, executed tests, modified files, or produced real results. - Do not write promise-like phrasing such as "auto-adapts", "guarantees passing", "perfect fit", or "strongly recommend installing". - If you describe how it works after install, you must use a conditional such as "if installed successfully and the host loads the Skill correctly, it might...". - The experience script may only be written as "example lines / hypothetical flow": use "might ask / might suggest / might show", not "has written, has generated, has passed, is running, is generating". - Prompt Preview does not hand out install commands; if the user is ready to trial, only prompt them to read Quick Start and the Risk Card first and to verify in an isolated environment. - Every project fact must come from a supported claim, evidence_refs, or source_paths; inferred/unverified items can only be risks or open questions. ``` ### Role / Skill selection - Goal: Pick the best-matching asset from the project's roles or Skills. - Expected output: A list of candidate roles or Skills, each with an applicable scenario, evidence paths, risk boundary, and whether after-install verification is needed. ```text Read role_skill_index and recommend 3-5 of the most relevant roles or Skills for my target task. For each recommendation, state the applicable scenario, likely output, risk boundary, and evidence_refs. ``` ### Risk pre-check - Goal: Identify environment, permission, rule-conflict, and quality risks before installing or adopting. - Expected output: A checklist of environment, permission, dependency, license, host-conflict, quality risk, and unknown items. ```text Based on risk_card, boundaries, and quick_start_candidates, give me a pre-install risk pre-check list. Do not run commands for me; only explain what I should check, why, and what impact a failure would have. ``` ### Host AI kickoff instruction - Goal: Turn the project context into a host AI instruction for the start of a conversation. - Expected output: A pre-work instruction with clear boundaries and clear evidence citations, suitable to copy to a host AI. ```text Based on the AI Context Pack for titan, generate a pre-work instruction I can paste to my host AI. This instruction must obey not_runtime=true and must not claim the project has been installed, run, or produced real results. ``` ## Role / Skill Index - Indexed 30 role / Skill / project-doc entries. - **agent-introspection-debugging** (skill): Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Activation hint: When the user's task is highly relevant to the workflow described by “agent-introspection-debugging”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/agent-introspection-debugging/SKILL.md` - **api-and-interface-design** (skill): Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend. Activation hint: When the user's task is highly relevant to the workflow described by “api-and-interface-design”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/api-and-interface-design/SKILL.md` - **browser-testing-with-devtools** (skill): Tests in real browsers. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data via Chrome DevTools MCP. Activation hint: When the user's task is highly relevant to the workflow described by “browser-testing-with-devtools”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/browser-testing-with-devtools/SKILL.md` - **ci-cd-and-automation** (skill): Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies. Activation hint: When the user's task is highly relevant to the workflow described by “ci-cd-and-automation”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/ci-cd-and-automation/SKILL.md` - **code-review-and-quality** (skill): Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch. Activation hint: When the user's task is highly relevant to the workflow described by “code-review-and-quality”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/code-review-and-quality/SKILL.md` - **code-simplification** (skill): Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity. Activation hint: When the user's task is highly relevant to the workflow described by “code-simplification”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/code-simplification/SKILL.md` - **context-engineering** (skill): Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project. Activation hint: When the user's task is highly relevant to the workflow described by “context-engineering”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/context-engineering/SKILL.md` - **continuous-agent-loop** (skill): Patterns for continuous autonomous agent loops with quality gates, evals, and recovery controls. Activation hint: When the user's task is highly relevant to the workflow described by “continuous-agent-loop”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/continuous-agent-loop/SKILL.md` - **continuous-learning** (skill): DEPRECATED - use continuous-learning-v2 Legacy v1 stop-hook skill extractor. v2 is a strict superset with instinct-based, project-scoped, hook-reliable learning. Do not invoke v1; route continuous learning, session learning, and pattern extraction requests to continuous-learning-v2. Activation hint: When the user's task is highly relevant to the workflow described by “continuous-learning”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/continuous-learning/SKILL.md` - **debugging-and-error-recovery** (skill): Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing. Activation hint: When the user's task is highly relevant to the workflow described by “debugging-and-error-recovery”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/debugging-and-error-recovery/SKILL.md` - **deprecation-and-migration** (skill): Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code. Activation hint: When the user's task is highly relevant to the workflow described by “deprecation-and-migration”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/deprecation-and-migration/SKILL.md` - **documentation-and-adrs** (skill): Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase. Activation hint: When the user's task is highly relevant to the workflow described by “documentation-and-adrs”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/documentation-and-adrs/SKILL.md` - **doubt-driven-development** (skill): Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when correctness matters more than speed, when working in unfamiliar code, when stakes are high production, security-sensitive logic, irreversible operations , or any time a confident output would be cheaper to verify now than to debug later. Activation hint: When the user's task is highly relevant to the workflow described by “doubt-driven-development”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/doubt-driven-development/SKILL.md` - **frontend-ui-engineering** (skill): Builds production-quality UIs. Use when building or modifying user-facing interfaces. Use when creating components, implementing layouts, managing state, or when the output needs to look and feel production-quality rather than AI-generated. Activation hint: When the user's task is highly relevant to the workflow described by “frontend-ui-engineering”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/frontend-ui-engineering/SKILL.md` - **git-workflow-and-versioning** (skill): Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams. Activation hint: When the user's task is highly relevant to the workflow described by “git-workflow-and-versioning”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/git-workflow-and-versioning/SKILL.md` - **idea-refine** (skill): Refines ideas iteratively. Refine ideas through structured divergent and convergent thinking. Use "idea-refine" or "ideate" to trigger. Activation hint: When the user's task is highly relevant to the workflow described by “idea-refine”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/idea-refine/SKILL.md` - **incremental-implementation** (skill): Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step. Activation hint: When the user's task is highly relevant to the workflow described by “incremental-implementation”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/incremental-implementation/SKILL.md` - **performance-optimization** (skill): Optimizes application performance. Use when performance requirements exist, when you suspect performance regressions, or when Core Web Vitals or load times need improvement. Use when profiling reveals bottlenecks that need fixing. Activation hint: When the user's task is highly relevant to the workflow described by “performance-optimization”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/performance-optimization/SKILL.md` - **planning-and-task-breakdown** (skill): Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. Activation hint: When the user's task is highly relevant to the workflow described by “planning-and-task-breakdown”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/planning-and-task-breakdown/SKILL.md` - **production-audit** (skill): Local-evidence production readiness audit for shipped apps, pre-launch reviews, post-merge checks, and "what breaks in prod?" questions without sending repo data to an external audit service. Activation hint: When the user's task is highly relevant to the workflow described by “production-audit”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/production-audit/SKILL.md` - **recursive-decision-ledger** (skill): Use when the user asks for repeated rollouts, marked decision processes, high-dimensional search, stochastic optimization, local-optima exploration, ensemble comparison, or recursive reasoning with a visible evidence trail. Activation hint: When the user's task is highly relevant to the workflow described by “recursive-decision-ledger”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/recursive-decision-ledger/SKILL.md` - **literature-review** (skill): Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging. Activation hint: When the user's task is highly relevant to the workflow described by “literature-review”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/scientific-thinking-literature-review/SKILL.md` - **scholar-evaluation** (skill): Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback. Activation hint: When the user's task is highly relevant to the workflow described by “scholar-evaluation”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/scientific-thinking-scholar-evaluation/SKILL.md` - **security-and-hardening** (skill): Hardens code against vulnerabilities. Use when handling user input, authentication, data storage, or external integrations. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services. Activation hint: When the user's task is highly relevant to the workflow described by “security-and-hardening”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/security-and-hardening/SKILL.md` - **shipping-and-launch** (skill): Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. Activation hint: When the user's task is highly relevant to the workflow described by “shipping-and-launch”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/shipping-and-launch/SKILL.md` - **source-driven-development** (skill): Grounds every implementation decision in official documentation. Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters. Activation hint: When the user's task is highly relevant to the workflow described by “source-driven-development”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/source-driven-development/SKILL.md` - **spec-driven-development** (skill): Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea. Activation hint: When the user's task is highly relevant to the workflow described by “spec-driven-development”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/spec-driven-development/SKILL.md` - **test-driven-development** (skill): Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality. Activation hint: When the user's task is highly relevant to the workflow described by “test-driven-development”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/test-driven-development/SKILL.md` - **using-agent-skills** (skill): Discovers and invokes agent skills. Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked. Activation hint: When the user's task is highly relevant to the workflow described by “using-agent-skills”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/using-agent-skills/SKILL.md` - **verification-loop** (skill): A comprehensive verification system for TITAN sessions. Activation hint: When the user's task is highly relevant to the workflow described by “verification-loop”, use it for a pre-install experience first, then decide whether to install. Evidence: `assets/agent-skills/verification-loop/SKILL.md` ## Evidence Index - Indexed 80 evidence entries. - **TITAN Autopilot Playbooks** (documentation): Pre-built autopilot templates for autonomous income generation. Copy the relevant sections into your ~/.titan/AUTOPILOT.md file. Evidence: `docs/autopilot-playbooks/README.md` - **TITAN** (documentation): TITAN — A local-first AI agent framework that runs on your hardware, with your models, under your control. Spawn a team of specialists around a goal, watch them work live — step-by-step, with real file diffs — and stay in the loop without giving up control. npm i -g titan-agent // : npm-text-end Evidence: `README.md` - **TITAN Benchmark Harness** (documentation): Automated health checks for TITAN. Run these to verify TITAN is healthy before and after changes. Evidence: `benchmarks/README.md` - **TITAN Examples** (documentation): Runnable examples for the titan-agent https://www.npmjs.com/package/titan-agent framework. Evidence: `examples/README.md` - **Agent Starter for React** (documentation): This is a starter template for LiveKit Agents https://docs.livekit.io/agents that provides a simple voice interface using Agents UI https://livekit.io/ui components and LiveKit JavaScript SDK https://github.com/livekit/client-sdk-js . It supports voice https://docs.livekit.io/agents/start/voice-ai , transcriptions https://docs.livekit.io/agents/build/text/ , and virtual avatars https://docs.livekit.io/agents/integrations/avatar . Evidence: `titan-voice-ui/README.md` - **Basic Agent Example** (documentation): A minimal CLI agent that demonstrates TITAN's core capabilities: sending messages, using tools, and managing sessions. Evidence: `examples/basic-agent/README.md` - **MCP Server Example** (documentation): A Model Context Protocol MCP server that exposes TITAN's tools to Claude Desktop, Cursor, and other MCP-compatible clients via JSON-RPC 2.0 over stdio and HTTP. Evidence: `examples/mcp-server/README.md` - **Mission Control Extension Example** (documentation): A custom admin panel for TITAN's Mission Control v2 dashboard. Demonstrates how to build and integrate custom UI panels into the Mission Control interface. Evidence: `examples/mission-control-extension/README.md` - **Multi-Agent Orchestration Example** (documentation): Demonstrates TITAN's multi-agent capabilities: spawning sub-agents with constrained toolsets, managing goal hierarchies, and enforcing Command Post budgets. Evidence: `examples/multi-agent-orchestration/README.md` - **Voice Integration Example** (documentation): A LiveKit WebRTC voice agent that demonstrates TITAN's voice pipeline capabilities including real-time speech recognition, TTS synthesis, and WebRTC audio streaming. Evidence: `examples/voice-integration/README.md` - **Package** (package_manifest): { "name": "titan-agent", "version": "7.2.1", "description": "TITAN — the AI agent that provably teaches itself. TypeScript agent framework with replay-verified self-learned skills Muscle Memory , one-minute Welcome Mode setup, a living desk with heartbeat/reminders/proactive memory, multi-agent orchestration, 36-provider routing, approval gates, receipts, evals, and a React Mission Control dashboard. Open-source, MIT.", "author": "Tony Elliott https://github.com/Djtony707 ", "repository": { "type": "git", "url": "git+https://github.com/Djtony707/TITAN.git" }, "license": "MIT", "homepage": "https://github.com/Djtony707/TITAN", "bugs": { "url": "https://github.com/Djtony707/TITAN/issues" }, "… Evidence: `package.json` - **Package** (package_manifest): { "name": "agent-starter-react", "version": "0.1.0", "private": true, "scripts": { "dev": "next dev --turbopack", "build": "next build", "start": "next start", "lint": "next lint", "format": "prettier --write .", "format:check": "prettier --check .", "shadcn:install": "pnpm dlx shadcn@latest add --yes --overwrite @agents-ui/agent-audio-visualizer-bar @agents-ui/agent-audio-visualizer-grid @agents-ui/agent-audio-visualizer-radial @agents-ui/agent-control-bar @agents-ui/agent-session-provider @agents-ui/agent-track-control @agents-ui/agent-track-toggle @agents-ui/agent-chat-transcript @agents-ui/agent-chat-indicator @agents-ui/start-audio-button @agents-ui/agent-audio-visualizer-aura @agents-… Evidence: `titan-voice-ui/package.json` - **Package** (package_manifest): { "name": "titan-mission-control", "private": true, "version": "0.0.1", "type": "module", "scripts": { "dev": "vite", "build": "tsc -b && vite build", "preview": "vite preview" }, "dependencies": { "@tanstack/react-query": "^5.99.2", "@tanstack/react-query-devtools": "^5.99.2", "clsx": "^2.1.1", "lucide-react": "^0.513.0", "motion": "^12.12.2", "react": "^19.1.0", "react-dom": "^19.1.0", "react-grid-layout": "^2.2.3", "react-markdown": "^10.1.0", "react-router": "^7.17.0", "rehype-highlight": "^7.0.2", "remark-gfm": "^4.0.1", "tailwind-merge": "^3.3.0", "y-indexeddb": "^9.0.12", "y-webrtc": "^10.3.0", "yjs": "^13.6.30" }, "devDependencies": { "@tailwindcss/vite": "^4.3.2", "@types/react": "… Evidence: `ui/package.json` - **Package** (package_manifest): { "name": "@titan-agent/example-basic-agent", "version": "1.0.0", "description": "TITAN example: Basic CLI agent with tool usage", "type": "module", "main": "src/index.ts", "scripts": { "start": "tsx src/index.ts", "dev": "tsx watch src/index.ts", "build": "tsc", "typecheck": "tsc --noEmit" }, "keywords": "titan-agent", "example", "ai-agent", "cli" , "author": "Tony Elliott", "license": "MIT", "dependencies": { "titan-agent": "^2026.10.68" }, "devDependencies": { "tsx": "^4.19.2", "typescript": "^5.7.2" } } Evidence: `examples/basic-agent/package.json` - **Package** (package_manifest): { "name": "@titan-agent/example-mcp-server", "version": "1.0.0", "description": "TITAN example: MCP Server exposing tools via JSON-RPC 2.0", "type": "module", "main": "src/index.ts", "scripts": { "start": "tsx src/index.ts", "dev": "tsx watch src/index.ts", "build": "tsc", "typecheck": "tsc --noEmit" }, "keywords": "titan-agent", "example", "mcp", "model-context-protocol", "claude", "cursor" , "author": "Tony Elliott", "license": "MIT", "dependencies": { "titan-agent": "^2026.10.68", "@modelcontextprotocol/sdk": "^0.5.0" }, "devDependencies": { "tsx": "^4.19.2", "typescript": "^5.7.2" } } Evidence: `examples/mcp-server/package.json` - **Package** (package_manifest): { "name": "@titan-agent/example-mission-control-extension", "version": "1.0.0", "description": "TITAN example: Custom admin panel for Mission Control v2", "type": "module", "main": "src/panel.tsx", "scripts": { "dev": "tsx watch src/panel.tsx", "build": "tsc", "typecheck": "tsc --noEmit" }, "keywords": "titan-agent", "example", "mission-control", "react", "admin-panel" , "author": "Tony Elliott", "license": "MIT", "dependencies": { "react": "^19.0.0", "react-dom": "^19.0.0" }, "devDependencies": { "@types/react": "^19.0.0", "@types/react-dom": "^19.0.0", "tsx": "^4.19.2", "typescript": "^5.7.2" } } Evidence: `examples/mission-control-extension/package.json` - **Package** (package_manifest): { "name": "@titan-agent/example-multi-agent-orchestration", "version": "1.0.0", "description": "TITAN example: Multi-agent orchestration with sub-agent spawning, goal hierarchy, and Command Post budgets", "type": "module", "main": "src/index.ts", "scripts": { "start": "tsx src/index.ts", "dev": "tsx watch src/index.ts", "build": "tsc", "typecheck": "tsc --noEmit" }, "keywords": "titan-agent", "example", "multi-agent", "orchestration", "sub-agent", "command-post" , "author": "Tony Elliott", "license": "MIT", "dependencies": { "titan-agent": "^2026.10.68" }, "devDependencies": { "tsx": "^4.19.2", "typescript": "^5.7.2" } } Evidence: `examples/multi-agent-orchestration/package.json` - **Package** (package_manifest): { "name": "@titan-agent/example-voice-integration", "version": "1.0.0", "description": "TITAN example: LiveKit WebRTC voice agent integration", "type": "module", "main": "src/index.ts", "scripts": { "start": "tsx src/index.ts", "dev": "tsx watch src/index.ts", "build": "tsc", "typecheck": "tsc --noEmit" }, "keywords": "titan-agent", "example", "voice", "livekit", "webrtc", "tts", "speech" , "author": "Tony Elliott", "license": "MIT", "dependencies": { "titan-agent": "^2026.10.68", "livekit-client": "^2.7.0", "livekit-server-sdk": "^2.9.0" }, "devDependencies": { "@types/ws": "^8.5.13", "tsx": "^4.19.2", "typescript": "^5.7.2" } } Evidence: `examples/voice-integration/package.json` - **First Steps with TITAN — A Developer's Tutorial** (documentation): First Steps with TITAN — A Developer's Tutorial Evidence: `docs/FIRST-STEPS.md` - **Contributing to TITAN** (documentation): Thank you for your interest in contributing to TITAN. Here's everything you need to get started. Evidence: `CONTRIBUTING.md` - **Agent Introspection Debugging** (skill_instruction): Use this skill when an agent run is failing repeatedly, consuming tokens without progress, looping on the same tools, or drifting away from the intended task. Evidence: `assets/agent-skills/agent-introspection-debugging/SKILL.md` - **API and Interface Design** (skill_instruction): Design stable, well-documented interfaces that are hard to misuse. Good interfaces make the right thing easy and the wrong thing hard. This applies to REST APIs, GraphQL schemas, module boundaries, component props, and any surface where one piece of code talks to another. Evidence: `assets/agent-skills/api-and-interface-design/SKILL.md` - **Browser Testing with DevTools** (skill_instruction): Use Chrome DevTools MCP to give your agent eyes into the browser. This bridges the gap between static code analysis and live browser execution — the agent can see what the user sees, inspect the DOM, read console logs, analyze network requests, and capture performance data. Instead of guessing what's happening at runtime, verify it. Evidence: `assets/agent-skills/browser-testing-with-devtools/SKILL.md` - **CI/CD and Automation** (skill_instruction): Automate quality gates so that no change reaches production without passing tests, lint, type checking, and build. CI/CD is the enforcement mechanism for every other skill — it catches what humans and agents miss, and it does so consistently on every single change. Evidence: `assets/agent-skills/ci-cd-and-automation/SKILL.md` - **Code Review and Quality** (skill_instruction): Multi-dimensional code review with quality gates. Every change gets reviewed before merge — no exceptions. Review covers five axes: correctness, readability, architecture, security, and performance. Evidence: `assets/agent-skills/code-review-and-quality/SKILL.md` - **Code Simplification** (skill_instruction): Inspired by the Claude Code Simplifier plugin https://github.com/anthropics/claude-plugins-official/blob/main/plugins/code-simplifier/agents/code-simplifier.md . Adapted here as a model-agnostic, process-driven skill for any AI coding agent. Evidence: `assets/agent-skills/code-simplification/SKILL.md` - **Context Engineering** (skill_instruction): Feed agents the right information at the right time. Context is the single biggest lever for agent output quality — too little and the agent hallucinates, too much and it loses focus. Context engineering is the practice of deliberately curating what the agent sees, when it sees it, and how it's structured. Evidence: `assets/agent-skills/context-engineering/SKILL.md` - **Continuous Agent Loop** (skill_instruction): This is the v1.8+ canonical loop skill name. It supersedes autonomous-loops while keeping compatibility for one release. Evidence: `assets/agent-skills/continuous-agent-loop/SKILL.md` - **Continuous Learning Skill - DEPRECATED** (skill_instruction): Continuous Learning Skill - DEPRECATED Evidence: `assets/agent-skills/continuous-learning/SKILL.md` - **Debugging and Error Recovery** (skill_instruction): Systematic debugging with structured triage. When something breaks, stop adding features, preserve evidence, and follow a structured process to find and fix the root cause. Guessing wastes time. The triage checklist works for test failures, build errors, runtime bugs, and production incidents. Evidence: `assets/agent-skills/debugging-and-error-recovery/SKILL.md` - **Deprecation and Migration** (skill_instruction): Code is a liability, not an asset. Every line of code has ongoing maintenance cost — bugs to fix, dependencies to update, security patches to apply, and new engineers to onboard. Deprecation is the discipline of removing code that no longer earns its keep, and migration is the process of moving users safely from the old to the new. Evidence: `assets/agent-skills/deprecation-and-migration/SKILL.md` - **Documentation and ADRs** (skill_instruction): Document decisions, not just code. The most valuable documentation captures the why — the context, constraints, and trade-offs that led to a decision. Code shows what was built; documentation explains why it was built this way and what alternatives were considered . This context is essential for future humans and agents working in the codebase. Evidence: `assets/agent-skills/documentation-and-adrs/SKILL.md` - **Doubt-Driven Development** (skill_instruction): A confident answer is not a correct one. Long sessions accumulate context that quietly turns assumptions into "facts" without anyone noticing. Doubt-driven development is the discipline of materializing a fresh-context reviewer — biased to disprove , not approve — before any non-trivial output stands. Evidence: `assets/agent-skills/doubt-driven-development/SKILL.md` - **Frontend UI Engineering** (skill_instruction): Build production-quality user interfaces that are accessible, performant, and visually polished. The goal is UI that looks like it was built by a design-aware engineer at a top company — not like it was generated by an AI. This means real design system adherence, proper accessibility, thoughtful interaction patterns, and no generic "AI aesthetic." Evidence: `assets/agent-skills/frontend-ui-engineering/SKILL.md` - **Git Workflow and Versioning** (skill_instruction): Git is your safety net. Treat commits as save points, branches as sandboxes, and history as documentation. With AI agents generating code at high speed, disciplined version control is the mechanism that keeps changes manageable, reviewable, and reversible. Evidence: `assets/agent-skills/git-workflow-and-versioning/SKILL.md` - **Idea Refine** (skill_instruction): Refines raw ideas into sharp, actionable concepts worth building through structured divergent and convergent thinking. Evidence: `assets/agent-skills/idea-refine/SKILL.md` - **Incremental Implementation** (skill_instruction): Build in thin vertical slices — implement one piece, test it, verify it, then expand. Avoid implementing an entire feature in one pass. Each increment should leave the system in a working, testable state. This is the execution discipline that makes large features manageable. Evidence: `assets/agent-skills/incremental-implementation/SKILL.md` - **Performance Optimization** (skill_instruction): Measure before optimizing. Performance work without measurement is guessing — and guessing leads to premature optimization that adds complexity without improving what matters. Profile first, identify the actual bottleneck, fix it, measure again. Optimize only what measurements prove matters. Evidence: `assets/agent-skills/performance-optimization/SKILL.md` - **Planning and Task Breakdown** (skill_instruction): Decompose work into small, verifiable tasks with explicit acceptance criteria. Good task breakdown is the difference between an agent that completes work reliably and one that produces a tangled mess. Every task should be small enough to implement, test, and verify in a single focused session. Evidence: `assets/agent-skills/planning-and-task-breakdown/SKILL.md` - **Production Audit** (skill_instruction): Use this skill when the user asks whether an application is ready to ship, what could break in production, or what must be fixed before a launch. This is a maintainer-safe rewrite of the stale community production-audit idea: it keeps the useful production-readiness lens and removes unpinned external execution and third-party data sharing. Evidence: `assets/agent-skills/production-audit/SKILL.md` - **Recursive Decision Ledger** (skill_instruction): Use this skill when the user is trying to force deeper computation through repeated rollouts or "Prime Gauss" style recursive prompting. Preserve the useful part: repeated trials, prior memory, fresh information, and explicit marks. Remove the unsafe part: pretending the loop proves certainty. Evidence: `assets/agent-skills/recursive-decision-ledger/SKILL.md` - **Literature Review** (skill_instruction): Use this skill when the task is to find, screen, synthesize, and cite a body of academic or technical literature. Evidence: `assets/agent-skills/scientific-thinking-literature-review/SKILL.md` - **Scholar Evaluation** (skill_instruction): Use this skill to evaluate academic or scientific work with a repeatable rubric. Evidence: `assets/agent-skills/scientific-thinking-scholar-evaluation/SKILL.md` - **Security and Hardening** (skill_instruction): Security-first development practices for web applications. Treat every external input as hostile, every secret as sacred, and every authorization check as mandatory. Security isn't a phase — it's a constraint on every line of code that touches user data, authentication, or external systems. Evidence: `assets/agent-skills/security-and-hardening/SKILL.md` - **Shipping and Launch** (skill_instruction): Ship with confidence. The goal is not just to deploy — it's to deploy safely, with monitoring in place, a rollback plan ready, and a clear understanding of what success looks like. Every launch should be reversible, observable, and incremental. Evidence: `assets/agent-skills/shipping-and-launch/SKILL.md` - **Source-Driven Development** (skill_instruction): Every framework-specific code decision must be backed by official documentation. Don't implement from memory — verify, cite, and let the user see your sources. Training data goes stale, APIs get deprecated, best practices evolve. This skill ensures the user gets code they can trust because every pattern traces back to an authoritative source they can check. Evidence: `assets/agent-skills/source-driven-development/SKILL.md` - **Spec-Driven Development** (skill_instruction): Write a structured specification before writing any code. The spec is the shared source of truth between you and the human engineer — it defines what we're building, why, and how we'll know it's done. Code without a spec is guessing. Evidence: `assets/agent-skills/spec-driven-development/SKILL.md` - **Using Agent Skills** (skill_instruction): Agent Skills is a collection of engineering workflow skills organized by development phase. Each skill encodes a specific process that senior engineers follow. This meta-skill helps you discover and apply the right skill for your current task. Evidence: `assets/agent-skills/using-agent-skills/SKILL.md` - **Verification Loop Skill** (skill_instruction): A comprehensive verification system for TITAN sessions. Evidence: `assets/agent-skills/verification-loop/SKILL.md` - **License** (source_file): Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files the "Software" , to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: Evidence: `LICENSE` - **Test-Driven Development** (skill_instruction): Write a failing test before writing the code that makes it pass. For bug fixes, reproduce the bug with a test before attempting a fix. Tests are proof — "seems right" is not done. A codebase with good tests is an AI agent's superpower; a codebase without tests is a liability. Evidence: `assets/agent-skills/test-driven-development/SKILL.md` - **License** (source_file): Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files the "Software" , to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: Evidence: `titan-voice-ui/LICENSE` - **TITAN Architecture** (documentation): TITAN -- The Intelligent Task Automation Network v5.0.0 "Spacewalk" Evidence: `ARCHITECTURE.md` - **Changelog** (documentation): v7.2.1 — 2026-07-06 — Reliability Mode composes all four disciplines Evidence: `CHANGELOG.md` - **ADR-001: TITAN-Soma — Homeostatic Drives as the Fourth Layer** (documentation): ADR-001: TITAN-Soma — Homeostatic Drives as the Fourth Layer Evidence: `docs/ADR-001-soma.md` - **TITAN Agent Orchestration Hierarchy** (documentation): TITAN Agent Orchestration Hierarchy Evidence: `docs/AGENT-HIERARCHY.md` - **Benchmarks & Performance** (documentation): Performance characteristics of TITAN titan-agent measured on typical development hardware. Evidence: `docs/BENCHMARKS.md` - **F5-TTS Voice Setup — TITAN 3.0** (documentation): TITAN 3.0 uses F5-TTS as its sole TTS engine. No Orpheus, no Qwen3-TTS, no Edge TTS, no browser fallback. Just F5-TTS with zero-shot voice cloning. Evidence: `docs/F5_TTS_VOICE_SETUP.md` - **TITAN FAQ — Frequently Asked Questions** (documentation): TITAN FAQ — Frequently Asked Questions Evidence: `docs/FAQ.md` - **TITAN — Harness Patterns** (documentation): A self-audit of where TITAN stands against the agent-harness ecosystem catalogued in Picrew/awesome-agent-harness https://github.com/Picrew/awesome-agent-harness and the principles in 12 Factor Agents https://github.com/humanlayer/12-factor-agents . Evidence: `docs/HARNESS-PATTERNS.md` - The remaining 20 evidence entries are in `AI_CONTEXT_PACK.json` or `EVIDENCE_INDEX.json`. ## Rules the Host AI Must Follow - **Treat this asset as pre-work context, not a runtime environment.**: The AI Context Pack contains only an evidence-backed understanding of the project, not the project's executable state. Evidence: `docs/autopilot-playbooks/README.md`, `README.md`, `benchmarks/README.md` - **When answering the user, distinguish what can be previewed from what can only be verified after install.**: The consumer value of the pre-install experience comes from reducing bad installs and misjudgments, not from pretending to be a real run. Evidence: `docs/autopilot-playbooks/README.md`, `README.md`, `benchmarks/README.md` ## Questions the User Should Answer First - Which host AI or local environment do you plan to use it in? - Do you just want to experience the workflow first, or are you ready to actually install? - What matters most to you: install cost, output quality, or conflicts with your existing rules? ## Acceptance Checks - Every capability claim can be traced back to a file path in evidence_refs. - AI_CONTEXT_PACK.md does not package previews as a real run. - The user can understand who it fits, what it can do, how to start, and the risk boundaries within 3 minutes. --- ## Doramagic Context Augmentation The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints. ## Human Manual Outline Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph. Host AI hard rules: - Do not treat page titles, section order, summaries, or importance values as factual project evidence. - When explaining the Human Manual outline, state that it is only a reading route or salience signal. - Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph. - **Overview & Getting Started**: importance `high` - source_paths: README.md, ARCHITECTURE.md, CHANGELOG.md, package.json, install.sh - **Core Agent System & Reliability Discipline (Fable-5)**: importance `high` - source_paths: src/agent/agent.ts, src/agent/agentLoop.ts, src/agent/orchestrator.ts, src/agent/specialists.ts, src/agent/planner.ts - **Providers, Channels & Interoperability**: importance `high` - source_paths: src/providers/router.ts, src/providers/anthropic.ts, src/providers/openai.ts, src/providers/google.ts, src/providers/ollama.ts - **Mission Control UI, Skills, Memory & Deployment**: importance `high` - source_paths: ui/src/App.tsx, ui/src/components/shell/TitanShell.tsx, ui/src/components/admin/OverviewPanel.tsx, ui/src/components/command-post/CPDashboard.tsx, ui/src/views/LiveStudio.tsx ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `60b3c927f5cbfc486206c5b0d8a9d5e059e3897c` - inspected_files: `Dockerfile`, `README.md`, `docker-compose.yml`, `package.json`, `docs/ADR-001-soma.md`, `docs/AGENT-HIERARCHY.md`, `docs/BENCHMARKS.md`, `docs/F5_TTS_VOICE_SETUP.md`, `docs/FAQ.md`, `docs/FIRST-STEPS.md`, `docs/HARNESS-PATTERNS.md`, `docs/INTEROP.md`, `docs/MIGRATION.md`, `docs/MIGRATIONS.md`, `docs/MODELS.md`, `docs/PIPELINES.md`, `docs/ROADMAP.md`, `docs/UPGRADING.md`, `docs/V6-ADMIN-BUCKETS.md`, `docs/VOICE.md` Host AI hard rules: - Without repo_clone_verified=true, do not claim that the source code has been read. - Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts. - Without quick_start_verified=true, do not claim that the Quick Start path has run successfully. ## Doramagic Pitfall Constraints These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes. ### Constraint 1: Capability evidence risk requires verification - Trigger: README/documentation is current enough for a first validation pass. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: capability.assumptions | https://github.com/Djtony707/TITAN - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: Security or permission risk requires verification - Trigger: no_demo - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: downstream_validation.risk_items | https://github.com/Djtony707/TITAN - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: Security or permission risk requires verification - Trigger: no_demo - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: risks.scoring_risks | https://github.com/Djtony707/TITAN - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: Maintenance risk requires verification - Trigger: issue_or_pr_quality=unknown。 - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: evidence.maintainer_signals | https://github.com/Djtony707/TITAN - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: Maintenance risk requires verification - Trigger: release_recency=unknown。 - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: evidence.maintainer_signals | https://github.com/Djtony707/TITAN - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.