molecule-ai/molecule-core
53
0
Fork 2
Code Issues 190 Pull Requests 45 Actions 1 Packages Projects Releases Wiki Activity

Phase 4 — docs + onboarding for standalone-as-SSOT #1599

New Issue
Open
opened 2026-05-20 09:21:32 +00:00 by core-be · 0 comments
core-be commented 2026-05-20 09:21:32 +00:00
Member
Copy Link
Copy Source

Follow-up task to the standalone-as-SSOT migration (CTO-GO 2026-05-20).

Pre-conditions

  • Phase 1 (migration PR) merged on standalone
  • Phase 2 (0.2.0 published) complete
  • Phase 3 (monorepo cleanup) at least started, ideally complete

Tasks

1. README in standalone repo — contribution guide + release process

Standalone README was already updated in Phase 1 to declare it as canonical editable source. Round trip:

  • Inline contribution guide (clone, branch, PR target, review pattern)
  • Release process (version bump → tag → publish workflow → cascade)
  • Local development quickstart (run tests, build wheel, smoke-install)
  • Contract with monorepo (what the wheel exposes, what monorepo consumes)

2. README in monorepo workspace-server/ — link to standalone

molecule-core/workspace-server/README.md (or create if missing):

  • One-liner: Python runtime lives in molecule-ai-workspace-runtime, this server hosts Go workspace-management code
  • Link to standalone repo
  • For runtime work, send PRs to standalone

3. CONTRIBUTING.md in both

Standalone has a 1-KB CONTRIBUTING.md already. Audit it post-migration:

  • Reviewer/persona patterns (core-be / core-qa / core-devops)
  • 2-eye gate, persona-token model
  • Sec-fix flow (mention the 2 standalone fixes that monorepo dropped — do not let it happen again)

Monorepo CONTRIBUTING.md: add a section noting which dirs are still monorepo-edit (Go workspace-server, CP, BE, etc.) vs which go to standalone (any Python runtime change).

4. Update mol_* helper docs

~/.molecule-ai/AGENTS.md and related:

  • mol_clone — verify it can reach standalone (should — same Gitea org)
  • Any docs that reference the old monorepo workspace/ → publish-mirror arrangement need updating

5. Update the orchestrator playbook entries

Memory files in ~/.claude/projects/-Users-hongming/memory/:

  • New file: reference_standalone_as_ssot_runtime_repo.md — canonical doc for the new SSOT location, contract, drift-watch SOP
  • Cross-link from feedback_no_single_source_of_truth

6. Drift-watch SOP

The migration was needed because bidirectional drift accumulated silently. To prevent recurrence:

  • Weekly automated diff: standalone main vs PyPI latest vs workspace-template image runtime version
  • Alert if any > 7 days out of sync
  • Reviewer checklist line: "Have you verified this change does not need a companion in monorepo workspace-server?"

References

/cc core-devops

Follow-up task to the standalone-as-SSOT migration (CTO-GO 2026-05-20). ## Pre-conditions - Phase 1 (migration PR) merged on standalone - Phase 2 (0.2.0 published) complete - Phase 3 (monorepo cleanup) at least started, ideally complete ## Tasks ### 1. README in standalone repo — contribution guide + release process Standalone README was already updated in Phase 1 to declare it as canonical editable source. Round trip: - Inline contribution guide (clone, branch, PR target, review pattern) - Release process (version bump → tag → publish workflow → cascade) - Local development quickstart (run tests, build wheel, smoke-install) - Contract with monorepo (what the wheel exposes, what monorepo consumes) ### 2. README in monorepo workspace-server/ — link to standalone `molecule-core/workspace-server/README.md` (or create if missing): - One-liner: Python runtime lives in molecule-ai-workspace-runtime, this server hosts Go workspace-management code - Link to standalone repo - For runtime work, send PRs to standalone ### 3. CONTRIBUTING.md in both Standalone has a 1-KB CONTRIBUTING.md already. Audit it post-migration: - Reviewer/persona patterns (core-be / core-qa / core-devops) - 2-eye gate, persona-token model - Sec-fix flow (mention the 2 standalone fixes that monorepo dropped — do not let it happen again) Monorepo CONTRIBUTING.md: add a section noting which dirs are still monorepo-edit (Go workspace-server, CP, BE, etc.) vs which go to standalone (any Python runtime change). ### 4. Update mol_* helper docs `~/.molecule-ai/AGENTS.md` and related: - `mol_clone` — verify it can reach standalone (should — same Gitea org) - Any docs that reference the old `monorepo workspace/ → publish-mirror` arrangement need updating ### 5. Update the orchestrator playbook entries Memory files in `~/.claude/projects/-Users-hongming/memory/`: - New file: `reference_standalone_as_ssot_runtime_repo.md` — canonical doc for the new SSOT location, contract, drift-watch SOP - Cross-link from `feedback_no_single_source_of_truth` ### 6. Drift-watch SOP The migration was needed because bidirectional drift accumulated silently. To prevent recurrence: - Weekly automated diff: standalone main vs PyPI latest vs workspace-template image runtime version - Alert if any > 7 days out of sync - Reviewer checklist line: "Have you verified this change does not need a companion in monorepo workspace-server?" ## References - Parent migration PR: https://git.moleculesai.app/molecule-ai/molecule-ai-workspace-runtime/pulls/19 - Phase 3 task: #1598 /cc core-devops
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/ci
CI/CD pipeline issues
 do-not-auto-merge
Opt out of autonomous merge-queue merging
 kind/infrastructure
Infrastructure-related issues
 merge-queue
Ready for serialized Gitea merge queue
 merge-queue-hold
Temporarily hold PR in merge queue
 platform/go
Go platform test issues
 release-blocker
Blocks the staging→main promotion / a release
 release-test
security
test-label-sre
tier:high
High risk per dev-sop §SOP-6 — ceo only, 24h cooldown
 tier:low
Low risk per dev-sop §SOP-6 — engineers/managers/ceo can approve
 tier:medium
Medium risk per dev-sop §SOP-6 — managers/ceo can approve
 triage-test
test
 wip
Work in progress — do not auto-merge
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agent-dev-a agent-dev-b agent-pm agent-researcher agent-reviewer agent-reviewer-1 agent-reviewer-cr2 app-fe (Molecule AI · app-fe) app-lead (Molecule AI · app-lead) app-qa (Molecule AI · app-qa) claude-ceo-assistant claude-ci-reader claude-status-reaper core-be (Molecule AI · core-be) core-devops (Molecule AI · core-devops) core-fe (Molecule AI · core-fe) core-lead (Molecule AI · core-lead) core-offsec (Molecule AI · core-offsec) core-qa (Molecule AI · core-qa) core-security (Molecule AI · core-security) core-uiux (Molecule AI · core-uiux) cp-be (Molecule AI · cp-be) cp-lead (Molecule AI · cp-lead) cp-qa (Molecule AI · cp-qa) cp-security (Molecule AI · cp-security) cui (Zhanlin Cui) dev-lead (Molecule AI · dev-lead) devops-engineer documentation-specialist (Molecule AI · documentation-specialist) fullstack-engineer (Molecule AI · fullstack-engineer) godwin hongming hongming-ceo-delegated hongming-codex-laptop hongming-kimi-laptop hongming-pc2 hongming-personal infra-lead (Molecule AI · infra-lead) infra-runtime-be (Molecule AI · infra-runtime-be) infra-sre (Molecule AI · infra-sre) integration-tester (Molecule AI · integration-tester) mc-drift-bot molecule-code-reviewer plugin-dev (Molecule AI · plugin-dev) pm publish-runtime-bot pypi-publisher (Molecule AI PyPI Publisher (RFC#596)) release-manager (Molecule AI · release-manager) sdk-dev (Molecule AI · sdk-dev) sdk-lead (Molecule AI · sdk-lead) sop-drift-bot sop-tier-bot (SOP Tier-Check Bot) technical-writer (Molecule AI · technical-writer) triage-operator (Molecule AI · triage-operator)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#1599
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?