Workflow-first MVPDocs Center liveHelp routes reservedProjects & Billing in codeSupply & Marketplace in code

Projects

Projects now expose workflow ownership, project scope, and object scope on top of the same shared foundation model as Team. That keeps later execution, billing, and marketplace expansion attached to one stable boundary.

Help Center Docs Center

Project Boundary

Projects now read and mutate against the same shared foundation

Day 11 now keeps org, project, and membership reads on the D1-backed foundation, while account root updates, project creation, active-project switching, and project detail updates all enforce the same actor-aware foundation boundary before D1 mutation begins.

Service boundary: foundation-control-plane-service

State demoLive Empty Error

Day 11 foundation RBAC live

Total projects

Active now

Staging

Planned

Projects

Project-first means workflows, registries, runs, and future installs all start from the same operational boundary.

ProjectStatusRuntimeFlowsMembersUpdated

Account

Toolplane

growth plan · owner qq260316514@gmail.com

Active project: autofill-mvp

Billing email

billing@toolplane.ai

Account status

active

Account root mutation

This slice now requires an explicit actor with `account.manage` before account name, commercial plan, or status can change. The write lands on the same D1-backed org context path and appends `account.updated` into recent foundation activity.

Account nameAccount planAccount status

growth plan currently unlocks accepted execution and the shared credit reservation path.

Selected project

Autofill MVP

Primary D1-backed project for workflow, profile, target, and accepted execution proof.

Visibility

team

Credit policy

Accepted runs reserve account credits before browser execution starts.

Membership records

Active project mutation

Switching the active project updates the shared account context first, so Team invite defaults and later project membership mutations keep resolving from the same D1-backed root.

Project detail mutation

This Day 11 slice keeps selected-project mutation on the same D1-backed control-plane path, but now requires an explicit actor with `project.manage` before name, status, or runtime target can change. The slug stays stable for now.

Project nameProject statusRuntime target

Stable slug: autofill-mvp

Role and permission ladder

Owner

Owns billing, projects, workflows, and the highest privilege boundary for the account.

account.manageproject.manageregistry.writeteam.manageworkflow.writebilling.managerun.execute

Builder

Builds workflows and registries inside an allowed project without owning billing.

registry.writeworkflow.writerun.execute

This project already carries 32 membership records. Project writes now fail closed on explicit actor + project.manage before later object and credit rules continue.

Project boundary Org and RBAC Data foundation

Recent foundation activity

The shared org context now carries the latest account-root and project mutation evidence, so operator review does not have to leave the workbench to confirm who changed the foundation boundary.

Account updated

Toolplane

2026-03-30 13:38

Toolplane updated: plan changed on the shared foundation path.