schalli/tessera-ctl
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 14 Wiki Activity

docs(12): create phase plan (4 vertical slices, waves 1-3)

Browse Source
This commit is contained in:
Schalli
2026-07-22 08:52:05 +02:00
parent 08b507ce8d
commit 09993b001c
5 changed files with 626 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.planning/ROADMAP.md
+14 -1
View File
@@ -410,9 +410,22 @@ Plans:
3. Activating a new search profile with many pre-existing historical matches does not flood the user with individual emails -- backfill is suppressed/batched on first activation, and a match already notified once (digest or instant) is never notified again for the same tender+profile pair (explicit matched-vs-notified state)
4. Notification emails are sent through the tenant's own SMTP configuration (reusing the DKV mail pattern), not a shared/global system mailer
**Plans**: TBD
**Plans**: 4 plans
**UI hint**: yes
**Wave 1**
- [ ] 12-01-PLAN.md — Schema (TenderMatch/NotificationPref/instantAlert) + delta-only Matching in den Poll-Tick (NOTIFY-03)
**Wave 2** *(blocked on Wave 1)*
- [ ] 12-02-PLAN.md — TenderMailService (mandanten-SMTP) + globaler Digest-Cron (NOTIFY-01/04)
**Wave 3** *(blocked on Wave 2)*
- [ ] 12-03-PLAN.md — Sofort-Alerts am Poll-Tick + Ein-Mail-Garantie über beide Kanäle (NOTIFY-02/03)
- [ ] 12-04-PLAN.md — Web-UI: Digest-Intervall + Sofort-Alert-Toggle, Pref-Backend (NOTIFY-01/02)
### Phase 13: Scraping Adapters & Cross-Source Deduplication
**Goal:** The platform expands tender coverage with AI-AG NetServer and cosinex portal adapters and collapses tenders seen on multiple sources into a single entry, while structurally refusing to ever scrape the AGB-prohibited portals.