Latest capacity correction — 2026-10-08: The human challenged the conservative four-owner allocation. Planner inspected real remaining source gaps and activated two independent implementation owners on existing approved Issues: Execute Storage #412 and Execute Verification #449. Current capacity is six Executes. Existing #495/#497/#498 leases and unique serial Integration remain. Ready owned code/check preparation proceeds in parallel; no duplicate task/store or permanent Review gate.

Latest global human directive — 2026-10-08 / #499: Apply responsibility owners to ALL Wonffice work. Planner may reduce, merge, split or reassign Execute roles when actual evidence warrants it. Current roles are the starting allocation, not a fixed quota. This supersedes earlier fixed-role/single-Execute/Planner-each-slice restrictions. Original product acceptance and release boundaries remain.

Latest human extension —2026-10-08: Planner must organize necessary Issues/Wiki AND create actual implementation Executes where an approved task lacks an owner. #498 justifies Execute Agent for the missing authenticated MCP read. #496 remains closed for its original two-author transition. Product delivery map and Agent contract record the extension; no new schedules, model changes or release authority.

Wonffice operating model — responsibility owners

Human approved on 2026-10-08. Transition and activation evidence #496 is the current transition record. This contract supersedes historical single-Execute/fixed Planner-dispatch statements. It preserves every original product acceptance criterion and release boundary.

Roles and stable ownership

Role	Responsibility	Chat
Planner	Whole goal, approved product direction, missing candidates/duplicates, cross-role ownership/dependencies, whole-product acceptance and release	01a0be9d-0a28-7741-8ce7-b500e1f41aaf
Execute Editor	Native editors/model/input/selection/history/serialization and Note/Word/Slides/Site consumers; Editor contract	01a11ad2-3ae3-71f0-ab7d-c0c5848664de
Execute Workspace	Office shell/tree/Project/My/auth/current permissions/API/PostgreSQL storage/recovery/schema-server; Workspace contract	01a11ad2-3e4e-7560-842a-bf51d1e5c0b3
Execute Agent	Agent-facing tools/transport/orchestration, first authenticated MCP read#498; Agent contract	01a11afc-7406-74b3-af37-53762d18b2a7
Execute Storage	Private document asset metadata/object-store/read/upload/fixed-attempt contract; existing #412, exact seven-file scope	01a11b92-e103-71d3-acc3-1b22720c5a69
Execute Verification	Deterministic actual-work-result/native criterion verification, existing #449; implementation author, no permanent Review gate	01a11b92-e58d-7e53-8325-ee0e4adb93a1
Execute Integration	Sole serial local develop/shared root/lock/config/policy writer and shared browser/API/privatePG verification owner	Existing Execute 01a0be0f-71b8-7570-b423-98b01a66631e
Research	Existing registered questions/evidence/intake; implementation is not automatic	Existing Research chats; no new schedules

Role activation, current task/liveness and exact base are read from #496 and each task Issue, not inferred from this stable ownership table. A completed readonly proposal is not implementation authority. The initial #496 transition introduced no Agent role; the latest human directive now adds only the justified Execute Agent under #498. There is no permanent Review gate.

Execution role display names

The latest human naming rule uses Execute XXX for every implementation/verification execution chat and its existing continuation automation. Current names: Execute Editor, Execute Workspace, Execute Agent, Execute Integration, Execute Storage, Execute Verification. The three existing execution continuation automations now use the same names. Current IDs/history/candidates/cadence/targets/status are preserved. A future split uses a clear functional suffix; a merge names its new responsibility and links preserved predecessors. Do not create duplicate chats or schedules to rename them. Planner and paused Research are coordination/intake identities.

Global default and adaptive role transitions

Each author owns approved functionality, checks, its Issue records and technical Wiki manuals. It selects the next actually ready approved Issue after completing its current acceptance, communicates directly for interfaces and defects, and sends one finished immutable candidate to Integration. Planner owns whole-goal direction, priorities, missing work/deduplication, capacity, cross-role conflicts and whole acceptance/release. Technical decisions and ordinary handoffs do not require a Planner approval or ACK relay.

Planner may consolidate duplicate work or idle dependency lanes, split independent ready implementation/check preparation, or add a role for an approved capability with no actual owner. Prefer existing owners and useful functional boundaries; neither package count nor an idle label justifies a new Execute. Record observed problem, exact Issue/base/files/API/dependencies, current producer, preserved candidate/evidence, safe transition point and successor owner before capacity changes. Finish or safely checkpoint atomic writes/checks first. Pause redundant continuation only after the successor accepts the preserved scope. Keep history/recoverable output; do not restart from elapsed time or create simultaneous writers.

Keep exactly one named Integration function for serial local develop/shared config/package/lock/policy and shared API/privatePG/browser resources. A future merged role must explicitly transfer that unique responsibility; the current Integration owner remains unchanged. Independent owned implementation and check preparation may run alongside the shared serial work.

This default covers the whole existing and future Wonffice backlog. Route each Issue when triaged or resumed; preserve current claims, original criteria and readiness. Do not bulk activate the backlog or rewrite human holds. Research categories and current PAUSED one-question lifecycle remain; evidence becomes planning intake, not automatic product work or release gates. All nine existing Wonffice automation instructions carry this policy while retaining complete historical prompts and exact cadence/target/status/notification. Latest direct author-continuation requests remain in effect. No model/effort/supervisor change is part of this rollout.

Current capacity decision: six Executes. The prior four-owner observation was too narrow: #495 ownership did not establish that the whole approved backlog lacked independent ready implementation. Source inspection found missing private asset service #412 and actual work-output/criterion binding #449. Storage and Verification implement those exact disjoint scopes from accepted a615, then hand finished candidates to Integration. Shared runtime and final integration are still serial. Collect actual overlap, dependency wait, defects and acceptance evidence; do not claim measured speedup from role creation. Repository policy #499 is accepted and closed after exact two-file local integration05ba7596220fee267160842e569a9af38ab505d8, full unchanged-budget Node22/pnpm8.15 preflight and actual integrated docs4PASS. All original sections and nine saved instructions are preserved. This accepts governance only; original product/Goal/release criteria remain.

Completed global policy rollout

#499 is closed for its governance scope only. Exact candidate/local develop 05ba7596220fee267160842e569a9af38ab505d8, tree 381f6fd097adc55bd4cb36e630c99a8fea66d626, changed only AGENTS.md and docs/operations/wonffice-workflow.md from d624. Original entire sections remain byte-preserved; latest human-approved six-role/naming prefix is explicit. Actual Node22.22/pnpm8.15 preflight exited0 with unchanged budgets, zero new/increased lint and three known source exclusions; integrated documentation4PASS0skip. Planner checked all13 frozen receipt files/83331bytes, exact two-file commit/current source/identity and all nine retained automation prompts/cadence/target/status/notification. RESULT 4a6fdd178c4693f57982f65b592a489c3220d6014bb163e15f1892d327d9bef4; manifest f0f6e74c02323d60d4113e54760cde107d5e8e431af7c4d78053ff477f4c8ba0. No product runtime replay or product/alpha/Goal acceptance follows. Current six authors continue exact scoped work; Integration queues named shared dependencies and resources serially.

Issues: current work and accountable evidence

Each author may deduplicate/create/refine/claim necessary work inside approved product scope, choose the next actually ready task, and maintain its own wonffice-work:v1 current record. A milestone/OPEN flag is not readiness. Preserve original body/acceptance and human holds. New product directions, cross-role scope expansion or release decisions go to Planner/human; routine technical choices do not wait for Planner.

Before code, record: Issue/owner/chat, exact immutable base/worktree/branch and owned files, dependencies, intended behavior/API/version/capabilities, original AC and meaningful verification. Cross-domain files get one named writer and agreed interface. Shared budgets are not raised to make tests pass.

One finished handoff goes directly from author to Integration: immutable parent/child SHA, complete owned delta, affected checks/first failures, limitations and actual readiness. Integration adopts each delta once, checks the current merged head and records integration SHA/evidence on the Issue. Mechanical reconciliation is recorded; semantic changes return to the author. No repeated ACK relay or historical test campaign merely because monitoring fires.

Implemented, verified, integrated, accepted and released are different. Close a task only when its full original acceptance is met with applicable integrated evidence; report unmet conditions explicitly. Parent trackers/Goal/alpha remain open until their own criteria pass. Planner checks the overall product and release rather than approving every author step.

Wiki: durable contracts and useful manuals

Planner owns this operating model, role boundaries, global roadmap/decisions and cross-role contracts. Editor, Workspace and Agent own their functional manuals, APIs, supported limits, real usage examples and evidence links. One writer per page; proposed cross-role edits are agreed before publication. Each role may publish its own Wiki pages within this approved scope without a routine Planner relay. Check the latest remote parent, preserve concurrent edits and verify easylogic [email protected] as both author and committer; record the actual published SHA. Product code publication remains separately governed. Keep existing Research pages and source/history.

Wiki links to Issues for current progress. It does not duplicate dynamic liveness tables or replace source contracts. Each capability states native/controlled/genuine/consumer/integrated/release stage and exact evidence. Record unsupported behavior and next owned Issue; do not claim release from a package configuration or local prototype. Old operational snapshots remain labelled history.

Integration and shared verification

Authors use isolated managed worktrees and issue branches from then-current accepted local develop. The shared user checkout is preserved. No arbitrary checkout/reset/stash, simultaneous same-file writer or mid-producer source change. Worktree isolation is not runtime/database isolation.

Integration is the sole local-develop and shared root/lock/config/policy writer. Shared browser/API/privatePG runs are serial with explicit owned processes, ports, databases and cleanup. Native/auth/current-ACL/PG/browser/recovery checks and actual Node22.22/pnpm8.15 preflight remain required where applicable. Reuse unaffected exact-source evidence only under the existing rule; do not weaken tests, fixtures or acceptance. Product commits remain local until separately authorized protected release; Scoped Wiki documentation publication is distinct from product code release. This role transition does not change saved model/reasoning-effort settings, supervisors or schedules; retain applicable latest human model instructions.

Preserved boundaries and first cycle

Original #495/Goal13/alpha remain incomplete. #434 is human-held; #420 Apply remains unavailable; Yorkie is paused; mobile QA is off; physical OS IME is separately unproved. Privacy/encryption/account/operator/backup/install/release criteria stay. No credential/customer contents enter public Issues or Wiki.

For the first jointly delivered feature, measure assignment wait, duplicate verification invocations, shared runtime/integration waiting, failures/repairs and acceptance completeness against a comparable prior cycle. Keep one current cycle record in #496 or its linked task. No speedup claim before results. Ambiguous ownership, omitted required evidence or runtime interference triggers a safe checkpoint and correction; no automatic restart or duplicate writer.