Skip to content

Discussion: role-first — hide Org chart, grow channel roles #231

Closed as not planned

Description

@cursor

Why

Founder lock 2026-08-19: role-first.

Org chart (#198) and channel roles (#116) both answer “who does this work?” and overlap. Oscar has not used the Org chart. Channel roles match how work actually happens (per room). Call-by-name CoS (sibling) needs channel roles for what a named person may do — not a company poster.

This is a discussion / decision issue, not a delete-and-ship work order. No production deletion until a decision entry supersedes D-060’s product surface (or explicitly keeps the protocol and hides UI only).

Locked

  • Role-first (A): Channel role = “what work is allowed in this room” + tool walls (D-043 / D-044).
  • Call by name, not by role (sibling call/wake issue).
  • CoS may prototype small; feature work must go to a named specialist (e.g. Dev).
  • Factory-as-code stays discussion.
  • Do not implement founder Inbox Wake as the recovery product.

Two layers today (overlap)

Question Channel role (#116) Org roster (#198)
In this room, who may code / write? Yes No
Who may CoS call? Names of holders (product) Manager-chain for crew-handoff auto-create
Budget brake No Yes
Chart UI No Yes (unused)

Proposed direction (not yet a DECISIONS.md entry)

  1. Invest in channel roles (intake CoS, code Dev, hard capabilities).
  2. Hide or demote Org chart UI (Settings / advanced). Hiding ≠ deleting 30680.
  3. Keep KIND_ORG_ROSTER + budget + crew-handoff dormant until we know whether the money brake is still needed.
  4. Do not make manager-chain the thing Oscar must draw before the company works. Calling @Dev by name is enough for day-one.

Officer loop in docs/crew/HERMES.md (ORG-CHECK, crew-office) is tied to the tree — must be rewritten to “CoS of this channel” or dropped if the chart goes away. Surface that conflict; do not silently pick.

Questions to answer before implementation

  1. Hide Org UI only, or also stop requiring 30680 for any happy path?
  2. Does crew-handoff stay (named call + optional handoff tag) or does plain mention replace kickoff?
  3. Where do budgets live if the tree is dormant?

Explicit non-goals

  • Paperclip-style ticket org
  • Rewriting mobile to React Native
  • Board-as-home (D-037)

Related

Activity

  1. oscarlehuu commented on Aug 19, 2026

    @oscarlehuu

    Superseded by #233 (remove unused Org product).

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions