Compendium

TaxProfessional + Suits adjacent-repo audit

6 min read

Adjacent-repo audit — TaxProfessional + Suits

Snapshot date: 2026-05-23 (audit performed 2026-05-24 in-session). Both repos are private; this report lists structural facts only — no client identifiers, financial figures, or matter-specific content.

Scope

Two repos sit adjacent to the vault and have not been touched in the current session. Both moved out of d:\Vault\AI Vault\ previously and are now standalone:

RepoPathRemote (private)
TaxProfessionald:\Projects\TaxProfessionalgithub.com/adamhudson777/TaxProfessionals
Suitsd:\Projects\Suitsgithub.com/adamhudson777/Suits

Repo 1 — TaxProfessional

Git state

  • Branch: main, clean working tree.
  • Sync: 0 commits ahead, 0 behind origin/main.
  • Commit history: 1 commit total — 7492be7 Initial commit: TaxProfessional project root (2026-05-20).
  • This is a freshly seeded repo — all code came over in one bulk commit and has not been iterated on yet.

Structure (top-level)

TaxProfessional/
  .claude/        # agent + command definitions
  research/       # placeholder (.gitkeep only)
  scripts/        # placeholder (.gitkeep only)
  .gitignore
  CLAUDE.md       # full project charter (12 KB, 156 lines)
  • Total markdown files: 9 (1 CLAUDE.md, 7 agents, 1 slash command).
  • No README.md — CLAUDE.md plays that role (mission, rules, KB layout in vault, workflow contract, source roster, agent catalog).

Agents (.claude/agents/) — confirmed 7 present

AgentSizeCanonical tag
tax-researcher.md6.0 KBtax-research
tax-strategist.md7.9 KBtax-strategy
entity-tax-specialist.md7.3 KBtax-entity
state-tax-specialist.md7.3 KBtax-salt
tax-knowledge-curator.md4.4 KBtax-curation
tax-update-watcher.md8.5 KBtax-updates
bookkeeper.md9.7 KBbookkeeping

Matches the 7-agent inventory documented in CLAUDE.md. All agent files dated 2026-05-20 (initial commit) — none have been edited since.

Commands

  • .claude/commands/tax-updates.md — /tax-updates [weekly|monthly|quarterly] slash command invoking the tax-update-watcher agent.
  • One command only; no other slash commands defined.

TODO/active-work signals

  • No TODO / FIXME / TBD / TKTK markers anywhere in the repo.
  • research/ and scripts/ are empty (placeholder .gitkeep files, dated 2026-05-20).
  • Zero files modified in the last 30 days outside of the initial commit. Repo has been dormant since seed.
  • Canonical knowledge-base content lives in the vault at d:\Vault\AI Vault\TaxProfessional\ (per the CLAUDE.md design — this repo is the agent infrastructure, the vault holds the KB content). Vault content was not audited in this pass.

Highest-value next moves (TaxProfessional)

  1. Seed the vault KB. The repo’s design assumes a populated TaxProfessional/ folder in the vault — but the agents have no notes to query yet. Highest-leverage first task: have tax-researcher build out Federal/IRC/, Federal/Regulations/, and Filings/Calendar.md for the entities the operator actually touches (sole prop, multi-member LLC, S-corp).
  2. Run the tax-update-watcher once to establish a baseline Updates/ log. Currently no historical entries exist, so the next run has no prior state to compare against.
  3. Populate research/ with a working notebook or two. The directory is committed empty. Either remove it from the tree, or seed it with the actual research scaffolding the scripts will reference (per CLAUDE.md, scripts may help with extraction from IRS/court bulk corpora).
  4. Stand up Books/ writes via the bookkeeper agent. The agent file is 9.7 KB (largest of the seven) but has not been invoked — no entries logged anywhere visible. First close cycle would prove the cluster works end-to-end.
  5. Add a minimal README.md or pointer file that explains the repo-vs-vault split, since CLAUDE.md is targeted at agents and not human onboarding. Optional — only if the repo will ever be browsed standalone.

Repo 2 — Suits

Git state

  • Branch: main, clean working tree.
  • Sync: 0 commits ahead, 0 behind origin/main.
  • Last 6 commits (subjects, no quoted matter detail):
    1. 8b9abdf Convert wikilinks for standalone-vault use
    2. 0205a2d Update internal path references from vault-relative to d:/Projects/Suits/
    3. 1572c98 11 case briefs, 5 playbooks, 3 new matters, currency snapshot
    4. 6311135 Document 3dCreation final follow-ups (cross-project reference)
    5. 8ce9860 Document 3dCreation final follow-ups
    6. 19ec380 Document 3dCreation vault persistence + LLM tool-calling
  • Most recent commit on the standalone repo: 2026-05-22 (move-out housekeeping + wikilink conversion).

Structure (top-level)

Suits/
  _MOC.md                    # map of content
  Agents/                    # Suits-Counsel persona
  Cases/                     # 12 case-law notes + 00-Index
  KnowledgeBase/             # 14 doctrine + 7 school-perspective notes
  Matters/                   # 5 matter folders + index + 2 closed/executed
  Operations/                # 1 ops note (email capability)
  Playbooks/                 # 14 playbooks + 00-Index
  Protected/                 # Registry of protected persons
  System/                    # Mission, Disclaimer, Operating-Principles, Annual-Review, Outbound/
  • Total markdown files: 86.
  • _MOC.md build status checklist: skeleton DONE; heavy knowledge base, playbooks, canonical cases all marked unchecked despite the contents being substantially built out — checklist is stale.

Active matters (Matters/)

Five matter subfolders following the documented YYYY-MM-DD-short-name/ template (intake → doctrine-map → tactical-options → recommendation → action-log):

Matter slugLast touchedFiles
2026-05-03-DEMO-cosign-request2026-05-225 (00-04, full template)
2026-05-05-IncomeProject-customer-facing-legal-templates2026-05-226 (extended template — adds engine-licensing-summary)
2026-05-05-Studio516-entity-status2026-05-245 (intake + action-log + 3 email-body HTMLs) — most recently active
2026-05-23-hudson-entity-classification-reconciliation2026-05-245 (intake → evidence → analysis → recommendation → memo)
2026-05-23-rdpmaster-eula-privacy-review2026-05-235 (intake → license-review → privacy-review → redlines → memo)

Plus 2 closed/executed matters at the root of Matters/ (operating agreement + voice-source license — both executed 2026-05-07 per index).

TODO/active-work signals

  • 8 files contain TODO / TBD markers, all under Matters/:
    • 5 of 5 files in Matters/2026-05-23-rdpmaster-eula-privacy-review/ — placeholders inside the redline drafts.
    • Files in Matters/2026-05-23-hudson-entity-classification-reconciliation/ and the 2026-05-02 executed matters.
    • These are normal in-document markers (e.g., “SKU TBD”, “address placeholder”) tracked in the matter intake/memo files — not orphaned tasks.
  • Currency snapshot (KnowledgeBase/_Currency-Snapshot.md) has explicit “next due 2026-08-03” quarterly re-verification deadline.
  • 87 files (effectively the whole repo) show modified-within-30-days, but that is an artifact of the 2026-05-22 wikilink-conversion commit rewriting nearly every note. True semantic activity is in the 5 matter folders listed above.

Highest-value next moves (Suits)

  1. Refresh _MOC.md build-status checklist. The skeleton task is the only one ticked, but Cases (12 briefs), Doctrine (14 areas), Playbooks (14 procedures), and SchoolPerspectives (7) are all substantively populated. Update the checkboxes to reflect reality so the file stops misleading future sessions.
  2. Close out the two 2026-05-23 matters with 05-closing-memo.md. Both rdpmaster-eula-privacy-review and hudson-entity-classification-reconciliation have reached 04-memo-to-operator.md but neither has a closing memo per the documented template. Add closing memos and move them to a “Closed / Executed” section of Matters/00-Index.md when the operator confirms.
  3. Schedule the next currency-snapshot re-verification. _Currency-Snapshot.md says next-due 2026-08-03. Put a reminder mechanism in place (cron-scheduled /loop or a calendar item) so the OBBBA-era dollar figures don’t go stale.
  4. Studio516-entity-status matter has no 01-doctrine-map.md / 02-tactical-options.md / 03-recommendation.md — it jumped from intake to action-log. Either backfill the missing steps or document why it skipped them (likely because the matter is corporate-housekeeping rather than adversarial — but should be noted explicitly).
  5. Annual-Review-Schedule.md exists in System/ but cadence cross-checks weren’t audited. Worth a one-pass review of which doctrine notes are due for re-verification this quarter, given the OBBBA-driven tax/estate changes the currency snapshot already captured.

Cross-repo observations

  • Both repos are synced with origin and have clean working trees — no commit/push action needed for either.
  • Both moved out of the vault in the same window (TaxProfessional initial commit 2026-05-20; Suits standalone-repo conversion 2026-05-22). The move-out is complete but neither has been iterated on heavily since.
  • The TaxProfessional charter explicitly references Suits as a peer cluster (cross-project handoff for “does Indiana need a separate sales-tax registration”). That handoff path is documented but has not been exercised — no cross-references from TaxProfessional agent notes back to Suits, partly because TaxProfessional has no agent notes yet.
  • Both clusters share the email-capability ops doc (tax@hudsonenterprisesllc.com for Tax, parallel cluster address for Suits via Operations/2026-05-05-email-capability-available.md). The infrastructure is there; usage is light.

Files referenced in this audit

  • d:\Projects\TaxProfessional\CLAUDE.md
  • d:\Projects\TaxProfessional\.claude\agents\*.md (7 files)
  • d:\Projects\TaxProfessional\.claude\commands\tax-updates.md
  • d:\Projects\Suits\_MOC.md
  • d:\Projects\Suits\Matters\00-Index.md
  • d:\Projects\Suits\KnowledgeBase\_Currency-Snapshot.md

Graph View