Matt
890795edd9
- Create 01-01-SUMMARY.md with schema decisions, deviations, self-check results - Update STATE.md with 01-01 decisions and session info - Update ROADMAP.md phase 1 progress (2/4 summaries) - Mark requirements RANK-01, RANK-05, RANK-08, RANK-09 complete Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2.8 KiB
Project State
Project Reference
See: .planning/PROJECT.md (updated 2026-02-26)
Core value: Admins can describe ranking criteria in natural language, the system interprets and ranks projects accordingly, and they can advance the top projects to the next round with one click — all with full override control. Current focus: Phase 1 — AI Ranking Backend
Current Position
Phase: 1 of 4 (AI Ranking Backend) Plan: 2 of TBD in current phase Status: In progress Last activity: 2026-02-26 — Plan 02 complete: AI ranking service built (ai-ranking.ts + AIAction RANKING)
Progress: [██░░░░░░░░] ~20%
Performance Metrics
Velocity:
- Total plans completed: 2
- Average duration: ~3 min
- Total execution time: ~6 min
By Phase:
| Phase | Plans | Total | Avg/Plan |
|---|---|---|---|
| 01-ai-ranking-backend | 2 | ~6 min | ~3 min |
Recent Trend:
- Last 5 plans: 01-01 (~3 min), 01-02 (~3 min)
- Trend: Fast (service-layer tasks)
Updated after each plan completion
Accumulated Context
Decisions
Decisions are logged in PROJECT.md Key Decisions table. Recent decisions affecting current work:
- [Init]: RankingSnapshot model (new table) preferred over Round.metadataJson for audit history — confirm with client before writing migration
- [Init]: Per-category processing (STARTUP / BUSINESS_CONCEPT) — two parallel AI calls, not one combined call
- [Init]: Phase 4 is independent and can be parallelized with Phases 2-3
- [01-01]: Used separate relation names per FK pair (RoundRankingSnapshots / TriggeredRankingSnapshots) — Prisma requires unique relation names per FK, not per target model
- [01-01]: All EvaluationConfig ranking fields are optional/defaulted for backward compatibility with existing rounds
- [01-01]: Created migration SQL manually (20260227000000_add_ranking_snapshot) — local DB credentials unavailable; migration applies on next deploy
- [01-02]: fetchAndRankCategory exported (not private) so tRPC router can execute pre-parsed rules without re-parsing
- [01-02]: Projects with zero SUBMITTED evaluations excluded from ranking entirely (not ranked last)
- [01-02]: PrismaClient imported as real type (not import type) so transaction clients are compatible
Pending Todos
None yet.
Blockers/Concerns
- [Phase 1]: French/English variable naming for EmailTemplate bilingual fields needs client confirmation before Phase 3 schema migration
- [Phase 1]: Poste.io bulk-send rate limits need verification before Phase 3 load testing
- [Phase 3]: Tiptap Mention extension API in v3.x should be validated against Tiptap v3 docs before implementation
Session Continuity
Last session: 2026-02-27 Stopped at: Completed 01-01-PLAN.md (RankingSnapshot schema + EvaluationConfig ranking fields) Resume file: None