Development record
The brief session page puts technical setup in front of a product thinker before they can see the brief: its first screen asks for a relay address (a term the page never explains), then for a GitHub personal access token, and the brief appears only after hosting and picking a file. Tested by the product thinker on the hosted-sites draft, who could not tell what the page was for or what to enter. A person who only wants to work on the brief should arrive with the relay already chosen and sign in with one GitHub button.
issueresolvedmajoriss-2610161332024554
The brief session page puts technical setup in front of a product thinker before they can see the brief: its first screen asks for a relay address (a term the page never explains), then for a GitHub personal access token, and the brief appears only after hosting and picking a file. Tested by the product thinker on the hosted-sites draft, who could not tell what the page was for or what to enter. A person who only wants to work on the brief should arrive with the relay already chosen and sign in with one GitHub button.
Frontmatter
| id | iss-2610161332024554 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | major |
.abcd/work/issues/resolved/iss-2610161332024554-the-brief-session-page-puts-technical.md
open on GitHub ↗ · commit history ↗
mentions3
- adr-2610161400542916The brief session page asks nobody for a relay address or a token, and a local session signs in by GitHub's device flow
- itd-2610091016262335A team edits its brief together live during a call, on abcdesign.app or on the host's own computer
- spc-2610141709430146the-product-thinker-and-the-technical