Skip to content

docs(rfc): draft a team board with human task owners, built as an app first - #30622

Open
JiaDe-Wu wants to merge 2 commits into
kirodotdev:mainfrom
JiaDe-Wu:rfc-team-board-task-owner
Open

JiaDe-Wu wants to merge 2 commits into
kirodotdev:mainfrom
JiaDe-Wu:rfc-team-board-task-owner

Conversation

@JiaDe-Wu

@JiaDe-Wu JiaDe-Wu commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: Record a design for a team board where every task has a human owner, so maintainers can react to the approach before any code is written.

#30572 asks for a shared team view: each person directs their own Bots and owns their tasks, and one shared Team Bot keeps the picture between them. Reading the code showed the starting point is lower than the issue first claimed (corrected in the issue): no board carries a task owner, roles are design only, a change card is confirmed by the dashboard owner alone, and a Bot cannot ask another person's Bot a question without a human relaying it. A design needs to say what to build first and in what order.

Why it matters

Without an agreed shape, the likely first attempts are the ones already declined: loosening session_send for everyone, or a member inbox subsystem. This draft proposes a path that avoids both.

Not a goal

  • Acceptance of every phase. The RFC asks for direction; only Phase 0 needs no core change.
  • Any code. Phase 1 to 3 are not started until a maintainer has reacted to the approach.
  • Relaxing the session_send withholding, or reviving the inbox subsystem.

What changed (motivation → approach → change)

Adds docs/request-for-change/rfc-team-board-human-task-owners.md (status draft) and its index row. The approach: ship a Team Board app first using what the platform already offers (app storage, an app MCP server for Bots, bundle import through the existing crewmate.import card), route Bot-to-Bot requests through the app's own request and answer records, then list the core gaps in dependency order, each PR-sized with exit criteria. Every code reference was read at 9c3c6b58e9 and cites a symbol, not a line, as the docs lint requires.

Backwards compatibility

Compatible. Documentation only.

Removes nothing: no code, config or behaviour changes.

Tests

N/A, documentation only. ./scripts/docs-lint.sh passes (exit 0) and the brand-name gate is clean.

Proof: not provable -- docs or config only

Manual verification

N/A — documentation only. The claims about current behaviour were re-checked against the code: people_policy has no hit in src/ or website/src/, PREVIEW_ENABLED = False in crewmate_sdk.py, change cards refuse a non-owner with owner_only, and #10690 (named by the 2026-09-13 decision) is closed unmerged.

Related Issues

Refs #30572

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title
  • Existing tests pass and new tests added for new functionality — N/A, documentation only
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

@JiaDe-Wu
JiaDe-Wu requested review from a team and KiroCrewCaptain as code owners November 5, 2026 17:49
@github-actions github-actions Bot added fork Pull request from a fork (external contributor) readiness: action required A blocking check or review needs attention merge conflict Branch has merge conflicts with its base — author must resolve before merge labels Nov 5, 2026
@JiaDe-Wu
JiaDe-Wu force-pushed the rfc-team-board-task-owner branch 2 times, most recently from d153c4e to 1052f6b Compare November 5, 2026 18:30
@github-actions github-actions Bot removed the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Nov 5, 2026
@JiaDe-Wu
JiaDe-Wu force-pushed the rfc-team-board-task-owner branch 2 times, most recently from 52c2f6b to 042c086 Compare November 5, 2026 23:33
@github-actions github-actions Bot added the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Nov 6, 2026
@JiaDe-Wu
JiaDe-Wu force-pushed the rfc-team-board-task-owner branch from 042c086 to 105868a Compare November 6, 2026 16:26
@github-actions github-actions Bot added merge conflict Branch has merge conflicts with its base — author must resolve before merge and removed merge conflict Branch has merge conflicts with its base — author must resolve before merge labels Nov 6, 2026
… first

A team that runs Bots on a shared Crew has no shared view: no board
carries a task owner, roles are design only (people_policy has no hit
in src), a change card is confirmed by the dashboard owner alone, and
one person's Bot cannot ask another's a question except through a
human.

This draft proposes a Team Board app first, using only what the
platform offers: tasks with a principal-id owner, an MCP server for
Bots, request and answer records instead of session_send, a per-Bot
switch that is off by default, and the Team Bot and role Bots shipped
as bundles. It then lists the core gaps in dependency order (enable
ctx.crewmate, give an app handler the acting person, let a change card
name an approver), a governance control for how open a team is, and
the cross-Crew phase that waits on remote dispatch.

Every code reference was read at 9c3c6b5. The document changes no
code and does not ask for acceptance of every phase.

Refs kirodotdev#30572
@JiaDe-Wu
JiaDe-Wu force-pushed the rfc-team-board-task-owner branch from 105868a to e139ec5 Compare November 7, 2026 10:49
@github-actions github-actions Bot added merge conflict Branch has merge conflicts with its base — author must resolve before merge and removed merge conflict Branch has merge conflicts with its base — author must resolve before merge labels Nov 7, 2026
A skeleton of the team board app was installed into an isolated gateway
built from main and the claims the RFC made about it were checked.

Corrects the Meetings bullet and its Phase 1 row: an app backend cannot
call another app's backend through the proxy, so the permissions.api
prefix does not reach it. Adds what held on the real gateway (proxy
path, the signed claim on a write, the local-app owner id, the trust
gate, the shared user-level agent spec) and what was not measured, and
extends open question 5 with the session label hook.
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Nov 14, 2026
@KiroCrewCaptain

Copy link
Copy Markdown
Collaborator

Code change approver recommendation: Approve

Why: the decider estimates a 10% chance that this change introduces a defect, within the 12% limit for approving on its own, and every check passes.

Docs-only PR: a draft RFC that asks for direction, plus one index row. I checked its claims about current behaviour against the code and they hold: people_policy is absent from src/, the proxy refuses an app backend calling another app's backend with 403, the gateway strips a caller-sent X-KiroCrew-Principal header, and the signed claim has the principal kinds the RFC lists. The design moves no trust boundary. session_send stays withheld, requests are stored as data, the per-Bot switch is off by default, and the governance control does nothing until a policy names it. The remaining gaps (no acting-person identity or Bot identity for an app in Phase 0) are stated as Phase 1b and Open question 5.

An automated recommendation, not a review: a maintainer still decides. It approves on its own only when the estimated chance of a defect is at most 12% and the change has at most 400 changed lines. Decider v3c (217fe607) · commit c9615ca055 · 304 changed lines. If this recommendation is wrong, reply here: replies are how the approver is evaluated.

This branch has not been deployed

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

Labels

fork Pull request from a fork (external contributor) merge conflict Branch has merge conflicts with its base — author must resolve before merge readiness: checking Automated validation is still running

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants