From 0b35896d4d0d0469ead57bccd3d74cdd2ab4b3b3 Mon Sep 17 00:00:00 2001 From: graphlemon Date: Thu, 6 Aug 2026 10:47:50 +0800 Subject: [PATCH] graphlemon: auto-commit uncommitted changes for 1f278c16-76a4-4d05-be48-89548a2285fa-main-checkout-drift --- CLAUDE.md | 27 ++++++++++++++++++++++++--- 1 file changed, 24 insertions(+), 3 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index be5c3e1..085e4ce 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -60,7 +60,7 @@ both (deliberately: `supervisor/` was added later as PH5 landed, see `development-plan.md`'s U-036 note): ```bash -# graphlemon's own backend/schema/agent-orchestration code (441 tests as of U-043) +# graphlemon's own backend/schema/agent-orchestration code (560+ tests as of PH5) python3 -m unittest discover -s src # Deploy Supervisor + the isolate/diff/apply library it depends on @@ -154,11 +154,32 @@ directly; anything worth reusing has already been copied and adapted into this r ## Repo layout -- `docs/` — architecture doc, SDD (`docs/sdd/`), development plan, self-hosting design docs. See - Status above for how stale the plan/unit-matrix "done" framing is relative to the real code. +- `docs/` — architecture doc (`graphlemon_architecture.md`), SDD (`docs/sdd/`, authoritative), + development plan, and gap-analysis all live at the top level as living/actively-read documents + (see Status above for how stale the plan/unit-matrix "done" framing is relative to the real + code). Point-in-time material is split into three subdirectories by role, not chronology: + `docs/done/` (design/decision docs whose conclusions have been fully absorbed into the SDD — + e.g. the Deploy Supervisor design chain — kept for the reasoning trail, not because they're + still authoritative), `docs/todo/` (requirements/design docs for work not yet implemented — + BRD/PRD-level requirements docs and, once confirmed, SDD-level design docs, same two-stage + split the Planner itself uses), `docs/reference/` (external source material — articles, course + notes — plus graphlemon's own "how does this compare to our architecture" notes on each one). + When adding a new doc, pick by role (has its conclusion shipped into the SDD? → done; still + pending confirmation/implementation? → todo; is it someone else's writing you're archiving? → + reference), not by putting everything loose in `docs/`. - `docs/wireframes/` — static no-build HTML prototypes for the PH3 console views (`v_*.html`), referenced per-page from `docs/sdd/02-V-界面与交互.md` §2.1-2.13; DOM/class names map 1:1 to that doc's field lists. +- `skills/` — the Skill library (architecture doc §7.3): one directory per skill + (`skills//SKILL.md` + optional `references/`), migrated/adapted from the Hermes profiles + (§9's role mapping) and referenced by name from each Org Agent's `.claude/agents/*.md` + `skills:` frontmatter list (`src/agent_profile.py::FRONTMATTER`, the canonical source of that + list — edit it there, not by hand-editing the deployed `.claude/agents/*.md`). +- `.claude/workflows/` — auto-generated, not hand-authored: real Dynamic Workflow scripts written + by `src/work_graph_execute.py::write_workflow_script()`/`src/work_graph_orchestrate.py` (one + script per Work Node execution) and by `e2e_pipeline.py`'s PRD-consistency check. Version- + controlled because it's inside the target repo (self-target case: this repo), but treat the + contents as execution artifacts, not source you maintain by hand. - `src/` — graphlemon's own backend: `schema.py` (17-table SQLite schema — the original 01-M 15 entities plus PH5's `deployment`/`deploy_health_signal`), `backend_server.py` (stdlib `http.server` HTTP API + WebSocket-ish log/event streaming, no third-party deps), the Org Graph -- libgit2 0.21.4