Initial commit: Fresh implementation of CHORUS architecture (ResetData Mandate)
This commit is contained in:
26
docs/Modules/SWOOSH.md
Normal file
26
docs/Modules/SWOOSH.md
Normal file
@@ -0,0 +1,26 @@
|
||||
# SWOOSH: Current Coordination State Machine
|
||||
|
||||
SWOOSH is the active CHORUS coordinator in this workspace.
|
||||
|
||||
## Runtime Source
|
||||
|
||||
- Code: `/home/tony/chorus/SWOOSH`
|
||||
- Core API: `/home/tony/chorus/SWOOSH/api.go`
|
||||
- Reducer/state machine: `/home/tony/chorus/SWOOSH/reducer.go`
|
||||
- State model: `/home/tony/chorus/SWOOSH/state.go`
|
||||
|
||||
## Current API Surface
|
||||
|
||||
- `POST /transition`
|
||||
- `GET /state`
|
||||
- `GET /health`
|
||||
- `POST /api/v1/opportunities/council` (ResetData-backed council planning)
|
||||
- `GET /api/v1/tasks` (currently 501 by design)
|
||||
|
||||
## Integration Notes
|
||||
|
||||
- CHORUS coordination points now target SWOOSH runtime behavior.
|
||||
- Keep deterministic transition mapping: API handlers submit transitions; reducer is state authority.
|
||||
- For implementation detail and known caveats, refer to:
|
||||
- `/home/tony/chorus/SWOOSH/API_INTEGRATION.md`
|
||||
- `/home/tony/chorus/SWOOSH/RESETDATA_INTEGRATION_PLAN.md`
|
||||
Reference in New Issue
Block a user