Status: current planning index Owner: repository maintainers Last verified: 2026-10-19 (Native Execution Engines row); 2026-10-17 (P2 and bundled GStack rows); other work retains its owning plan's verification date Document type: governance index
This is the only cross-feature index of unfinished or protected implementation work. Owning contracts remain authoritative for behavior; this index answers only whether material delivery work remains and where it is tracked.
The categories are mutually exclusive:
- Active delivery or platform closure: implementation or release work is currently defined and can proceed without a new product decision.
- Pending product reopening or architecture decision: code may exist, but the product entry or architecture is intentionally not approved for delivery.
- Tracked follow-up without an active delivery plan: the contract records a real gap, but it is not an active queue item.
- Reference contract: long-term boundary only, not a separate work queue.
Completed plans transfer durable behavior to their owning contracts and are deleted. Test counts, screenshots, hashes and run diaries belong in CI or Release artifacts.
| Work | Current boundary | Closure condition |
|---|---|---|
| Native Execution Engines | T0–T6 implemented; complete frozen-source Core/daemon regression passes with explicit skips. License replacements and synthetic browser flows verified. Codex real owned scenes pass on their named snapshots. Kimi CLI 2.2.0 is installed locally; isolated real conversation, database-reopen recovery and cancellation pass after sandbox adaptation. OpenClaw real conversation/recovery pass after preventing detached self-respawn. Ling's completed-output delivery and cleanup cancellation races are repaired with adapter regression; host authority and identity revocation remain enforced. Electron IPC/migration/blocked composer have partial interaction evidence. See the validation record for source boundaries and failed historical runs | T7: OpenClaw approval/remote-stop and its retained unknown submission remain external acceptance boundaries, excluded from the Ling-only repair. Electron remaining interaction, complete Main/default startup, trusted checks/publication and production requests, other platforms/signing and language quality remain open. No production evidence was published or whole-repository pass claimed; uncertified native combinations stay blocked |
| P2 Conversation Experience | UX1-UX3 source/local complete with concerns. Rebased onto origin/main@a44c4377; Core 3339, Daemon 4899 plus one existing skip, Runner 407, Contracts 88, API 91, Web 520, Desktop Node 2426 plus four conditional skips, renderer 28, accessibility 3 and P2 browser 285 pass. No UX4 |
Review/CI/merge plus provider, installed-client, native Windows and packaging gates remain open. Native follow-up uses a local protocol fixture and normal chat, not all-surface external execution. Unknown effects stay blocked; original failed/interrupted reports remain retained. |
| Bundled GStack Client | Independent source delivery for GStack 1.91.101.0, all 57 skills, original TestSavant, package-owned browser, source publication, follow/pin/rollback, and frozen resource binding |
Review and merge the source PR, then complete Mac/Windows package, simulated-offline, damaged-resource, and 57 real-workflow acceptance without mixing the separate conversation answer/recovery UI follow-up |
| Channel Execution Completion | Required-participant fan-in, operation evidence, TerminalReport/source-Turn convergence, clean-break Attempt fencing, restart recovery, migration rollback/reopen, and aggregate source verification are green on the isolated delivery branch | Review the isolated diff, open PR/CI, merge, verify the actual remote main merge commit, then clean exact QA resources |
| Channel Context Processing | Channel and direct-message context views exist | Condensation, quote eligibility, persistence and redaction ownership are closed |
| Chrome Browser Built-in Plugin | Manual V1 pairing and six approved browser tools exist; Native Messaging 0.1.1 implementation is active |
Automatic Host connection, dual-platform package gates, real Chrome acceptance and Store resubmission close |
| Project Defect Remediation 2026-09 | Source remediation and automated Web/daemon/native regression are green across right-dock review, Runs, Profile i18n, Native Broker startup, and Native migration | Real macOS/Windows packaged-client and Chrome-extension environment acceptance closes |
| Workspace Command Rule Approval | Approval contracts, storage, daemon matching, and Composer split-button implementation exist | Real-browser proof of once versus persistent approval, cross-surface/restart behavior, revoke, and unsafe-command rejection closes |
| Permission Presets | Enforcement modes exist | Preset UI, effective preview and run audit agree with daemon enforcement |
| Provider Model Catalog And Discovery | Implemented and verified: versioned catalog, native discovery adapters, secure saved-key discovery and workbench provenance | Daily catalog PR review and normal provider connector maintenance continue |
| Conversation Surface | Shared primitives and initial package extraction are implemented | WorkCell, evidence, attachment, package CSS and Desktop-consumption boundaries close |
| Conversation Media Generation | Runner tools, target resolution, background MediaJob projection, and three-surface integration are defined | Shared tool registration, idempotent paid-task creation, recovery projection, and browser acceptance close |
| Conversation Right Dock Responsive Visibility | Shared requested/rendered/available state and narrow-width layout ownership are implemented | Real-browser proof at and around 900px across channel, normal conversation, and private chat, including restoration and no reserved blank region, closes |
| Bundled CUA Driver | Packaging, integrity and platform foundations exist | Computer Control Settings surface and remaining signed platform gates close |
| Desktop Computer Use PiP | Renderer and fail-closed local harness exist | Signed macOS, Windows, assistive-technology and clean-host release gates pass |
| External Work Phase 8.0 | Approved registry refactor; not yet implemented | Generic GitHub/Linear registry lands without behavior drift |
| External Work Phase 8.1 | Approved checkout-hint plan; not yet implemented | workspace.gitRemoteUrl remains separate from provider identity and authority |
| Ling Agent Session | Initial P1-P6 control-plane slices exist | Durable identity, instruction, report and execution ownership decisions close |
| Memory Review Policy | MRP.1-MRP.5 and first MRP.7 surface exist | Recall audit closes and global review-center decision is recorded |
| Office Documents Native Plugin | Source implementation and automated acceptance are complete | Real Excel/WPS acceptance and Windows/macOS packaged driver gates close |
| Sidebar, Approval, And Proposal Dialogs | Sidebar context previews, runtime approval queue, and channel proposal dialog boundaries are defined | Focused Web, Playwright, and real-browser acceptance across all three surfaces closes |
| Thread-First Work History | V1/V2 storage, evidence, archive and fork foundations exist | Diagnostics UI placement and remaining V2 work close |
| Desktop Theme Persistence | Web, repository and Apple Silicon implementation exist | Intel macOS and Windows packaged gates pass |
| Work | Decision required |
|---|---|
| Core Tools Runtime Boundary | Approve removal of built-in tools from Plugin presentation while preserving approval and diagnostics ownership |
| Mobile Remote Access | Mobile remains outside current acceptance until explicitly reopened after security review |
| Work Board Reopening | Reopen only after workspace projection and fresh browser acceptance |
| Startup And Diagnostics Reopening | Reopen only after product-copy and current-state revalidation |
| Workspace Tools Embedded Reopening | Reopen only after shared shell, scroll and overlay revalidation |
These are real gaps, but they must not be described as currently scheduled work.
| Contract | Remaining boundary |
|---|---|
| Provider Hardening And Media Adapters | Jimeng live generation and stored-artifact image-edit materialization |
| Two-Layer Configuration | Provider-profile cleanup and remaining Keychain migration, shared with runtime inheritance |
| Workspace State Storage | Opt-in rollout and remaining migration ownership |
| AI Councils | Council runtime and remaining product surfaces |
| Governance Notifications | Teammate-private delivery and Ling Agent/workspace digest |
| Conversation Memory Citations | Transcript citation footer and active source presentation |
| Conversation Activity Summary And Exploration Batching | Approved reversible presentation projection; implementation pending |
| Input Materialization | Remaining rich-input materializers and ownership gates |
| Media Production Image To Video | Source implementation is locally verified; real Provider acceptance still requires explicit paid authorization |
| Multi-Agent App | Next multi-agent protocol and product slices |
| Native Skill Recording | Message-overflow and Settings follow-up entry points |
| SQLite Modularization | Further split only after transaction and coordinator ownership is designed |
| Automations | Richer monitor sources, desktop notification policy and external destinations |
| Document | Role |
|---|---|
| External Work Roadmap | Shipped phase ledger and ordering authority for the active 8.x plans |
| Conversation Plan And Goal Modes | Active product and control-plane contract |
| Runtime Control Plane Roadmap | Single phased roadmap for operator, daemon-owned state and transport evolution |
| Runtime Control Plane Detailed Design | Object, API, event, ownership and verification contract |
- Update this index in the same change that changes a material work status.
- Do not infer implementation state from filenames or old phase numbers.
- A completed plan must move durable rules into its owning contract and be deleted.
- A real but unscheduled gap belongs in the tracked-follow-up table, not the active queue.
- Platform evidence plans remain only while a real signing, architecture or target-platform gate is open.
- Security, approval, recovery, migration and release boundaries require explicit review before consolidation.