Skip to content

feat(service-ai): ADR-0040 — unify the platform assistant (data + authoring registers)#1735

Merged
os-zhuang merged 1 commit into
mainfrom
feat/adr-0040-unified-assistant
Jun 11, 2026
Merged

feat(service-ai): ADR-0040 — unify the platform assistant (data + authoring registers)#1735
os-zhuang merged 1 commit into
mainfrom
feat/adr-0040-unified-assistant

Conversation

@os-zhuang

Copy link
Copy Markdown
Contributor

Implements the agent half of ADR-0040: data_chat becomes the platform assistant.

  • skills += metadata_authoring, solution_design (cloud AI Studio plugin registers them; without it the references don't resolve and the assistant gracefully degrades to data-only).
  • Intent preamble: classify build/change vs data intent first; apply that register's discipline; never mix registers or narrate tool failures.
  • Persona: label Assistant, role Business Application Assistant; temperature 0.2; 60s budget; react ×10 + replan.
  • Guardrails: blocklist union minus alter_schema/drop_table — the build register IS schema work and is already draft-gated (ADR-0033); keeps delete_records, drop_database, raw_sql, system_tables.

Tests updated to the new persona (role/label/instructions/temperature/skills). service-ai 334/335 — the 1 failure (embedder binding) fails identically on unmodified origin/main in a fresh worktree (env-dependent optional provider; user's built checkout passes it 97/97).

Note: agent metadata registration is exists-gated — durable envs keep the old persona until their agent record refreshes; ephemeral staging kernels pick this up on next boot (known limitation, same as skills).

objectui half (picker removal) lands separately; the ADR-0038 L5 golden-prompt suite guards both registers post-unification.

🤖 Generated with Claude Code

…horing registers)

The default data_chat agent becomes THE platform assistant:

- skills: + metadata_authoring + solution_design (registered by the cloud
  AI Studio plugin; deployments without it degrade gracefully to data-only —
  the skill registry ignores unresolved names).
- instructions: intent preamble — classify build/change vs data intent FIRST,
  apply that register's discipline, never mix registers or narrate failures.
- persona: label 'Assistant', role 'Business Application Assistant'.
- model: temperature 0.2 (authoring determinism wins).
- guardrails: blocklist union MINUS alter_schema/drop_table (the build
  register IS schema work, and it is already draft-gated per ADR-0033);
  60s execution budget for whole-app builds.
- planning: react ×10 with replan (builds take more steps than answers).

Motivation (staging 2026-06-11): the data-only persona accepted a whole-app
build — tools are registry-global — without the authoring disciplines, hand-
rolled the schema, collided with leftovers, and narrated its debugging to a
business user. ADR-0040: the end user never picks an agent; one assistant
carries both registers and the skills system does per-intent behavior.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@vercel

vercel Bot commented Jun 11, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
spec Ready Ready Preview, Comment Jun 11, 2026 3:45pm

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant