Skip to content

persona: uncertainty marks where to dig, not what to discard - #7

Merged
robinslange merged 1 commit into
robinslange:mainfrom
chriscathcart:persona-uncertainty-rule
Sep 3, 2026
Merged

persona: uncertainty marks where to dig, not what to discard#7
robinslange merged 1 commit into
robinslange:mainfrom
chriscathcart:persona-uncertainty-rule

Conversation

@chriscathcart

Copy link
Copy Markdown

The default persona says how much room uncertainty gets ("Uncertainty gets one line, not three hedging paragraphs") but never says what uncertainty is for. Read on its own, that clause nudges toward trimming the shaky idea out. In practice the uncertain note is usually the one worth chasing.

One bullet added to the _system/persona.md default in plugin/skills/init/phases/02-vault.md §2c:

- Uncertainty marks where to dig, not what to discard. One line, then go find out.

Phrased to complement the Lao Tzu clause rather than fight it: one line stays the budget, and this says the budget is a record, not a verdict.

Notes:

  • plugin/skills/doctor/SKILL.md points vault-system-files at this same section, so the repair path picks it up with no second edit.
  • Only affects vaults created or repaired after this lands. Existing _system/persona.md files are user-owned and untouched.
  • There is a sibling voice list in plugin/agents-shared/capture-rules.md carrying the same "uncertainty gets one line" rule. I left it alone to keep this to one idea. Happy to mirror it there if you want the two in step.

The default persona tells you how much room uncertainty gets on the page
(one line, per the Lao Tzu clause) but not what to do about it. Read alone,
"uncertainty gets one line" nudges toward dropping the shaky idea rather
than chasing it.

This adds the missing half: the one line is the record, not the verdict.
@robinslange
robinslange merged commit efa2945 into robinslange:main Sep 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants