Skip to content

Ticket System

Repo: savvydealer-adam/ticket-system · Path: not cloned to ~/ · Owner: Adam Status: Dormant (docs/specs only; no implementation yet) · % Done: 20 · Last commit: 2026-02-28 Deployed: not deployed

What it is

Internal ticket / task system docs repo. PRD, architecture, data model, API contracts, test strategy, and P0 specs for the Freshdesk replacement. Currently a specs queue, not running code.

Why it exists

SavvyDealer wants to exit Freshdesk. Before writing the code, Adam wrote down the PRD, v1 scope, Freshdesk-parity matrix, and P0 specs so the build can be driven from contracts instead of guesswork.

How it works

Markdown specs only. - Foundation: PRD.md, v1-scope.md, freshdesk-parity-matrix.md - Architecture: architecture.md, data-model.md, api-contracts.md - Execution: delivery-process.md, test-strategy.md, reliability.md, security.md, project-state.md - Specs queue (P0-001 through P0-005): - Ticket lifecycle - Conversations + private notes - Attachments service - Assignment + bulk routing - SLA policy CRUD + breaches

What's done

  • Full docs tree: PRD, architecture, data model, API contracts
  • 5 P0 specs drafted
  • Freshdesk-parity matrix

What's next

  • Generate OpenAPI skeleton from api-contracts.md
  • Implement P0-001 (ticket lifecycle) with tests
  • Un-dormant the repo — no commits since Feb 2026

Where the code lives

  • Repo: savvydealer-adam/ticket-system (docs only)
  • Target implementation: inside savvy-platform-suite once built

Integrations

Don't rebuild this — extend it

When actually building the ticket system, implement against these specs — do not redo the PRD / parity matrix / data model.