docs(adr): ADR-0083 — metadata-type taxonomy (Airtable 3 + 3)#2499
Closed
os-zhuang wants to merge 1 commit into
Closed
docs(adr): ADR-0083 — metadata-type taxonomy (Airtable 3 + 3)#2499os-zhuang wants to merge 1 commit into
os-zhuang wants to merge 1 commit into
Conversation
…rce of truth) ObjectStack has a superset of Airtable's surface (~27 metadata types) but no single model for it, and the two places that group types disagree and are each muddled: `os` stats (format.ts) files `action` under UI and buries `agent` in Logic; Studio nav (studio.app.ts) mixes Data with Interface and splits "Logic" from "Automation". Define the model once: keep Airtable's three (Data · Automation · Interface) and add the three Airtable lacks (Access · Intelligence · Integration), with Integration as a cross-cutting EDGE (datasource/connector/webhook get a primary home + a documented secondary, never a duplicate listing). Each pillar has an anchor type; the rest disclose progressively. Mandate a single source of truth — a spec `METADATA_CATEGORY` map — that Studio nav, the `os` stats sections, the docs reference, and the showcase Start Here all derive from, so they stop disagreeing. Records the placement of every type, cross-cutting rules, and the alternatives rejected (force into 3 / flat 27 / per-surface grouping / Integration as a 7th peer). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
added
documentation
Contributor
Author
|
Voided — superseded by ADR-0084 (application-builder information architecture, #2503). The design pass corrected two of this ADR's claims (AI is a platform capability, not a peer pillar; Integration folds into Advanced, not a peer tier), and 0084 captures the builder-relevant taxonomy directly. Closing without merge. |
xuyushun441-sys
pushed a commit
that referenced
this pull request
Jul 1, 2026
ADR-0083 (metadata-type taxonomy) was voided (#2499 closed); 0084 subsumes the builder-relevant taxonomy. Remove the Builds-on citation and the Relationship section — their content (AI is a platform capability not a pillar; Integration folds into Advanced) already lives in the TL;DR and Alternatives. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Answers "Airtable categorizes as Data / Automation / Interface — I have more metadata types, how do I express and present them?" by defining the model once, as a single source of truth.
The problem
ObjectStack has a superset of Airtable's surface (~27 top-level metadata types) but no single model — and the two places that group types disagree and are each muddled:
osstats (format.ts): Data / UI / Logic / Security — filesactionunder UI (it's behavior), buriesagentin Logic (it's AI).studio.app.ts): a Build group mixing Data with Interface, then splits "Logic" (actions/hooks) from "Automation" (flows) — two names for one concern.The model — keep the 3, add the 3
objectflowpageroleagentdatasourceSingle source of truth
A spec
METADATA_CATEGORYmap that Studio nav,osstats, the docs reference, and the showcase Start Here all derive from — so they stop disagreeing, and the build agent gains a canonical category to reason with.Docs-only; all cross-ADR links verified.
Follow-ups (separate PRs, per your call): encode
METADATA_CATEGORYin spec; regroup Studio nav; alignosstats; extend Start Here to the six-pillar map.🤖 Generated with Claude Code