feat(spec): segment ObjectStackProtocol into per-domain interfaces (ADR-0076 D9, step 1)#2429
Merged
Merged
Conversation
…rfaces (ADR-0076 D9) Split the 70-method, 11-domain ObjectStackProtocol god-interface into focused, exported per-domain contracts (DataProtocol, MetadataProtocol, AnalyticsProtocol, AutomationProtocol, PackageProtocol, ViewProtocol, PermissionProtocol, WorkflowProtocol, RealtimeProtocol, NotificationProtocol, AiProtocol, I18nProtocol, FeedProtocol). ObjectStackProtocol now `extends` all of them — shape-identical to the old flat interface, so non-breaking. This is the lowest-risk, foundational step of ADR-0076 D9: pure type-level, shape-preserving, no runtime change. Consumers can now depend on the narrowest slice (e.g. DataProtocol). The composed union is transitional (D9 rev.7). Verified: turbo build (spec + rest + metadata-protocol + objectql) green incl. DTS — the impl class still satisfies `implements ObjectStackProtocol`; spec suite 243 files / 6602 tests pass. 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
📓 Docs Drift CheckThis PR changes 1 package(s): 90 hand-written doc(s) reference the affected code and may need an implementation-accuracy re-verification:
|
…l interfaces The api-surface ratchet flagged 13 additive exports (0 breaking) from the ObjectStackProtocol segmentation. Regenerated the committed snapshot. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
os-zhuang
added a commit
that referenced
this pull request
Jun 28, 2026
…ta-protocol name; no rename) (#2431) Per maintainer decision: keep the already-published `@objectstack/metadata-protocol` package name. Renaming churns downstream for ~0 benefit. The `protocol` suffix is a deliberate, low-cost naming exception — the real contract lives in `@objectstack/spec/api`, not the impl package. - D10: replace the "rename → metadata-runtime" clause with "name retained; content converges to the metadata-management impl". - Open Question #7: resolved (keep the name; README note to clarify impl-vs-contract). - Status: rev.8; notes D9 step-1 (interface segmentation) shipped in #2429. Docs only; empty changeset. Co-authored-by: Jack Zhuang <277994282+os-zhuang@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
6 tasks
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.
What
First, lowest-risk implementation step of ADR-0076 D9: segment the 70-method, 11-domain
ObjectStackProtocolgod-interface into focused, exported per-domain contracts.New exported interfaces in
@objectstack/spec/api:DataProtocol,MetadataProtocol,AnalyticsProtocol,AutomationProtocol,PackageProtocol,ViewProtocol,PermissionProtocol,WorkflowProtocol,RealtimeProtocol,NotificationProtocol,AiProtocol,I18nProtocol,FeedProtocol.ObjectStackProtocolnowextendsall of them.Why this is the safe first pick
ObjectStackProtocolis identical in shape to the old flat interface, so every implementer (ObjectStackProtocolImplementation) and consumer (rest, objectql) is unaffected. Non-breaking.New code can now depend on the narrowest slice (e.g.
DataProtocol). Per D9 (rev.7) the composed union is transitional; runtime capability availability comes from the discoveryservicesregistry.Verification
turbo build(spec + rest + metadata-protocol + objectql) green incl. DTS —implements ObjectStackProtocolstill satisfied; consumers compile unchanged.@objectstack/specsuite: 243 files / 6602 tests pass.🤖 Generated with Claude Code