molecule-dev-department/pick-up-work.md at 1dd614a4f14b5dda2c71876c8b154ba7393ed787

claude-ceo-assistant 1dd614a4f1 atomize(dev-tree): nest sub-teams + leaf workspaces under dev-lead/, dissolve teams/

Phase 3c-3 of internal#77 (dev-department extraction).

Atomization completes the structural goal of the RFC (Hongming Q3+Q5):
each workspace is a self-contained folder; no cross-tree '..' refs;
the validator can enforce orphans-impossible-by-construction in --strict mode.

What changed:

  Folder moves (history preserved via git mv):
  - core-be, core-fe, core-qa, core-security, core-uiux, core-devops,
    core-offsec → core-lead/<self>/
  - cp-be, cp-qa, cp-security → cp-lead/<self>/
  - app-fe, app-qa, technical-writer, documentation-specialist
    → app-lead/<self>/
  - infra-sre, infra-runtime-be → infra-lead/<self>/
  - sdk-dev, plugin-dev → sdk-lead/<self>/
  - core-lead, cp-lead, app-lead, infra-lead, sdk-lead,
    release-manager, integration-tester, fullstack-engineer,
    triage-operator → dev-lead/<self>/

  Workspace.yaml content:
  - dev-lead/workspace.yaml: lifted from teams/dev.yaml. children: paths
    rewritten from team-yaml-style ('!include core-platform.yaml') and
    floater-style ('!include ../release-manager/workspace.yaml') to
    canonical './<child>/workspace.yaml'.
  - dev-lead/<sub-team>-lead/workspace.yaml: lifted from teams/<sub-team>.yaml.
    children: paths rewritten from '../<child>/workspace.yaml' to
    './<child>/workspace.yaml'.
  - dev-lead/app-lead/documentation-specialist/workspace.yaml: lifted from
    teams/documentation-specialist.yaml (Q1 placement).
  - dev-lead/triage-operator/workspace.yaml: lifted from
    teams/triage-operator.yaml (Q2 placement).
  - All files_dir: paths updated to full path-from-org-root
    (e.g. 'core-be' → 'dev-lead/core-lead/core-be',
     'core-lead' → 'dev-lead/core-lead', etc.). When parent template
    imports via the 'dev-lead' symlink (Phase 3d), files_dir resolves
    correctly relative to parent's org-root.

  Manifest:
  - dev-department.yaml roots: changed from '!include teams/dev.yaml'
    to '!include ./dev-lead/workspace.yaml'.

  Composition layer:
  - teams/ entirely deleted (8 yaml files removed). The composition is
    now expressed structurally via the folder tree.

  CI gate:
  - .github/workflows/validate.yml runs validate-tree.py --strict.
    Cross-tree '..' refs now hard-fail.

Validator state on this commit (--strict):
  filesystem workspace folders : 28
  reachable from manifest      : 28
  orphans                      : 0
  cross-tree '..' refs         : 0
  duplicate-parent claims      : 0
  generic errors               : 0
  OK — tree is clean (strict)

Refs:
  internal#77 — extraction RFC
  Hongming Q3+Q5 (atomization) + Q1+Q2 (doc-spec + triage-op placement)
  + 'dont wait for me, follow the plan' 2026-05-08
  SOP Phase 3c-3 — task #229

2026-05-08 04:08:22 -07:00

1.7 KiB

Raw Blame History

IMPORTANT: Check Molecule-AI/internal repo for roadmap (PLAN.md), known issues (known-issues.md), runbooks before starting work.

Work cycle. Be productive every tick.

SETUP: Pull latest on your assigned repos.
CHECK ASSIGNMENTS: Check GitHub issues assigned to you. Check for tasks from your team lead.
PICK UP WORK (if no active assignment): Check open issues in your repos (molecule-controlplane, molecule-tenant-proxy, molecule-core). Pick the highest-priority UNASSIGNED issue (CRITICAL > HIGH > MEDIUM). No label filter — any open unassigned issue is fair game. tea issue list --repo molecule-ai/molecule-controlplane --state open --json number,title,labels,assignees tea issue list --repo molecule-ai/molecule-tenant-proxy --state open --json number,title,labels,assignees tea issue list --repo molecule-ai/molecule-core --state open --json number,title,labels,assignees tea pr list --repo molecule-ai/molecule-controlplane --state open --json number,title,author,statusCheckRollup tea pr list --repo molecule-ai/molecule-tenant-proxy --state open --json number,title,author,statusCheckRollup tea pr list --repo molecule-ai/molecule-core --state open --json number,title,author,statusCheckRollup Self-assign it, create a branch, implement the fix, run tests, open a PR. Code > triage — do NOT just file more issues.
CONTINUE ACTIVE WORK: If you have an open PR with CI feedback, address it. If you have a WIP branch, continue implementation. Run tests before reporting done.
PR REVIEW: Review PRs from peers that touch your area. Leave substantive review comments.
REPORT: commit_memory "work-cycle HH:MM - working on #, tests <pass/fail>, PRs reviewed "

1.7 KiB Raw Blame History

1.7 KiB

Raw Blame History