@panaversity/ksor 0.0.52 → 0.0.53

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.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,18 @@
1
1
  # @panaversity/ksor
2
2
 
3
+ ## 0.0.53
4
+
5
+ ### Patch Changes
6
+
7
+ - f77ca55: The emitted README documents `.ksor/people.yaml`.
8
+
9
+ Display names shipped documented in the scaffold's AGENTS.md and not in its
10
+ README — so the coding agent knew about the feature and the owner did not, on
11
+ the one feature whose entire input is a human typing their colleagues' names.
12
+ The README now carries it beside the keys that publish a document: the map
13
+ shape, that an actor with no entry renders exactly as stored, and that
14
+ appearing in the file grants no authority at all.
15
+
3
16
  ## 0.0.52
4
17
 
5
18
  ### Patch Changes
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@panaversity/ksor",
3
- "version": "0.0.52",
3
+ "version": "0.0.53",
4
4
  "description": "Knowledge System of Record — compile governed markdown into a static site for people and an MCP server for AI agents, with citations and measured abstention.",
5
5
  "keywords": [
6
6
  "abstention",
@@ -72,8 +72,8 @@
72
72
  "tsdown": "0.22.14",
73
73
  "typescript": "7.0.2",
74
74
  "vitest": "^4.1.10",
75
- "@panaversity/ksor-content-gateway": "0.0.0",
76
- "@panaversity/ksor-content": "0.0.0"
75
+ "@panaversity/ksor-content": "0.0.0",
76
+ "@panaversity/ksor-content-gateway": "0.0.0"
77
77
  },
78
78
  "engines": {
79
79
  "node": ">=24"
@@ -372,6 +372,29 @@ approved has to be the text that was written. That act is yours.
372
372
  Run `pnpm check` before you commit. It runs the rules as a program, and every
373
373
  failure it reports says what is wrong, why the rule exists, and how to fix it.
374
374
 
375
+ ### Names instead of handles
376
+
377
+ The record stores actors as identifiers — `human:you`, `team:legal-ops` — and a
378
+ page would otherwise lead with the slug: "Owner · human:bashiraziz". Put the
379
+ name beside the identifier in `.ksor/people.yaml` and pages print that instead:
380
+
381
+ ```yaml
382
+ people:
383
+ "human:bashiraziz": Bashir Aziz
384
+ "human:ciso": Ayesha Khan
385
+ ```
386
+
387
+ Keyed by the identifier exactly as the record stores it, quoted because it
388
+ contains a colon. There is no rule that turns a name into a handle — `ciso` is
389
+ nobody's squashed full name — so both are written down, and an actor with no
390
+ entry renders exactly as stored rather than being guessed at.
391
+
392
+ **This is presentation, and nothing else.** It grants no authority: who may
393
+ approve or withdraw is `.ksor/governance.yaml`, and the two files are not
394
+ checked against each other, because someone who leaves the authority list is
395
+ still the recorded approver of everything they approved. Optional — a record
396
+ that declares no names reads exactly as it did before.
397
+
375
398
  ### Presenting a document
376
399
 
377
400
  Ask your coding agent for slides and it writes them, from the document, into the