# boffin - 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 boffin. 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_0004` supported 0.86 - **Users who want to bring professional workflows into a host AI**: The repo contains Skill documents. Evidence: `skills/boffin/SKILL.md`, `skills/boffin-review/SKILL.md` Claim: `clm_0005` 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: `skills/boffin/SKILL.md`, `skills/boffin-review/SKILL.md` Claim: `clm_0001` supported 0.86 - **Multi-Host Install and Distribution** (Verify after install): The project contains plugin or marketplace configuration, indicating it targets install and distribution across one or more AI hosts. Evidence: `.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json`, `.codex-plugin/plugin.json` Claim: `clm_0002` 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_0003` supported 0.86 ## How to Start - `npx boffinit cursor` Evidence: `README.md` Claim: `clm_0006` supported 0.86, `clm_0010` supported 0.86 - `/plugin marketplace add MicSm/boffin` Evidence: `README.md` Claim: `clm_0007` supported 0.86 - `/plugin install boffin@boffin` Evidence: `README.md` Claim: `clm_0008` supported 0.86 - `npx boffinit opencode` Evidence: `README.md` Claim: `clm_0009` supported 0.86, `clm_0011` supported 0.86 - `npx boffinit cursor uninstall` Evidence: `README.md` Claim: `clm_0010` supported 0.86 - `npx boffinit opencode uninstall` Evidence: `README.md` Claim: `clm_0011` supported 0.86 ## Continue-or-Stop Decision Card - **Current recommendation**: Sandbox trial only - **Why**: The project has signals of install commands, host configuration, or local writes; do not go straight into your primary environment—trial it in isolation first. ### 30-Second Read - **What to do now**: Sandbox trial only - **Minimum safe next step**: Run Prompt Preview first; if you still want to install, trial only in an isolated environment - **Do not trust yet**: Real output quality cannot be trusted before install. - **Continuing will touch**: Command execution, Host AI configuration, Local environment or project files ### 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_0004` 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: `skills/boffin/SKILL.md`, `skills/boffin-review/SKILL.md` Claim: `clm_0005` 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: `skills/boffin/SKILL.md`, `skills/boffin-review/SKILL.md` Claim: `clm_0001` supported 0.86 - **Capability exists: Multi-Host Install and Distribution** (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: `.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json`, `.codex-plugin/plugin.json` Claim: `clm_0002` 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_0003` 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_0006` supported 0.86, `clm_0010` supported 0.86 ### What You Cannot Trust Yet - **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: `.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json`, `.codex-plugin/plugin.json`, `AGENTS.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. Evidence: `.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json`, `.codex-plugin/plugin.json` - **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. - **Do the install commands require network access, permissions, or global writes?** (unverified): This affects install risk in both enterprise and personal environments. Evidence: `README.md` ### What Continuing Will Touch - **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: `.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json`, `.codex-plugin/plugin.json`, `AGENTS.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: `.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json`, `.codex-plugin/plugin.json`, `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**: Use a pre-install interactive trial to judge whether the way of working fits; it needs no authorization or environment change. (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.) - **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. - **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_0012` inferred 0.45 - **Host AI plugin or Skill rule conflicts**: New rules may change how the user's existing host AI behaves. Mitigation: Inspect the plugin manifest and Skill files before installing, and test in isolation if needed. Evidence: `.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json`, `.codex-plugin/plugin.json` Claim: `clm_0013` supported 0.86 - **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_0014` 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: `skills/boffin/SKILL.md`, `skills/boffin-review/SKILL.md` Claim: `clm_0001` supported 0.86 - **Multi-Host Install and Distribution**: 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: `.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json`, `.codex-plugin/plugin.json` Claim: `clm_0002` 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_0003` supported 0.86 ### Context Scale - Total files: 76 - Important-file coverage: 40/76 - Evidence index entries: 69 - Role / Skill entries: 2 ### 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 boffin, 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 boffin 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 boffin, 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 2 role / Skill / project-doc entries. - **boffin-review** (skill): Reviews code, diffs, cleanup proposals, and refactors against Boffin's staged architectural guardrails. Use when the user requests a Boffin review, architecture audit, compliance review, cleanup review, or open-ended refactor assessment. Activation hint: When the user's task is highly relevant to the workflow described by “boffin-review”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/boffin-review/SKILL.md` - **boffin** (skill): Activates Boffin's routed architectural guardrails for coding, debugging, refactoring, and design work. Use when the user invokes Boffin or asks to apply ParselFire Core guidance to a software task. Activation hint: When the user's task is highly relevant to the workflow described by “boffin”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/boffin/SKILL.md` ## Evidence Index - Indexed 69 evidence entries. - **Local Target Repositories** (documentation): Clone repositories that you want to run Boffin against into this directory. Evidence: `.repos/README.md` - **Boffin** (documentation): Boffin npm: boffinit is a staff-engineer control layer for AI coding agents: it feeds the agent the architectural constraints for the exact file it is editing and makes it verify the result -- DuckDB case study examples/before-after-cpp.md : a guided refactor landed at +17 / -17 lines with 2,104 assertions passing. Evidence: `README.md` - **External Packs** (documentation): This directory is reserved for third-party or community-maintained pack families that follow the ParselFire Core public format without becoming part of the maintainer-shipped core surface in packs/ . Evidence: `external/README.md` - **Pack Guides** (documentation): This file is NOT intended for LLM consumption. Human-readable guide only. Evidence: `packs/README.md` - **Signatures** (documentation): ParselFire Core reserves a detached GPG signing surface for its public pack files. For now, release numbering is tracked manually in the root VERSION file, and signatures are prepared manually during release packaging. CI-side signing is intentionally deferred until after the initial OSS release. Evidence: `signatures/README.md` - **C++ Architecture Pack Guide** (documentation): This file is NOT intended for LLM consumption. Human-readable guide only. Evidence: `packs/cpp-architecture/README.md` - **Python Architecture Pack Guide** (documentation): This file is NOT intended for LLM consumption. Human-readable guide only. Evidence: `packs/python-architecture/README.md` - **Universal Pack Guide** (documentation): This file is NOT intended for LLM consumption. Human-readable guide only. Evidence: `packs/universal/README.md` - **Public Keys** (documentation): This directory stores ASCII-armored public verification keys for maintainers and accepted external contributors. Evidence: `signatures/pubkeys/README.md` - **Package** (package_manifest): { "name": "boffinit", "version": "0.3.2", "description": "Boffin: staff-engineer layer for AI coding agents. Routes per-edit architectural constraints and requires verification. Not a static AGENTS.md. Install: npx boffinit cursor", "license": "MIT", "author": { "name": "MicSm", "url": "https://github.com/MicSm" }, "homepage": "https://github.com/MicSm/boffin readme", "repository": { "type": "git", "url": "git+https://github.com/MicSm/boffin.git" }, "bugs": { "url": "https://github.com/MicSm/boffin/issues" }, "keywords": "boffin", "parselfire", "cursor", "opencode", "claude-code", "codex", "ai-coding-agent", "guardrails", "code-review", "agent-steering", "review-safe", "code-quality", "refa… Evidence: `package.json` - **Boffin Review** (skill_instruction): Read AGENTS.md at the installed plugin root, two directories above this file. It is authoritative; this skill only activates its review path. Evidence: `skills/boffin-review/SKILL.md` - **Boffin** (skill_instruction): Treat Boffin as active for the coding task. Evidence: `skills/boffin/SKILL.md` - **Marketplace** (structured_config): { "name": "boffin", "owner": { "name": "MicSm" }, "description": "Boffin plugins for routed architectural guardrails.", "plugins": { "name": "boffin", "displayName": "Boffin", "source": "./", "description": "Strict, routed architectural guardrails for AI coding agents, powered by ParselFire Core.", "version": "0.3.2", "author": { "name": "MicSm" }, "category": "productivity", "tags": "architecture", "code-review", "guardrails" } } Evidence: `.claude-plugin/marketplace.json` - **Plugin** (structured_config): { "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json", "name": "boffin", "displayName": "Boffin", "version": "0.3.2", "description": "Strict, routed architectural guardrails for AI coding agents, powered by ParselFire Core.", "author": { "name": "MicSm", "url": "https://github.com/MicSm" }, "homepage": "https://github.com/MicSm/boffin", "repository": "https://github.com/MicSm/boffin", "license": "MIT", "keywords": "architecture", "code-review", "guardrails", "productivity" , "skills": "./skills/", "hooks": "./hooks/claude-codex-hooks.json" } Evidence: `.claude-plugin/plugin.json` - **Plugin** (structured_config): { "name": "boffin", "version": "0.3.2", "description": "Strict, routed architectural guardrails for AI coding agents, powered by ParselFire Core.", "author": { "name": "MicSm", "url": "https://github.com/MicSm" }, "homepage": "https://github.com/MicSm/boffin", "repository": "https://github.com/MicSm/boffin", "license": "MIT", "keywords": "architecture", "code-review", "guardrails", "productivity" , "skills": "./skills/", "hooks": "./hooks/claude-codex-hooks.json", "interface": { "displayName": "Boffin", "shortDescription": "Routed architectural guardrails", "longDescription": "Apply focused architectural constraints, staged reviews, and post-change verification to coding work.", "developerN… Evidence: `.codex-plugin/plugin.json` - **ParselFire Core Portable Routing Contract** (documentation): ParselFire Core Portable Routing Contract Evidence: `AGENTS.md` - **ParselFire Core Portable Routing Contract** (documentation): ParselFire Core Portable Routing Contract Evidence: `CLAUDE.md` - **ParselFire Core** (documentation): ParselFire Core is the routing engine behind Boffin ../README.md . Boffin is the public product and character; ParselFire Core is the exact name of the technical engine underneath it. Evidence: `docs/engine.md` - **Boffin on OpenCode** (documentation): Boffin installs on OpenCode as a project-local host: shared packs, an always-on contract via opencode.json , and native skills and commands. Cursor and OpenCode can coexist in the same project. Evidence: `docs/opencode.md` - **Contributing to Boffin** (documentation): Boffin accepts improvements to the public pack surface, format docs, and release tooling. The repository is intentionally small, so contribution quality matters more than contribution volume. Evidence: `CONTRIBUTING.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` - **C++ Before/After Evidence** (documentation): This note summarizes a guided refactoring experiment against a real C++ project cloned under .repos/ : DuckDB, an analytical in-process SQL database ~39k stars . It uses the current live pack surfaces and fresh verification gathered in this session rather than historical notes. Evidence: `examples/before-after-cpp.md` - **Python Before/After Evidence** (documentation): These notes summarize two guided refactoring experiments against external Python repositories cloned under .repos/ . They use the current live pack surfaces and fresh verification gathered in this session rather than historical notes. Evidence: `examples/before-after-python.md` - **C++ Boundaries Leaf** (documentation): C++ Boundaries Leaf KERNELS EXCLUDES Evidence: `packs/cpp-architecture/boundaries.urf.md` - **C++ Lifecycle Leaf** (documentation): C++ Lifecycle Leaf KERNELS EXCLUDES Evidence: `packs/cpp-architecture/lifecycle.urf.md` - **C++ Architecture Pack Index** (documentation): Portable C++ runtime routing surface for language mechanics, state modeling, concurrency, lifecycle, shared abstractions, and subsystem boundaries. Evidence: `packs/cpp-architecture/pack.urf.md` - **Python Architecture Pack Index** (documentation): Portable Python runtime routing surface for native primitive selection, imports, async lifecycle, runtime ownership, schema boundaries, and cleanup. Evidence: `packs/python-architecture/pack.urf.md` - **Python State-Lifecycle Leaf** (documentation): Python State-Lifecycle Leaf KERNELS EXCLUDES Evidence: `packs/python-architecture/state-lifecycle.urf.md` - **Universal Boundaries Leaf** (documentation): Universal Boundaries Leaf KERNELS EXCLUDES Evidence: `packs/universal/boundaries.urf.md` - **Universal Control-Flow Leaf** (documentation): Universal Control-Flow Leaf KERNELS EXCLUDES Evidence: `packs/universal/control-flow.urf.md` - **Universal Foundations Leaf** (documentation): Universal Foundations Leaf KERNELS EXCLUDES Evidence: `packs/universal/foundations.urf.md` - **Universal Lifecycle Leaf** (documentation): Universal Lifecycle Leaf KERNELS EXCLUDES Evidence: `packs/universal/lifecycle.urf.md` - **Universal Pack Index** (documentation): Language-agnostic runtime entry surface for ParselFire Core. Evidence: `packs/universal/pack.urf.md` - **.gitattributes** (source_file): bin/ .js text eol=lf Evidence: `.gitattributes` - **Citation** (source_file): cff-version: 1.2.0 message: "If you reference Boffin, cite this repository." title: "Boffin" type: software authors: - name: "MicSm" repository-code: "https://github.com/MicSm/boffin" url: "https://github.com/MicSm/boffin" license: MIT keywords: - ai-coding-agents - code-review - agent-steering Evidence: `CITATION.cff` - **Boffin Runtime** (source_file): function getStatePath options = ⋮---- function readProfile options = ⋮---- function setProfile value, options = ⋮---- function detectHost env = process.env ⋮---- function formatHookOutput event, profile, context, options = ⋮---- function writeHookOutput event, profile, context, options = ⋮---- function parseHookInput value ⋮---- function runHook handler, options = ⋮---- function finish forceExit = false ⋮---- function onData chunk ⋮---- function onEnd ⋮---- function onError Evidence: `hooks/boffin-runtime.js` - **Cli** (source_file): function parseArgs argv ⋮---- function operationsForHost host ⋮---- async function runCli argv, options = Evidence: `lib/cli.js` - **Installer** (source_file): function isMissing error ⋮---- async function lstatIfExists filePath ⋮---- async function pathExists filePath ⋮---- function rewritePackReferences content ⋮---- function generateManagedRule content ⋮---- function generateBoffinAgents content ⋮---- function validateManifest manifest ⋮---- function validateOpenCodeManifest manifest ⋮---- async function readManifest target ⋮---- async function readOpenCodeManifest target ⋮---- async function listTreeFiles root, relativeDirectory = '' ⋮---- async function copyEntry source, destination ⋮---- async function treeHasUnknownFiles existingDirectory, relativeDirectory, previousManagedFiles, ⋮---- async function mergeUnknownPackFiles existingDirectory,… Evidence: `lib/installer.js` - **Paths** (source_file): function isMissing error ⋮---- async function findRepoRoot startDirectory = process.cwd ⋮---- async function resolveTarget target, cwd = process.cwd ⋮---- function toPosixPath value ⋮---- function isAllowedManagedPath value ⋮---- function isAllowedOpenCodeManagedPath value ⋮---- function validateManagedPathShape value ⋮---- function validateManagedPath value ⋮---- function validateOpenCodeManagedPath value ⋮---- function managedPathToAbsolute target, managedPath ⋮---- function openCodeManagedPathToAbsolute target, managedPath ⋮---- function projectPathToAbsolute target, relativePath Evidence: `lib/paths.js` - **Check Versions** (source_file): readVersion manifest ⋮---- function readText filePath ⋮---- function readJson relativePath ⋮---- function main Evidence: `scripts/check-versions.js` - **Check Adapter Copies** (source_file): ROOT = Path file .resolve .parents 1 CANONICAL PATH = Path "AGENTS.md" ⋮---- def identity text: str - str ⋮---- def strip frontmatter text: str - str ⋮---- @dataclass frozen=True class TextAdapterCheck ⋮---- rel path: Path label: str normalize: Callable str , str = identity ⋮---- TEXT ADAPTER CHECKS: tuple TextAdapterCheck, ... = ⋮---- MANIFEST ADAPTER PATHS: tuple Path, ... = Path "gemini-extension.json" , SHARED SKILL PATHS: tuple Path, ... = INSTRUCTION BUILDER PATH = Path "hooks/boffin-instructions.js" HOOK WRAPPER PATH = Path "hooks/claude-codex-hooks.json" PLUGIN MANIFEST PATHS: tuple Path, ... = MARKETPLACE MANIFEST PATH = Path ".claude-plugin/marketplace.json" ⋮---- def read text re… Evidence: `scripts/check_adapter_copies.py` - **Pack Lint** (source_file): ROOT = Path file .resolve .parents 1 PACKS DIR = ROOT / "packs" ROUTING RULE PATH = ROOT / ".cursor" / "rules" / "boffin-pack-routing.mdc" AGENTS CONTRACT PATH = ROOT / "AGENTS.md" STAGE SUMMARY PATHS = ROUTING RULE PATH, AGENTS CONTRACT PATH MAX SCOPE REPEATS = 5 HEADING RE = re.compile r"^ ⋮---- tokens: list str = ⋮---- def parse urf file path: Path, state: LintState - list Record ⋮---- records: list Record = current section = "" ⋮---- stripped = line.strip ⋮---- heading match = HEADING RE.match stripped ⋮---- current section = heading match.group "name" ⋮---- parts = stripped.split " " record id = parts 0 tokens = tuple parts 1: fields: dict str, str = {} ⋮---- def parse stage record: Re… Evidence: `scripts/pack_lint.py` - **Pack Signatures** (source_file): ROOT = Path file .resolve .parents 1 DEFAULT PACKS DIR = ROOT / "packs" SIGNATURES PACKS DIR = ROOT / "signatures" / "packs" ⋮---- @dataclass frozen=True class OperationResult ⋮---- file path: Path ok: bool message: str ⋮---- def parse args - argparse.Namespace ⋮---- common = argparse.ArgumentParser add help=False ⋮---- parser = argparse.ArgumentParser subparsers = parser.add subparsers dest="command", required=True ⋮---- sign parser = subparsers.add parser ⋮---- def resolve target dir raw target dir: Path - Path ⋮---- def relative path path: Path - str ⋮---- def iter markdown files target dir: Path - list Path ⋮---- def signature path for file path: Path - Path ⋮---- relative to packs = fi… Evidence: `scripts/pack_signatures.py` - **C++ Pack Activation** (source_file): - Load packs/cpp-architecture/pack.urf.md . - Use its ROUTING and LEAVES records for leaf selection. - Use its STAGE-REFS records to gather the family K ids and their mirrored X ids at each stage of the walk. Evidence: `.cursor/rules/boffin-cpp-routing.mdc` - **Pre-Flight Review and Post-Change Audit** (source_file): Pre-Flight Review and Post-Change Audit Evidence: `.cursor/rules/boffin-post-change-audit.mdc` - **Maintainer 75C5C154F685E4Ef** (source_file): -----BEGIN PGP PUBLIC KEY BLOCK----- Evidence: `signatures/pubkeys/maintainer-75C5C154F685E4EF.asc` - **ParselFire Core Portable Routing Contract** (documentation): ParselFire Core Portable Routing Contract Evidence: `.clinerules/boffin.md` - **Changelog** (documentation): All notable changes to this project are documented in this file. Evidence: `CHANGELOG.md` - **ParselFire Core Portable Routing Contract** (documentation): ParselFire Core Portable Routing Contract Evidence: `.agents/rules/boffin.md` - **ParselFire Core Portable Routing Contract** (documentation): ParselFire Core Portable Routing Contract Evidence: `.kiro/steering/boffin.md` - **ParselFire Core Portable Routing Contract** (documentation): ParselFire Core Portable Routing Contract Evidence: `.windsurf/rules/boffin.md` - **C++ Concurrency Leaf** (documentation): C++ Concurrency Leaf KERNELS EXCLUDES Evidence: `packs/cpp-architecture/concurrency.urf.md` - **C++ Contracts Leaf** (documentation): C++ Contracts Leaf KERNELS EXCLUDES Evidence: `packs/cpp-architecture/contracts.urf.md` - **C++ Core Leaf** (documentation): C++ Core Leaf KERNELS EXCLUDES Evidence: `packs/cpp-architecture/core.urf.md` - **C++ Shared-Abstractions Leaf** (documentation): C++ Shared-Abstractions Leaf KERNELS EXCLUDES Evidence: `packs/cpp-architecture/shared.urf.md` - **C++ State-Outcome Modeling Leaf** (documentation): C++ State-Outcome Modeling Leaf KERNELS EXCLUDES Evidence: `packs/cpp-architecture/state-modeling.urf.md` - **Python Async-Surfaces Leaf** (documentation): Python Async-Surfaces Leaf KERNELS EXCLUDES Evidence: `packs/python-architecture/async-surfaces.urf.md` - **Python Boundaries-Cleanup Leaf** (documentation): Python Boundaries-Cleanup Leaf KERNELS EXCLUDES Evidence: `packs/python-architecture/boundaries-cleanup.urf.md` - **Python Native-Primitives Leaf** (documentation): Python Native-Primitives Leaf KERNELS EXCLUDES Evidence: `packs/python-architecture/native-primitives.urf.md` - **Python Runtime-Bootstrap Leaf** (documentation): Python Runtime-Bootstrap Leaf KERNELS EXCLUDES Evidence: `packs/python-architecture/runtime-bootstrap.urf.md` - The remaining 9 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: `.repos/README.md`, `README.md`, `external/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: `.repos/README.md`, `README.md`, `external/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 and Installation**: importance `high` - source_paths: README.md, package.json, LICENSE, CITATION.cff, CREDITS - **ParselFire Core Engine**: importance `high` - source_paths: docs/engine.md, bin/boffinit.js, lib/cli.js, lib/installer.js, lib/paths.js - **Packs and Constraint Routing**: importance `high` - source_paths: packs/README.md, packs/universal/pack.urf.md, packs/universal/foundations.urf.md, packs/universal/control-flow.urf.md, packs/universal/lifecycle.urf.md - **Host Integrations**: importance `high` - source_paths: docs/opencode.md, lib/opencode-templates.js, .claude-plugin/marketplace.json, .claude-plugin/plugin.json, .codex-plugin/plugin.json - **Skills, Profiles and Workflows**: importance `medium` - source_paths: skills/boffin/SKILL.md, skills/boffin-review/SKILL.md, hooks/boffin-activate.js, hooks/boffin-mode-tracker.js, hooks/boffin-runtime.js - **Security, Signatures and Trust**: importance `medium` - source_paths: signatures/README.md, signatures/pubkeys/README.md, signatures/pubkeys/maintainer-75C5C154F685E4EF.asc, scripts/pack_signatures.py, scripts/pack_lint.py - **Case Studies and Evidence**: importance `high` - source_paths: examples/before-after-cpp.md, examples/before-after-python.md - **Operations, Scripts and Maintenance**: importance `low` - source_paths: scripts/check-versions.js, scripts/check_adapter_copies.py, scripts/pack_lint.py, scripts/pack_signatures.py, .repos/README.md ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `ac5249b34ed2b1951e9d4e89aeabd56e0d77f557` - inspected_files: `README.md`, `package.json`, `docs/engine.md`, `docs/opencode.md`, `examples/before-after-cpp.md`, `examples/before-after-python.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://news.ycombinator.com/item?id=49060279 - 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://news.ycombinator.com/item?id=49060279 - 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://news.ycombinator.com/item?id=49060279 - 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://news.ycombinator.com/item?id=49060279 - 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://news.ycombinator.com/item?id=49060279 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.