bytelyst/learning_ai_common_plat
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(ecosystem): add Hermes delegation pack

Browse Source
This commit is contained in:
root 2026-05-25 01:58:45 +00:00
parent 7381d0f5c0
commit 0ddda36d1a
4 changed files with 191 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/ecosystem/delegation/README.md
View File

@ -1,6 +1,6 @@
# Delegation Pack
> Ready-to-send task files for Saravana, Codex, Windsurf, and Cursor.
> Ready-to-send task files for Saravana, Codex, Windsurf, Cursor, and Hermes.
> Use these files when assigning bounded ecosystem work to another coding agent.
---
@ -19,6 +19,9 @@
- [`cursor/TASK.md`](/Users/saravana/BytelystAI/learning_ai/learning_ai_common_plat/docs/ecosystem/delegation/cursor/TASK.md)
- [`cursor/STATUS.md`](/Users/saravana/BytelystAI/learning_ai/learning_ai_common_plat/docs/ecosystem/delegation/cursor/STATUS.md)
- [`cursor/FEEDBACK.md`](/Users/saravana/BytelystAI/learning_ai/learning_ai_common_plat/docs/ecosystem/delegation/cursor/FEEDBACK.md)
- [`hermes/TASK.md`](./hermes/TASK.md)
- [`hermes/STATUS.md`](./hermes/STATUS.md)
- [`hermes/FEEDBACK.md`](./hermes/FEEDBACK.md)
- [`TWO_WAY_COMMUNICATION_REFACTOR_PLAN.md`](/Users/saravana/BytelystAI/learning_ai/learning_ai_common_plat/docs/ecosystem/delegation/TWO_WAY_COMMUNICATION_REFACTOR_PLAN.md)
- historical refactor blueprint for how the 3-file communication loop was introduced
@ -38,6 +41,12 @@ Example:
git pull origin main && read /Users/saravana/BytelystAI/learning_ai/learning_ai_common_plat/docs/ecosystem/delegation/windsurf/TASK.md and /Users/saravana/BytelystAI/learning_ai/learning_ai_common_plat/docs/ecosystem/delegation/windsurf/FEEDBACK.md, execute within ownership boundaries, and update /Users/saravana/BytelystAI/learning_ai/learning_ai_common_plat/docs/ecosystem/delegation/windsurf/STATUS.md
```
Hermes example:
```bash
git pull --rebase origin main && read /opt/bytelyst/learning_ai_common_plat/docs/ecosystem/delegation/hermes/TASK.md and /opt/bytelyst/learning_ai_common_plat/docs/ecosystem/delegation/hermes/FEEDBACK.md, execute within ownership boundaries, and write progress back to /opt/bytelyst/learning_ai_common_plat/docs/ecosystem/delegation/hermes/STATUS.md
```
---
## Rules

29
docs/ecosystem/delegation/hermes/FEEDBACK.md Normal file
View File

@ -0,0 +1,29 @@
# Hermes Feedback Log
> Persistent review log for Hermes-owned delegated and closeout work.
> Record feedback here after Codex review so the guidance stays in the repo and in commit history.
---
## Entry Template
- **Task file:** [`TASK.md`](./TASK.md)
- **Reviewed by:** Saravana or Codex self-review
- **Review status:** approved | approved-with-follow-up | changes-required
- **Related commit:**
### What was good
- pending
### What was wrong
- pending
### Rule Going Forward
- pending
### Final Outcome
- pending

14
docs/ecosystem/delegation/hermes/STATUS.md Normal file
View File

@ -0,0 +1,14 @@
# Status
- **Task:** [`TASK.md`](./TASK.md)
- **Owner:** Hermes
- **Status:** not-started
- **Updated at:** 2026-05-25T01:57:51Z
- **Latest commit:** none
- **Verification command:** none
- **Verification result:** not-run
- **Blocker:** none
## Notes For Reviewer
- pending

138
docs/ecosystem/delegation/hermes/TASK.md Normal file
View File

@ -0,0 +1,138 @@
# Hermes Task
> **Role:** Hermes
> **Repo Lead:** `learning_ai_invt_trdg`
> **Mission:** own the next useful slice of trading-platform development, devops, and paper-trading operations using the repo docs as the source of truth
## Primary Objective
Take the trading platform forward without breaking live paper-trading flows, deployment safety, or documentation integrity.
You are the long-lived execution agent for this product line. Work like an operator, not a one-off implementer:
- start from the repo docs
- choose the smallest high-value slice that is actually shippable
- keep paper trading only
- prefer clean, reviewable commits over large, risky bundles
- report progress back through `STATUS.md`
- return any final recommendation or ambiguity to Codex before claiming completion
## Source Of Truth
Read these before making changes:
- [`learning_ai_invt_trdg/AGENTS.md`](/opt/bytelyst/learning_ai_invt_trdg/AGENTS.md)
- [`learning_ai_invt_trdg/docs/ROADMAP.md`](/opt/bytelyst/learning_ai_invt_trdg/docs/ROADMAP.md)
- [`learning_ai_invt_trdg/docs/CHAT_INTERFACE_HYBRID_ROADMAP.md`](/opt/bytelyst/learning_ai_invt_trdg/docs/CHAT_INTERFACE_HYBRID_ROADMAP.md)
- [`learning_ai_invt_trdg/docs/GOALS_ROADMAP.md`](/opt/bytelyst/learning_ai_invt_trdg/docs/GOALS_ROADMAP.md)
- [`learning_ai_invt_trdg/docs/inprogress/LAUNCH_READY_UI_UX_ROADMAP.md`](/opt/bytelyst/learning_ai_invt_trdg/docs/inprogress/LAUNCH_READY_UI_UX_ROADMAP.md)
- [`learning_ai_invt_trdg/docs/MULTI_ACCOUNT_IMPLEMENTATION_ROADMAP.md`](/opt/bytelyst/learning_ai_invt_trdg/docs/MULTI_ACCOUNT_IMPLEMENTATION_ROADMAP.md)
- [`learning_ai_invt_trdg/backend/REPO_AUDIT_ROADMAP.md`](/opt/bytelyst/learning_ai_invt_trdg/backend/REPO_AUDIT_ROADMAP.md)
- [`learning_ai_common_plat/AGENTS.md`](/opt/bytelyst/learning_ai_common_plat/AGENTS.md)
- [`learning_ai_common_plat/docs/ecosystem/ECOSYSTEM_AGENT_OPERATING_MODEL.md`](/opt/bytelyst/learning_ai_common_plat/docs/ecosystem/ECOSYSTEM_AGENT_OPERATING_MODEL.md)
- [`learning_ai_common_plat/docs/ecosystem/ECOSYSTEM_IMPLEMENTATION_TRACKER.md`](/opt/bytelyst/learning_ai_common_plat/docs/ecosystem/ECOSYSTEM_IMPLEMENTATION_TRACKER.md)
- [`learning_ai_common_plat/docs/ecosystem/delegation/README.md`](/opt/bytelyst/learning_ai_common_plat/docs/ecosystem/delegation/README.md)
- [`bytelyst-devops-tools/AGENTS.md`](/opt/bytelyst/bytelyst-devops-tools/AGENTS.md)
- [`bytelyst-devops-tools/REPO_CONTEXT.md`](/opt/bytelyst/bytelyst-devops-tools/REPO_CONTEXT.md)
- [`bytelyst-devops-tools/deploy-invttrdg.sh`](/opt/bytelyst/bytelyst-devops-tools/deploy-invttrdg.sh)
If a task touches shared platform behavior, also cross-check the common platform docs first. If a task touches deployment or release automation, use the existing devops scripts before inventing a new path.
## Operating Rules
- Paper trading only. Never enable or suggest real-money execution.
- Treat market-hours and asset-class rules as hard constraints, not suggestions.
- Use the existing deployment path for this product. Do not create an ad hoc deploy flow if `deploy-invttrdg.sh` already covers the need.
- Keep changes narrow enough to review in one pass whenever possible.
- Preserve unrelated local work. Do not overwrite or revert changes outside your owned scope.
- If the repo is behind `origin/main`, rebase cleanly before you start editing or before you push.
- If a required verification cannot run in the current environment, record the exact blocker and the closest successful validation you did run.
## What You Own
Hermes may work across three lanes, but should keep each change set bounded:
### 1. Product Development
Implement the next roadmap slice in `learning_ai_invt_trdg` with a bias toward:
- chat/orchestrator coverage
- goals and progress visibility
- UI consistency for loading, empty, and error states
- trading safety and account state correctness
- multi-account and profile behavior when it is already documented
### 2. DevOps And Release Hygiene
Use the existing deploy tooling to:
- validate the current release path
- keep backend/web deploys aligned
- confirm health endpoints after rollout
- update deployment docs when the script contract changes
### 3. Trading Safety And Live-State Checks
Use live paper-trading state to answer:
- what filled
- what failed
- why a goal or order did not fire
- whether the current app behavior matches the roadmap and code
Do not change trading logic blindly. Verify the cause before fixing it.
## Do Not Touch
- real-money trading pathways
- secrets, `.env` files, or credentials
- unrelated repos unless the task explicitly expands the scope
- broad refactors that are not required for the current slice
- shared platform contracts unless the change truly needs them
## Expected Workflow
1. Read the task and prior feedback.
2. Rebase onto `origin/main` if needed.
3. Check the relevant roadmap and implementation docs.
4. Pick one bounded slice that can be completed and verified.
5. Implement the smallest correct fix.
6. Run the narrowest real verification that proves the change.
7. Write the result to `STATUS.md`.
8. Return the result for Codex review before claiming done.
## Verification Expectations
Use the verification command that best matches the change:
- backend changes: service-specific tests plus build or typecheck
- web changes: component tests plus build
- deployment changes: the real deploy script plus health checks
- trading or account-state changes: a live-state readback plus a regression test when available
Record the exact command in `STATUS.md`, not just a summary.
## Commit Discipline
- Prefer small conventional commits.
- Keep each commit reviewable by itself.
- Do not force-push.
- Do not amend unless explicitly instructed.
- If you need to stack work, describe the stack clearly in `STATUS.md`.
## Status Channel
Update [`STATUS.md`](./STATUS.md) with:
- current status
- latest commit
- exact verification command
- exact verification result
- blockers
- short reviewer notes
## Launch One-Liner
```bash
git pull --rebase origin main && read /opt/bytelyst/learning_ai_common_plat/docs/ecosystem/delegation/hermes/TASK.md and /opt/bytelyst/learning_ai_common_plat/docs/ecosystem/delegation/hermes/FEEDBACK.md, execute within ownership boundaries, and write progress back to /opt/bytelyst/learning_ai_common_plat/docs/ecosystem/delegation/hermes/STATUS.md
```