Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
spec(FIX-1786): every statement of the sharing rule names org scope
The teams table, the real-need row, the concept's rule line and figure
title, and DOCS.md's proposed overview now say the same thing as the goal:
a worker's own state and user-scoped data are private; shared resources and
org scope are shared, and a flow writes to org scope by its author's choice.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XMg2dz8sMEdyzCQTRsaMTV
  • Loading branch information
claude committed Oct 6, 2026
commit 3aee05db0ecaab2ea35da0b710fc40d48ff17fb1
5 changes: 3 additions & 2 deletions specs/epics/FIX-1786/DOCS.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,8 +13,9 @@ what Workforce does, never what it used to do. Each child's own `DOCS.md` carrie
> `@flow-state-dev/workforce` gives each user a roster of workers: agents, or deterministic
> workflows, that work for that user and act as them.
>
> One rule covers who sees what. Everything is private to one user, and the only shared
> things are shared resources. Your workers, your private projects and every session
> One rule covers who sees what: a worker's own state and your user data are private to you,
> while shared resources and org-scope data are shared with your org, and a flow writes to org
> scope only when its author built it to. Your workers, your private projects and every session
> are yours alone. A shared project, its workstream entries and the org's worker library are
> shared, and each line written there names the user and the worker that wrote it.
>
Expand Down
4 changes: 2 additions & 2 deletions specs/epics/FIX-1786/SPEC.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@

| A team that… | Today | After this epic |
|---|---|---|
| **builds an app on Workforce** | Learns hires, mailboxes, rooms, talk sessions, flow instances and owner pins, and three meanings of "shared" | Learns one rule: everything is private to one user, and only shared resources are shared. Then workers, each naming the flow that runs it, coordinators and workstreams |
| **builds an app on Workforce** | Learns hires, mailboxes, rooms, talk sessions, flow instances and owner pins, and three meanings of "shared" | Learns one rule: a worker's own state and user-scoped data are private to one user, while shared resources and org scope are shared, and a flow writes to org scope by its author's choice. Then workers, each naming the flow that runs it, coordinators and workstreams |
| **runs an org with more than one user** | A hire locked to the org alone is reachable by every member. Mailbox boards are org rows no session narrows, and a drain runs as whoever triggers it | A worker belongs to one user and acts as them. Shared work enters a roster only through its owner |
| **wants a worker of their own** | Edits a `WORKER.md` and restarts, or gets an org hire every member can reach | Forks a standard worker, or copies a template from the org's library. The copy is theirs alone |
| **hands work between workers** | A mailbox's members are fixed when it opens, and workers can't answer each other | A coordinator routes by judgment, best fit, round robin or everyone, to delegates it can add and remove |
Expand All @@ -33,7 +33,7 @@ out of it ([D3](DECISIONS.md#d3), [ER-2](BUSINESS-RULES.md#what-a-team-gets-and-

| Is it the right goal? | |
|---|---|
| **The real need** | Jake's PRD: one rule set, where everything is private to one user and the only shared things are shared resources. The model is the problem, not its docs. Under it sits a hole: an org-locked hire reaches every member |
| **The real need** | Jake's PRD: one rule set, where a worker's own state and user-scoped data are private to one user, while shared resources and org scope, which a flow writes by its author's choice, are shared (Jake, 2026-10-06). The model is the problem, not its docs. Under it sits a hole: an org-locked hire reaches every member |
| **Smaller, and rejected** | "The terms are renamed." FIX-1796 alone meets it, and the org-locked hire still reaches everyone. Or "workers are private": FIX-1788 alone, while boards and projects stay org rows any member's session drains |
| **Bigger, and not this epic's** | Channels · user-to-user communication · transcript resources · files as migrations · long-lived session memory (FIX-1775) · removing flow instances and owner pins from the engine ([FIX-1798](https://linear.app/fixpoint-labs/issue/FIX-1798), after FIX-1788) |
| **Not done if** | Every child is Done and the closure check hasn't run · it ran with one user · Bob opens, names or writes any of Alice's workers, sessions, boards or workstream sessions · a task in Alice's chain runs as anyone else · one of Alice's boards claims another's rows · a user changes a standard worker · leg b never made a private project · a record stored before FIX-1790 reads in two orgs · a `MAILBOX.md` loads · Workforce still registers a flow instance or sets an owner pin · a retired term is left in an export or a published page ([ER-12](BUSINESS-RULES.md#what-a-team-gets-and-what-it-doesnt)) · a bug the closure run found is open |
Expand Down
2 changes: 1 addition & 1 deletion specs/epics/FIX-1786/concept/CONCEPT.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ This doc describes how Workforce should work, from first principles, in terms a

**A user is always a person.** The framework doesn't own identity and has no system users. An app can create a "system user" of its own, and to the framework it's just another user.

**Everything is private to one user. The only shared things are shared resources.** Every session belongs to one user, and nobody else can open it. Something is shared only when it's written to a shared resource, such as a channel's conversation or a shared project.
**A worker's own state and user data are private to one user. Shared resources and org scope are shared, and a flow writes to org scope by its author's choice.** Every session belongs to one user, and nobody else can open it. Something is shared only when it's written to a shared resource, such as a channel's conversation or a shared project.

The engine already works this way. What changes is that Workforce stops describing anything else as shared.

Expand Down
4 changes: 2 additions & 2 deletions specs/epics/FIX-1786/figures/concept-1-private-and-shared.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading