docs(adr): ADR-0040 Unified Assistant — the end user never picks an agent#1734
Merged
Conversation
…gent agent = assembled runtime configuration + governance unit (model, guardrails, planning, memory, persona, skill composition), selected by SCENARIO via the existing resolution chain (app.defaultAgent → platform default → first active) and configured by BUILDERS; skill = reusable capability fragment. The consumer picker leaves chat UX; custom agents stay a builder feature on the same draft→verify→publish pipeline; the tool-scoping gap (tools are registry-global; skills carry discipline, not access control) is named as the follow-up contract. Motivated by the 2026-06-11 staging incident: the Data Assistant accepted a build-an-app job without the authoring disciplines and narrated its own debugging to a business user. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
added
documentation
This was referenced Jun 11, 2026
xuyushun441-sys
pushed a commit
that referenced
this pull request
Jun 14, 2026
fix(plugin-grid): row Edit/Delete honor object userActions.{edit,delete} (#1734)
objectui@209633cf5883030f54517c3e580e9aaca70a26d9
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 free
to 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.
Design record for the agent/skill boundary question raised in today's staging incident (Data Assistant accepted a whole-app build without the authoring disciplines and narrated its debugging to the user).
Core positions:
?agent=/API pins stay for builder/developer/programmatic surfaces.agentstays in the spec, redefined: assembled runtime configuration + governance unit (model/guardrails/planning/memory/persona/skills), selected by scenario via the existing resolution chain, configured by builders. Agents : assistants :: views : lists.Implementation lands separately (service-ai default-agent composition + objectui picker removal), gated by the ADR-0038 L5 suite.
🤖 Generated with Claude Code