@vectros-ai/blueprints 0.6.2 → 0.6.3

package/CHANGELOG.md

@@ -3,6 +3,22 @@
 All notable changes to `@vectros-ai/blueprints` are documented here.
 This project adheres to [Semantic Versioning](https://semver.org).
 
+## 0.6.3 — 2026-07-01
+
+### Added
+
+- **`agentic-sdlc` now declares an `editor` role for the human owner.** `bootstrap`
+  provisions a scoped key for your *agent*, but doesn't join *you* — so a blueprint's
+  context doesn't appear in the data-plane app until your own user is granted access
+  there. The blueprint now ships a reusable `editor` role at **parity with the service
+  key** (`records:r/c/u`, `search:r`, `schemas:r`, `inference:r`, `documents:r/c`,
+  `folders:r/c`; no delete, no control-plane), which `bootstrap` creates in the context.
+  Bind it to your user once to browse and curate the KB in the app:
+  `vectros access grant --principal usr_<your-user-id> --context agentic-sdlc --role editor`
+  (or via the admin app's Access → Contexts → Profiles). The guide and walkthrough
+  document the one-time join, and the package README now documents the top-level
+  `roles` format field (previously undocumented — no bundled blueprint used it).
+
 ## 0.6.2 — 2026-06-29
 
 ### Changed

package/README.md

@@ -115,6 +115,16 @@ The `accessProfile.dataScope` value lists accept a **`null` sentinel** — e.g.
 (owner-less / shared) records. Omitting `null` restricts the key to the listed
 owners only.
 
+A blueprint may also declare top-level **`roles`** — a map of `roleId` → ordered
+scope clauses (each an `allowedActions` list with an optional `dataScope`). Unlike
+`accessProfile` (which scopes the service-principal key `bootstrap` mints), roles
+are reusable, identity-agnostic rules you bind to a principal *after* bootstrap with
+`vectros access grant --principal <p> --role <roleId>`. `bootstrap` provisions the
+declared roles in the context but binds them to no one. The bundled `agentic-sdlc`
+ships an `editor` role for this — join your own user to the context so you can
+browse and curate the knowledge base in the app. Role clauses pass the same
+data-plane scope gate as `accessProfile`.
+
 All of the above are **optional and backward-compatible** — a blueprint that
 omits them parses and provisions exactly as before.
 

package/dist/index.js

@@ -1065,6 +1065,18 @@ var codingAgentMemory = {
 var coding_agent_memory_default = codingAgentMemory;
 
 // src/blueprints/agentic-sdlc.ts
+var DATA_PLANE_ACTIONS = [
+  "records:r",
+  "records:c",
+  "records:u",
+  "search:r",
+  "schemas:r",
+  "inference:r",
+  "documents:r",
+  "documents:c",
+  "folders:r",
+  "folders:c"
+];
 var agenticSdlc = {
   name: "agentic-sdlc",
   version: "1.0.0",
@@ -1718,23 +1730,25 @@ var agenticSdlc = {
       ]
     }
   ],
-  // Least-privilege, data-plane only. r/c/u records + search + schema discovery +
-  // inference:r (grounded recall over the document bodies) + document/folder r/c
-  // (the content artifacts are documents). NO :d — knowledge is superseded/retired
-  // via a status flip, so the trail of how the team's thinking evolved stays intact.
+  // Least-privilege, data-plane only. The scope of the `ssk_*` key the bootstrap
+  // mints for THIS blueprint's service principal (the MCP/API runtime). See
+  // DATA_PLANE_ACTIONS above for the action set + rationale.
   accessProfile: {
-    allowedActions: [
-      "records:r",
-      "records:c",
-      "records:u",
-      "search:r",
-      "schemas:r",
-      "inference:r",
-      "documents:r",
-      "documents:c",
-      "folders:r",
-      "folders:c"
-    ]
+    allowedActions: DATA_PLANE_ACTIONS
+  },
+  // A reusable `editor` role for the HUMAN owner — DISTINCT from `accessProfile`
+  // (which scopes only the service-principal key). `bootstrap` provisions this
+  // role in the context but binds it to no one; the owner joins themselves so the
+  // data-plane app (app.vectros.ai) shows their KB — its switcher lists only
+  // contexts the signed-in user holds an active access profile in, and bootstrap
+  // grants the human none by default. Bind it after bootstrap with:
+  //   vectros access grant --principal usr_<your-user-id> --context agentic-sdlc --role editor
+  // (or the admin app's Access > Contexts > agentic-sdlc > Profiles > Create).
+  // Editor PARITY with the service key (same DATA_PLANE_ACTIONS) so a human
+  // curator can browse AND write/correct the KB; still no :d and no control-plane
+  // action, so the scope gate accepts it exactly like the accessProfile.
+  roles: {
+    editor: [{ allowedActions: DATA_PLANE_ACTIONS }]
   },
   servicePrincipal: {
     externalId: "agentic-sdlc",