← Commit history

Dock Bar guide: the park contract (both halves behind one flag, body over transport)

John Lauer ·a31371ebbc ·2mo ago ·parent 3de58bd
1 file changed +1−1
docs/dockbar.md+1−1
@@ -151,7 +151,7 @@ Users drive Adom by talking to their AI, and the single most useful thing a dash ] ``` -The dock shows them at the two moments the user is already looking: on the interstitial while your app starts (click copies the phrase) and in the card's hover preview. Your dashboard should carry the same lesson **at the very top**, above the status cards: a "Say it" strip with the phrases, copy on click. (A "Try it" that stages the phrase into the app's own AI thread is part of the design but is PARKED for now: ship copy-only until the platform broadcasts the all-clear on the AI-thread typing path.) The staging recipe, for when it returns (your server can reach the Hydrogen control API, and the thread is findable by its `app:<owner/slug>` tag). Every phrase uses your app's noun exactly as users should say it; include the qualifier words they will need (which browser, which profile, which editor).+The dock shows them at the two moments the user is already looking: on the interstitial while your app starts (click copies the phrase) and in the card's hover preview. Your dashboard should carry the same lesson **at the very top**, above the status cards: a "Say it" strip with the phrases, copy on click. (A "Try it" that stages the phrase into the app's own AI thread is part of the design but is PARKED for now: ship copy-only until the platform broadcasts the all-clear on the AI-thread typing path. Park BOTH halves behind one flag: render no Try buttons, and have the server's try endpoint refuse BEFORE any control-API call with `parked: true` plus a human-readable reason in the body. The HTTP status may be 503 or your uniform-200 envelope; callers judge the body, never the transport.) The staging recipe, for when it returns (your server can reach the Hydrogen control API, and the thread is findable by its `app:<owner/slug>` tag). Every phrase uses your app's noun exactly as users should say it; include the qualifier words they will need (which browser, which profile, which editor).  #### Finding the app's own thread (for "Try it")