docs: start frontend mvp milestone
This commit is contained in:
user
@@ -20,20 +20,38 @@ each short practice loop.
|
||||
|
||||
### Validated
|
||||
|
||||
(None yet; ship to validate.)
|
||||
- [x] Developer job seekers can complete a diagnostic technical interview.
|
||||
- [x] Answers are graded with rubrics and preserved as evidence.
|
||||
- [x] Learner memory tracks concept mastery, misconceptions, evidence, and
|
||||
interventions.
|
||||
- [x] The system selects the next best interview challenge from learner state.
|
||||
- [x] The user sees a readiness map and meaningful progression after each loop.
|
||||
- [x] Uploaded learning materials can become source-backed ontology candidates.
|
||||
- [x] Generated learning assets preserve prompt, source, and review lineage.
|
||||
- [x] Backend implementation uses Go and keeps `agent-farm-go` workflow patterns
|
||||
internalized behind typed interfaces.
|
||||
|
||||
### Active
|
||||
|
||||
- [ ] Developer job seekers can complete a diagnostic technical interview.
|
||||
- [ ] Answers are graded with rubrics and preserved as evidence.
|
||||
- [ ] Learner memory tracks concept mastery, misconceptions, evidence, and
|
||||
interventions.
|
||||
- [ ] The system selects the next best interview challenge from learner state.
|
||||
- [ ] The user sees a readiness map and meaningful progression after each loop.
|
||||
- [ ] Uploaded learning materials can become source-backed ontology candidates.
|
||||
- [ ] Generated learning assets preserve prompt, source, and review lineage.
|
||||
- [ ] Backend implementation uses Go and keeps `agent-farm-go` workflow patterns
|
||||
internalized behind typed interfaces.
|
||||
- [ ] Job seekers can use the first web app without API tooling.
|
||||
- [ ] The web app guides users through diagnostic practice and shows feedback.
|
||||
- [ ] The web app shows learner memory, readiness, and next challenge after
|
||||
practice.
|
||||
- [ ] Operators can ingest learning material and inspect ontology candidates.
|
||||
- [ ] Operators can generate source-backed teaching asset prompt candidates.
|
||||
|
||||
## Current Milestone: v2 Frontend MVP
|
||||
|
||||
**Goal:** Turn the completed backend learning loop into a usable web service
|
||||
experience for developer job seekers.
|
||||
|
||||
**Target features:**
|
||||
|
||||
- Web app shell served by the Go backend.
|
||||
- Diagnostic interview practice UI.
|
||||
- Learner memory, readiness map, and next challenge views.
|
||||
- Material ingestion and ontology snapshot UI.
|
||||
- Teaching asset prompt candidate UI.
|
||||
|
||||
### Out of Scope
|
||||
|
||||
@@ -81,6 +99,26 @@ each short practice loop.
|
||||
| Game-inspired progression must be evidence-backed | Creates retention without empty rewards | Pending |
|
||||
| 600-line source limit | Forces responsibility boundaries early | Pending |
|
||||
| Backend Developer Interview first track | Gives a broad but testable MVP concept set | Pending |
|
||||
| v2 frontend first | The backend loop is proven; the next risk is whether users can operate it as a web service | Active |
|
||||
|
||||
## Evolution
|
||||
|
||||
This document evolves at phase transitions and milestone boundaries.
|
||||
|
||||
**After each phase transition**:
|
||||
|
||||
1. Requirements invalidated? Move to Out of Scope with reason.
|
||||
2. Requirements validated? Move to Validated with phase reference.
|
||||
3. New requirements emerged? Add to Active.
|
||||
4. Decisions to log? Add to Key Decisions.
|
||||
5. "What This Is" still accurate? Update if drifted.
|
||||
|
||||
**After each milestone**:
|
||||
|
||||
1. Full review of all sections.
|
||||
2. Core Value check: still the right priority?
|
||||
3. Audit Out of Scope: reasons still valid?
|
||||
4. Update Context with current state.
|
||||
|
||||
---
|
||||
*Last updated: 2026-04-26 after first track and Phase 1 plan were set.*
|
||||
*Last updated: 2026-04-26 after v2 Frontend MVP milestone start.*
|
||||
|
||||
@@ -68,6 +68,22 @@ interview-ready after each short practice loop.
|
||||
|
||||
## v2 Requirements
|
||||
|
||||
### Frontend MVP
|
||||
|
||||
- [ ] **WEB-01**: User can open a web app served by the Go service.
|
||||
- [ ] **WEB-02**: User can create a diagnostic interview session from the web
|
||||
app.
|
||||
- [ ] **WEB-03**: User can answer a diagnostic question and see rubric feedback.
|
||||
- [ ] **WEB-04**: User can see learner memory, readiness, and next challenge
|
||||
after answering.
|
||||
- [ ] **WEB-05**: Operator can ingest source material from the web app.
|
||||
- [ ] **WEB-06**: Operator can inspect ontology candidate concepts, edges, and
|
||||
gaps.
|
||||
- [ ] **WEB-07**: Operator can generate and inspect teaching asset prompt
|
||||
candidates.
|
||||
- [ ] **WEB-08**: Web UI includes loading, empty, and error states for the MVP
|
||||
flows.
|
||||
|
||||
### General Student Expansion
|
||||
|
||||
- **GEN-01**: Support non-interview learning tracks.
|
||||
@@ -100,12 +116,16 @@ interview-ready after each short practice loop.
|
||||
| PROG-01..PROG-05 | Phase 4 | Complete |
|
||||
| ONTO-01..ONTO-04 | Phase 5 | Complete |
|
||||
| ASSET-01..ASSET-03 | Phase 6 | Complete |
|
||||
| WEB-01..WEB-03 | Phase 7 | Pending |
|
||||
| WEB-04 | Phase 8 | Pending |
|
||||
| WEB-05..WEB-08 | Phase 9 | Pending |
|
||||
|
||||
**Coverage:**
|
||||
- v1 requirements: 28 total
|
||||
- Mapped to phases: 28
|
||||
- v2 frontend requirements: 8 total
|
||||
- Mapped to phases: 36
|
||||
- Unmapped: 0
|
||||
|
||||
---
|
||||
*Requirements defined: 2026-04-26*
|
||||
*Last updated: 2026-04-26 after Phase 6 execution.*
|
||||
*Last updated: 2026-04-26 after v2 Frontend MVP milestone start.*
|
||||
|
||||
@@ -94,5 +94,50 @@ diagnostic interview.
|
||||
- Company-specific interview packs.
|
||||
- Human ontology review console.
|
||||
|
||||
## Milestone 2: Frontend MVP
|
||||
|
||||
### Phase 7: Web App Shell and Diagnostic Start
|
||||
|
||||
**Goal:** Serve the first web app from the Go service and let a job seeker
|
||||
start diagnostic practice without API tooling.
|
||||
|
||||
**Requirements:** WEB-01, WEB-02, WEB-03
|
||||
|
||||
**Success Criteria:**
|
||||
|
||||
- Go service serves a web app at `/`.
|
||||
- User can enter target role, stack, and interview timeline.
|
||||
- User can create a diagnostic session from the browser.
|
||||
- User can submit an answer and see typed grading feedback.
|
||||
- UI has loading and error states for the diagnostic flow.
|
||||
|
||||
### Phase 8: Learning Progress View
|
||||
|
||||
**Goal:** Show evidence-backed learning progress after practice.
|
||||
|
||||
**Requirements:** WEB-04
|
||||
|
||||
**Success Criteria:**
|
||||
|
||||
- User can see learner profile and concept mastery after answering.
|
||||
- User can see readiness percentage and concept ladder state.
|
||||
- User can see the next recommended challenge and its evidence.
|
||||
- Empty states explain what to do before memory/progression exists.
|
||||
|
||||
### Phase 9: Material and Asset Workspace
|
||||
|
||||
**Goal:** Let an operator use ontology and teaching asset prompt workflows from
|
||||
the web app.
|
||||
|
||||
**Requirements:** WEB-05, WEB-06, WEB-07, WEB-08
|
||||
|
||||
**Success Criteria:**
|
||||
|
||||
- Operator can ingest text material from the browser.
|
||||
- Operator can inspect ontology candidate concepts, edges, and gaps.
|
||||
- Operator can generate teaching asset prompt candidates from a concept.
|
||||
- UI clearly shows candidate review state, source evidence, and model
|
||||
verification guard.
|
||||
|
||||
---
|
||||
*Roadmap created: 2026-04-26 after initial product planning and Go backend decision.*
|
||||
*Roadmap updated: 2026-04-26 after v2 Frontend MVP milestone start.*
|
||||
|
||||
@@ -7,7 +7,7 @@ See: `.planning/PROJECT.md` (updated 2026-04-26)
|
||||
**Core value:** The user should feel and prove that they are becoming more
|
||||
interview-ready after each short practice loop.
|
||||
|
||||
**Current focus:** v1 milestone audited; ready to choose the next milestone.
|
||||
**Current focus:** v2 Frontend MVP milestone started; ready for Phase 7.
|
||||
|
||||
## Current Decisions
|
||||
|
||||
@@ -35,11 +35,12 @@ interview-ready after each short practice loop.
|
||||
evidence, model config, review state, and model-id verification guard.
|
||||
- v1 milestone audit completed with all 28/28 requirements satisfied and
|
||||
tech-debt items recorded in `.planning/v1-MILESTONE-AUDIT.md`.
|
||||
- v2 Frontend MVP milestone selected to turn the backend learning loop into a
|
||||
usable web service.
|
||||
|
||||
## Next Actions
|
||||
|
||||
1. Choose the next milestone: frontend MVP, persistence, real workflow runtime,
|
||||
or document parser integration.
|
||||
1. Plan and execute Phase 7: Web App Shell and Diagnostic Start.
|
||||
2. Verify the production OpenAI image model identifier before real image
|
||||
generation calls.
|
||||
3. Add standardized SUMMARY frontmatter or Nyquist validation files if future
|
||||
@@ -73,6 +74,8 @@ interview-ready after each short practice loop.
|
||||
integration, E2E diagnostic/progression and material/asset flows. Audit
|
||||
status is `tech_debt` because MVP storage, real workflow runtime, parsers,
|
||||
real image generation, and Nyquist validation artifacts remain deferred.
|
||||
- 2026-04-26: v2 Frontend MVP milestone started with WEB-01..WEB-08 mapped to
|
||||
phases 7 through 9.
|
||||
|
||||
---
|
||||
*State initialized: 2026-04-26.*
|
||||
|
||||
Reference in New Issue
Block a user