_b00t_

Canonical b00t reviewer capability — adversarial multi-framework code/datum review. Shared across all harnesses (Claude Code, opencode, Hermes, b00t-cli). Loaded via: b00t learn reviewer, or by harness-specific role supplements.

Remove AI-generated artifacts from code. Three-phase certainty-graded cleanup. Use after any AI implementation session or before PR creation.

8-phase agile workflow — strategy→ideate→brainstorm→plan→work→review→compound→pulse. State machine with FOL-guarded transitions, gh-issues backlog, executable just harness. Inspired by everyinc/compound-engineering-plugin.

Australian crypto tax treatment per ATO guidance QC 53725. Crypto assets are CGT assets under ITAA 1997 s 108-5. Each disposal triggers CGT event A1. Covers personal-use exception, trading stock test, and the 50% CGT discount.

Australian R&D Tax Incentive (RDTI) — ITAA 1997 Division 355. Covers eligibility criteria for core and supporting R&D activities, registration with AusIndustry/IP Australia, expenditure categories, offset rates, and the company size threshold test.

Evidence graph construction for tax audit trails. Each Satisfies check emits EvidenceNode structs with Blake3 content hashes. Evidence chains are tamper-evident and link legislative citations to factual findings.

ISO and IFRS accounting standards used in the Tax-Lawyer Platform: ISO 20022 (financial messaging), IFRS 9 (financial instruments), LEI (ISO 17442), and ISO 4217 (currency codes). Grounds monetary domain objects in formal standards.

MCP tool design patterns for the Tax-Lawyer Platform. Thin Satisfies wrappers (<=10 lines per handler), TaxArgs contract types, and the full tool name taxonomy for ledgerr_tax MCP actions.

UFO (Unified Foundational Ontology) stereotypes and the Satisfies<C> trait pattern. Foundation for all Tax-Lawyer Platform domain objects. Every domain struct MUST declare its UfoCategory and implement Satisfies<ConstraintType>.

Root dispatch skill for the Tax-Lawyer Platform. Grounds multi-jurisdiction R&D and crypto tax analysis in UFO ontology stereotypes with Satisfies constraint verification and Blake3-hashed evidence chains for ATO/IRS audit.

US crypto tax treatment under IRS guidance. Crypto as property (Notice 2014-21). Cost basis methods under Rev. Proc. 2024-28 safe harbor. Capital gains/losses, Form 8949/Schedule D, staking income, mining, and DeFi considerations.

US R&D Tax Credit under IRC Section 41 (Internal Revenue Code). The 4-part test for qualifying research, QRE categories (wages, supplies, contract), ASC vs Regular Credit, Form 6765 filing requirements, and AU-parent/US-sub structure considerations.

GitHub issue triage and integration review agent for the b00ty-verse. Dogfoods b00t's grok RAG subsystem to research an issue topic, then posts a structured integration review on the GH issue. Evaluates external tools/frameworks/libraries for potential integration into the b00t ecosystem. Output is a machine-parseable review comment covering: datum creation, integration level, overlap analysis, capability gaps, and recommended next actions.

b00t hooks implementation status — Claude Code hooks (PostToolUse/PreToolUse/SessionStart) and git hooks (pre-commit/pre-push)

Bayesian reasoning: beliefs are probabilities; evidence updates them proportionally.

|-

Canonical datum authoring conventions: [b00t] required fields, [b00t.skill] tags, tail-map footer.

|-

Datum types (skill, cli, mcp, agent, role, gate, schema, hardware) with [b00t] required fields, skill-specific fields, tail-map format, and forbidden fields.

First-principles reasoning: refuse inherited assumptions; derive from base truths.

Five Whys (Toyota): iterate "why?" until you reach a systemic/actionable root cause.

IDEO design thinking: solve the right problem before solving the problem correctly.

Kaizen (改善): every process has waste; eliminate it incrementally.

|-

MECE (Mutually Exclusive, Collectively Exhaustive): the McKinsey structuring principle.

Occam's Razor (William of Ockham): among competing explanations, prefer the one with fewest assumptions.

Pre-mortem (Gary Klein): before starting, assume the project has catastrophically failed.

Rubber duck debugging: explain the problem to a non-expert (or inanimate object) step by step.

Rust trait object layout — DST fat pointers, vtable placement, generic last-field coercion surprise.

|-

Six Sigma: reduce defects to 3.4 per million by eliminating variance.

Socratic method: expose false beliefs by disciplined questioning, not assertion.

.tomllm / .tomllmd = valid TOML + enriched # comment conventions for LLM context.

TRIZ (Theory of Inventive Problem Solving): contradictions are solvable without tradeoffs.

Rust development skill — requires rust-doc MCP server. Enforces agentic guards for safe code generation.

Visual process documentation — SysMLv2/KerML flow charts, state machines, and health metrics from hive nodes

Access the b00t maintenance loop — check status, view cake token balance, confirm exercise reminders, and inspect the research queue. The 👍🏻/👎🏻 vote tokens feed the probabilistic cake lottery resolved at pre-commit review.

CLI-first AWS orchestration skill for Lambda, ECS/Fargate, and S3 workflows rooted in `.☁️` runbooks.

Design and implement a Rust interface library in l3dg3rr that acts as a feature-configurable lifecycle manager for b00t processes. The library compliantly implements init → operate → terminate → lifecycle maintenance of miscellaneous process surfaces (MCP servers, daemons, sidecars) with deterministic governance controls. Uses the autoresearch pattern (karpathy/autoresearch): agent reads program.md, iterates on the library, experiments autonomously.

Helps work with the b00t datum system - TOML-based configuration for AI models, providers, and services. Datums are stored in ~/.dotfiles/_b00t_/ and specify WHICH environment variables are required (not the values). Enables DRY approach by centralizing configuration in Rust, exposed to Python via PyO3.