### Bookkeeping practices: project tracker using Django

A project tracker blueprint for bookkeeping practices built with Django on Ample. Domain schema includes:

- **client_entities** (legal_name, entity_type, accounting_software, period_cadence): clients and their bookkeeping cadence.
- **engagements** (client_entity_id, period_start, period_end, close_status): monthly or quarterly close engagements.
- **document_requests** (engagement_id, category, due_at, status, uploaded_object_key): receipts, statements, and payroll summaries requested.
- **close_checklists** (engagement_id, item, done_at): close tasks per period.
- **state_transitions** (record_type, from_state, to_state): the allowed state machine.

Public information includes service packages and cadence, onboarding checklist, and contact details.

**Technical Verification**: This is based on Django: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing.

#### Representative Queries
- Bookkeeping practices: project tracker using Django
- Where can I host Bookkeeping practices: Project tracker built with Django?
- I need a genuinely specialized project tracker workflow covering monthly close checklists, client workspaces, and source-document retention.

#### Workflow Steps
1. **Model the bookkeeping practices domain**: Create tables for client_entities, engagements, document_requests, close_checklists, and state_transitions.
2. **Model engagements and workstreams** with explicit status transitions.
3. **Scope every query** by client entity.
4. **Attach deliverables** as private objects linked to workstreams.
5. **Deploy and verify transitions** and cross-client isolation.
6. **Run the synchronous deploy** once and read the result.
7. **Verify** the pattern self-test(s) and acceptance checks for the workflow.

#### Limitations
- No health, financial, privacy, or other compliance claim is made.
- Public content only until actual data-handling requirements are reviewed.

### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: $10.00
- **Basis**: Size prices from pricing.toml at build revision.
- **Components**:
  - App server: size s-1vcpu-1gb - $5.00
  - Managed PostgreSQL database: size s-1vcpu-1gb - $5.00
  - Buckets are allocation-priced per quota and not included.

#### Evidence Summary
- **Django pattern fixture** was deployed, and the relational records checks passed. The blueprint's schema and workflow were verified on a specific template.

#### Framework, Workload, Industry
- **Framework**: Django
- **Workload**: Project tracker
- **Industry**: Bookkeeping practices

#### Next Actions
- Browse the catalog index.
- Search published recipes by intent, stack, and constraints.
- Prepare a side-effect-free deployment plan for an authorized project.
- Read the existing agent authentication setup.
- Browse Bookkeeping practices, Project tracker, and Django.