Repository navigation
docs(security): document scope-depth (ADR-0057 D1) + open/paid boundary (ADR-0016) - #2118
Merged
Merged
Conversation
…ry (ADR-0016) scope-depth (readScope/writeScope = own/own_and_reports/unit/unit_and_below/org) is the core declarative ERP authz axis, but it was undocumented in both the objectstack-data skill and the security guide — so an AI author wouldn't know it exists (and would fall back to hand-written RLS, exactly what ADR-0057 removes), and wouldn't know the open/paid boundary (using `unit` in open-source silently fails closed to `own`). - skills/objectstack-data: new "Access depth (scope-depth)" section before RLS — the 5-value table + a usage example + the ADR-0016 open-core boundary (hierarchy-relative scopes need @objectstack/security-enterprise; fail closed to `own` without it; defineStack requires ['hierarchy-security']). - guides/security.mdx: matching scope-depth section under Object Permission Levels. Doc/skill-only. check:skill-docs in sync; docs build green (1113 pages). showcase deliberately NOT touched — it's open-source, so a `unit` scope there would fail-closed to `own` and mislead; the showcase-scope-depth dogfood already proves the capability with a reference resolver. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
os-zhuang
added a commit
that referenced
this pull request
Jun 30, 2026
chore: release packages (#2118) objectui@4a259042dbede9cfab04580f444d1184b6f375dc
This branch was successfully deployed
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.
Audit follow-up after cloud #401 (security-enterprise / hierarchy rollup landed): scope-depth + the open/paid boundary were undocumented in both the
objectstack-dataskill and the security guide.Why it matters
readScope/writeScope(own / own_and_reports / unit / unit_and_below / org) is the core declarative ERP authz axis (ADR-0057 D1). Undocumented, an AI author:unitin open-source, where it silently fails closed toown.What
@objectstack/security-enterprise; fail closed toownwithout it;defineStackrequires['hierarchy-security']).Doc/skill-only · check:skill-docs in sync · docs build green (1113 pages).
showcase deliberately NOT touched — it's open-source, so a
unitscope there would fail-closed toownand mislead; theshowcase-scope-depthdogfood already proves the capability with a reference resolver.🤖 Generated with Claude Code