molecule-ai/molecule-core
52
0
Fork 2
Code Issues 183 Pull Requests 14 Actions Packages Projects Releases Wiki Activity

Concierge-provisioned workspaces are created as parent_id NULL orphans — breaks A2A ("cannot communicate per hierarchy rules"), canvas depth-1 (#2601), and the single-root org model #2609

New Issue
Open
opened 2026-06-11 22:12:27 +00:00 by core-devops · 0 comments
core-devops commented 2026-06-11 22:12:27 +00:00
Member
Copy Link
Copy Source

Live repro on the fresh enter-os tenant (2026-06-11, second first-run blocker after #2608):

The org concierge provisioned enter-product + enter-growth via the management MCP. Both rows landed with parent_id: NULL — orphan ROOTS beside the kind='platform' org root, not children of it. Consequences, all observed live:

  1. A2A delegation hard-fails: every delegate_task_async from the concierge to its own team died with access denied: workspaces cannot communicate per hierarchy rules (sameOrg = subtree under THE single NULL root; an orphan sibling is outside it). The concierge then told the user it had "an RBAC restriction" — confabulated diagnosis, the real error was only on the delegation rows.
  2. Canvas depth-1 placement — this is the mechanism behind #2601 ("provisioned ws lands depth-1 beside old root").
  3. Org model violation: multiple parent_id-NULL rows per org breaks the org-scope invariant platform_agent.go documents (org = subtree under the single NULL root; org_api_tokens etc. anchor on it).

Hand-fix applied to enter-os: PATCH /workspaces/:id {parent_id: <org root>} for both, after which the same delegation completes cleanly (verified: delegation completed, no error).

Fix: the workspace-create path used by the management surface (and any path reachable without an explicit parent) must default parent_id to the org's kind='platform' root when none is specified — only the install/bootstrap path may create a NULL-parent row. Probably one default + a guard in workspace.go create (INSERT ... parent_id) keyed off the platform-root lookup that platform_agent.go already has. A backfill sweep for existing orphan rows (non-platform, parent NULL, org has a platform root) closes #2601 retroactively.

Refs #2601 (same root cause), #2608 (the other first-run blocker), core#2573 (context).

Live repro on the fresh `enter-os` tenant (2026-06-11, second first-run blocker after #2608): The org concierge provisioned `enter-product` + `enter-growth` via the management MCP. Both rows landed with **`parent_id: NULL`** — orphan ROOTS beside the kind='platform' org root, not children of it. Consequences, all observed live: 1. **A2A delegation hard-fails**: every `delegate_task_async` from the concierge to its own team died with `access denied: workspaces cannot communicate per hierarchy rules` (sameOrg = subtree under THE single NULL root; an orphan sibling is outside it). The concierge then told the user it had "an RBAC restriction" — confabulated diagnosis, the real error was only on the delegation rows. 2. **Canvas depth-1 placement** — this is the mechanism behind **#2601** ("provisioned ws lands depth-1 beside old root"). 3. **Org model violation**: multiple parent_id-NULL rows per org breaks the org-scope invariant platform_agent.go documents (org = subtree under the single NULL root; org_api_tokens etc. anchor on it). **Hand-fix applied to enter-os**: `PATCH /workspaces/:id {parent_id: <org root>}` for both, after which the same delegation completes cleanly (verified: delegation `completed`, no error). **Fix**: the workspace-create path used by the management surface (and any path reachable without an explicit parent) must default `parent_id` to the org's kind='platform' root when none is specified — only the install/bootstrap path may create a NULL-parent row. Probably one default + a guard in `workspace.go` create (`INSERT ... parent_id`) keyed off the platform-root lookup that `platform_agent.go` already has. A backfill sweep for existing orphan rows (non-platform, parent NULL, org has a platform root) closes #2601 retroactively. Refs #2601 (same root cause), #2608 (the other first-run blocker), core#2573 (context).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
approved
area/ci
CI/CD pipeline issues
 do-not-auto-merge
Opt out of autonomous merge-queue merging
 do-not-merge
hold from auto-merge (design review in progress)
 kind/infrastructure
Infrastructure-related issues
 merge-queue
Ready for serialized Gitea merge queue
 merge-queue-hold
Temporarily hold PR in merge queue
 needs-engineer
platform/go
Go platform test issues
 ready-to-build
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 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#2609
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?