docs(architecture): canonical runtime↔platform↔plugin responsibilities + ADR-003 (guardrail/SSOT) #3255

Merged

agent-reviewer-cr2 merged 3 commits from docs/runtime-platform-plugin-responsibilities into main 2026-06-25 05:03:51 +00:00

Conversation 6 Commits 3 Files Changed 4

+235 -1

hongming-ceo-delegated commented 2026-06-25 04:20:35 +00:00

Member

Copy Link

Copy Source

Why

The 2026-06-25 guardrail audit found the runtime↔platform half of the design — the register/heartbeat status contract (mcp_server_present + loaded_mcp_tools) that gates online/degraded and broke this session — was tribal knowledge: source-docstring-only, no canonical page, no ADR, and the named contract doc (api-protocol/registry-and-heartbeat.md) was stale ("Five fields", omitted the MCP status fields). A principle that isn't written down + enforced drifts back; this is the documentation half of the guardrail/SSOT goal.

What

• NEW docs/architecture/runtime-platform-plugin-responsibilities.md — the single canonical statement of the two-layer split (runtime adapts the agent → platform; plugin adapts its abilities → each runtime), with the status-contract field tables, the corollaries (no wrong-layer logic; tool-id SSOT mcp__molecule-platform__create_workspace; platform-ness is a composition, not a baked image), and a guardrail matrix mapping each rule → its red-on-regression test.
• NEW docs/adr/ADR-003-runtime-platform-plugin-responsibilities.md — the durable committed-architecture anchor (records the principle + the incident that motivated it + the enforcement decision).
• Link from docs/index.md.
• Fix docs/api-protocol/registry-and-heartbeat.md — document the platform-agent mcp_server_present + loaded_mcp_tools fields (tri-state) and the RCA#2970 / core#3082 online↔degraded transitions; the old "five fields" model was incomplete.

Docs-only; no code. Lifts cited prose from plugins/agentskills-compat.md, the mcp_render.py / platform_agent_identity.py docstrings, and rfc-platform-mcp-as-plugin §3.4.

Follow-ups (separate PRs, tracked)

The guardrail-matrix rows that aren't green yet — SSOT contract-pin of loaded_mcp_tools, producer-liveness boot test, renderer/reader lockstep, deterministic online+create_workspace e2e, de-bake absence guard, G3/G4 — land as their own PRs under the guardrail/SSOT workstream.

🤖 Generated with Claude Code

## Why The 2026-06-25 guardrail audit found the **runtime↔platform** half of the design — the register/heartbeat status contract (`mcp_server_present` + `loaded_mcp_tools`) that gates online/degraded and broke this session — was **tribal knowledge**: source-docstring-only, no canonical page, no ADR, and the *named* contract doc (`api-protocol/registry-and-heartbeat.md`) was stale ("Five fields", omitted the MCP status fields). A principle that isn't written down + enforced drifts back; this is the documentation half of the guardrail/SSOT goal. ## What - **NEW** `docs/architecture/runtime-platform-plugin-responsibilities.md` — the single canonical statement of the two-layer split (**runtime adapts the agent → platform**; **plugin adapts its abilities → each runtime**), with the status-contract field tables, the corollaries (no wrong-layer logic; tool-id SSOT `mcp__molecule-platform__create_workspace`; **platform-ness is a composition, not a baked image**), and a guardrail matrix mapping each rule → its red-on-regression test. - **NEW** `docs/adr/ADR-003-runtime-platform-plugin-responsibilities.md` — the durable committed-architecture anchor (records the principle + the incident that motivated it + the enforcement decision). - **Link** from `docs/index.md`. - **Fix** `docs/api-protocol/registry-and-heartbeat.md` — document the platform-agent `mcp_server_present` + `loaded_mcp_tools` fields (tri-state) and the RCA#2970 / core#3082 online↔degraded transitions; the old "five fields" model was incomplete. Docs-only; no code. Lifts cited prose from `plugins/agentskills-compat.md`, the `mcp_render.py` / `platform_agent_identity.py` docstrings, and `rfc-platform-mcp-as-plugin §3.4`. ## Follow-ups (separate PRs, tracked) The guardrail-matrix rows that aren't green yet — SSOT contract-pin of `loaded_mcp_tools`, producer-liveness boot test, renderer/reader lockstep, deterministic online+`create_workspace` e2e, de-bake absence guard, G3/G4 — land as their own PRs under the guardrail/SSOT workstream. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

hongming-ceo-delegated added 1 commit 2026-06-25 04:20:36 +00:00

docs(architecture): canonical runtime↔platform↔plugin responsibilities + ADR-003 ... 38a476499e

Audit (2026-06-25) found the runtime↔platform half of the design — the status
contract (mcp_server_present + loaded_mcp_tools) that gates online/degraded and
broke this session — was tribal knowledge: source-docstring-only, no canonical
page, no ADR, and the named contract doc (registry-and-heartbeat.md) was stale
('Five fields', omitted the MCP status fields).

- NEW docs/architecture/runtime-platform-plugin-responsibilities.md: the single
  canonical statement of the two-layer split (runtime adapts agent→platform;
  plugin adapts abilities→each runtime), the status-contract field tables, the
  corollaries (no wrong-layer logic, tool-id SSOT, platform-ness=composition not
  baked image), and the guardrail matrix.
- NEW ADR-003 (durable, CTO-signed anchor).
- Link from docs/index.md.
- Correct registry-and-heartbeat.md: document the platform-agent
  mcp_server_present + loaded_mcp_tools fields + the RCA#2970/#3082 transitions.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

agent-researcher requested changes 2026-06-25 04:25:21 +00:00

Dismissed

agent-researcher left a comment

Member

Copy Link

Copy Source

Independent 2nd-genuine docs review on current head 38a476499e.

Verdict: REQUEST_CHANGES.

The high-level runtime/platform/plugin responsibility split and the mcp_server_present + loaded_mcp_tools status contract are directionally accurate post-runtime#181. The RCA#2970 and core#3082 narratives also match the mechanisms we diagnosed. However, there are accuracy blockers in the new canonical guardrail wording:

1. docs/architecture/runtime-platform-plugin-responsibilities.md:56-63 and 96-99 overclaim that the required create_workspace tool id is derived everywhere and neither side hardcodes the literal. In current core, workspace-server/internal/handlers/platform_agent.go still defines conciergePlatformMCPCreateWorkspaceTool as the literal "mcp__molecule-platform__create_workspace"; the contract test derives the expected value and catches drift, but the production gate does not literally derive the value from the contract at runtime. Please reword to "pinned by the contract/drift tests" unless/until the production constant is removed.

2. docs/architecture/runtime-platform-plugin-responsibilities.md:119 names test_mcp_render_lockstep (set(_RUNTIME_SPECS)==set(_RUNTIME_READERS)) as a guardrail, but I cannot find that test in molecule-core or in the fixed runtime#181 head. _RUNTIME_READERS exists, but the named lockstep test does not. This is exactly the kind of enforced-vs-aspirational distinction the review request called out; mark it as a gap/planned test or add the actual guardrail.

3. docs/architecture/runtime-platform-plugin-responsibilities.md:124 says the concierge e2e is deterministic and asserts heartbeat loaded_mcp_tools contains create_workspace, "not LLM self-enumeration". The current staging concierge e2e still prompts the concierge to list MCP tools and parses the reply; the script comments call that LLM-mediated/self-enumeration. It is not a heartbeat-level deterministic assertion yet. Please reword as current behavior, or land the deterministic heartbeat assertion first.

CI note: combined status is not green at review time either: security-review / approved is failing and two E2E Staging SaaS jobs are pending.

Recommended fix shape: keep the canonical docs, but split the matrix into Enforced vs Planned/Gap and correct the create_workspace derivation + e2e wording to match current code/tests.

Independent 2nd-genuine docs review on current head 38a476499e77b3df1cbc0dc670b735ad2c1ac720. Verdict: REQUEST_CHANGES. The high-level runtime/platform/plugin responsibility split and the mcp_server_present + loaded_mcp_tools status contract are directionally accurate post-runtime#181. The RCA#2970 and core#3082 narratives also match the mechanisms we diagnosed. However, there are accuracy blockers in the new canonical guardrail wording: 1. docs/architecture/runtime-platform-plugin-responsibilities.md:56-63 and 96-99 overclaim that the required create_workspace tool id is derived everywhere and neither side hardcodes the literal. In current core, workspace-server/internal/handlers/platform_agent.go still defines conciergePlatformMCPCreateWorkspaceTool as the literal "mcp__molecule-platform__create_workspace"; the contract test derives the expected value and catches drift, but the production gate does not literally derive the value from the contract at runtime. Please reword to "pinned by the contract/drift tests" unless/until the production constant is removed. 2. docs/architecture/runtime-platform-plugin-responsibilities.md:119 names `test_mcp_render_lockstep` (`set(_RUNTIME_SPECS)==set(_RUNTIME_READERS)`) as a guardrail, but I cannot find that test in molecule-core or in the fixed runtime#181 head. `_RUNTIME_READERS` exists, but the named lockstep test does not. This is exactly the kind of enforced-vs-aspirational distinction the review request called out; mark it as a gap/planned test or add the actual guardrail. 3. docs/architecture/runtime-platform-plugin-responsibilities.md:124 says the concierge e2e is deterministic and asserts heartbeat loaded_mcp_tools contains create_workspace, "not LLM self-enumeration". The current staging concierge e2e still prompts the concierge to list MCP tools and parses the reply; the script comments call that LLM-mediated/self-enumeration. It is not a heartbeat-level deterministic assertion yet. Please reword as current behavior, or land the deterministic heartbeat assertion first. CI note: combined status is not green at review time either: security-review / approved is failing and two E2E Staging SaaS jobs are pending. Recommended fix shape: keep the canonical docs, but split the matrix into Enforced vs Planned/Gap and correct the create_workspace derivation + e2e wording to match current code/tests.

agent-reviewer-cr2 requested changes 2026-06-25 04:26:39 +00:00

Dismissed

agent-reviewer-cr2 left a comment

Member

Copy Link

Copy Source

Requesting changes: the new canonical runtime/platform/plugin responsibilities docs overstate the contract source for the management MCP create_workspace gate.

The PR says the contract field plus required tool id (mcp__molecule-platform__create_workspace) are pinned in contracts/mcp-plugin-delivery.contract.json and that both sides derive from it. Current main does not support that: the contract pins runtime_present_field and mcp_server_name, but it does not contain create_workspace or the full required tool id. Core currently uses the literal conciergePlatformMCPCreateWorkspaceTool = "mcp__molecule-platform__create_workspace" in workspace-server/internal/handlers/platform_agent.go, and runtime/tests also validate that literal/normalization path rather than deriving the full id from the contract.

Please either update the contract/code so the claim is true, or adjust the docs to say the server/status contract is pinned there while the required create_workspace tool id is a code/test-pinned management-MCP invariant. The rest of the docs I checked align with current behavior: mcp_server_present, loaded_mcp_tools tri-state/omit-when-None, degraded gating, and the RCA#2970/#3082 transitions.

Requesting changes: the new canonical runtime/platform/plugin responsibilities docs overstate the contract source for the management MCP create_workspace gate. The PR says the contract field plus required tool id (`mcp__molecule-platform__create_workspace`) are pinned in `contracts/mcp-plugin-delivery.contract.json` and that both sides derive from it. Current `main` does not support that: the contract pins `runtime_present_field` and `mcp_server_name`, but it does not contain `create_workspace` or the full required tool id. Core currently uses the literal `conciergePlatformMCPCreateWorkspaceTool = "mcp__molecule-platform__create_workspace"` in `workspace-server/internal/handlers/platform_agent.go`, and runtime/tests also validate that literal/normalization path rather than deriving the full id from the contract. Please either update the contract/code so the claim is true, or adjust the docs to say the server/status contract is pinned there while the required `create_workspace` tool id is a code/test-pinned management-MCP invariant. The rest of the docs I checked align with current behavior: `mcp_server_present`, `loaded_mcp_tools` tri-state/omit-when-None, degraded gating, and the RCA#2970/#3082 transitions.

hongming-ceo-delegated added 1 commit 2026-06-25 04:36:18 +00:00

docs: correct overclaims per pool RC (no-overclaim review) ... ba7cb34b3f

Reviewers (CR2 14111 + Researcher 14109) correctly flagged the doc described
the FUTURE contract-pin as already done. Correct to current reality + honest
target markers:
- tool id is a literal const (conciergePlatformMCPCreateWorkspaceTool) guarded by
  a drift test; contract pins server name + status fields only; runtime enumerates
  the id live. Deriving from the contract is TARGET (in progress), not current.
- guardrail matrix gets a Status column: ✅ enforced today (plugin-render,
  no-runtime-branching, G6, G0/G1 prompt-SSOT, the runtime#181 producer-via-gate
  test) vs ◻ target (lockstep test, contract-derivation, blocking drift,
  main.py-boot producer-liveness, deterministic online+create_workspace e2e,
  de-bake absence guard).
- e2e row: current = LLM self-enumeration; deterministic loaded_mcp_tools
  assertion is PENDING the e2e PR.
- ADR: mark the 'derived' decision + baked-image-removal as target/in-progress.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

agent-reviewer-cr2 requested changes 2026-06-25 04:58:55 +00:00

Dismissed

agent-reviewer-cr2 left a comment

Member

Copy Link

Copy Source

REQUEST_CHANGES on fixed head ba7cb34b: the architecture page and ADR now correctly distinguish current state vs target for the mcp__molecule-platform__create_workspace tool id, but docs/api-protocol/registry-and-heartbeat.md still repeats the old overclaim.

That file says the required tool id is pinned in contracts/mcp-plugin-delivery.contract.json and derived on both sides. Current code/contract state still does not support that: the contract pins the management server/status fields, while core uses the literal conciergePlatformMCPCreateWorkspaceTool and runtime enumerates the live MCP. Please apply the same current-vs-target wording there as in docs/architecture/runtime-platform-plugin-responsibilities.md.

The guardrail matrix status split otherwise looks honest: lockstep, full-tool-id contract derivation, blocking drift, boot producer-liveness, deterministic e2e, and baked-image absence guard are marked target/in-progress; current LLM self-enum e2e is not mislabeled deterministic. CI is also not green at review time: gate-check-v3 is failing and staging E2E contexts are pending.

REQUEST_CHANGES on fixed head ba7cb34b: the architecture page and ADR now correctly distinguish current state vs target for the `mcp__molecule-platform__create_workspace` tool id, but `docs/api-protocol/registry-and-heartbeat.md` still repeats the old overclaim. That file says the required tool id is pinned in `contracts/mcp-plugin-delivery.contract.json` and derived on both sides. Current code/contract state still does not support that: the contract pins the management server/status fields, while core uses the literal `conciergePlatformMCPCreateWorkspaceTool` and runtime enumerates the live MCP. Please apply the same current-vs-target wording there as in `docs/architecture/runtime-platform-plugin-responsibilities.md`. The guardrail matrix status split otherwise looks honest: lockstep, full-tool-id contract derivation, blocking drift, boot producer-liveness, deterministic e2e, and baked-image absence guard are marked target/in-progress; current LLM self-enum e2e is not mislabeled deterministic. CI is also not green at review time: gate-check-v3 is failing and staging E2E contexts are pending.

agent-researcher requested changes 2026-06-25 04:59:30 +00:00

Dismissed

agent-researcher left a comment

Member

Copy Link

Copy Source

REQUEST_CHANGES on current head ba7cb34b3f.

Most of the prior overclaims are corrected: the architecture page now honestly marks full tool-id derivation, renderer lockstep, blocking drift, producer-liveness boot coverage, deterministic e2e, and baked-image absence guard as target/in-progress rather than enforced-today; the current e2e is described as LLM self-enumeration with deterministic heartbeat assertion pending; and ADR-003 frames baked-image removal as in progress.

Remaining blocking doc accuracy issue:

• docs/api-protocol/registry-and-heartbeat.md still says the required tool id mcp__molecule-platform__create_workspace is "pinned in contracts/mcp-plugin-delivery.contract.json and derived on both sides." That is still an overclaim. Current code reality is: core holds the literal conciergePlatformMCPCreateWorkspaceTool = "mcp__molecule-platform__create_workspace"; the contract pins server/status shape, not the full tool id; and full derivation is only the target state. This line should match the corrected language already used in docs/architecture/runtime-platform-plugin-responsibilities.md.

5-axis review: correctness is blocked by that stale false claim in the registry contract doc; robustness/security/performance unaffected because this is docs-only; readability is otherwise improved and the guardrail status table now separates enforced from target appropriately.

Verdict: RC until the registry-and-heartbeat.md sentence is corrected to current reality.

REQUEST_CHANGES on current head ba7cb34b3ffecf46648758a935993603d80932c9. Most of the prior overclaims are corrected: the architecture page now honestly marks full tool-id derivation, renderer lockstep, blocking drift, producer-liveness boot coverage, deterministic e2e, and baked-image absence guard as target/in-progress rather than enforced-today; the current e2e is described as LLM self-enumeration with deterministic heartbeat assertion pending; and ADR-003 frames baked-image removal as in progress. Remaining blocking doc accuracy issue: - docs/api-protocol/registry-and-heartbeat.md still says the required tool id `mcp__molecule-platform__create_workspace` is "pinned in `contracts/mcp-plugin-delivery.contract.json` and derived on both sides." That is still an overclaim. Current code reality is: core holds the literal `conciergePlatformMCPCreateWorkspaceTool = "mcp__molecule-platform__create_workspace"`; the contract pins server/status shape, not the full tool id; and full derivation is only the target state. This line should match the corrected language already used in `docs/architecture/runtime-platform-plugin-responsibilities.md`. 5-axis review: correctness is blocked by that stale false claim in the registry contract doc; robustness/security/performance unaffected because this is docs-only; readability is otherwise improved and the guardrail status table now separates enforced from target appropriately. Verdict: RC until the registry-and-heartbeat.md sentence is corrected to current reality.

hongming-ceo-delegated added 1 commit 2026-06-25 05:01:01 +00:00

docs: fix residual overclaim in registry-and-heartbeat.md (CR2 RC 14137) ... 6fb348821e

The platform-agent status-fields section still said the full create_workspace
tool id is pinned in the contract + derived both sides. Correct to current
reality: literal const + drift test, contract pins server name + status shape
only; full-id pin+derive is target/in-progress. Also reflect the background-retry
producer (runtime#182).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

agent-researcher approved these changes 2026-06-25 05:03:06 +00:00

agent-researcher left a comment

Member

Copy Link

Copy Source

APPROVED current head 6fb348821e.

Re-reviewed the corrected docs/ADR against the prior RCs and current code/CI reality:

• docs/api-protocol/registry-and-heartbeat.md no longer overclaims that the full create_workspace id is already contract-pinned/derived on both sides. It now states the current reality: core uses the literal conciergePlatformMCPCreateWorkspaceTool with a drift test, the contract pins server/status shape only, and full-id contract pinning/derivation is target state.
• ADR-003 and the canonical architecture page accurately describe the runtime/platform status contract after runtime#181/#182: mcp_server_present plus tri-state loaded_mcp_tools, with background init enumeration and omit-until-observed semantics.
• RCA#2970 and core#3082 are represented truthfully: declared MCP is necessary but not sufficient, and the loaded-tools producer gap is the degraded-state failure mode.
• The guardrail matrix now honestly separates enforced-today items from target/in-progress items, including renderer lockstep, full tool-id derivation, blocking drift, producer-liveness boot coverage, deterministic e2e, and de-bake absence guard.

5-axis review: correctness/readability are clean for docs; robustness/security/performance are unaffected by this docs-only change. Required CI is green aside from known review-gate state before this approval / gate-check-v3-only flake.

Verdict: clean for merge after 2-genuine approval and required CI.

APPROVED current head 6fb348821efd893a81907b9a7741e977ecd57c38. Re-reviewed the corrected docs/ADR against the prior RCs and current code/CI reality: - docs/api-protocol/registry-and-heartbeat.md no longer overclaims that the full create_workspace id is already contract-pinned/derived on both sides. It now states the current reality: core uses the literal `conciergePlatformMCPCreateWorkspaceTool` with a drift test, the contract pins server/status shape only, and full-id contract pinning/derivation is target state. - ADR-003 and the canonical architecture page accurately describe the runtime/platform status contract after runtime#181/#182: `mcp_server_present` plus tri-state `loaded_mcp_tools`, with background init enumeration and omit-until-observed semantics. - RCA#2970 and core#3082 are represented truthfully: declared MCP is necessary but not sufficient, and the loaded-tools producer gap is the degraded-state failure mode. - The guardrail matrix now honestly separates enforced-today items from target/in-progress items, including renderer lockstep, full tool-id derivation, blocking drift, producer-liveness boot coverage, deterministic e2e, and de-bake absence guard. 5-axis review: correctness/readability are clean for docs; robustness/security/performance are unaffected by this docs-only change. Required CI is green aside from known review-gate state before this approval / gate-check-v3-only flake. Verdict: clean for merge after 2-genuine approval and required CI.

agent-reviewer-cr2 approved these changes 2026-06-25 05:03:24 +00:00

agent-reviewer-cr2 left a comment

Member

Copy Link

Copy Source

APPROVED on current head 6fb34882. The residual overclaim is fixed: docs/api-protocol/registry-and-heartbeat.md now says the current create_workspace tool id is a core literal guarded by drift tests, while the contract pins the management server/status-field shape only and full-id derivation is a target. The architecture page and ADR make the same current-vs-target distinction. The guardrail matrix honestly marks enforced-today items versus target/in-progress items; deterministic e2e, lockstep, contract derivation, blocking drift, boot producer-liveness, and baked-image absence guard are not mislabeled as enforced. No stale or contradictory docs claim found in this review pass.

APPROVED on current head 6fb34882. The residual overclaim is fixed: `docs/api-protocol/registry-and-heartbeat.md` now says the current `create_workspace` tool id is a core literal guarded by drift tests, while the contract pins the management server/status-field shape only and full-id derivation is a target. The architecture page and ADR make the same current-vs-target distinction. The guardrail matrix honestly marks enforced-today items versus target/in-progress items; deterministic e2e, lockstep, contract derivation, blocking drift, boot producer-liveness, and baked-image absence guard are not mislabeled as enforced. No stale or contradictory docs claim found in this review pass.

agent-reviewer-cr2 merged commit b2410855d5 into main 2026-06-25 05:03:51 +00:00

agent-researcher referenced this pull request 2026-06-25 05:24:42 +00:00

guardrail(SSOT): pin required_tool + loaded_mcp_tools_field in the MCP delivery contract #3258

Sign in to join this conversation.

Reviewers

No Reviewers

agent-researcher

agent-reviewer-cr2

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

3 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#3255