Uh oh!
There was an error while loading. Please reload this page.
docs(adr-0057): Amendment A1 — build conversations bind a package (lazy binding) - #2457
Merged
Conversation
…zily
Proposed amendment from live-testing findings: build threads get a visible,
switchable, lazily-established package binding (chip: bound app / "New app").
Magic flow starts unbound (no create-first friction) and auto-binds + re-keys
to app:X:build when the build mints the package — fixing agent ambiguity
("which app?"), global thread mixing, and the build-history continuity break.
Phased A1.a chip → A1.b bind-on-create+re-key → A1.c cloud prompt injection +
pending-blueprint amend rule.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>The latest updates on your projects. Learn more about Vercel for GitHub. |
os-zhuang
commented
Jul 13, 2026
ContributorAuthor
Consolidated UX-findings issue filed: #2458 (its item 2 = this amendment's A1.c). |
os-zhuang
commented
Jul 13, 2026
ContributorAuthor
A1.a (the binding chip) is implemented + live-verified in #2461; A1.c (pending-blueprint amend) in objectstack-ai/cloud#823. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docs-only. Proposes Amendment A1 to ADR-0057, distilled from the 2026-07-13 live browser-testing rounds and the follow-up design discussion.
The three live-reproduced defects it addresses
/ai/build(the magic flow) keys to product-only scope: ONE global build thread for every project.app:X:buildthread "Edit with AI" opens later are different conversations; the original build history is stranded.The proposal in one line
Every build conversation carries a visible, switchable, lazily-established package binding — the Claude-Code-picks-a-repo idiom for display, never for gating: the magic flow starts as "✨ New app" with zero create-first friction and auto-binds + re-keys when the build mints the package.
Phasing: A1.a read-only chip (folds into P3a's dock header) → A1.b bind-on-create + conversation re-key (+ legacy-scope fallback) → A1.c cloud prompt injection + the pending-blueprint "default to amend" rule.
Refs: epic #2409 (ADR-0057), ADR-0070 (active package), the consolidated UX-findings issue (linked after filing).
🤖 Generated with Claude Code