Empire Teas CRM β Delivery Harness
The delivery harness for the Empire Teas CRM engagement: every specification, plan, architectural decision, gate record, client-facing document, and piece of process automation that governs how the product gets built. No application code lives here β this repo is the projectβs brain; the app repos are its hands.
The system being built
A custom, single-tenant B2B sales CRM for Empire Teas (Pvt) Ltd β a top-five Sri Lankan tea exporter β replacing Pipedrive. It models the tea-export sales process as first-class (multi-round samples, certification checks, export-document checklists, weekly bulk pricing, quote readiness gating) and embeds a human-in-the-loop AI layer (Claude via Amazon Bedrock, inside the projectβs AWS account). A trade-show lead-capture PWA ships alongside it. The full contract is .forge/project-prd.md; the system design is .forge/design/architecture.md.
Repos
| Repo | What | Stack |
|---|---|---|
forge-et-harness |
This repo β specs, plans, decisions, gates, client pack, automation | Markdown + Claude Code harness |
forge-et-be |
Backend API + background worker | Java 21, Spring Boot 4.2.x, PostgreSQL (Gradle, Groovy DSL) |
forge-et-fe |
CRM frontend | TypeScript, React SPA on Vite (pnpm) |
forge-et-pwa |
Trade-show capture PWA β own hosting/URL | TypeScript, React PWA on Vite |
forge-et-pwa-poc |
Capture-app POC β read-only reference the capture stream ports from; never written to. Run it with /et-run-pwa-poc |
React + Vite frontend (portable) + its own Python/FastAPI backend (reference only) + its docs |
forge-et-iaac |
DevOps β all Terraform and other infrastructure code for the AWS estate (AD #23); worked in by Shyamin Ayesh and Senuthmi Thimansa, and by the delivery team through PRs to its dev branch |
Terraform |
All six are cloned as siblings under one plain parent directory β the layout every
team member uses and the one cross-repo tooling assumes (.forge/team-guide.md Β§ Repos on This Project).
Start here
./forge-start.sh # opens a Claude Code session with the project's turn-1 protocol
- Project constitution:
.claude/CLAUDE.mdβ locked decisions, boundaries, and the Reference Map to everything else. - Team playbook:
.forge/team-guide.mdβ whoβs who, ceremonies, environments, review pairings. - Live status:
.forge/tracker.yaml, rendered as a double-clickable dashboard at.forge/dashboard/index.html. - Readable doc site:
docs-html/index.htmlβ the whole human-read doc set as themed HTML (generated and gitignored β./forge-start.shbuilds it once, ornode .claude/lib/render-docs-html.js; the hosted copy is built by thePublish dashboardworkflow on every push tomain). - Client-facing pack:
.forge/client/β the issued proposal (frozen), timeline, dependencies register, and plain-language PRD.
How delivery works
Every feature moves through Spec β Plan β Implement β Check β Review β Ship β Reflect, with human-approved gates between phases β driven by the /forge-deliver orchestrator, guarded by deterministic hooks (.claude/hooks/), and recorded in the tracker. Engagement-level gates (PRD readiness, architecture, decomposition) are audited in .forge/engagement-gate-runs.md. The methodology itself is documented in .forge/forge-harness-framework.md.
Harness changes ship by PR like everything else: repo-hygiene CI checks front-matter, shell scripts, and that the generators (doc site, reference graph) run clean on the tree, on every pull request β the generated mirrors themselves are gitignored.
Branching and releases β main is the trunk in every delivery repo; work branches from it and merges back by PR once the required checks pass (no approval is currently required). Releases are annotated tags (vX.Y.Z), and a release/vX.Y.Z maintenance branch exists only once that release is live in production. Branch, commit and PR names carry the ticket id. Full rules in .claude/rules/git-conventions.md.