@vectros-ai/blueprints 0.6.2 → 0.6.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -32,6 +32,9 @@ populated, queryable KB, and to wiring an agent to use it day-to-day.
32
32
  - **A least-privilege key** — `records:r/c/u`, `search:r`, `schemas:r`,
33
33
  `inference:r`, `documents:r/c`, `folders:r/c`. No delete: knowledge is
34
34
  superseded/retired via a status flip, so the audit trail stays intact.
35
+ - **An `editor` role for you, the human** — the same data-plane scope as the key,
36
+ ready to bind to your user so you can browse and curate the KB in the app (see
37
+ "Browse it as yourself" below).
35
38
  - **Range/sort on every artifact's date**, a governance `control` that records its
36
39
  own evidence, a `convention` with distinct rule/why/howToApply fields, and a
37
40
  glossary `term` with a `unique` exact-lookup.
@@ -71,6 +74,31 @@ it. (Prefer not to install globally? Prefix each command with `npx -y`, e.g.
71
74
  Add `--tenant test` to provision into the **test tenant** first (useful for a
72
75
  dry-run before committing to your live tenant). Omit for live (the default).
73
76
 
77
+ ### Browse it as yourself — grant your user access
78
+
79
+ `bootstrap` provisions the context and a scoped key for your **agent** (the MCP
80
+ server), but it does **not** join **you** — the signed-in human — to the new
81
+ context. So when you open the data-plane app the context switcher won't list it
82
+ yet: the app shows only contexts your user holds access in, and bootstrap grants
83
+ your user none by default. Do this once so you can browse and curate the KB
84
+ yourself. `bootstrap` already provisioned an **`editor`** role in the context
85
+ (read + write, no delete — the same data-plane scope as the agent's key); bind it
86
+ to your user two ways:
87
+
88
+ - **In the admin app (easiest):** go to **Access → Contexts → `agentic-sdlc` →
89
+ Profiles → Create profile**, pick **yourself** (users list by email), choose the
90
+ **`editor`** role, and save.
91
+ - **From the CLI:** `--principal me` resolves to your own user, so no id lookup is
92
+ needed:
93
+
94
+ ```bash
95
+ vectros access grant --principal me --context agentic-sdlc --role editor
96
+ ```
97
+
98
+ (Prefer an explicit id? `vectros identity list --type user` lists every tenant
99
+ user's id + email; your principal is `usr_` + the id next to your email.) Reopen
100
+ the data-plane app and `agentic-sdlc` now appears in the switcher with your data.
101
+
74
102
  ### Seeds
75
103
 
76
104
  This blueprint ships **without bundled seeds** — it provisions the nine schemas +
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@vectros-ai/blueprints",
3
- "version": "0.6.2",
3
+ "version": "0.6.3",
4
4
  "description": "Curated Vectros use-case blueprints (schemas + least-privilege AccessProfile + seed) and the Blueprint format + structural validation. Enforcement (the scope gate) lives in @vectros-ai/cli, not here.",
5
5
  "license": "Apache-2.0",
6
6
  "repository": {