liang/sales-ai
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

Rebuild Project Matter schema baseline with smoke workflow #3

New issue
Closed
opened 2026-06-14 10:21:20 +00:00 by liang · 1 comment
liang commented 2026-06-14 10:21:20 +00:00
Owner
Copy link

Parent

Parent PRD: #2

What to build

Rebuild the disposable prototype database around the confirmed Project Matter model, reset Alembic to a new baseline, and expose a minimal smoke workflow that can create and read a Project, Project Matter, Task, Communication, Document, Review Item, Proposed Change Set, Matter Event, and audit Event through the repo's normal application seams. The slice should prove the new vocabulary and relationships work end to end without preserving old test data.

Acceptance criteria

  • A new Alembic baseline represents the Project Matter schema and old active migrations are archived outside the active chain.
  • Projects use Project Title instead of codename, and Project Matter uses matter-based terminology including Matter Code, Matter Type, Matter Status, Matter Priority, Matter Owner, Matter Deadline, Matter Milestone, Matter Link, and Matter Event.
  • Communication Project Hint remains available while Matter Links support one Communication linking to multiple Project Matters with separate Link Rationales.
  • Stored File, File Reference, Document, Intake Item, Review Item, Proposed Change Set, Proposed Change, Classification Decision, Classification Feedback, and Rule Suggestion records exist with the relationships required by the PRD.
  • A deterministic smoke test exercises the minimal create/read path and verifies no legacy codename-centered assumptions remain in the smoke workflow.

Blocked by

None - can start immediately

## Parent Parent PRD: #2 ## What to build Rebuild the disposable prototype database around the confirmed Project Matter model, reset Alembic to a new baseline, and expose a minimal smoke workflow that can create and read a Project, Project Matter, Task, Communication, Document, Review Item, Proposed Change Set, Matter Event, and audit Event through the repo's normal application seams. The slice should prove the new vocabulary and relationships work end to end without preserving old test data. ## Acceptance criteria - [ ] A new Alembic baseline represents the Project Matter schema and old active migrations are archived outside the active chain. - [ ] Projects use Project Title instead of codename, and Project Matter uses matter-based terminology including Matter Code, Matter Type, Matter Status, Matter Priority, Matter Owner, Matter Deadline, Matter Milestone, Matter Link, and Matter Event. - [ ] Communication Project Hint remains available while Matter Links support one Communication linking to multiple Project Matters with separate Link Rationales. - [ ] Stored File, File Reference, Document, Intake Item, Review Item, Proposed Change Set, Proposed Change, Classification Decision, Classification Feedback, and Rule Suggestion records exist with the relationships required by the PRD. - [ ] A deterministic smoke test exercises the minimal create/read path and verifies no legacy codename-centered assumptions remain in the smoke workflow. ## Blocked by None - can start immediately
liang commented 2026-06-14 10:38:38 +00:00
Author
Owner
Copy link

Implemented issue #3.

Summary:

  • Rebuilt SQLAlchemy models around Project Matter baseline and removed active Project codename field in favor of title.
  • Added single Alembic baseline 20260614_0001_project_matter_baseline.py and archived old active migrations under db/migrations/archive/pre_project_matter/.
  • Added deterministic Project Matter smoke workflow covering Project, Project Matter, Task, Communication Project Hint, Matter Link + Link Rationale, Document, Stored File, File Reference, Review Item, Proposed Change Set, Matter Event, and audit Event.
  • Updated obvious runtime codename references to title in API, seed data, daily log, frontend, and prompt context.
  • Added pytest collection config and integration-style smoke tests.

Verification:

  • .venv/bin/pytest -q -> 4 passed
  • .venv/bin/python -m compileall db services tests api ingestors scheduler scripts frontend -q -> passed
Implemented issue #3. Summary: - Rebuilt SQLAlchemy models around Project Matter baseline and removed active Project `codename` field in favor of `title`. - Added single Alembic baseline `20260614_0001_project_matter_baseline.py` and archived old active migrations under `db/migrations/archive/pre_project_matter/`. - Added deterministic Project Matter smoke workflow covering Project, Project Matter, Task, Communication Project Hint, Matter Link + Link Rationale, Document, Stored File, File Reference, Review Item, Proposed Change Set, Matter Event, and audit Event. - Updated obvious runtime `codename` references to `title` in API, seed data, daily log, frontend, and prompt context. - Added pytest collection config and integration-style smoke tests. Verification: - `.venv/bin/pytest -q` -> 4 passed - `.venv/bin/python -m compileall db services tests api ingestors scheduler scripts frontend -q` -> passed
liang closed this issue 2026-06-14 10:38:38 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
No results found.
Labels
Clear labels   
ready-for-agent
Fully specified, ready for an AFK agent

No labels
ready-for-agent
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
liang/sales-ai#3
No description provided.