2.6 KiB
2.6 KiB
AI-DLC State Tracking
Project Information
- Feature Name: Media library (one place to manage, keep and reuse photos for all modules)
- Feature Slug: media-library
- Project Type: Brownfield
- Start Date: 2026-11-17
- Current Stage: INCEPTION - Requirements Analysis and Application Design drafted on assumptions (awaiting Bryan's later check); nothing that moves data is built
- Branch: feature/media-library (from origin/master
e0b3782)
Workspace State
- Existing Code: Yes (Core/Media, Modules.Hero)
- Reverse Engineering Needed: No (artifacts in
_shared/reverse-engineering/; targeted read of Core/Media and Modules.Hero) - Workspace Root: K:\Development\Projects\SlpModularCms
Language Configuration
- Documentation Language: English
- Conversation Language: User Language (Dutch)
- Note: Inherited from the other features.
overview.mdstays Dutch (written by SLS-Main for Bryan).
Source Of Truth / Coordination
- Requirements 1 to 7 of Bryan are in
overview.md(2026-11-17). Bryan is away: no questions to him; every open question has a most probable assumption inassumptions-and-open-questions.md; Bryan checks them later. - Allowed now: requirements, design, and safe, reversible building. Not allowed without prior alignment (via SLS-Main with Bryan): an EF migration that moves existing
HeroImages, any change of public addresses (/media/hero/<hash>/...), set-hashes or golden files. - No merge to master, production deploy or production variables without go.
Extension Configuration
| Extension | Enabled | Decided At |
|---|---|---|
| Security Baseline | Yes (blocking), as for hero-module | Inherited (upload, delete and file serving are security relevant) |
| Property-Based Testing | Partial (pure functions and round-trips) | Inherited |
Operations Configuration
- Include Operations Phase: No (points go into docs/release-checklist-productie.md when built)
Stage Progress
INCEPTION PHASE
- Workspace Detection (Feature, brownfield)
- Reverse Engineering (skipped: targeted read)
- Requirements Analysis (inception/requirements/requirements.md; no questions file: assumptions instead)
- User Stories - SKIP (one persona, acceptance criteria in the requirements)
- Workflow Planning (section 9 of requirements: phases A to D)
- Application Design (inception/application-design/application-design.md, draft)
- Units Generation (after Bryan's check of the assumptions)
CONSTRUCTION PHASE
- Not started. Phase A (safe, reversible) may start after the assumptions are acknowledged; phases B and C move data and need alignment first.