docs(adr): ADR-0033 — AI-assisted metadata authoring#1528
Merged
Conversation
Proposes the authoring loop for an AI-authored platform: one agent/chat brain across all metadata types (not per-designer generators); every AI write lands in the ADR-0027 draft (never publishes) and is confirmed via the designer's review/diff; a type-agnostic update_metadata tool validated per-type (ADR-0005); plan-first blueprint for vague intent; and the open-core boundary (OSS BYO-model authoring vs EE managed AI + governance). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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.
Summary
Proposes the authoring loop for an AI-authored platform — how an AI generates/modifies any metadata type and how a human safely confirms it before it goes live. Status: Proposed (for discussion).
Decisions:
requiresConfirmation).update_metadata(type,name,patch,mode:'draft')(+ create/describe) validated against the per-type Zod schema (ADR-0005), instead of N per-type write tools.Builds on ADR-0010 (NL→flow) / ADR-0011 (actions-as-tools) / ADR-0027 (authoring lifecycle) / ADR-0032 (validate-by-default) / ADR-0005 / ADR-0019.
Why now
The pieces exist but aren't a safe loop: the metadata tools publish immediately (no draft,
requiresConfirmationunenforced); write tools cover only objects/fields; and nothing handles low-specificity "design me a system" input. This ADR specifies the target end-state (pre-launch, no deprecation path).Note
Doc-only. The objectui side already shipped the client foundations referenced here (per-designer designers, review/diff, designer→chat context + "Ask AI"). The framework-side changes (draft-routed tools, generic
update_metadata, blueprint) are the Phase A/C work this ADR motivates.🤖 Generated with Claude Code