You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1.6 KiB
1.6 KiB
Devil's Advocate Prioritization Memo
Position
Do not start with "clean architecture" refactors yet. First, remove business-risk mismatches that can produce incorrect behavior despite clean code.
What Should Be Prioritized in This Conversation
- Decide the product contracts that are currently ambiguous.
- Theme creation rules
- Schedule GET semantics
- Canonical defaults
- Theme scoping for import/export/preferred
- Approve a short "correctness-first" implementation batch.
- Theme-scoped source import/export/preferred fixes
- Theme creation contract alignment
- Theme ownership validation on source writes
- Lock a test gating policy before refactoring.
- Add deterministic tests for scheduler and SSE progress first
- Avoid relying on live external-provider E2E for CI confidence
What To Defer (For Now)
- Large structural decomposition of
synthesis.rsand major frontend pages. - Broad style/lint cleanups.
- Performance tuning beyond obvious correctness-adjacent fixes.
Why This Order Is Safer
- It prevents regressions in core multi-theme behavior before code motion.
- It creates a stable contract baseline for any future refactor team.
- It avoids spending effort simplifying code that may be simplified in the wrong direction if contracts change.
Concrete Next Decision Request
Please confirm these five items so implementation teams can proceed without churn:
- Draft theme creation allowed or not
- Schedule GET absent behavior (
404vs200 null) - Defaults (
4/3vs5/2) - Theme-scoped import/export/preferred policy (yes/no)
- Fallback label and source-link extraction mode policy