Skip to content

docs(atlas): Workforce is the product; Conductor is a team config - #1635

Merged
jhoffner merged 1 commit into
mainfrom
cursor/atlas-workforce-product-lock-c35a
Sep 8, 2026
Merged

jhoffner merged 1 commit into
mainfrom
cursor/atlas-workforce-product-lock-c35a

Conversation

@jhoffner

@jhoffner jhoffner commented Sep 7, 2026

Copy link
Copy Markdown
Collaborator

The atlas still taught Jake’s old lock: Workforce and Conductor as sibling tracks, Conductor-as-L3-on-Workforce as a later triangulation. That sentence is now wrong. A reader could keep shipping Conductor-only surface, or wait to “put Conductor on Workforce later,” as if Workforce were not the product.

This rewrite teaches the room lock: Workforce is the Layer 2 product. Conductor is one Workforce team whose seats include coding-harness workers. The roster names the harness. omp can fill that seat and is marked proposed. One harness-manager stack. Layer 1 stays substrate. #1612 console half is a parked Conductor-only cut.

flowchart TD
  W["Workforce — L2 product<br/>roster / teams + seats + rooms + helpers"]
  C["Conductor — one team config<br/>coding-harness seats"]
  O["other teams<br/>client / personal / org"]
  L1["Layer 1 substrate<br/>no Team / Channel / MessageBoard"]
  W --> C
  W --> O
  W --> L1
Loading

What's asked of you

Nothing here is yours to decide. This follows the room lock (Jake / Cycle PM / Architect / Systems Thinker).

Parts worth reviewing closely

The rest of this is for whoever reviews the pages.

1. Honesty, not invention. Does the page still tag factory / seat bind / omp / OnSecurity as proposed? Does it still keep FIX-1320 and #1600 as floor? Astra gaps in §18 must still be named, not papered over.
2. Sibling framing is dead. Standfirst, §01 diagram, §15, and gate 5 should not read as two products or a later peel-off. Conductor and Framework only got honesty pointers — the Conductor encyclopedia was not rewritten.
3. #1612 console half. Mentioned as a parked Conductor-only cut (PI-1..3). The rest of that epic is not cancelled here.

Linear: room lock (Jake / Cycle PM / Architect / Systems Thinker). Related FIX-1320, #1600, #1612. Atlas-only. No changeset needed. roadmap.html still uses the older three-jobs / sibling framing; Strategy owns that rewrite.

How to review this — altitude, what's in scope, what's deliberately unsettled

This is an atlas editorial following a room lock. No spec, no package change. In scope: whether the pages now teach Workforce as the product and Conductor as a config, whether exists vs proposed vs cut matches main, and whether anything claimed as existing was invented. Out of scope: implementing the factory, landing #1600, integrating omp, rewriting the Conductor encyclopedia, rewriting roadmap.html.

Engineering calls — decided along the way, no product sign-off needed
  • Pin moved to 088181af7 (2026-09-07), current origin/main.
  • omp is not in the tree; tagged proposed. Claude Code and Codex already fill harness-manager.
  • #1612 PI-1..3 (operator console) named as park/cut because it does not ride Workforce. The harness half of that epic is not declared dead.
  • OnSecurity named as GTM example only. No impl claim.
  • roadmap.html left alone on purpose. README now says it is the older framing and does not outrank this lock.
  • Conductor thread 11: product fork closed in one paragraph; the mechanical materializeAgent question is left as implementer.
Everything else

What landed

  • workforce.html: new standfirst and product/config diagrams; §15 rewritten; §16 / §19 / §20 honesty; Astra / seat / worker / agent / 1→4 build-out kept.
  • conductor.html / framework.html: honesty pointers only.
  • index.html / README.md: listing copy.

Verification: HTML parses (empty stack, no mismatch) on workforce, conductor, framework, index. Twenty workforce sections. Cross-flow not tagged exists. omp / OnSecurity not claimed shipped.

Atlas URL after merge: https://fixpoint-labs.github.io/flow-state-dev/workforce.html (GitHub Pages root is docs/atlas). Until then, the PR copy of docs/atlas/workforce.html.

Open in Web Open in Cursor 

Supersede the sibling-track / later-triangulation lock. Teach Workforce
as the L2 product surface and Conductor as one team whose seats include
coding-harness workers. Mark omp, seat wiring, and OnSecurity as
proposed; park the #1612 console half; keep FIX-1320 and #1600 as floor.

Co-authored-by: Jake Hoffner <jhoffner@users.noreply.github.com>
@vercel

vercel Bot commented Sep 7, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

3 Skipped Deployments
Project Deployment Actions Updated
flow-state-dev-docs Ignored Ignored Sep 7, 2026 9:13pm UTC
flow-state-dev-kitchen-sink Ignored Ignored Sep 7, 2026 9:13pm UTC
flow-state-dev-ui Ignored Ignored Sep 7, 2026 9:13pm UTC

Request Review

@jhoffner
jhoffner marked this pull request as ready for review September 8, 2026 01:10
@jhoffner
jhoffner merged commit b0ba45b into main Sep 8, 2026
12 checks passed
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 8, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-08T01:11:30.458818Z bba8788 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Simplify review — direction sound, repetition is the cost

The product lock is right: Workforce is the shippable Layer 2 product; Conductor is one team config on it. Cross-links to workforce.html#conductor and the conductor/framework deferrals are the correct architecture for this atlas set.

The concern is not the lock — it is how much surface area the PR rewrites to say the same sentence. Net diff is ~179 insertions / ~178 deletions: complexity moved from “two sibling products” to many parallel copies of one claim across mastheads, ledes, SVG labels, tables, gates, cuts, and the one-sentence recap. Performance impact is negligible (~3 KB on workforce.html); the cost is reader and maintainer load.

Cleaner approach (if revisiting)

A surgical pass could have shipped the same lock with less churn:

  1. Canonize in workforce.html §15 only — masthead + §15 + (maybe) one diagram.
  2. Pointer sentences elsewhere — conductor/framework/index/README get one line + link, not restated pitch.
  3. Bundle scope separately — omp, OnSecurity GTM naming, and #1612 console park are orthogonal; they belong in §15 + §20 cuts, not sprinkled through §01 SVGs, §16 inventory, §19 gates, and conductor thread bodies.
  4. One archaeology note — “supersedes separate-tracks / later-triangulation” once in §15; drop repeated negation in figcaptions and sib lines.
  5. Match README on index.html — README warns roadmap is stale; index still sells “three jobs” with no disclaimer.

What I would not block on

  • Leaving roadmap.html for Strategy (README disclaimer is enough if index matches).
  • Replacing the Eve/Grok analog — tradeoff, not clearly wrong.
  • Atlas self-contained HTML duplication (pre-existing pattern; extracting shared CSS is a separate refactor).

Skipped / your call

  • Whether heavy “superseded” negation is deliberate archaeology for readers of the prior pin.
  • Whether omp / OnSecurity prominence reflects active GTM you want repeated everywhere.

Verdict: COMMENT — mergeable direction; a dedupe pass could cut ~30–40% of the new prose without weakening honesty tags. Inline notes on the highest-leverage spots.

Open in Web View Automation 

Sent by Cursor Automation: Review For Best Approach

Comment thread docs/atlas/workforce.html
<h1>One worker contract. Then compose.</h1>
<p class="standfirst">Workforce is the general Layer&nbsp;2 convention: <strong>one worker shape, one flow per worker</strong>. A <strong>seat</strong> is a roster slot that binds a <strong>worker</strong> &#8212; not an Agent. A worker is any flow on that contract; thin sequencers count. <strong>Agent</strong> (product) is the opinionated worker: sequencer + generators + persona + durable member memory. A seat can be any worker. Thin seats do not need <code>AgentRegistry</code> or member memory. The target is the <strong>RC collaboration story &#8212; teams, plural</strong>. The build-out is <a href="#vision">&#167;03</a>. The three words are <a href="#fence">&#167;04</a>. This page teaches the target. It does not ship it. Conductor does not wait on it.</p>
<h1>Workforce is the product. Conductor is a team on it.</h1>
<p class="standfirst">Workforce is the <strong>Layer&nbsp;2 product</strong>: roster / teams + seats + rooms + thin helpers. It can ship for a client (OnSecurity is a GTM name, not an impl) and for personal or org workforces. A <strong>seat</strong> binds a <strong>worker</strong>, not an Agent. A worker is any flow on the contract; thin sequencers count. <strong>Agent</strong> (product) is the opinionated worker: sequencer + generators + persona + durable member memory. <strong>Conductor</strong> is one consumer: a Workforce team whose seats include coding-harness workers. The roster <em>names</em> the harness; <strong>omp</strong> (opinionated Pi harness) can fill that seat &#8212; proposed, not integrated. One harness-manager stack. Layer&nbsp;1 stays substrate. The three words are <a href="#fence">&#167;04</a>. The build-out is <a href="#vision">&#167;03</a>. Astra gaps stay in <a href="#gaps">&#167;18</a>.</p>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Scope bundling. The standfirst now carries the full product lock plus OnSecurity GTM, omp, harness-manager, and Conductor-as-consumer in one paragraph. Consider keeping the masthead to Workforce vocabulary (seat/worker/agent/teams) and deferring Conductor/omp/GTM to §15 — otherwise every reader hits three orthogonal decisions before §01.

Comment thread docs/atlas/workforce.html
<span><i class="sw" style="background: var(--prose-soft); border: 1.2px solid var(--prose)"></i> later / cut &#8212; not foundation</span>
</div>
<p class="sib">Pinned to <code>origin/main</code> at <code>d8899c9b5</code> (2026-09-07, #1614). Sibling: <a href="conductor.html">Conductor</a> &#8212; this-cycle coding product on the same dispatch spine. Cross-flow PR <a href="https://github.com/fixpoint-labs/flow-state-dev/pull/1600">#1600</a> is open; the refuse is still on this pin.</p>
<p class="sib">Pinned to <code>origin/main</code> at <code>088181af7</code> (2026-09-07). Conductor is a Workforce config, not a sibling product and not a parallel Proof. The old lock &#8212; separate tracks, later triangulation &#8212; is <strong>superseded</strong>. Cross-flow PR <a href="https://github.com/fixpoint-labs/flow-state-dev/pull/1600">#1600</a> is open; instances (<a href="https://linear.app/fixpoint-labs/issue/FIX-1320">FIX-1320</a>) still first-wins. GTM timing stays Strategy.</p>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Superseded archaeology. “The old lock … is superseded” plus sibling-ship negation repeats in figcaptions, §15, gates, and cuts. One short “what changed” note in §15 should be enough; readers who never saw the old lock pay rent on every section.

Comment thread docs/atlas/workforce.html
<div class="sec-head"><span class="sec-num">15</span><h2>Conductor</h2></div>
<p class="lede">This cycle, Conductor is a <strong>thin shell on Layer&nbsp;1 dispatch</strong>. It does not wait on a Workforce package, including a foundation kick. It <em>does</em> care about slice&nbsp;1 of the build-out (cross-flow, resume, bare-kind, member memory). Conductor-as-a-coding-extension-on-Workforce is slice 4, not a dependency arrow. If a team seat names a harness, it rides Conductor&#8217;s harness-manager track &#8212; one stack; team/roster only names the harness as L2 config &#8212; once that path exists. The two products stay triangulated. GTM timing is Strategy.</p>
<div class="sec-head"><span class="sec-num">15</span><h2>Conductor as a Workforce config</h2></div>
<p class="lede">The lock: <strong>Workforce is the product. Conductor is one Workforce team</strong> whose seats include coding-harness workers. The roster names the harness. <code>omp</code> can fill that seat for now &#8212; proposed, not integrated. One harness-manager stack. Do not grow a Conductor-only path beside Workforce. The old lock &#8212; separate tracks, later triangulation, Conductor-as-L3-on-Workforce as a horizon &#8212; is <strong>superseded</strong>. GTM timing is Strategy.</p>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Canonical home — good. This §15 lede is the right place to own the lock, exists-vs-proposed split, and omp/harness-manager honesty. I'd treat this as the only place that states the full pitch; other sections could link here instead of restating (masthead h1 + link is enough upstream).

Comment thread docs/atlas/workforce.html
<div class="note" style="margin-top:26px">
<span class="lbl">The one-sentence version</span>
<p>Workforce is one worker contract on Layer&nbsp;1 &#8212; a sequencer flow; generator calls do not mint a second type. A seat is a roster slot that binds a worker, not an Agent. Thin seats skip <code>AgentRegistry</code> and member memory. Product Agent is L2 opinion (sequencer + generators + persona + member memory). The core <code>Agent</code> / <code>AgentRegistry</code> types are the thin seam; do not grow them; do not delete them; engine never sees the registry as product. The target is RC collaboration: teams, plural. Build-out is 1&#8594;4. Readiness is named gaps on that inventory &#8212; instances, then conversation + board proofs, then durable delegation, then the materializer. A roster is a seat-list. A team is that roster plus shared rooms plus dispatch &#8212; Layer&nbsp;2, not an L1 <code>Team</code> type, not a TeamFlow. Product folders are <code>teams/&lt;teamId&gt;/workers/&lt;name&gt;/</code>. Projects live as resources, boards, sessions, and content &#8212; no <code>projects/</code> tree, no <code>Project</code> type. A new seat is a file on that path. Scan feeds today&#8217;s <code>defineFlow</code> for every seat; <code>AgentRegistry</code> only when that seat is an opinionated agent. A tree scan is a named gap. Hot-dynamic kinds after boot are a named gap. Address-the-team is an intake seat, a worker with a static DM. Identity lives on agent/member scope, not on the seat. Knowledge is four uses of existing <code>user</code> / <code>org</code> resources. Member identity is the named gap &#8212; prove <code>flowIsolation</code> first. Helpers take a team key from day one. Ordered multi-reply is proposed Layer&nbsp;2. RC gates are proposed until they are true. No second Agent. No second registry. No one-team-only API. Cross-flow is still refused on this pin. Conductor does not wait. GTM is Strategy.</p>
<p>Workforce is the Layer&nbsp;2 product: one worker contract on Layer&nbsp;1 &#8212; a sequencer flow; generator calls do not mint a second type. A seat is a roster slot that binds a worker, not an Agent. Thin seats skip <code>AgentRegistry</code> and member memory. Product Agent is L2 opinion (sequencer + generators + persona + member memory). The core <code>Agent</code> / <code>AgentRegistry</code> types are the thin seam; do not grow them; do not delete them; do not fold Workforce into core; engine never sees the registry as product. Conductor is one Workforce team whose seats include coding-harness workers. The roster names the harness. <code>omp</code> can fill that seat and is proposed, not integrated. One harness-manager stack. Park Conductor-only surfaces that skip Workforce (#1612 console half). The target is RC collaboration: teams, plural. Build-out is 1&#8594;4. Readiness is named gaps on that inventory &#8212; instances, then conversation + board proofs, then durable delegation, then the materializer. A roster is a seat-list. A team is that roster plus shared rooms plus dispatch &#8212; Layer&nbsp;2, not an L1 <code>Team</code> type, not a TeamFlow. Product folders are <code>teams/&lt;teamId&gt;/workers/&lt;name&gt;/</code>. Projects live as resources, boards, sessions, and content &#8212; no <code>projects/</code> tree, no <code>Project</code> type. A new seat is a file on that path. Scan feeds today&#8217;s <code>defineFlow</code> for every seat; <code>AgentRegistry</code> only when that seat is an opinionated agent. A tree scan is a named gap. Hot-dynamic kinds after boot are a named gap. Address-the-team is an intake seat, a worker with a static DM. Identity lives on agent/member scope, not on the seat. Knowledge is four uses of existing <code>user</code> / <code>org</code> resources. Member identity is the named gap &#8212; prove <code>flowIsolation</code> first. Helpers take a team key from day one. Ordered multi-reply is proposed Layer&nbsp;2. RC gates are proposed until they are true. No second Agent. No second registry. No one-team-only API. Cross-flow is still refused on this pin. Multi-hire waits on FIX-1320. GTM is Strategy.</p>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One-sentence version bloat. This paragraph grew again (Conductor, omp, #1612, multi-hire) and now largely mirrors §15 + §20. Prior atlas reviews flagged the same pattern on #1606. Either trim to a real one-liner or rename to “full recap” and drop clauses already in §15/§20.

Comment thread docs/atlas/conductor.html
</div>
<p class="sib">Two names collide on this page, and every use keeps them apart. The board's <code>dispatcher: "topological"</code> is an ordering <em>strategy</em> (exists); the <code>dispatcher()</code> of section 6 is a block <em>factory</em>, and it exists. This page's <code>inbox/**</code> is the <em>question collection</em>; the dispatch-protocol design's &#8220;one inbox per flow&#8221; is the <em>typed entry set</em>.</p>
<p class="sib">Sibling: <a href="workforce.html">Workforce atlas</a> &#8212; the Layer&nbsp;2 convention. This cycle writes that page. Conductor does not wait on a Workforce product.</p>
<p class="sib">Workforce is the Layer&nbsp;2 product. Conductor is <strong>one Workforce team config</strong> whose seats include coding-harness workers &#8212; not a sibling ship, not a parallel Proof. The lock lives on the <a href="workforce.html#conductor">Workforce atlas &#167;15</a>. This page stays the Conductor encyclopedia; do not grow Conductor-only surfaces that skip Workforce (park the #1612 console half).</p>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good deferral shape. Short pointer to Workforce §15 + encyclopedia boundary is exactly what conductor.html should do. If you dedupe workforce.html, keep this as the template for framework/index too.

Comment thread docs/atlas/conductor.html

<div class="tension">
<h5>11 &middot; Which layer of workforce do Conductor&#8217;s roles sit on?</h5>
<p><strong>Product fork closed.</strong> Workforce is the product; Conductor is a team config on it. The remaining question is mechanical &#8212; where <code>materializeAgent</code> lives &#8212; not whether Conductor stays a sibling ship. See <a href="workforce.html#conductor">Workforce atlas &#167;15</a>.</p>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thread 11 framing drift. “Product fork closed” is right, but the heading still asks “Which layer of workforce…” and the next paragraphs reopen a “fork” between wrapper vs primitives. Consider retitling to the mechanical question (materializeAgent placement) and trimming wrapper/primitives prose that reads like an unresolved product fork.

Comment thread docs/atlas/framework.html
<div class="sec-head"><span class="sec-num">04</span><h2>Workforce: the layer that isn't built</h2></div>
<p class="lede">Workforce is meant to be the top of the stack — teams of named agents that work together, powered by every system beneath them. Today it is 397 lines that define <em>what one agent is</em>, and nothing that defines <em>how a set of them relate</em>.</p>
<div class="sec-head"><span class="sec-num">04</span><h2>Workforce: the Layer 2 product, not a Layer 1 type</h2></div>
<p class="lede">Workforce is the shippable Layer&nbsp;2 product — roster / teams + seats + rooms + thin helpers. Conductor is one team config on it, not a sibling ship. Today the package is still 397 lines that define <em>what one agent is</em>, and nothing that defines <em>how a set of them relate</em>. The product lock and the honesty tags live on the <a href="workforce.html">Workforce atlas</a>. Do not mint Team / Channel / MessageBoard here, and do not fold Workforce into core.</p>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Duplicate pitch. §04 lede now restates the Workforce product lock (Conductor-as-config, no sibling ship) that lives on the Workforce atlas. Framework inventory should stay L1/L2 boundary + link to workforce.html#conductor, not a second copy of Strategy positioning.

Comment thread docs/atlas/README.md
board plus one session per subscriber, talk on the dispatch spine.
Conductor is a team config on this surface. The page teaches the lock and
the honesty tags; the factory is still proposed.
- `roadmap.html` — the public product horizon. Still written in the older

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Roadmap stale note — good. Explicit that roadmap.html still uses sibling framing is the right honesty tag. index.html roadmap blurb wasn't updated to match; easy consistency fix if you want one front door.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants