DDK OS

Roadmap / Execution Board

Read-only V1 board backed by data/roadmap-board.json. No drag-and-drop, edit controls, execution triggers, or Supabase calls.

Last updated: 2026-04-30T17:54:10Z

35 total cards

5 active / gated

14 approval required

9 blocked or awaiting

Backlog

DDK-INFRA-001

Infrastructure · Backlog

Approval: Yes

Root Host Nginx 502

Owner: CTO
Status: Backlog / accepted known issue

Priority: Low unless we intend the root host to serve DDK OS.Risk: low

Next action

Leave untouched unless the root host is intentionally assigned to serve DDK OS.

Blocker status

Not blocking DDK OS because https://os.srv1374269.hstgr.cloud/roadmap works.

Approval gate

Sherman approval required before nginx config changes, service restarts, port changes, or root-host routing changes.

Source refs

https://os.srv1374269.hstgr.cloud/roadmap
https://srv1374269.hstgr.cloud/roadmap

P0F-001

Phase 0 · Phase 0F

Approval: No

Payload validation fixtures and transform test skeleton

Owner: CTO / CQO
Status: Backlog / sequenced after event audit decisions

Priority: mediumRisk: medium

Next action

Create redacted fixture plan for GHL, Stripe, and Meta transforms; keep tests read-only and secret-safe.

Blocker status

Awaiting Phase 0D/0E decisions

Approval gate

Sherman approval needed only if new packages, replay harness writes, or production fixtures are requested.

Source refs

specs/phase-0-data-foundation-plan.md#workstream-e--payload-validation-and-fixtures
specs/testing-and-qa-plan.md

P0G-001

Phase 0 · Phase 0G

Approval: Yes

Stripe/payment idempotency and unmatched handling

Owner: CTO / CSO / CQO
Status: Backlog / reliability hardening not started

Priority: mediumRisk: high

Next action

Verify production Stripe event delivery, uniqueness anchors, duplicate handling, and unmatched-payment reconciliation path.

Blocker status

Requires careful CSO/CQO review before any payment-path write changes

Approval gate

Sherman approval required before production payment handler writes or schema changes.

Source refs

specs/phase-0-data-foundation-plan.md#workstream-f--stripe-payment-reliability

P0H-001

Phase 0 · Phase 0H

Approval: No

Meta sync reliability and partial-sync visibility

Owner: CTO / CMO / CQO
Status: Backlog / health classification pending

Priority: mediumRisk: medium

Next action

Classify recurring 403 service failures and define dashboard/API behavior for partial sync data.

Blocker status

Awaiting Phase 0C and reporting contract alignment

Approval gate

Sherman approval required before changing sync behavior, mappings, or production schedules.

Source refs

specs/phase-0-data-foundation-plan.md#workstream-g--meta-sync-reliability
reports/phase-0/mapping-health-baseline-2026-04-28.md

P1-QA-001

Phase 1 · Testing / QA

Approval: Yes

Playwright/e2e implementation checklist

Owner: CTO / CQO
Status: Backlog / approved in principle, install deferred

Priority: mediumRisk: medium

Next action

Prepare checklist and request approval before package install; first tests should cover /dashboard and read-only API smoke behavior.

Blocker status

No package additions approved for current V1 board task

Approval gate

Sherman approval required before installing Playwright or adding test dependencies.

Source refs

specs/testing-and-qa-plan.md
specs/ddk-os-engineering-framework.md#7-qa-gates

P2-001

Phase 2 · Data Contracts / Supabase Accuracy

Approval: Yes

Stable reporting contracts and validation surface

Owner: CTO / CQO
Status: High-level backlog

Priority: mediumRisk: medium

Next action

Convert Phase 0 contract decisions into durable module contracts and validation routines.

Blocker status

Depends on Phase 0 closure and Phase 1 module cleanup sequence

Approval gate

Sherman approval required for schema/reporting-contract changes.

Source refs

specs/ddk-os-engineering-framework.md#3-module-architecture

P3-001

Phase 3 · UX / Operating Dashboard

Approval: Yes

Usability, filters, saved views, and state handling

Owner: CTO / CMO / CQO
Status: High-level backlog

Priority: mediumRisk: medium

Next action

Define UX scope after core Media Buying data contract is reliable.

Blocker status

Depends on Phase 1-2 foundations

Approval gate

Sherman approval required before major product UX expansion.

Source refs

specs/ddk-os-engineering-framework.md#3-module-architecture

P4-001

Phase 4 · Client Ops

Approval: Yes

Client status, onboarding, services, and account health module

Owner: CTO / CMO / CQO
Status: High-level backlog

Priority: mediumRisk: medium

Next action

Scope after Media Buying and data contracts stabilize.

Blocker status

Not started

Approval gate

Sherman approval required before new module build.

Source refs

specs/ddk-os-engineering-framework.md#3-module-architecture

P5-001

Phase 5 · Creative / Offers

Approval: Yes

Creative inventory, approvals, and asset performance module

Owner: CTO / CMO / CQO
Status: High-level backlog

Priority: lowRisk: medium

Next action

Define after campaign performance and client ops workflows are stable.

Blocker status

Not started

Approval gate

Sherman approval required before new module build.

Source refs

specs/ddk-os-engineering-framework.md#3-module-architecture

P6-001

Phase 6 · Sales / Appointments

Approval: Yes

Leads, booked calls, appointment quality, and pipeline visibility

Owner: CTO / CMO / CQO
Status: High-level backlog

Priority: lowRisk: medium

Next action

Scope once lead/appointment data contracts and attribution paths are validated.

Blocker status

Not started

Approval gate

Sherman approval required before new module build.

Source refs

specs/ddk-os-engineering-framework.md#3-module-architecture

P7-001

Phase 7 · Executive Overview

Approval: Yes

Business-level reporting and cross-module summaries

Owner: CTO / CEO / CQO
Status: High-level backlog

Priority: lowRisk: medium

Next action

Aggregate only after lower-level modules have reliable source contracts and QA coverage.

Blocker status

Not started

Approval gate

Sherman approval required before executive reporting module build.

Source refs

specs/ddk-os-engineering-framework.md#3-module-architecture

Ready

DB-SAFE-001

Controls · DB-sensitive workstream guardrail

Approval: No

Force read-only DB mode unless scoped WRITE_APPROVED=true token exists

Owner: CTO / CSO / CQO
Status: Required before next DB-sensitive workstream

Priority: highRisk: high

Next action

Implement and validate the guardrail before Phase 0E or any other DB-sensitive workstream begins.

Blocker status

Blocks next DB-sensitive workstream until implemented/validated.

Approval gate

No DB writes implied by this control card. Sherman approval remains required for any actual DDL/DML, production write, migration, deploy, or Phase 0E activation.

Source refs

docs/ddk-os-files/phase-0d-closure-note-2026-04-30.md

P1-MB-001

Phase 1 · Media Buying / Campaign Performance

Approval: Yes

Media Buying module cleanup and API contract lock

Owner: CTO / CMO / CQO
Status: Ready after Phase 0 gates; current active module remains /dashboard

Priority: highRisk: medium

Next action

Start with MB-0 baseline, then extract API logic, normalize metrics, split UI components, document Supabase contracts, and run QA pass.

Blocker status

Blocked from expansion until Phase 0 reliability gates pass

Approval gate

Sherman approval required before broader UI/API refactors or reporting view changes.

Source refs

specs/media-buying-module-plan.md
specs/ddk-os-engineering-framework.md#3-module-architecture

OPENCLAW-BUILDMODE-001

OpenClaw Stability · Codex CTO Build Mode

Approval: Yes

Codex CTO Build Mode safe operating rule

Owner: CTO / CQO / Dan
Status: Ready with restrictions / isolated worktree implementation tasks only

Priority: highRisk: high

Next action

Use only for scoped repo implementation tasks in isolated worktrees. Route every Build Mode task with explicit scope, worktree path, expected diff/artifact, and review gate.

Blocker status

Not blocked for isolated worktree implementation tasks; blocked for production workspace writes, runtime/config/deploy/security-sensitive work, and ACP/acpx.

Approval gate

CQO validation required before merge. Sherman approval required before merge, deploy, live writes, or any Tier 3 work. CSO required for secrets/auth/security-sensitive scope.

Source refs

proposals/OPENCLAW-CTO-001-codex-harness-build-mode.md
standards/cto-build-mode.md
standards/session-lifecycle.md

In Progress

No cards in this column.

CTO Review

No cards in this column.

CQO Validation

No cards in this column.

CSO Gate

OPENCLAW-ACP-001

OpenClaw Stability · ACP/acpx

Approval: Yes

ACP/acpx backend validation and enablement

Owner: CTO / CSO
Status: Blocked / ACP-acpx disabled and off-limits

Priority: highRisk: high

Next action

Do not enable or route through ACP/acpx. If revisited, start with an explicit CSO-gated validation plan and isolated non-production test.

Blocker status

Blocked: ACP/acpx is disabled/off-limits and not approved for runtime use.

Approval gate

CSO + Sherman approval required before enabling ACP/acpx, changing plugin-runtime-deps, or using ACP/acpx in production/runtime routing.

Source refs

logs/openclaw-acpx-package-install-verification-20260429T1713.md
logs/openclaw-cto-002-isolated-acp-functional-validation-20260429T1746.md

Needs User Approval

P0E-001

Phase 0 · Phase 0E

Approval: Yes

Webhook/event audit rollout planning

Owner: CTO / CSO / CQO
Status: WP1 complete; WP2 rollout planning needs approval

Priority: highRisk: high

Next action

Ask Sherman to approve WP2 bounded technical planning for broader metadata-only webhook/event audit rollout across remaining webhook/event surfaces; keep no-raw-payload standard and scope future production writes through DB-SAFE-001.

Blocker status

WP1 closed. WP2 awaits Sherman approval before broader handler changes, schema changes, production writes, or rollout execution.

Approval gate

Sherman approval required before WP2 implementation, additional handler audit writes, schema changes, migrations, production writes, or any raw payload/body/header/token/customer/contact/plaintext PII storage.

Source refs

specs/phase-0-data-foundation-plan.md#workstream-d--webhookevent-audit-design
public.webhook_events
P0E-WP1 / DB-SAFE-001

Done

P0A-001

Phase 0 · Phase 0A

Approval: No

Mapping health baseline and repeatable report

Owner: CTO
Status: Done / baseline report implemented

Priority: highRisk: low

Next action

Use baseline as reference for later Phase 0 validation and regression checks.

Blocker status

Closed

Approval gate

No active approval gate; future data writes still require separate approval.

Source refs

reports/phase-0/mapping-health-baseline-2026-04-28.md
scripts/reports/phase0-mapping-health.js
specs/sql/phase0-mapping-health-validation.sql

P0B-001

Phase 0 · Phase 0B

Approval: No

Parser blank-only backfill closure

Owner: CTO / CQO
Status: Done / closed after blank-only backfill and CQO validation

Priority: highRisk: low

Next action

Keep closure docs as the durable record; do not reopen unless a new parser defect is approved as separate work.

Blocker status

Closed

Approval gate

Closed; any future parser writes require separate Sherman approval.

Source refs

specs/phase-0-data-foundation-plan.md#19-phase-0b-parser-backfill-closure--complete
specs/phase-0-backlog.md
reports/phase-0/phase-0b-parser-backfill-apply-2026-04-29T14-52-52-175Z.md

P0C-001

Phase 0 · Phase 0C

Approval: No

Service type standardization implementation/local validation

Owner: CTO
Status: Done / closed

Priority: highRisk: low

Next action

Use Phase 0C closure as the baseline for the next Phase 0 workstream; any future production write or schema change remains separately gated.

Blocker status

Closed

Approval gate

Closed; separate Sherman approval required for any future deploy, production data write, or schema change.

Source refs

reports/phase-0/phase-0c-service-type-readonly-inspection-2026-04-29T15-10-00Z.md
specs/phase-0-data-foundation-plan.md#workstream-b--service-type-standardization

ROADMAP-001

Phase 0 · DDK-OPS-BOARD-V1

Approval: No

Read-only roadmap execution board V1

Owner: CTO / CQO
Status: Done / Roadmap Board V1 complete

Priority: highRisk: low

Next action

Preserve V1 scope as a read-only board backed by data/roadmap-board.json; future enhancements should be separate backlog cards.

Blocker status

Closed

Approval gate

Closed for V1; no Supabase calls, schema changes, or execution triggers are included in this scope.

Source refs

specs/roadmap-execution-board-v1-plan.md
data/roadmap-board.json
/home/dan/.openclaw/workspace/wiki/projects/ddk-os.md

P0D-001

Phase 0 · Phase 0D

Approval: No

Supabase data contract for Media Buying and identity joins

Owner: CTO / CQO
Status: Done / Phase 0D functionally complete; CQO PASS accepted

Priority: highRisk: medium

Next action

Preserve closure evidence as durable record. Before Phase 0E or any DB-sensitive workstream, complete DB-SAFE-001 read-only/write-token guardrail.

Blocker status

Closed; no rollback needed. Phase 0E remains not approved.

Approval gate

Phase 0D closure accepted. Phase 0E and any future deploy, schema change, migration, production write, dashboard/API implementation, or DB-sensitive write remain separately gated.

Source refs

docs/ddk-os-files/phase-0d-supabase-data-contract-2026-04-29.md
docs/ddk-os-files/phase-0d-validation-checklist-2026-04-29.md
specs/phase-0-data-foundation-plan.md#workstream-a--supabase-contract-lock
specs/media-buying-module-plan.md#4-data-contract-draft
docs/ddk-os-files/phase-0d-closure-note-2026-04-30.md
docs/ddk-os-files/phase-0d-validation-evidence-2026-04-30/phase-0d-closure-cqo-evidence.md
docs/ddk-os-files/phase-0d-validation-evidence-2026-04-30/phase-0d-closure-validation.json

P0E-WP1

Phase 0 · Phase 0E WP1

Approval: No

Metadata-only webhook/event audit foundation

Owner: CTO / CSO / CQO
Status: Done / WP1 closed; CSO APPROVED and CQO PASS

Priority: highRisk: high

Next action

Use WP1 as the safe baseline for WP2 planning; keep future production writes scoped through DB-SAFE-001 and preserve no-raw-payload audit storage.

Blocker status

Closed

Approval gate

WP1 closed. Separate Sherman approval required before WP2 implementation, new handler writes, schema changes, migrations, production writes, or raw payload storage.

Source refs

public.webhook_events
P0E-WP1 / DB-SAFE-001
client-won / client-onboarded / ghl-payment handlers

P0D-FU-001

Phase 0 · Phase 0D validation/follow-up

Approval: No

Live-column exports for Meta sync/mapping tables

Owner: CTO / CQO
Status: Done / accepted in Phase 0D closure evidence

Priority: highRisk: medium

Next action

No active Phase 0D action. Retain evidence; route any future changes as a separately approved workstream after DB-SAFE-001.

Blocker status

Closed by accepted Phase 0D CQO PASS; not an active Phase 0D blocker.

Approval gate

Closed for Phase 0D. Separate approval still required before any future production write, migration, deploy, schema change, dashboard/API implementation, or Phase 0E activation.

Source refs

docs/ddk-os-files/phase-0d-supabase-data-contract-2026-04-29.md#phase-1-blockersgates
docs/ddk-os-files/phase-0d-validation-checklist-2026-04-29.md
docs/ddk-os-files/phase-0d-closure-note-2026-04-30.md
docs/ddk-os-files/phase-0d-validation-evidence-2026-04-30/phase-0d-closure-cqo-evidence.md
docs/ddk-os-files/phase-0d-validation-evidence-2026-04-30/phase-0d-closure-validation.json

P0D-FU-002

Phase 0 · Phase 0D validation/follow-up

Approval: No

Meta campaign mapping uniqueness enforcement

Owner: CTO / CQO
Status: Done / accepted in Phase 0D closure evidence

Priority: highRisk: medium

Next action

No active Phase 0D action. Retain evidence; route any future changes as a separately approved workstream after DB-SAFE-001.

Blocker status

Closed by accepted Phase 0D CQO PASS; not an active Phase 0D blocker.

Approval gate

Closed for Phase 0D. Separate approval still required before any future production write, migration, deploy, schema change, dashboard/API implementation, or Phase 0E activation.

Source refs

docs/ddk-os-files/phase-0d-supabase-data-contract-2026-04-29.md#phase-1-blockersgates
docs/ddk-os-files/phase-0d-validation-checklist-2026-04-29.md
docs/ddk-os-files/phase-0d-closure-note-2026-04-30.md
docs/ddk-os-files/phase-0d-validation-evidence-2026-04-30/phase-0d-closure-cqo-evidence.md
docs/ddk-os-files/phase-0d-validation-evidence-2026-04-30/phase-0d-closure-validation.json

P0D-FU-003

Phase 0 · Phase 0D validation/follow-up

Approval: No

Payment revenue recognition basis

Owner: CTO / CQO
Status: Done / accepted in Phase 0D closure evidence

Priority: highRisk: high

Next action

No active Phase 0D action. Retain evidence; route any future changes as a separately approved workstream after DB-SAFE-001.

Blocker status

Closed by accepted Phase 0D CQO PASS; not an active Phase 0D blocker.

Approval gate

Closed for Phase 0D. Separate approval still required before any future production write, migration, deploy, schema change, dashboard/API implementation, or Phase 0E activation.

Source refs

docs/ddk-os-files/phase-0d-supabase-data-contract-2026-04-29.md#phase-1-blockersgates
docs/ddk-os-files/phase-0d-validation-checklist-2026-04-29.md
docs/ddk-os-files/phase-0d-closure-note-2026-04-30.md
docs/ddk-os-files/phase-0d-validation-evidence-2026-04-30/phase-0d-closure-cqo-evidence.md
docs/ddk-os-files/phase-0d-validation-evidence-2026-04-30/phase-0d-closure-validation.json

P0D-FU-004

Phase 0 · Phase 0D validation/follow-up

Approval: No

Appointment status/outcome pollution resolution

Owner: CTO / CQO
Status: Done / accepted in Phase 0D closure evidence

Priority: highRisk: high

Next action

No active Phase 0D action. Retain evidence; route any future changes as a separately approved workstream after DB-SAFE-001.

Blocker status

Closed by accepted Phase 0D CQO PASS; not an active Phase 0D blocker.

Approval gate

Closed for Phase 0D. Separate approval still required before any future production write, migration, deploy, schema change, dashboard/API implementation, or Phase 0E activation.

Source refs

docs/ddk-os-files/phase-0d-supabase-data-contract-2026-04-29.md#phase-1-blockersgates
docs/ddk-os-files/phase-0d-validation-checklist-2026-04-29.md
docs/ddk-os-files/phase-0d-closure-note-2026-04-30.md
docs/ddk-os-files/phase-0d-validation-evidence-2026-04-30/phase-0d-closure-cqo-evidence.md
docs/ddk-os-files/phase-0d-validation-evidence-2026-04-30/phase-0d-closure-validation.json

P0D-FU-005

Phase 0 · Phase 0D validation/follow-up

Approval: No

Canonical join validation

Owner: CTO / CQO
Status: Done / accepted in Phase 0D closure evidence

Priority: highRisk: medium

Next action

No active Phase 0D action. Retain evidence; route any future changes as a separately approved workstream after DB-SAFE-001.

Blocker status

Closed by accepted Phase 0D CQO PASS; not an active Phase 0D blocker.

Approval gate

Closed for Phase 0D. Separate approval still required before any future production write, migration, deploy, schema change, dashboard/API implementation, or Phase 0E activation.

Source refs

docs/ddk-os-files/phase-0d-supabase-data-contract-2026-04-29.md#phase-1-blockersgates
docs/ddk-os-files/phase-0d-validation-checklist-2026-04-29.md
docs/ddk-os-files/phase-0d-closure-note-2026-04-30.md
docs/ddk-os-files/phase-0d-validation-evidence-2026-04-30/phase-0d-closure-cqo-evidence.md
docs/ddk-os-files/phase-0d-validation-evidence-2026-04-30/phase-0d-closure-validation.json

P0D-FU-006

Phase 0 · Phase 0D validation/follow-up

Approval: No

Null/orphan/duplicate handling validation

Owner: CTO / CQO
Status: Done / accepted in Phase 0D closure evidence

Priority: highRisk: medium

Next action

No active Phase 0D action. Retain evidence; route any future changes as a separately approved workstream after DB-SAFE-001.

Blocker status

Closed by accepted Phase 0D CQO PASS; not an active Phase 0D blocker.

Approval gate

Closed for Phase 0D. Separate approval still required before any future production write, migration, deploy, schema change, dashboard/API implementation, or Phase 0E activation.

Source refs

docs/ddk-os-files/phase-0d-supabase-data-contract-2026-04-29.md#phase-1-blockersgates
docs/ddk-os-files/phase-0d-validation-checklist-2026-04-29.md
docs/ddk-os-files/phase-0d-corrected-write-plan-2026-04-29.md
docs/ddk-os-files/phase-0d-closure-note-2026-04-30.md
docs/ddk-os-files/phase-0d-validation-evidence-2026-04-30/phase-0d-closure-cqo-evidence.md
docs/ddk-os-files/phase-0d-validation-evidence-2026-04-30/phase-0d-closure-validation.json

P0D-FU-007

Phase 0 · Phase 0D validation/follow-up

Approval: No

Campaign-mode mapping validation

Owner: CTO / CQO
Status: Done / accepted in Phase 0D closure evidence

Priority: highRisk: medium

Next action

No active Phase 0D action. Retain evidence; route any future changes as a separately approved workstream after DB-SAFE-001.

Blocker status

Closed by accepted Phase 0D CQO PASS; not an active Phase 0D blocker.

Approval gate

Closed for Phase 0D. Separate approval still required before any future production write, migration, deploy, schema change, dashboard/API implementation, or Phase 0E activation.

Source refs

docs/ddk-os-files/phase-0d-supabase-data-contract-2026-04-29.md#phase-1-blockersgates
docs/ddk-os-files/phase-0d-validation-checklist-2026-04-29.md
docs/ddk-os-files/phase-0d-closure-note-2026-04-30.md
docs/ddk-os-files/phase-0d-validation-evidence-2026-04-30/phase-0d-closure-cqo-evidence.md
docs/ddk-os-files/phase-0d-validation-evidence-2026-04-30/phase-0d-closure-validation.json

P0D-FU-008

Phase 0 · Phase 0D validation/follow-up

Approval: No

Mock-data validation pass

Owner: CTO / CQO
Status: Done / accepted in Phase 0D closure evidence

Priority: highRisk: medium

Next action

No active Phase 0D action. Retain evidence; route any future changes as a separately approved workstream after DB-SAFE-001.

Blocker status

Closed by accepted Phase 0D CQO PASS; not an active Phase 0D blocker.

Approval gate

Closed for Phase 0D. Separate approval still required before any future production write, migration, deploy, schema change, dashboard/API implementation, or Phase 0E activation.

Source refs

docs/ddk-os-files/phase-0d-supabase-data-contract-2026-04-29.md#phase-1-blockersgates
docs/ddk-os-files/phase-0d-validation-checklist-2026-04-29.md
docs/ddk-os-files/phase-0d-closure-note-2026-04-30.md
docs/ddk-os-files/phase-0d-validation-evidence-2026-04-30/phase-0d-closure-cqo-evidence.md
docs/ddk-os-files/phase-0d-validation-evidence-2026-04-30/phase-0d-closure-validation.json

P0D-FU-009

Phase 0 · Phase 0D validation/follow-up

Approval: No

CQO Phase 0D checklist 100% pass

Owner: CTO / CQO
Status: Done / accepted in Phase 0D closure evidence

Priority: highRisk: medium

Next action

No active Phase 0D action. Retain evidence; route any future changes as a separately approved workstream after DB-SAFE-001.

Blocker status

Closed by accepted Phase 0D CQO PASS; not an active Phase 0D blocker.

Approval gate

Closed for Phase 0D. Separate approval still required before any future production write, migration, deploy, schema change, dashboard/API implementation, or Phase 0E activation.

Source refs

docs/ddk-os-files/phase-0d-supabase-data-contract-2026-04-29.md#phase-1-blockersgates
docs/ddk-os-files/phase-0d-validation-checklist-2026-04-29.md
docs/ddk-os-files/phase-0d-closure-note-2026-04-30.md
docs/ddk-os-files/phase-0d-validation-evidence-2026-04-30/phase-0d-closure-cqo-evidence.md
docs/ddk-os-files/phase-0d-validation-evidence-2026-04-30/phase-0d-closure-validation.json

OPENCLAW-STAB-001

OpenClaw Stability · Gateway / Discord

Approval: No

Gateway stability and Discord connectivity

Owner: CTO
Status: Done / gateway stable and reachable; Discord connected

Priority: highRisk: medium

Next action

Monitor gateway reachability, running-task drain, and CPU return-to-idle during future CTO/Codex sessions.

Blocker status

Closed for current connectivity baseline; reopen only if gateway or Discord routing regresses.

Approval gate

No active gate for status tracking. Any gateway, Discord routing, systemd, nginx, or runtime config change still requires separate approval.

Source refs

wiki/projects/ddk-os.md#operating-note--cto-discord-channel
runtime-manifest.md

OPENCLAW-CODEX-001

OpenClaw Stability · Native Codex

Approval: No

Native Codex app-server and CLI smoke validation

Owner: CTO / CSO
Status: Done / native app-server smoke passed; direct Codex CLI works with GPT-5.5

Priority: highRisk: medium

Next action

Keep Codex usage confined to approved Build Mode boundaries; do not treat smoke-test success as production write approval.

Blocker status

Closed for native app-server/CLI smoke only; production workspace writes and sensitive runtime/config work remain blocked.

Approval gate

No additional approval for completed smoke-test tracking. Separate Sherman approval required before merge/deploy/live writes; CSO gate required for sensitive areas.

Source refs

handoffs/2026-04-29/OPENCLAW-CTO-003-native-codex-app-server-discovery-handoff.md
handoffs/2026-04-29/OPENCLAW-CTO-003-native-codex-smoke-test-handoff.md
handoffs/restricted/2026-04-29/OPENCLAW-CTO-003-native-codex-smoke-cso-gate-handoff.md

Follow-up / Watchlist

P0-FU-001

Phase 0 · Follow-up

Approval: No

Review 9 newly classified unparsed entries

Owner: CTO / CQO
Status: Watchlist / explicitly not a Phase 0B blocker

Priority: lowRisk: low

Next action

Review later for possible reusable parser refinements if the pattern recurs.

Blocker status

No active blocker

Approval gate

Separate approval required only if future parser changes/write backfill are proposed.

Source refs

specs/phase-0-backlog.md#follow-up-backlog
specs/phase-0-data-foundation-plan.md#follow-up-not-a-phase-0b-blocker

OPENCLAW-SANDBOX-001

OpenClaw Stability · Sandbox / Worktree Guardrails

Approval: Yes

Workspace-write sandbox failure and danger-full-access guardrails

Owner: CTO / CSO / CQO
Status: Blocked for workspace-write / safe fallback is isolated worktree plus process boundaries

Priority: highRisk: high

Next action

Treat workspace-write as unavailable on this VPS. Keep danger-full-access confined to isolated worktrees and forbid production workspace writes, OpenClaw runtime/config changes, plugin-runtime-deps changes, secrets/auth files, Supabase production writes, schema migrations, Stripe/GHL/Meta config, webhook replay, nginx/systemd, deploys/restarts, and destructive cleanup.

Blocker status

Blocked: workspace-write sandbox unavailable due VPS namespace/Bubblewrap restrictions; production workspace writes not approved.

Approval gate

Sherman approval required before any production write/merge/deploy/live write. CSO required for runtime/config/security-sensitive work. CQO validation required before merge.

Source refs

handoffs/restricted/2026-04-29/OPENCLAW-CTO-runtime-codex-ENOENT-readonly-audit-handoff.md
proposals/OPENCLAW-CTO-001-codex-harness-build-mode.md
standards/cto-build-mode.md