Skip to content

Mark PRODUCT Connected settle as target vs shipped #405

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
TheGreatAxios merged 1 commit into from
Aug 24, 2026
Merged

Mark PRODUCT Connected settle as target vs shipped #405

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
17 changes: 14 additions & 3 deletions PRODUCT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,9 +83,15 @@ Code review is the product scene for the template path: Connect GitHub
with a personal access token (the shipped path today) → the connect card
flips in place to pick repositories → reviewers introduce themselves as
left-aligned messages with avatars. A GitHub App / hosted OAuth welcome
mat is future work (CL-6343), not current product. Never: a stale Connect
after success; the product posting as the signed-in user; an agent 401
after GitHub already succeeded.
mat is future work (CL-6343), not current product.

Connected/settle honesty — no stale Connect after success; settle never
posting as the signed-in user; no agent 401 after GitHub already
succeeded — is the **target**, not shipped end-to-end. What ships today
is narrower: live credential reads that resolve at call, and a GitHub
settle path that can still attribute as the connecting user. Point
implementers at IMPLEMENTATION.md open questions, CL-6737, and CL-6738;
do not treat those three guarantees as current product law.

## Plugins and Skills

Expand Down Expand Up @@ -168,6 +174,11 @@ vocabulary above.

## Open questions

- Connected/settle honesty (no stale Connect after success; settle never
posting as the signed-in user; no agent 401 after GitHub already
succeeded) stays **target** until CL-6737 and CL-6738 land — see
IMPLEMENTATION.md open questions; do not document those guarantees as
shipped.
- Whether "Space" and "Chat" as user-facing labels are fully rolled out
across the UI or still landing incrementally is not settled in the
docs reviewed for this pass — treat the sidebar and conversation-header
Expand Down
Loading