@panaversity/ksor 0.0.46 → 0.0.48

package/CHANGELOG.md

@@ -1,5 +1,34 @@
 # @panaversity/ksor
 
+## 0.0.48
+
+### Patch Changes
+
+- 4883d2c: A document page gives its text 16px more room: the horizontal padding drops
+  from 32px to 24px. The reading measure itself is unchanged — widening it was
+  tried and reverted, because measuring what the column already is showed it is
+  wider than the comment beside it claimed, not narrower.
+
+## 0.0.47
+
+### Patch Changes
+
+- 00c99da: **The intake interview asks its three questions in the owner's words.** The
+  previous wording was precise and unanswerable: question 1 asked the owner to
+  finish "when someone here disagrees with this corpus, the corpus wins about
+  ___", which is not a sentence unless you already know the ledger analogy the
+  README uses, and then explained what the answer would be used for inside the
+  question itself. An owner reported being unable to tell what it wanted at all.
+
+  Now: "What is this knowledge base about?", "What is close to that, but not part
+  of it?", and "Who signs off on a document, and who can take one down?" — each
+  with one too-vague example and one specific enough, and nothing about
+  `instance.md` or the MCP surface in the question. The reasoning that used to sit
+  inside the questions moved below them, where it explains the design to whoever
+  maintains the skill instead of blocking the person answering.
+
+  Nothing about what gets written changed.
+
 ## 0.0.46
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@panaversity/ksor",
-  "version": "0.0.46",
+  "version": "0.0.48",
   "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.",
   "keywords": [
     "abstention",

package/templates/scaffold/.agents/skills/intake-interview/SKILL.md

@@ -14,32 +14,55 @@ question at a time, and write down what they actually say.
 
 ## Ask THREE questions, one at a time
 
-Seven questions is where this skill used to start, and it did not survive
-contact: an agent running it decided five were too many, defaulted them, and
-reported "answered: all seven" — including the one that decides who may
-approve a document. A process the tool executing it shortcuts is too long.
-
-So three are asked, and they are the three that cannot be defaulted:
-
-1. **Scope** — "What should this record be the _final word_ on? Finish the
-   sentence: when someone here disagrees with this corpus, the corpus wins
-   about ___."
-2. **Boundary** — "What is just _outside_ that — the near-miss topics people
-   will ask about here that the record should refuse rather than guess at?"
-3. **Authority** — "Who may approve a document for publication, and who may
-   withdraw one?"
-
-Scope and Boundary are asked because the abstention gate is meaningless
-without an edge: a record authoritative for everything has no outside, so an
-agent asked something the owner never wrote about reaches for its training
-instead of declining. Authority is asked because a governance act names its
-actor and the tool never guesses one — the scaffold ships `human:you` in
-both authority lists, and a placeholder that survives this conversation is a
-person who was never there.
-
-Follow up until each is concrete. "Our engineering docs" is not yet an
-answer; "our leave, expense and conduct policies — the current ones, not
-historical versions" is.
+Ask them in the OWNER's words, not this project's. The vocabulary on this page
+— record, corpus, abstention, governance act — is precise and it is ours; an
+owner meeting it for the first time in a question cannot answer, and says so
+(reported 2026-08-26, against the wording these replaced: "the corpus wins
+about ___" asked them to complete a sentence that is not English unless you
+already know the ledger analogy).
+
+Ask exactly this much. Do not explain what the answer will be used for inside
+the question — that is what made the last version unanswerable.
+
+---
+
+**1 of 3 — What is this knowledge base about?**
+
+> Be specific enough that I would know what does NOT belong in it.
+>
+> Too vague: "our engineering docs" — I still could not tell what to leave out.
+> Specific enough: "our leave, expense and conduct policies, current versions
+> only."
+
+---
+
+**2 of 3 — What is close to that, but not part of it?**
+
+> Things people will ask this and it should NOT answer. A confident wrong
+> answer is worse than "I do not cover that."
+>
+> For the policies example: "not salaries, not individual HR cases, not last
+> year's versions."
+
+---
+
+**3 of 3 — Who signs off on a document, and who can take one down?**
+
+> Names or handles, not job titles. If it is just you, say so.
+
+---
+
+Follow up until each is concrete, but follow up in their words too: "what would
+someone actually ask this?" gets further than "name the boundary".
+
+**Why these three and no others.** The first two give the record an EDGE, and
+the abstention gate is meaningless without one: a knowledge base that is
+authoritative for everything has no outside, so an agent asked something the
+owner never wrote about reaches for its training instead of declining. The
+third cannot be guessed at all — the scaffold ships `human:you` in both
+authority lists, and a placeholder that survives this conversation is a person
+who was never there. Everything else has a sane default, and defaults are
+stated rather than asked.
 
 ## Then STATE the defaults; do not ask them
 

package/templates/scaffold/.claude/skills/intake-interview/SKILL.md

@@ -14,32 +14,55 @@ question at a time, and write down what they actually say.
 
 ## Ask THREE questions, one at a time
 
-Seven questions is where this skill used to start, and it did not survive
-contact: an agent running it decided five were too many, defaulted them, and
-reported "answered: all seven" — including the one that decides who may
-approve a document. A process the tool executing it shortcuts is too long.
-
-So three are asked, and they are the three that cannot be defaulted:
-
-1. **Scope** — "What should this record be the _final word_ on? Finish the
-   sentence: when someone here disagrees with this corpus, the corpus wins
-   about ___."
-2. **Boundary** — "What is just _outside_ that — the near-miss topics people
-   will ask about here that the record should refuse rather than guess at?"
-3. **Authority** — "Who may approve a document for publication, and who may
-   withdraw one?"
-
-Scope and Boundary are asked because the abstention gate is meaningless
-without an edge: a record authoritative for everything has no outside, so an
-agent asked something the owner never wrote about reaches for its training
-instead of declining. Authority is asked because a governance act names its
-actor and the tool never guesses one — the scaffold ships `human:you` in
-both authority lists, and a placeholder that survives this conversation is a
-person who was never there.
-
-Follow up until each is concrete. "Our engineering docs" is not yet an
-answer; "our leave, expense and conduct policies — the current ones, not
-historical versions" is.
+Ask them in the OWNER's words, not this project's. The vocabulary on this page
+— record, corpus, abstention, governance act — is precise and it is ours; an
+owner meeting it for the first time in a question cannot answer, and says so
+(reported 2026-08-26, against the wording these replaced: "the corpus wins
+about ___" asked them to complete a sentence that is not English unless you
+already know the ledger analogy).
+
+Ask exactly this much. Do not explain what the answer will be used for inside
+the question — that is what made the last version unanswerable.
+
+---
+
+**1 of 3 — What is this knowledge base about?**
+
+> Be specific enough that I would know what does NOT belong in it.
+>
+> Too vague: "our engineering docs" — I still could not tell what to leave out.
+> Specific enough: "our leave, expense and conduct policies, current versions
+> only."
+
+---
+
+**2 of 3 — What is close to that, but not part of it?**
+
+> Things people will ask this and it should NOT answer. A confident wrong
+> answer is worse than "I do not cover that."
+>
+> For the policies example: "not salaries, not individual HR cases, not last
+> year's versions."
+
+---
+
+**3 of 3 — Who signs off on a document, and who can take one down?**
+
+> Names or handles, not job titles. If it is just you, say so.
+
+---
+
+Follow up until each is concrete, but follow up in their words too: "what would
+someone actually ask this?" gets further than "name the boundary".
+
+**Why these three and no others.** The first two give the record an EDGE, and
+the abstention gate is meaningless without one: a knowledge base that is
+authoritative for everything has no outside, so an agent asked something the
+owner never wrote about reaches for its training instead of declining. The
+third cannot be guessed at all — the scaffold ships `human:you` in both
+authority lists, and a placeholder that survives this conversation is a person
+who was never there. Everything else has a sane default, and defaults are
+stated rather than asked.
 
 ## Then STATE the defaults; do not ask them
 

package/templates/scaffold/system/site/app/global.css

@@ -228,20 +228,37 @@
 }
 
 /* ── The reading measure ─────────────────────────────────────────────────────
-   The shell caps the article at 900px, which at the body's 16px puts 78
-   characters on a line (measured) — half again the 45–75 that reading research
-   and every typographic manual settle on, and the reason the page read as a
-   slab. 46rem holds the text to 672px, about 66 characters, and the article
-   still centres itself in the main column.
+   The shell caps the article at 900px, which puts far more than the 45–75 that
+   reading research and every typographic manual settle on a line, and is the
+   reason the page read as a slab. 46rem holds the text to 688px and the
+   article still centres itself in the main column. (The character counts this
+   paragraph used to give were wrong in both directions — see below.)
 
    It is also half of what stops the column moving: the other half is holding
    the table-of-contents column on every page (app/docs/[[...slug]]/page.tsx).
    Sidebar and rail are both 268px, so main is centred in the viewport and this
    measure is centred in main — the same place on a document with headings and
    one without. `data-full` is the shell's own escape hatch for a page that
-   asked for the whole width; it keeps it. */
+   asked for the whole width; it keeps it.
+
+   The measure STAYS at 46rem, and the number above is corrected here rather
+   than trusted: asked for a wider column, the honest thing was to measure what
+   this one already is. Simulating the browser's own line-breaking over this
+   record's prose in its real font gives 89 characters at 46rem — not 66 — and
+   the shell's 900px gives 122, not 78. Both figures in the paragraph above
+   were wrong; the CONCLUSION they supported was right, and by a wider margin
+   than it claimed.
+
+   So widening was tried and reverted: 49rem counts 95 and 52rem counts 104,
+   each further from the 45–75 the research settles on, not closer. What is
+   left is a real gain that costs nothing — the horizontal padding drops from
+   32px to 24px, which gives the text 16px more without touching the measure.
+
+   The white space either side of a bounded column on a 1728px screen is the
+   price of the column being bounded. It is not a bug to be tuned away. */
 #nd-page:not([data-full="true"]) {
   max-width: 46rem;
+  padding-inline: 1.5rem;
 }
 
 html {