feat: permission sets for Hypercerts & Certified data by aspiers · Pull Request #222 · hypercerts-org/hypercerts-lexicon

aspiers · 2026-06-09T13:22:53Z

Summary

Adds permission sets for the org.hypercerts.*, org.hyperboards.*, and app.certified.* record collections — both the design and the implementation.

A permission set lets any AT Protocol app request a whole bundle of repo: scopes with one include:<nsid> OAuth scope, instead of enumerating each collection by hand. The user's PDS resolves and expands the set during the OAuth grant; the same published set can also be consumed by services (e.g. the Certified group service) when expanding API-key scopes.

One set per namespace, by spec mandate

There are three separate sets — not one combined set — because the spec requires it. A permission set "is limited to expressing permissions that reference resources under the same NSID namespace as the set itself" and "can not address 'sibling groups' or 'parents'". org.hypercerts, org.hyperboards, and app.certified are different namespace authorities (hypercerts.org, hyperboards.org, certified.app), so a single set legally cannot span them. An app needing more than one requests each include: scope.

NSID shape (single segment under the namespace root)

The same authority rule constrains the set's own NSID: NSID.authority is the reversed domain of all-but-the-last segment, so the set must be a single leaf directly under the namespace root — org.hypercerts.authWrite, not org.hypercerts.permissions.crud (whose authority permissions.hypercerts.org would fail to parent org.hypercerts.claim.*, making IncludeScope.toScopes silently return []). This matches Bluesky's own published sets (app.bsky.authViewAll, app.bsky.authCreatePosts, app.bsky.authDeleteContent, app.bsky.authFullApp — single segment, auth-prefixed leaf) and the spec's com.example.authFull examples.

Lexicon → NSID	Grants write (create/update/delete) on
`lexicons/org/hypercerts/authWrite.json` → `org.hypercerts.authWrite`	all `org.hypercerts.*` record collections (11)
`lexicons/org/hyperboards/authWrite.json` → `org.hyperboards.authWrite`	all `org.hyperboards.*` record collections (2)
`lexicons/app/certified/authWrite.json` → `app.certified.authWrite`	all `app.certified.*` record collections (9)

Each enumerates every type: "record" collection in its namespace with action: [create, update, delete], and expands to a single combined repo: scope.

Process docs — AGENTS.md's "Adding / modifying a lexicon" checklist gains a step: when a new org.hypercerts.* / org.hyperboards.* / app.certified.* record lexicon is added (or removed), update its namespace's permission set to match, since the enumerated collection list is both the grant and its boundary.

Design rules followed (spec-cited in the doc)

Own-namespace authority → one set per namespace, single-segment NSID under the root (above).
No wildcards inside a set → collections enumerated (the list is the grant + boundary; a Maintenance section flags keeping it in sync).
repo: scopes carry no aud → requested without ?aud=. No read action exists in the scope grammar (records are world-readable), so these are write sets; title/detail are authorization-dialog consent copy.

Tooling note

permission-set is a lexicon primitive lex gen-api cannot codegen (it has no TS shape; verified both @atproto/lex-cli@0.9.6 and 0.10.0 throw). These sets need no TS shape — they are the source of truth published to AT Protocol. So they are:

excluded from the lex codegen invocations via scripts/run-lex-codegen.js — a Node runner that builds the lexicon file list (filtering out defs.main.type === "permission-set") and spawns lex <subcommand> … <files> with it as argv, forwarding lex's exit code, and
skipped by scripts/generate-exports.js (same content check),

the single content-based exclusion shared by both, so it doesn't break when set files move. They still ship as raw lexicon JSON and appear in SCHEMAS.md. Full npm run check passes.

(The runner replaced an earlier shell pipeline: lex … $(node …) swallowed a producer failure, and the node … | xargs form needed set -o pipefail, which the dash that npm runs scripts with on GitHub's Ubuntu runners rejects. A single Node process gives one authoritative exit code with no shell word-splitting or pipefail dependency.)

Rebased onto #219

PR #219 (signature support, HYPER-181) has since merged, adding the app.certified.signature.proof record lexicon. This branch is rebased onto it and app.certified.signature.proof is now included in app.certified.authWrite (9 collections), so the set covers every app.certified.* record on main. The earlier "pending follow-up" note has been dropped from the design doc's Maintenance section.

Notes

Suggested NSIDs (*.authWrite) follow Bluesky's auth* convention; rename freely.
Includes a minor changeset.

🤖 Generated with Claude Code

Summary by CodeRabbit

New Features
- Added three new permission-set lexicons (Hypercerts, Hyperboards, and Certified), enabling scoped write access (create/update/delete) per namespace via include:<nsid> OAuth scopes.
Documentation
- Added a permission-sets design guide, expanded setup/maintenance steps to keep permissions aligned with record collections (no wildcards), and updated schema documentation to render permission-set entries.
Chores
- Updated lexicon generation/tooling so permission-set lexicons are consistently excluded from code generation while still being correctly reflected in generated schema output.

changeset-bot · 2026-06-09T13:23:03Z

🦋 Changeset detected

Latest commit: 733f555

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@hypercerts-org/lexicon	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

coderabbitai · 2026-06-09T13:23:04Z

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

@coderabbitai resume to resume automatic reviews.
@coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

▶️ Resume reviews
🔍 Trigger review

📝 Walkthrough

Walkthrough

Adds three namespace-scoped permission-set lexicons, documents how to request and maintain them, and updates code generation so permission-set JSON is excluded from generated outputs while still shipping as raw lexicon files.

Changes

Permission set definitions

Layer / File(s)	Summary
Permission-set lexicon definitions and schemas `SCHEMAS.md`, `lexicons/org/hypercerts/authWrite.json`, `lexicons/org/hyperboards/authWrite.json`, `lexicons/app/certified/authWrite.json`, `.changeset/permission-sets-crud.md`	Adds three `authWrite` permission-set lexicons and matching schema entries, plus a changeset describing the new scope bundles and collection enumeration rules.

Documentation and workflow updates

Layer / File(s)	Summary
Permission-set design and workflow docs `docs/design/permission-sets.md`, `.agents/skills/building-with-hypercerts-lexicons/SKILL.md`, `AGENTS.md`	Adds design and workflow documentation for `include:<nsid>` permission sets, namespace and collection constraints, resolution behavior, and maintenance steps for keeping them aligned with record lexicons.

Code generation and export filtering

Layer / File(s)	Summary
Lex codegen runner and export filtering `package.json`, `scripts/run-lex-codegen.js`, `scripts/generate-exports.js`, `scripts/generate-schemas.js`	Switches lex codegen scripts to a Node runner that filters permission-set lexicons, and updates export generation and schema rendering to handle permission-set lexicon JSON directly.

Estimated code review effort: 4 (Complex) | ~45 minutes

Possibly related PRs

hypercerts-org/hypercerts-lexicon#70: Updates the AGENTS.md changesets workflow that this PR now references in its regeneration steps.
hypercerts-org/hypercerts-lexicon#195: Introduced the downstream AI skill guide that this PR extends with permission-set documentation.
hypercerts-org/hypercerts-lexicon#97: Added the schema-generation path that this PR extends to render permission-set lexicons.
Suggested reviewers: s-adamantine, holkexyz

🚥 Pre-merge checks | ✅ 6 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (6 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the addition of permission sets, though it omits Hyperboards from the full scope.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Lexicon Documentation Sync	✅ Passed	New permission-set lexicons are added in JSON and mirrored in SCHEMAS.md; README.md and ERD.puml don’t reference these IDs, so no sync issue.
Lexicons Styleguide Compliance	✅ Passed	PASS: The new lexicon files use the expected auth-prefixed NSIDs and permission-set type; I found no undocumented styleguide deviations.

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch feature/permission-sets-design

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

Copilot

Pull request overview

Adds a new design document describing two AT Protocol permission sets intended to bundle repo-scope permissions for the org.hypercerts.* and app.certified.* record-collection namespaces, so OAuth clients (and CGS) can request a single include:<nsid> scope instead of enumerating per-collection repo: scopes.

Changes:

Introduces docs/design/permission-sets.md documenting proposed permission-set NSIDs and their expanded scopes.
Enumerates the targeted record collections for each namespace and records design constraints (namespace authority, no wildcards, no aud for repo:).
Describes publication/resolution flow and CGS consumption patterns.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.

Copilot

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated 5 comments.

Copilot

Pull request overview

Copilot reviewed 8 out of 8 changed files in this pull request and generated 5 comments.

Copilot

Pull request overview

Copilot reviewed 8 out of 8 changed files in this pull request and generated 2 comments.

…$(…) Copilot was right that command substitution is the wrong shape here. A `$(…)` arg list silently swallows a producer failure (the script could exit non-zero and lex would still run on partial/empty input and "succeed"). Switch to the pipe + xargs form the original gen-* used: node ./scripts/codegen-lexicon-files.js | xargs -0 -r lex gen-… - `set -o pipefail` makes a producer failure abort the pipeline (verified: a plain pipe reports exit 0 on producer failure; pipefail reports 1). dash — the sh on Ubuntu CI and here — supports it. - `-r` skips lex on empty input; `-0` (NUL-delimited from the script) is robust to any path chars; xargs also sidesteps ARG_MAX. - The script now exits non-zero + writes nothing if it finds no lexicons, so an internal bug surfaces rather than codegenning nothing. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

`set -o pipefail` is NOT portable: GitHub's Ubuntu `sh` (dash) rejects it (`set: Illegal option -o pipefail`), which broke CI. And no `xargs` option replaces it — `-r` only skips empty input, it does not propagate a producer's non-zero exit, so a crashed list-generator still yields a "successful" pipeline. Replace the pipe entirely with scripts/run-lex-codegen.js: a single Node process that builds the permission-set-excluded file list and spawns `lex <subcommand> <args> <files…>` with the list as argv, forwarding lex's exit code. One authoritative exit code, no shell builtins, no ARG_MAX (argv, not a command line), no pipefail. Empty list or spawn failure → non-zero exit. (Renamed from codegen-lexicon-files.js, which only printed the list.) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…x-codegen) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot is right: spawnSync still calls execve and is subject to the OS argument-length limit. The runner's real wins are avoiding shell pipeline exit-code masking and shell word-splitting, not removing ARG_MAX. Reworded the comments in run-lex-codegen.js and package.json accordingly (the limit is ~2 MB on Linux, far above this few-KB list). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…list The "Adding / modifying a lexicon" steps covered codegen, ERD, README/SKILL, SCHEMAS.md, format, check, and changeset — but never the permission sets. Each authWrite.json enumerates every type:"record" collection in its namespace (the list is both the grant and its boundary; no wildcards allowed inside a set), so a new org.hypercerts.* / app.certified.* record lexicon is NOT grantable via the published set until added to the matching set — and must be removed when deleted. Add a step spelling this out, including the own-namespace-authority rule (each record goes only in its own namespace's set) and the non-record exemption (query/object/permission-set defs are not repo collections). Links to docs/design/permission-sets.md for the full rationale. Prettier also renumbered the list (fixing a pre-existing duplicate-"4" bug). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…nted The repo has a third first-class record namespace — org.hyperboards (board, displayProfile, described in AGENTS.md as the "Hyperboards visual layer") — that had no permission set, so a user's Hyperboards data was not grantable via any published set. Add org.hyperboards.authWrite granting create/update/delete over both org.hyperboards.* record collections, matching the other two namespaces. Verified it enumerates exactly the type:"record" defs on disk and expands to one combined repo: scope. Also update the surrounding docs that the new set and the now-shipped state make stale: - docs/design/permission-sets.md: Status "Proposed" -> "Implemented" (the sets are published lexicon files in this PR, not a proposal); "two sets" -> three throughout, with a new org.hyperboards.authWrite subsection and the three distinct authorities (hypercerts.org, hyperboards.org, certified.app) spelled out; corrected a stray claim that hypercerts/hyperboards "share a domain". - SKILL.md: third table row; "two sets, never one" -> "one set per namespace". - .changeset/permission-sets-crud.md: two -> three sets. - AGENTS.md: the add-a-lexicon permission-set step now lists all three namespaces. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

… set PR #219 (signature support, HYPER-181) has now merged to main, adding the app.certified.signature.proof record lexicon. This was the documented follow-up: app.certified.authWrite must enumerate every app.certified.* record collection, so the newly-landed collection has to be added or it is not grantable via the published set. Add it (the set now lists all 9 app.certified.* records, verified identical to the type:"record" defs on disk), sync the JSONC example in the design doc, and drop the now-resolved "Known pending update (#219)" note from the Maintenance section. SCHEMAS.md regenerated. npm run check passes (182 tests). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot flagged the bullets under step 9 as unindented, so Markdown renderers treated them as a separate top-level list and the blank line broke the ordered-list numbering. Indent them 3 spaces to match the sub-bullet convention used by the other steps. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

…owth semantics Two review points from Ashex on PR #222: - `description` is not a valid field on a `permission-set` def — the spec defines only `title`/`detail` (+ `:lang`) as user-facing consent copy, and it is not shown in the OAuth dialog. It was an AI hallucination in the original set files. Removed from all three sets, their JSONC examples in the design doc, and the generated SCHEMAS.md. All 182 tests still pass, confirming the field was never load-bearing. - Document what happens when a published set later grows: OAuth grants persist the raw `include:<nsid>` and re-expand it on token refresh, so existing sessions gain newly-added (same-authority) collections with no re-auth and no `.vN` NSID; CGS API keys stay a frozen snapshot until re-issued. Grounded in the permission spec and the reference PDS `rotateToken`/`buildTokenScope` path, with a caveat that non-reference Auth Servers should be verified. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

…ePDS parity Reframe the 'growing a set' subsection around the real concern: on the OAuth path, adding collections to a published set silently widens every existing grant on next token refresh, with no new consent prompt (verified: rotateToken re-expands and re-issues without a consent re-check). State that plainly, and note the two bounds that make it tolerable — additions are same-namespace by the authority rule (highly correlated with what the user already granted; a set can never silently pull in a cross-namespace permission), and growth only ever adds, never narrows. Guidance: publish under a new set NSID when re-consent is the point. Also record that ePDS inherits this behaviour: it wraps stock @atproto/pds / @atproto/oauth-provider (0.15.10) with a Better Auth login layer and does not fork or override token issuance/refresh, so it persists the raw include:<nsid> and re-expands via the stock rotateToken exactly like the reference PDS. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

…ontext Two Copilot review fixes on the permission-sets PR: - generate-schemas.js: permission-set defs (title/detail/permissions) now render in SCHEMAS.md instead of producing empty header-only sections. - generate-exports.js: extract a readLexicon() helper that rethrows JSON.parse failures with the offending file path, mirroring generate-schemas.js, so codegen errors are traceable. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

…owth semantics Two review points from Ashex on PR #222: - `description` is not a valid field on a `permission-set` def — the spec defines only `title`/`detail` (+ `:lang`) as user-facing consent copy, and it is not shown in the OAuth dialog. It was an AI hallucination in the original set files. Removed from all three sets, their JSONC examples in the design doc, and the generated SCHEMAS.md. All 182 tests still pass, confirming the field was never load-bearing. - Document what happens when a published set later grows: OAuth grants persist the raw `include:<nsid>` and re-expand it on token refresh, so existing sessions gain newly-added (same-authority) collections with no re-auth and no `.vN` NSID; CGS API keys stay a frozen snapshot until re-issued. Grounded in the permission spec and the reference PDS `rotateToken`/`buildTokenScope` path, with a caveat that non-reference Auth Servers should be verified. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Copilot

Pull request overview

Copilot reviewed 12 out of 12 changed files in this pull request and generated 2 comments.

Ashex

Approved pending testing per our discussion

coderabbitai

Actionable comments posted: 1

🧹 Nitpick comments (1)

scripts/generate-schemas.js (1)
275-293: 🎯 Functional Correctness | 🔵 Trivial | ⚡ Quick win

Only handles repo-type permissions; rpc permissions would render incomplete.

Per the AT Protocol permission spec, a permission's resource field can be "rpc" (with lxm/aud/inheritAud fields) in addition to "repo" (collection/action). This function only renders collection/action, so an rpc permission would print just **Resource:** \rpc`with no endpoint/audience detail — not incorrect for the three lexicons in this PR (allrepo-only), but incomplete if a future permission set in this repo adds rpc` permissions.
♻️ Optional: extend to cover `rpc` permissions
   for (const permission of permissions) {
     const collections = (permission.collection || [])
       .map((c) => `\`${c}\``)
       .join(", ");
     const actions = (permission.action || []).map((a) => `\`${a}\``).join(", ");
     output.push(`**Resource:** \`${permission.resource}\``, "");
     if (collections) output.push(`**Collections:** ${collections}`, "");
     if (actions) output.push(`**Actions:** ${actions}`, "");
+    const lxm = (permission.lxm || []).map((l) => `\`${l}\``).join(", ");
+    if (lxm) output.push(`**LXM:** ${lxm}`, "");
+    if (permission.aud) output.push(`**Audience:** \`${permission.aud}\``, "");
   }
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@scripts/generate-schemas.js` around lines 275 - 293,
generatePermissionSetSection only formats repo-style permissions, so rpc
permissions would be incomplete. Update this helper to branch on
permission.resource and, for rpc entries, render the rpc-specific fields such as
lxm, aud, and inheritAud alongside the resource label; keep the existing
collection/action rendering for repo permissions.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/design/permission-sets.md`:
- Around line 85-87: The blockquote in the permission-sets documentation is
broken by an empty separator line, which triggers MD028. Update the quoted
section so the gap is either removed or the separator line is also prefixed with
the blockquote marker, keeping the entire paragraph sequence within the same
blockquote near the “Naming” text.

---

Nitpick comments:
In `@scripts/generate-schemas.js`:
- Around line 275-293: generatePermissionSetSection only formats repo-style
permissions, so rpc permissions would be incomplete. Update this helper to
branch on permission.resource and, for rpc entries, render the rpc-specific
fields such as lxm, aud, and inheritAud alongside the resource label; keep the
existing collection/action rendering for repo permissions.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

Push a commit to this branch (recommended)
Create a new PR with the fixes

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 3777a009-7424-4d96-8e04-d0a98e383519

📥 Commits

Reviewing files that changed from the base of the PR and between 2f281d4 and cd08e55.

📒 Files selected for processing (12)

.agents/skills/building-with-hypercerts-lexicons/SKILL.md
.changeset/permission-sets-crud.md
AGENTS.md
SCHEMAS.md
docs/design/permission-sets.md
lexicons/app/certified/authWrite.json
lexicons/org/hyperboards/authWrite.json
lexicons/org/hypercerts/authWrite.json
package.json
scripts/generate-exports.js
scripts/generate-schemas.js
scripts/run-lex-codegen.js

✅ Files skipped from review due to trivial changes (1)

lexicons/app/certified/authWrite.json

🚧 Files skipped from review as they are similar to previous changes (6)

lexicons/org/hyperboards/authWrite.json
lexicons/org/hypercerts/authWrite.json
package.json
scripts/generate-exports.js
SCHEMAS.md
AGENTS.md

aspiers · 2026-07-11T18:32:11Z

Tested in hypercerts-org/ePDS#188 and it looks good:

aspiers · 2026-07-11T18:36:52Z

(comment generated by Claude Code)

Re: CodeRabbit review-summary nitpick — "generatePermissionSetSection only handles repo-type permissions; rpc permissions would render incomplete" (scripts/generate-schemas.js ~275-293):

Stale — no action taken. There is no generatePermissionSetSection (or any permission-rendering code) in scripts/generate-schemas.js anymore; grep -rn "generatePermissionSetSection|permission.resource|\*\*Collections:\*\*" scripts/ returns nothing. Permission-set lexicons are excluded from schema/codegen output entirely (by the main.type === "permission-set" content check), so there is no repo-vs-rpc rendering path to extend. The nitpick refers to code that is not present in this PR.

- generate-exports.js: normalize findJsonFiles output to POSIX separators so downstream split("/") helpers work on Windows (Copilot) - generate-schemas.js: return consistent {output,...} shape from generateMainSection's !mainDef early-return branch (Copilot); render rpc-permission fields (lxm/aud/inheritAud) in generatePermissionSetSection so rpc permissions aren't reduced to a bare "Resource: rpc" (CodeRabbit) - permission-sets.md: prefix blockquote separator with > to fix MD028 (CodeRabbit) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

aspiers · 2026-07-11T19:42:10Z

(comment generated by Claude Code)

Correction to my earlier comment (above): I wrongly called this nitpick "stale." I searched a stale local checkout that was behind this PR's HEAD and lacked commit cd08e55, so I did not see generatePermissionSetSection. It does exist and the nitpick is valid.

Fixed in 733f555. generatePermissionSetSection now renders rpc-permission fields (**LXM:** / **Audience:** / **Inherit audience:**) alongside the existing repo collection/action rendering, so an rpc permission no longer collapses to a bare **Resource:** +""+rpc+""+`. No change to current SCHEMAS.md output — all three published sets are repo-only — but future rpc permissions now render completely.

Copilot

Pull request overview

Copilot reviewed 12 out of 12 changed files in this pull request and generated no new comments.

aspiers · 2026-07-22T15:16:11Z

This is already published and working - thought we'd already merged this -> merging.

Copilot AI review requested due to automatic review settings June 9, 2026 13:22

Copilot started reviewing on behalf of aspiers June 9, 2026 13:23 View session

Copilot AI reviewed Jun 9, 2026

View reviewed changes

Comment thread docs/design/permission-sets.md Outdated

Comment thread docs/design/permission-sets.md

Comment thread docs/design/permission-sets.md Outdated

Comment thread docs/design/permission-sets.md Outdated

Comment thread docs/design/permission-sets.md Outdated

aspiers changed the title ~~docs(design): permission-sets for Hypercerts & Certified data~~ feat: permission sets for Hypercerts & Certified data Jun 9, 2026

Copilot AI review requested due to automatic review settings June 9, 2026 13:36

aspiers force-pushed the feature/permission-sets-design branch from 5462c64 to 89f2e68 Compare June 9, 2026 13:36

Copilot started reviewing on behalf of aspiers June 9, 2026 13:36 View session

aspiers force-pushed the feature/permission-sets-design branch from 89f2e68 to d92f323 Compare June 9, 2026 13:38

Copilot AI reviewed Jun 9, 2026

View reviewed changes

Comment thread lexicons/app/certified/authWrite.json

Comment thread docs/design/permission-sets.md

Copilot AI review requested due to automatic review settings June 9, 2026 13:41

aspiers force-pushed the feature/permission-sets-design branch 2 times, most recently from dd5967d to 46843a8 Compare June 9, 2026 13:46

Copilot AI reviewed Jun 9, 2026

View reviewed changes

Comment thread package.json Outdated

Comment thread scripts/generate-exports.js Outdated

Comment thread scripts/generate-exports.js Outdated

Comment thread package.json Outdated

Comment thread docs/design/permission-sets.md Outdated

Copilot AI review requested due to automatic review settings June 9, 2026 13:49

aspiers force-pushed the feature/permission-sets-design branch from 46843a8 to 6ebc898 Compare June 9, 2026 13:49

Copilot started reviewing on behalf of aspiers June 9, 2026 13:49 View session

Copilot started reviewing on behalf of aspiers June 9, 2026 13:52 View session

aspiers force-pushed the feature/permission-sets-design branch from 6ebc898 to 0a9d0e9 Compare June 9, 2026 13:54

Copilot AI reviewed Jun 9, 2026

View reviewed changes

Comment thread lexicons/app/certified/authWrite.json

Comment thread docs/design/permission-sets.md Outdated

Comment thread docs/design/permission-sets.md

Comment thread docs/design/permission-sets.md

Comment thread docs/design/permission-sets.md

Copilot AI review requested due to automatic review settings June 9, 2026 13:57

aspiers force-pushed the feature/permission-sets-design branch from 0a9d0e9 to 7b80639 Compare June 9, 2026 13:57

Copilot started reviewing on behalf of aspiers June 9, 2026 13:57 View session

Copilot AI reviewed Jun 9, 2026

View reviewed changes

Comment thread lexicons/app/certified/authWrite.json

Comment thread docs/design/permission-sets.md

aspiers mentioned this pull request Jun 9, 2026

[HYPER-181] add cryptographic signature support to record lexicons (resubmission of #170) #219

Merged

5 tasks

aspiers requested review from Kzoeps, bitbeckers, holkexyz and s-adamantine June 9, 2026 14:22

aspiers and others added 11 commits July 6, 2026 15:19

docs: fix stale script-name reference (codegen-lexicon-files → run-le…

9ad6b00

…x-codegen) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot AI review requested due to automatic review settings July 6, 2026 14:19

aspiers force-pushed the feature/permission-sets-design branch from 0e0c2a6 to 83596a9 Compare July 6, 2026 14:19

Copilot started reviewing on behalf of aspiers July 6, 2026 14:21 View session

Copilot AI reviewed Jul 6, 2026

View reviewed changes

Comment thread scripts/generate-schemas.js Outdated

Comment thread scripts/generate-exports.js

Ashex approved these changes Jul 7, 2026

View reviewed changes

aspiers force-pushed the feature/permission-sets-design branch from 83596a9 to cd08e55 Compare July 7, 2026 14:30

coderabbitai Bot reviewed Jul 7, 2026

View reviewed changes

Comment thread docs/design/permission-sets.md

Ashex mentioned this pull request Jul 7, 2026

Replace transition:generic with permission sets scopes hypercerts-org/ePDS#188

Merged

Copilot AI review requested due to automatic review settings July 11, 2026 19:41

Copilot started reviewing on behalf of aspiers July 11, 2026 19:42 View session

Copilot AI reviewed Jul 11, 2026

View reviewed changes

aspiers merged commit 456c55c into main Jul 22, 2026
7 checks passed

aspiers deleted the feature/permission-sets-design branch July 22, 2026 15:16

Uh oh!

Conversation

aspiers commented Jun 9, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

One set per namespace, by spec mandate

NSID shape (single segment under the namespace root)

Contents

Design rules followed (spec-cited in the doc)

Tooling note

Rebased onto #219

Notes

Summary by CodeRabbit

Uh oh!

changeset-bot Bot commented Jun 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🦋 Changeset detected

Uh oh!

coderabbitai Bot commented Jun 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviews paused

Walkthrough

Changes

❌ Failed checks (1 warning)

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

Ashex left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

aspiers commented Jul 11, 2026

Uh oh!

aspiers commented Jul 11, 2026

aspiers commented Jun 9, 2026 •

edited by coderabbitai Bot

Loading

changeset-bot Bot commented Jun 9, 2026 •

edited

Loading

coderabbitai Bot commented Jun 9, 2026 •

edited

Loading