sherpa-tax-rule-studio

README

No README.

STATUS

---
type: project-status
project: sherpa-tax-rule-studio
last_updated: 2026-04-27
---

# STATUS — sherpa-tax-rule-studio

*The freshest file. Answers "where am I on this project?" Updated at the end of every substantive session.*

---

## Current state

<One short paragraph: what state is the project in right now? Mid-build? Shipped MVP? Stalled waiting on something? Be concrete.>

## In progress

- [ ] <What's actively being worked on. If nothing, write "Nothing in flight.">

## Next up

1. <The next thing to pick up when work resumes.>
2. <The thing after that, if obvious.>

## Blocked / waiting on

<External dependencies, decisions you need from someone, vendor responses, etc. "Nothing blocking" is a fine answer.>

## Known issues

<Bugs you know about but haven't fixed, edge cases not yet handled, debt you've taken on. Be specific so future-you doesn't get blindsided.>

## Recent wins

- 2026-04-27: <What was completed in the last session or two. Concrete, with dates.>

## Last session recap

*2026-04-27* — <One paragraph: what got done, what was learned, anything surprising. Read this first when picking up the project after a break.>

DECISIONS

---
type: project-decisions
project: sherpa-tax-rule-studio
last_updated: 2026-04-27
---

# DECISIONS — sherpa-tax-rule-studio

*Architectural and scope choices. Append-only log. Each entry is a decision that shouldn't be re-litigated without new information. If you find yourself reopening a decision, either add a new entry that overrides the old (and say why) or leave both so the history is visible.*

---

## How to use this file

Each decision gets a dated entry with: what was decided, why, what was considered instead, and what would change our mind. Never delete entries — if a decision is reversed, add a new one that supersedes it.

---

## 2026-04-27 — <Short decision title>

**Decision:** <what we chose>

**Context:** <the problem or question that forced a choice>

**Alternatives considered:** <what else was on the table and why we passed>

**Reasoning:** <why this option won>

**Would reconsider if:** <what new information would flip this>

---

## 2026-04-27 — <Short decision title>

**Decision:**

**Context:**

**Alternatives considered:**

**Reasoning:**

**Would reconsider if:**

---

<!-- Append new entries at the top. Older decisions remain below. -->

MEMORY

---
type: project-memory
project: sherpa-tax-rule-studio
last_updated: 2026-04-27
---

# MEMORY — sherpa-tax-rule-studio

*Standing facts, preferences, and accumulated context. Long-lived — not "what I did yesterday" (that's STATUS.md). Update when you learn something worth keeping.*

---

## Purpose and scope

<Why this app exists, who uses it, what problem it solves. 2-3 sentences max.>

## Domain knowledge

<Rules of the domain that Claude should know before making changes. For tax apps: the specific IRS rules this module implements, state conformity notes, edge cases. For non-tax apps: business rules, workflows, naming conventions specific to this app's world.>

## User preferences discovered

<Things Ken has said he prefers, or patterns that work / don't work. Example: "Ken prefers server-rendered HTML over SPAs for internal tools." "Don't auto-format tax return numbers with commas on input, only on display.">

## Integrations and external systems

<APIs, webhooks, third-party services this app talks to. Auth patterns, rate limits, quirks.>

## Gotchas and lessons learned

<The things that have bitten us. Non-obvious behavior, debugging dead-ends, environment quirks. Write these when they happen so the next session doesn't repeat the mistake.>

## Data model highlights

<Key tables/models and what's non-obvious about them. Don't duplicate the schema — reference it. Focus on the things you'd warn someone about.>

CLAUDE.md

# Sherpa Tax Rule Studio

## What This Is
A standalone tax law specification engine. NOT a tax prep app.
Ken (CPA) uses it to author structured, machine-readable rule packages
grounded in cited, versioned authority sources. Output gets handed to
coding agents to implement in tts-tax-app.

## Tech Stack
- Backend: Django 5.2 LTS + Django REST Framework
- Frontend: Vite + React 19 + TypeScript (SPA)
- Styling: Tailwind CSS (no hardcoded hex colors)
- Database: Supabase Postgres (own project, NOT shared with tts-tax-app)
- Serving: Django + WhiteNoise serves React SPA (same origin)
- Python deps: Poetry (Python 3.13)
- JS deps: npm
- Config: python-dotenv

## Project Structure
```
server/          — Django project (settings, urls, wsgi)
specs/           — Django app: form specification models
                   (TaxForm, FormFact, FormRule, FormLine,
                    FormDiagnostic, TestScenario)
sources/         — Django app: authority source models
                   (AuthoritySource, AuthorityExcerpt, AuthorityTopic,
                    RuleAuthorityLink, AuthorityFormLink, AuthorityVersion,
                    JurisdictionConformitySource, SourceFeedDefinition)
client/          — React/Vite/TypeScript SPA
client/src/      — React source code
tests/           — pytest + pytest-django tests
staticfiles/     — WhiteNoise collected static files (gitignored)
```

## Commands
- Backend: `poetry run python manage.py runserver`
- Frontend dev: `cd client && npm run dev`
- Tests: `poetry run pytest`
- Migrations: `poetry run python manage.py makemigrations && poetry run python manage.py migrate`
- Build frontend: `cd client && npm run build`
- Seed data: `poetry run python manage.py seed_sources`

## Database
- Own Supabase project (not shared with tts-tax-app)
- UUID primary keys, created_at/updated_at timestamps
- No firm_id (single-user tool)

## Key Design Principles
- Every rule must be grounded in cited, versioned authority
- Authority linkage via RuleAuthorityLink

…(truncated for upload size)

Diary mentions

No recent diary mentions for this app.