WIP: Staged all changes

This commit is contained in:
2025-12-19 22:40:28 +03:00
parent 8f4b469c96
commit ce703322c2
64 changed files with 5985 additions and 833 deletions

View File

@@ -0,0 +1,28 @@
# [PROJECT NAME] Development Guidelines
Auto-generated from all feature plans. Last updated: [DATE]
## Active Technologies
[EXTRACTED FROM ALL PLAN.MD FILES]
## Project Structure
```text
[ACTUAL STRUCTURE FROM PLANS]
```
## Commands
[ONLY COMMANDS FOR ACTIVE TECHNOLOGIES]
## Code Style
[LANGUAGE-SPECIFIC, ONLY FOR LANGUAGES IN USE]
## Recent Changes
[LAST 3 FEATURES AND WHAT THEY ADDED]
<!-- MANUAL ADDITIONS START -->
<!-- MANUAL ADDITIONS END -->

View File

@@ -0,0 +1,40 @@
# [CHECKLIST TYPE] Checklist: [FEATURE NAME]
**Purpose**: [Brief description of what this checklist covers]
**Created**: [DATE]
**Feature**: [Link to spec.md or relevant documentation]
**Note**: This checklist is generated by the `/speckit.checklist` command based on feature context and requirements.
<!--
============================================================================
IMPORTANT: The checklist items below are SAMPLE ITEMS for illustration only.
The /speckit.checklist command MUST replace these with actual items based on:
- User's specific checklist request
- Feature requirements from spec.md
- Technical context from plan.md
- Implementation details from tasks.md
DO NOT keep these sample items in the generated checklist file.
============================================================================
-->
## [Category 1]
- [ ] CHK001 First checklist item with clear action
- [ ] CHK002 Second checklist item
- [ ] CHK003 Third checklist item
## [Category 2]
- [ ] CHK004 Another category item
- [ ] CHK005 Item with specific criteria
- [ ] CHK006 Final item in this category
## Notes
- Check items off as completed: `[x]`
- Add comments or findings inline
- Link to relevant resources or documentation
- Items are numbered sequentially for easy reference

View File

@@ -31,8 +31,8 @@
*GATE: Must pass before Phase 0 research. Re-check after Phase 1 design.*
- [ ] **Causal Validity**: Do all planned modules have defined Contracts (inputs/outputs/invariants) before implementation logic?
- [ ] **Immutability**: Are architectural layers and constraints defined in Module Headers?
- [ ] **Causal Validity**: Do all planned modules/components have defined Contracts (inputs/outputs/props/events) before implementation logic?
- [ ] **Immutability**: Are architectural layers and constraints defined in Module/Component Headers?
- [ ] **Format Compliance**: Does the plan ensure all code will be wrapped in `[DEF]` anchors?
- [ ] **Belief State**: Is logging planned to follow the `Entry` -> `Validation` -> `Action` -> `Coherence` state transition model?

View File

@@ -93,7 +93,9 @@ Examples of foundational tasks (adjust based on your project):
- [ ] T014 [P] [US1] Define [Service] Module Header & Contracts in src/services/[service].py
- [ ] T015 [US1] Implement [Service] logic satisfying contracts (depends on T012)
- [ ] T016 [US1] Define [endpoint] Contracts & Logic in src/[location]/[file].py
- [ ] T017 [US1] Verify `[DEF]` syntax and Belief State logging compliance
- [ ] T017 [US1] Define [Component] Header (Props/Events) in frontend/src/components/[Component].svelte
- [ ] T018 [US1] Implement [Component] logic satisfying contracts
- [ ] T019 [US1] Verify `[DEF]` syntax and Belief State logging compliance
**Checkpoint**: At this point, User Story 1 should be fully functional and testable independently
@@ -107,15 +109,16 @@ Examples of foundational tasks (adjust based on your project):
### Tests for User Story 2 (OPTIONAL - only if tests requested) ⚠️
- [ ] T018 [P] [US2] Contract test for [endpoint] in tests/contract/test_[name].py
- [ ] T019 [P] [US2] Integration test for [user journey] in tests/integration/test_[name].py
- [ ] T020 [P] [US2] Contract test for [endpoint] in tests/contract/test_[name].py
- [ ] T021 [P] [US2] Integration test for [user journey] in tests/integration/test_[name].py
### Implementation for User Story 2
- [ ] T020 [P] [US2] Define [Entity] Module Header & Contracts in src/models/[entity].py
- [ ] T021 [P] [US2] Implement [Entity] logic satisfying contracts
- [ ] T022 [US2] Define [Service] Module Header & Contracts in src/services/[service].py
- [ ] T023 [US2] Implement [Service] logic satisfying contracts
- [ ] T022 [P] [US2] Define [Entity] Module Header & Contracts in src/models/[entity].py
- [ ] T023 [P] [US2] Implement [Entity] logic satisfying contracts
- [ ] T024 [US2] Define [Service] Module Header & Contracts in src/services/[service].py
- [ ] T025 [US2] Implement [Service] logic satisfying contracts
- [ ] T026 [US2] Define [Component] Header & Logic in frontend/src/components/[Component].svelte
**Checkpoint**: At this point, User Stories 1 AND 2 should both work independently
@@ -129,14 +132,15 @@ Examples of foundational tasks (adjust based on your project):
### Tests for User Story 3 (OPTIONAL - only if tests requested) ⚠️
- [ ] T024 [P] [US3] Contract test for [endpoint] in tests/contract/test_[name].py
- [ ] T025 [P] [US3] Integration test for [user journey] in tests/integration/test_[name].py
- [ ] T027 [P] [US3] Contract test for [endpoint] in tests/contract/test_[name].py
- [ ] T028 [P] [US3] Integration test for [user journey] in tests/integration/test_[name].py
### Implementation for User Story 3
- [ ] T026 [P] [US3] Define [Entity] Module Header & Contracts in src/models/[entity].py
- [ ] T027 [US3] Define [Service] Module Header & Contracts in src/services/[service].py
- [ ] T028 [US3] Implement logic for [Entity] and [Service] satisfying contracts
- [ ] T029 [P] [US3] Define [Entity] Module Header & Contracts in src/models/[entity].py
- [ ] T030 [US3] Define [Service] Module Header & Contracts in src/services/[service].py
- [ ] T031 [US3] Implement logic for [Entity] and [Service] satisfying contracts
- [ ] T032 [US3] Define [Component] Header & Logic in frontend/src/components/[Component].svelte
**Checkpoint**: All user stories should now be independently functional
@@ -179,9 +183,10 @@ Examples of foundational tasks (adjust based on your project):
### Within Each User Story
- Tests (if included) MUST be written and FAIL before implementation
- Module Headers & Contracts BEFORE Implementation (Causal Validity)
- Module/Component Headers & Contracts BEFORE Implementation (Causal Validity)
- Models before services
- Services before endpoints
- Components before Pages
- Story complete before moving to next priority
### Parallel Opportunities