Repository navigation
Fill the live inventory at boot (FIX-1405 S5–S7) - #1928
Conversation
A channel built with `inventory: true` carries the writer half: the three collections and two actions. `openInventory` runs them — one per open channel, in that channel's own session so the row's members come from the session state the post fence reads, and one for the roster's seats. The binder carries no member data. A roster's `members:` is what a file said when it was last read, and an edit to it does not reach an open channel, so a binder copying it forward would publish a file-time answer under a live name. Deviation from the spec's boot snippet: `openInventory` takes a `seatWriter` naming the flow the seat rows are written through. A collection can only be written from inside a running block — the resource routes carry an item's content, not its state — so the seat rows need a flow, and the roster does not say which. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PxDE76gD3BxXnPPjT7BT1T
A new `apps/docs` page for the two layers — what the declared tree answers, what the inventory answers, and the boot wiring — plus the package README's writer half: the boot call, the new exports, the two refusals and the collected `problems`, and the limits. Prose written and revised by docs-writer against the public surface and the tests, reviewed by docs-editor (SHIP, four nits, applied by the writer). Docusaurus build clean with no broken-link warnings. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PxDE76gD3BxXnPPjT7BT1T
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
The latest updates on your projects. Learn more about Vercel for GitHub. 3 Skipped Deployments
|
There was a problem hiding this comment.
Code Snob — outcome 3: already tight. No POC.
Read: packages/workforce/src/inventory/open-inventory.ts (the walker), packages/workforce/src/channel/channel-flow.ts (inventoryWriterActions and the inventory? spread), packages/workforce/src/channel/channel-binder.ts (the inventoryChannelFlow memo, exported kindOf / orderedById), the two barrels, packages/workforce/src/inventory/collections.ts (the floor the rows land on), and packages/workforce/test/inventory-binder.test.ts.
The new contract is two dispatches and two handlers: seats in one run through a named seatWriter, each channel writing its own row from its own session. A rewrite does not shrink that. Sharing kindOf / orderedById with openChannels is the one derivation that had to stay single; putting the seat writer on the channel kind is the recorded way to keep seatWriter to one field.
Rejected as not a different shape: orderedById(roster.seats) instead of the inline sort; dropping the { id, kind } rematerialize; a shared messageOf; deleting the factory memo; moving inventoryWriterActions to its own file; collapsing InventorySeatWriter into an inline type; stripping the essay comments (density matches openChannels / defineChannelFlow). Folding this into openChannels or deriving seatWriter would change the two-call boot that was already signed off.
Leftovers left alone: membership prune / reconcile (filed as follow-up).
Sent by Cursor Automation: Code Snob
There was a problem hiding this comment.
Simplify review (FIX-1405)
Parallel read-only passes (code quality, performance, reuse) on the PR diff.
Verdict: The core approach is the right tradeoff, not an over-engineered detour. Approve from a simplify lens, with nits below.
Did this go too far?
The two-writer split is doing real work:
- Seats: one batched action (no session).
- Channels: per-channel
registerChannelInInventorywith empty input somemberscome from live session state, not roster files.
Upserting channel rows from ChannelManifest would be less code but would republish file-time members: under a live name (the PR invariant; tests encode it). The app-supplied run door and pinned action names are awkward DX but match openChannels (no client package in workforce, multi-flowKind at boot). I would not simplify by bypassing flow actions for org-scoped collections.
Complexity that does not change the model:
- ~190 lines of inventory writer actions inside already-large
channel-flow.ts— considerinventory/inventory-writer-actions.ts. - Inventory imports
kindOf/orderedByIdfromchannel-binder— consider a neutral shared module. - Triplicated
messageOfacross boot binders — small DRY win. - Inline seat sort while channels use
orderedById— reuseorderedByIdfor seats.
Alternatives considered
- fast-glob/chokidar: boot is action-driven, not a disk walk.
- Single
openWorkforceBoot()helper: DX only; does not remove the two writer paths. - Parallel per-channel
runcalls: optional boot perf; needs concurrency policy + tests. - Batch membership upserts: valid follow-up for wide channels.
Performance
Serial run per channel and per-member membership upserts are O(N) at boot — fine for typical rosters.
Docs
README API table has two mismatches with code (inline).
Please fix README drift; channel-flow extract can be this PR or a quick follow-up.
Sent by Cursor Automation: Review For Best Approach
| * reach; there is no undoing a row that should not have been removed. | ||
| */ | ||
|
|
||
| import { kindOf, orderedById } from "../channel/channel-binder"; |
There was a problem hiding this comment.
Layer coupling: inventory imports kindOf / orderedById from channel-binder. Consider channel/manifest-kinds.ts or a deliberate public export so inventory does not depend on binder internals.
| * actions: { ...myActions, ...inventoryWriterActions("briefing") } | ||
| * }); | ||
| */ | ||
| export function inventoryWriterActions(kind: string) { |
There was a problem hiding this comment.
Structure: consider extracting inventoryWriterActions to inventory/inventory-writer-actions.ts — same API, easier navigation than growing this 1k+ line file.
| // The index is a projection of the row above, written from the same read | ||
| // of the same session state in the same run. It is never written alone, | ||
| // which is what stops the two from ever disagreeing. | ||
| for (const seatId of members) { |
There was a problem hiding this comment.
Boot perf (optional): one memberships.upsert per member; batch or bounded parallelism only if wide channels become common.
second-look: PR #1928Verdict: Appropriately scoped — no candidate here clears the bloat calibration gate; the surface tracks the already-approved spec's decisions, with real consumers (tests, docs, custom-kind path) for every abstraction added. Went through the five lenses (premise, requirement origin, YAGNI, 80/20, hindsight) plus a check for a while-you're-here Considered & deemed justified
One optional, non-blocking note (didn't clear the gate, flagging since it's cheap)
No action needed from this comment alone — informational second-look pass, not a review verdict. Generated by Claude Code |
| "@flow-state-dev/workforce": patch | ||
| --- | ||
|
|
||
| `openInventory` fills the live workforce inventory at boot: one row per hired seat, and one per open channel written by that channel itself from its own session state. `channelInstances({ inventory: true })` builds the built-in channel kind carrying the writer, and `inventoryWriterActions(kind)` puts the same two actions on a hand-rolled channel kind (FIX-1405). |
There was a problem hiding this comment.
Changeset includes internal rationale
The release note names FIX-1405, but it also explains internal writer placement, session ownership, and hand-rolled kind construction. The repository requires changesets to be concise, consumer-facing sentences and excludes implementation rationale. Reduce this to what consumers can now do and any wiring they must add before merging.
Rule Used: For changeset reviews in this repository, require at least a one-sentence user-facing description naming the Linear issue. Flag additional material when it is implementation rationale, decision lineage, file paths, exact test counts, out-of-scope sec... (source)
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 4cd4f13. Configure here.
…oid partial commit, document the seat-write exposure - packages/workforce/README.md: correct two wrong lines in the exports table (INVENTORY_SEAT_WRITER_SESSION's real value, InventoryBinding's real shape) found by a doc-vs-source sweep of the whole "live inventory" section; add a callout that registerSeatsInInventory is a public action whose input is unvalidated row data, with the app-level mitigation (authentication.resolvePrincipal keyed on envelope.action). - channel-flow.ts: write membership rows before the channel row they are named from, so a member id that can never become a valid membership key fails before anything is written instead of leaving a channel row with no matching index row (regression test added); replace the explicit `ctx: BlockContext` annotations on the two inventory-writer blocks with inferred ctx, matching every other block in the file, which drops the `as Record<string, any>` cast; rewrite the "public rather than internal" comment, which claimed a safety property that only held for one of the two actions, to say plainly what registerSeatsInInventory does and does not guard against. - open-inventory.ts: reuse the already-imported orderedById instead of an inline copy of the same comparator. - collections.ts: seat row id/kind reject the empty string. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PxDE76gD3BxXnPPjT7BT1T
|
Pushed FixedREADME/exports drift (Cursor Automation, Greptile). Full sweep of the rest of the section, as asked. I checked every factual claim (name, literal value, type shape, signature, default, return) the PR's new prose makes in Registration can partially commit (Greptile P1 + Cursor Bugbot, converging). Real, and Bugbot's addition was the constraint that mattered: a malformed member id fails Public action forges seats (Greptile P1, security) —
Declined, with reasons
Update: the exposure is now actually closed (
|
registerSeatsInInventory now lives only in the channel kind's
internal.actions map, not its public actions map. resolveEntry reads
exactly one map per dispatch type with no fallback, so a caller-addressed
HTTP or MCP request can never resolve into it — only the trusted, direct
runAction({ source: "internal" }) call openInventory makes for it.
registerChannelInInventory stays public; it takes no input and derives
its row from the channel's own already-open session state, so it is
harmless from any caller.
InventoryActionRequest gains an optional `source` field that openInventory
sets to "internal" on the seat write; an app's `run` door must forward it
into runAction's own `source` option for the write to land. Dropping it
fails closed (the write becomes unreachable, named in `problems`), not
insecure.
Adds a regression test proving the seat-write action cannot be reached
through the public door, verified RED (forged row written) against the
prior single-actions-map shape before the split, GREEN after. Updates the
README and the live-inventory docs page to describe the split and show
`run` forwarding `source`.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PxDE76gD3BxXnPPjT7BT1T
Folds the two settled child PRs and the findings they carried back up: - #1928 (FIX-1405 S5-S7) and #1929 (FIX-1430) are open, green and mergeable; the set table, the dependency read and the path figure all move. - ER-20 stays OPEN with its row at NOT RUN: the acceptance goal calls a real model and no environment here has an inference key. The wrap term is enforced against the rule as written, in all three places it is stated. - Drain width is 1 - work queues behind a busy seat. Closes FIX-1408's auto-scale wall on FIX-1430's evidence; citable at DECISIONS.md#drain-width. - BR-5 and BR-11 of FIX-1430 had their stated mechanism refuted by the code. Both rules stand; the corrected mechanisms are recorded at DECISIONS.md#refuted-mechanisms and sharpen ER-4's "checked at". - The sub-agent-on-a-board-row question is recorded unowned and named out at the wrap, beside ER-19's repo-wide pass and the unminted-board-id residue, so none can close as a pass nobody ran. - ER-14 is contested and UNRESOLVED: #1928 is a ship PR by the fence's letter while FIX-1435 is still Todo, and the overlap is empty by file. Written as a pending re-gate with the recommendation named as the epic's, not the owner's. ER-14's own row is untouched. Editorial pass alongside: derivation cut, the three phrases the EDITING NOTEs protect held deliberately. Prose words SPEC 2065->1579, DECISIONS 3516->3120, BUSINESS-RULES 1803->1710, PLAN 1908->1577. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PxDE76gD3BxXnPPjT7BT1T
Four of five children are now complete. The gate is not. - FIX-1405 terminal: #1920, #1923 and #1928 all merged (#1928 merged by the owner at 15:08:04Z, merge commit 8428614). - FIX-1430 terminal: #1929 merged (15:11:47Z, merge commit 45ef6d7) off head 78bc4f8. - FIX-1394 is the only child still open; its matrix #1921 never merges and its ratify waits on the documents question. ER-20 is unchanged and still reads NOT RUN. Merging the proof did not run the proof. The spec now says plainly that every child of the set can be complete while the thing the set exists to prove has never been observed, so nobody reads "everything merged" as "the epic is done". The wrap stays enforced against the rule as written, and the two things in front of it are both the owner's: the documents question, and a machine with an inference key. ER-14, recorded precisely and deliberately narrowly: - The owner merged #1928 through a live fence - FIX-1435 has no branch and no PR at all, verified here, not remembered. That act SETTLES #1928. It is not a breach and nothing about it needs remediation. - It is NOT an answer about the rule. He has said nothing. The re-gate keeps stating the narrowing recommendation as the epic's and unanswered, and the merge is not cited as approval anywhere. - What is recorded as decided is only the epic's own OPERATING DEFAULT (DECISIONS.md#fence-default): treat the fence as narrowed to per-PR file overlap, read from his action rather than his words, countermandable by him at any time. - ER-14's row text is byte-identical again. Only the note around it moved. - ER-14's remaining bite is named: FIX-1394's eventual ship PR, and the wrap. Path figure redrawn and looked at in both themes: FIX-1405 and FIX-1430 become merged bars, and FIX-1430's runs straight into the red ER-20 NOT RUN gate - which is the picture worth having right now. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PxDE76gD3BxXnPPjT7BT1T



A team can be declared and hired, and at run time nothing answers which seats and channels actually exist. The three collections that hold that answer are on
main, and nothing writes to them — an app that installs them is on its own to fill them, which is how two labs each grew the same private reader byte for byte. Until something writes the rows, a seat that wants to find another seat, or to know which channels it is in, has to re-walk a folder tree that a running block cannot reach.What this does
Two things now write the inventory, and which one writes what is decided by where the live answer lives.
A seat has no session. What it is — its id and the kind it was hired into — is the roster the process was hired from, so the binder writes those rows from what it already holds.
A channel has a session, and who is in it lives there and nowhere else. So the binder does not write a channel's row at all. It runs an action inside that channel's own session, and the channel writes its own row from its own state. The binder carries no member data, deliberately: a
CHANNEL.md'smembers:is what a file said when it was last read, an edit to it does not reach a channel that is already open, and a binder copying it forward would publish that file-time answer under a live name.Turning it on is two lines at boot —
channelInstances(channels, { inventory: true }), thenopenInventory(...)afteropenChannels. An app that doesn't declares nothing and writes nothing, and its channels behave exactly as they do today.What's asked of you
This implements the approved direction in spec PR #1916; nothing about the approach is reopened here.
One thing is worth a look because it touches the one item you weighed at sign-off — that this adds a call an app has to make. That call takes one more piece of wiring than the spec's snippet showed:
openInventoryneeds to be told which flow to write the seat rows through (seatWriter: { flowKind: "channel" }for most apps).Parts worth reviewing closely
openInventory's failure split (packages/workforce/src/inventory/open-inventory.ts). Two things throw — noorgId, and seats with noseatWriter— and everything else is collected intoproblemsand returned. Worth checking that the split is the right one and that nothing that should stop a boot is quietly in the list.rundoor's contract. It must reject when the action fails. A door that hands a failed run back as an ordinary value would make the binder report every channel registered while writing nothing, and there is no other signal this package can read. The doc comment says so; whether that is enough is a fair question.registerChannelInInventoryis public: closed, empty input, and the row is derived from the channel's own session state, so a caller cannot make it write anything but that channel's true members.registerSeatsInInventoryis ininternal.actionsonly, because a seat has no session and its whole input is the row data, with nothing in this package to check it against.resolveEntryreads exactly one map per dispatch type with no fallback, so a caller-addressed dispatch has no path to it at all; the only way in is the binder's ownrunAction({ source: "internal" }). Worth checking the split is drawn in the right place, and thatInventoryActionRequest.sourcefails closed for arundoor that drops it.openedAtis written create-only, so a second boot does not restamp a channel that has been open since the first. That is the one field where an upsert would otherwise lose information.Links
Linear FIX-1405 · spec on the issue's Linear document and on closed PR #1916 · epic #1905 · follows #1920 (PR-A) and #1923 (the collections) · this one merges.
How to review this — altitude, what's in scope, what's deliberately unsettled
How to review this. This implements an approved spec — the approach and the numbered
decisions in its
DECISIONS.mdare already signed off by a human, so please review thecode against that direction, not the direction itself. The spec lives on the issue's
Linear document (the durable copy) and on the closed spec PR (#1916), which keeps
its review history. Don't expect
spec/FIX-1405/to be in this diff — the spec PR closesunmerged at approval and the spec never lands on
main(BP-037).Most valuable here: correctness on the second path (the legacy shape, the null
boundary, the concurrent case, the cancel path), anything deriving an auth or routing
decision from caller-controllable input, and a behaviour the tests assert around
rather than on.
Already settled upstream: the approach and every decision in the spec's
DECISIONS.md(human-approved — if one is wrong, say so as a spec finding and it gets folded back; don't
re-argue it inline), and the conventions in
docs/contributing/best-practices.md.Deviations from the spec — where the landed code won
The spec was written against
mainatd8e4c99, before FIX-1385's channel boards and this issue's own collections merged. Two of its assumptions did not survive.1.
openInventorytakes aseatWriter. The spec's boot snippet isopenInventory({ seats, channels }, { run, userId, orgId }), andPLAN.md→ Write moments says the seat rows are written by the binder "directly", with "no flow run, no dispatch". That is not reachable. Checked before deviating:ResourceCollectionRef— the only API that writes a collection's state — is reached throughctx.resourcesinside a running block and nowhere else.createResourceClient(packages/client/src/resource-client/resources.ts) is session-scoped and itscreateCollectionItemtakes{ topic, content }. It writes an item's content body, not its state. There is no resource route that writes row state.@flow-state-dev/engineis a devDependency of this package, so the store registry is reachable from a test and not from shipped code — whichPLAN.mditself states aboutrunAction.So the seat rows must go through a flow, and a flow has to be named. The binder therefore dispatches once for all seats (not once per seat — that part of the plan's cost claim holds) and once per channel. The channel half is exactly as specified: the channel's own kind, the channel's own session, no member data in the payload.
2. The
defineChannelFlowmerge is oneactionsmap, not one widenedresourcesmap.PLAN.md→ At implement time says S5 "adds to all three" of FIX-1385'sresources,actionsandinternal.actions. The inventory collections are declared on the blocks that write them instead, which is how the shipped collections' own tests already install them and which is sufficient for the rows to resolve — a block'sresourcesbubbles up throughmergeDeclaredResources.boardResourcesstays ondefineFlowbecause the board blocks resolve their ledger by a dynamic id and cannot declare it. Declaring the same collections in both places would be redundant, so the merge is:boardResourcesuntouched on the flow, the two inventory entries appended toactions, andinternal.actionsuntouched — nothing dispatches the registration internally.3. The inventory flag reaches the built-in kind only.
channelInstances({ inventory: true })rebuilds the built-in carrying the writer. A kind passed underkindsis zero-arg by contract, so there is nowhere to hand it the flag — the same reasonboardscannot reach one. A hand-rolled kind carries the writer by spreadinginventoryWriterActions("<its kind>"), which is what makes "every open channel has a row" true for a custom kind rather than aspirational. A kind that carries neither is a named entry inproblems, never a silent gap.Engineering calls — decided along the way, no product sign-off needed
inventoryWriterActions(kind)call). Any flow carrying it can host the seat write; putting it on the kind the app already has is what keepsseatWriterto one field. Wrong call costs a second export an app has to install somewhere.kindis closed over at build time, not taken from the action's input. A block cannot read its own flow's kind —ctx.flowis narrowed to the create-time config bag — so the alternative was the binder passing it as input, which puts a row field on caller-controllable input for no gain. Wrong call means a hand-rolled kind that passes the wrong string writes a row that mislabels itself, in the same way a wrongcardinalitydoes.kindOfandorderedByIdare exported fromchannel-binder.tsfor the inventory binder, not re-exported from the package root. A second derivation of "which flow is this channel on" would silently diverge from the oneopenChannelsuses.problemsrather than throwing them, matching the declared-roster reader beside it: the caller decides what is fatal. An app that ignores the return value loses rows silently, which is the cost.Verification — what was checked, and what would have made it fail
The new cases live in
packages/workforce/test/inventory-binder.test.tsand all run on the real path: a registered kind, a session opened byopenChannels, and a real action run. The reader in every case is a flow that is not a channel and that declares its own instances of the three collections, so nothing is green merely because the writer read back its own objects.Every assertion was then shown to discriminate. Each red state below was applied to the source, the case it targets was run, and it failed — then the red state was reverted.
membersand the channel writes themBR-10— the row holds the session's memberskind === "channel"branchBR-22— a custom kind's channels get rowsopenedAtwritten on every upsert instead of create-onlyBR-9— a second boot is a no-opBR-13— the off state declares and writes nothingorgIdguard removedBR-11— refuses rather than writing where nothing readsBR-23— rows outlive a roster that drops themBeyond the red states, three cases carry a live control in the same process: the off-state case runs the identical roster one flag apart; the custom-kind case registers a third hand-rolled kind that deliberately omits the registration, so "the row is there" is an assertion about the writer and not about the roster; and the membership-index case seeds
eng.leadershipalongsideeng.leadso a prefix read without the segment boundary would drag the wrong channel in.Run:
pnpm --filter @flow-state-dev/workforce test— green, and the pre-existing channel suites are untouched, which is the off-state claim at suite scale.pnpm --filter @flow-state-dev/workforce typecheck,pnpm --filter @flow-state-dev/fsdev typecheck,pnpm --filter @flow-state-dev/goals typecheck— clean.pnpm --filter @flow-state-dev/docs build— clean, no broken-link warnings, run as the last action on the docs.pnpm --filter kitchen-sink typecheckreports 13 errors, all inpackages/tools/src/bash/adapters/moat.ts, a package this branch does not touch at all — nothing in this diff is underpackages/tools. Pre-existing, not introduced by this PR.Files
packages/workforce/src/inventory/open-inventory.tsopenInventory, its roster/options/result types, and the seat-writer session constant.packages/workforce/src/channel/channel-flow.tsinventoryWriterActions(kind)— the two registration blocks and the collections they write — plus theinventory?option ondefineChannelFlow, which spreads them intoactions.packages/workforce/src/channel/channel-binder.tsinventory?onchannelInstances, which seeds the built-in kind rebuilt holding the writer;kindOfandorderedByIdexported for the inventory binder.packages/workforce/src/channel/index.ts,src/inventory/index.tspackages/workforce/test/inventory-binder.test.tspackages/workforce/README.mdproblems, and the limits. The channels section's re-bind limitation is unchanged and still scoped to the three settings written at create.apps/docs/docs/workforce/inventory.mdapps/docs/sidebars.ts,documents-on-disk.md,capabilities-on-disk.mdsidebar_positionbumps the insertion needs..changeset/inventory-binder.mdpatchfor@flow-state-dev/workforce, as the plan pins.The user-facing prose was written and revised by
docs-writerfrom the public surface and the tests, and reviewed bydocs-editor(SHIP; four prose nits, applied by the writer). Neither saw the spec or this diff.🤖 Generated with Claude Code
https://claude.ai/code/session_01PxDE76gD3BxXnPPjT7BT1T
The PR is not safe to merge until the public seat writer is protected, channel registration cannot leave contradictory inventory after partial failure, and the explicit documentation-rule violations are corrected.
Findings
<img alt="P1" src="https://greptile-static-assets.s3.amazonaws.com/badges/p1.svg?v=9" align="top"><img alt="Security" src="https://greptile-static-assets.s3.amazonaws.com/badges/Security.svg?v=2" align="top">Public action forges seats ▶<img alt="P1" src="https://greptile-static-assets.s3.amazonaws.com/badges/p1.svg?v=9" align="top">Registration can partially commit ▶<img alt="P2" src="https://greptile-static-assets.s3.amazonaws.com/badges/p2.svg?v=9" align="top">API table contradicts exports ▶<img alt="P2" src="https://greptile-static-assets.s3.amazonaws.com/badges/p2.svg?v=9" align="top">Changeset includes internal rationale ▶Summary
This PR adds opt-in boot-time population of workforce seat, channel, and membership inventory, including public writer actions, binder orchestration, tests, and user documentation.
Diagram
%%{init: {'theme': 'neutral'}}%% flowchart LR Caller["Public action caller"] -->|"registerSeatsInInventory\ncaller-supplied seats"| SeatWriter["Public seat writer"] Binder["openInventory"] -->|"trusted roster seats"| SeatWriter SeatWriter --> SeatInventory["Org seat inventory"] ChannelSession["Open channel session"] --> ChannelWriter["Channel registration action"] ChannelWriter -->|"1. commit channel row"| ChannelInventory["Org channel inventory"] ChannelWriter -->|"2. sequential membership writes"| MembershipInventory["Org membership index"] MembershipInventory -. "failure does not roll back step 1" .-> Inconsistent["Partially populated inventory"]Reviews (1) · Last reviewed commit: "FIX-1405: document the live inventory's ..."
Generated by Claude Code