김경종
43 lines
1.2 KiB
Markdown
43 lines
1.2 KiB
Markdown
# Step 4: validation-report-handoff
|
|
|
|
## Read First
|
|
|
|
Read these files before editing:
|
|
|
|
- `/AGENTS.md`
|
|
- `/docs/PLAN.md`
|
|
- `/docs/PROGRESS.md`
|
|
- `/docs/WORKNOTE.md`
|
|
- `/docs/AGENT_RULES.md`
|
|
- `/docs/implementation-plans/property-model-foundation-implementation-plan.md`
|
|
- `/phases/property-model-foundation/index.json`
|
|
|
|
## Task
|
|
|
|
Record validation evidence and handoff notes after the property model foundation implementation.
|
|
|
|
Required updates:
|
|
|
|
- Update `/docs/PROGRESS.md` with completed property base and Domain property ownership work.
|
|
- Update `/docs/PLAN.md` only if sequencing or acceptance criteria changed.
|
|
- Update `/docs/WORKNOTE.md` only if there were failures, repeated mistakes, or environment traps.
|
|
- Mark `/phases/property-model-foundation/index.json` steps and `/phases/index.json` according to actual results.
|
|
|
|
## Tests To Write First
|
|
|
|
- Documentation/reporting step. No new C++ test is required.
|
|
|
|
## Acceptance Criteria
|
|
|
|
```powershell
|
|
python -m unittest discover -s scripts -p "test_*.py"
|
|
python scripts/validate_workspace.py
|
|
git diff --check
|
|
```
|
|
|
|
## Verification Notes
|
|
|
|
1. Do not claim MITC4 formulation correctness.
|
|
2. Do not claim HDF5 result output is implemented.
|
|
3. Keep validation evidence concrete: command, result, and scope.
|