Skip to content

OperationalPreferences: add the Vocabulary section Shape.ts cites, and define e - #2738

Closed
rathko wants to merge 1 commit into
danielmiessler:mainfrom
rathko:e-shortcut-vocabulary
Closed

rathko wants to merge 1 commit into
danielmiessler:mainfrom
rathko:e-shortcut-vocabulary

Conversation

@rathko

@rathko rathko commented Nov 10, 2026

Copy link
Copy Markdown

LIFEOS/ROUTER/Shape.ts recognizes bare shortcuts (s, c, y, e, v, u, uc, f) and cites "OPERATIONAL_PREFERENCES § Vocabulary" for their meaning. The shipped template has no such section, so on a fresh install a bare e has no definition. The only public trace is one line in the Explain skill: "explains my last answer more, and more simply".

This PR adds the missing section and defines e as a re-explain in the sentence rules of ASD-STE100 (Simplified Technical English), without its dictionary. The HTML-plan renderer already lints against the same standard. The section keeps a placeholder for the other shortcuts.

Evidence from a three-week local trial: the principal asked for STE explanations about 25 times on 15 separate days, and stopped asking for "explain like I am 12". In a blind, length-matched comparison, the plain version was easier to follow in 67% of cases (95% CI 58 to 75%), with 3.3 points lower fact recall. The lost facts were minor caveats, which is why the definition says to keep the same length and every caveat.

One file, 7 lines, no code changes.

…d define e as a plain-language re-explain using ASD-STE100 sentence rules
@danielmiessler

Copy link
Copy Markdown
Owner

Note

🤖 Kai (AI assistant) responding on behalf of Daniel Miessler

Thanks @rathko, you're right that a fresh install recognizes a bare e and then has nothing that says what it means. The missing section already exists in the next release: the Preferences template (renamed from OPERATIONAL_PREFERENCES) now carries a ## Vocabulary section. We're not taking the STE definition, though. e already has a written definition in commands/e.md that goes the other way (shorter, sectioned, Paul Graham-plain rather than length-preserving), and the open question on our side is shipping that command publicly, not adding a second definition in the template.

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