premise: the task is an instruction (decision 010) - #6
Merged
Conversation
`etymd premise "<task>"` checks every path, script, well-known doc and decision id a task names against the repo, with the same precision rules instruction files get, and writes a brief handing the agent the premises only it can verify. A missing thing the task is about ranks as risk. `--file`, `--json` (schema premise/1), `--no-brief`, `--fail-on`. Zero trace without `.etymd/`; no ledger. The command/path/doc-reference truth checks move into one shared implementation (`checks.ts`) used by instruction-truth and premise alike — ids, tiers and disclosures of existing findings are unchanged. The objective widens by one notch, everywhere it is stated: an instruction is anything told to an agent, in a file or in the prompt. Decision record: docs/decisions/010.
Promoting bare tokens with the code-span filters as-is accuses ordinary prose: a package manager named before any noun, a slash-joined phrase with a trailing slash, a URL with its scheme dropped — each a RISK, each false. Prose is now stricter than a code span: a script needs the `run` form (or the `npm test` / `npm start` shorthands), a directory claim needs a first segment that exists, a host-shaped first segment is a URL. Every class left as prose is counted and disclosed. The `D-NNN` reference check moves into the shared checks (it existed in two copies), and every check returns what it examined beside what it flagged, so premise never re-runs the extractors. The brief heading stays on one line for multi-line tasks, `~/` doc mentions are disclosed, `--file -` reads stdin, and the command layer is tested.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
etymd premise "<task>". The task you hand an agent is an instruction too. Whatever it names (paths, scripts, well-known docs,D-NNNids) gets checked against the repo with the shared truth checks. A missing thing the task is about ranks as risk. A brief hands the agent the premises only it can verify. Flags:--file(-reads stdin),--json(schemapremise/1),--no-brief,--fail-on <tier>. Zero trace without.etymd/, no ledger.What ships
etymd premise. Decision 010 widens the objective one notch: an instruction is anything we tell an agent, in a file or in the promptD-NNNreference truth checks are now one shared implementation (checks.ts), used byinstruction-truthandpremisealike. Existing ids, tiers and disclosures don't changeOne changeset, 0.15.0. No pack change.
Second commit, review fixes
Promoting bare prose tokens with the code-span filters as-is accused ordinary prose: a package manager before any noun, a slash-joined phrase with a trailing slash, a scheme-less URL, each a RISK, each false. Prose is stricter than a code span now, and every class we leave as prose is disclosed. Also, the
D-NNNcheck existed in two copies, now shared. The brief heading stays on one line for multi-line tasks,~/doc mentions are disclosed,--file -reads stdin, and the command layer is tested.Gates: format, typecheck, tests, build, self-audit, content screen. All green.