@erclx/aitk 1.1.0 → 1.2.0

package/governance/rules/claude/560-diagrams.md

@@ -9,7 +9,7 @@ paths:
 
 ## Authority
 
-- Follow `.claude/standards/diagrams.md` for Mermaid diagram layout, budgets, accessibility, verification, and explanation prose. It is the single source.
+- Follow the diagrams standard for Mermaid diagram layout, budgets, accessibility, verification, and explanation prose. It is the single source. Read it with `aitk standards diagrams`.
 - A diagram entry carries structure and flow, not implementation. Read the standard before adding or revising a kind.
 
 ## Scope

package/governance/rules/claude/561-teach.md

@@ -16,6 +16,6 @@ paths:
 
 ## Authority
 
-- Follow `.claude/standards/teach.md` for the folder layout, ordinal naming, frontmatter, and the mission and learning-record formats. It is the single source.
+- Follow the teach standard for the folder layout, ordinal naming, frontmatter, and the mission and learning-record formats. It is the single source. Read it with `aitk standards teach`.
 - Read `references/glossary.md` inside the `claude-teach` skill for the glossary every workspace carries at its root. It is the single source for the entry shape, the ordering, and which terms the file carries. Read it rather than invoking the skill, which resumes a workspace and runs lessons.
 - Report it rather than proceeding silently when that file does not resolve. It ships with the plugin and this rule ships with the CLI, so a project that installed governance alone does not have it.

package/governance/rules/claude/562-session.md

@@ -16,4 +16,4 @@ paths:
 
 ## Authority
 
-- Follow `.claude/standards/session.md` for the filename and location, frontmatter, the core sections, and the write and read procedures. It is the single source.
+- Follow the session standard for the filename and location, frontmatter, the core sections, and the write and read procedures. It is the single source. Read it with `aitk standards session`.

package/governance/rules/claude/570-skill.md

@@ -20,4 +20,4 @@ paths:
 
 ## Authority
 
-- Follow `.claude/standards/skill.md` for skill structure, frontmatter fields, invocation rules, and the shape a `REQUIREMENT.md` states. It is the single source.
+- Follow the skill standard for skill structure, frontmatter fields, invocation rules, and the shape a `REQUIREMENT.md` states. It is the single source. Read it with `aitk standards skill`.

package/governance/rules/claude/580-readme.md

@@ -16,4 +16,4 @@ paths:
 
 ## Authority
 
-- Follow `.claude/standards/readme.md` for voice, structure, required and optional sections, heading hierarchy, badge classes, per-project-type content, and what to link out rather than inline. It is the single source.
+- Follow the readme standard for voice, structure, required and optional sections, heading hierarchy, badge classes, per-project-type content, and what to link out rather than inline. It is the single source. Read it with `aitk standards readme`.

package/governance/rules/claude/590-rule-authoring.md

@@ -19,5 +19,5 @@ paths:
 
 ## Authority
 
-- Follow `.claude/standards/rule.md` for rule frontmatter, body shape, and voice. It is the single source.
+- Follow the rule-authoring standard for rule frontmatter, body shape, and voice. It is the single source. Read it with `aitk standards rule`.
 - Read it before writing or editing a rule. Do not work the shape from memory.

package/governance/rules/claude/591-standard-authoring.md

@@ -17,5 +17,5 @@ paths:
 
 ## Authority
 
-- Follow `.claude/standards/standard.md` for a standard's frontmatter, shape, scope, and success criterion. It is the single source.
+- Follow the standard-authoring standard for a standard's frontmatter, shape, scope, and success criterion. It is the single source. Read it with `aitk standards standard`.
 - Read it before writing or editing a standard. Do not work the shape from memory.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@erclx/aitk",
   "type": "module",
-  "version": "1.1.0",
+  "version": "1.2.0",
   "description": "Infrastructure and quality tooling for developer workflows",
   "license": "MIT",
   "bin": {

package/src/markdown/structure.ts

@@ -536,10 +536,45 @@ function measureParagraph(block: readonly BodyLine[]): CadenceFinding {
  * absence of something, so no addition to that set catches a paragraph whose
  * sentences are all one length. The measure stops at what is countable. A
  * sentence's grammatical shape and whether it carries a finite verb are the two
- * rules `write-human` states that this does not implement, because identifying
- * either needs a parse rather than a match, and an imperative or a heading
- * fragment would read as a defect. Reporting them wrong is worse than not
- * reporting them, since they name the exact failure this exists to measure.
+ * rules `write-human` states that this does not implement. Reporting them wrong
+ * is worse than not reporting them, since they name the exact failure this
+ * exists to measure.
+ *
+ * That was a prediction and it has now been measured, against two parsers
+ * rather than against the idea of one. Both ran over 11,389 paragraph sentences
+ * across 503 markdown files at `c7e92612` on 2026-08-20, and they disagree by
+ * a factor of four on a number one of them has to be wrong about.
+ *
+ * `compromise` reported 2 percent. It tags a fronted past participle as a
+ * finite past-tense verb, so all twelve of those sentences in
+ * `.claude/ARCHITECTURE.md` read as carrying one, eleven opening `Measured at`
+ * and one `Overturned by`, which is the exact shape the measure exists to
+ * catch. It is not even consistent with itself there: `Measured at` tags a verb
+ * and `Measured against` tags an adjective.
+ *
+ * `wink-pos-tagger` reported 9 percent and fixes that class, tagging the
+ * participle `VBN`. Roughly three quarters of what it flags is still wrong:
+ * hand-classifying every 21st of the 1,071 flagged sentences put 12 of 51
+ * genuinely verbless. Two classes split the other 39 almost evenly and neither
+ * is a tuning problem. Nineteen are imperatives, which this instructional
+ * corpus is full of and whose verb tags as a proper noun as often as a verb.
+ * Twenty are ordinary declaratives whose predicate is noun-ambiguous and tags
+ * as a noun outright, so `Each maps to a skill.` and `Nothing checks either
+ * one.` both report verbless. This corpus is built from exactly those words:
+ * reports, answers, checks, maps, holds, names, carries, records, measures.
+ *
+ * Separating them needs to know which token is the predicate, which is syntax
+ * rather than a tag. Neither tagger carries one and nothing was found worth
+ * taking for a number nothing gates on, so the rule the deferral set is met and
+ * still returns no: a parse was tried, twice, and neither produced a number
+ * worth printing beside two that hold.
+ *
+ * Where a shape sits is a different question and is already answered. A heading
+ * fragment, a list item, and a table cell are all legitimately verbless and
+ * none of them reaches this measure, because `paragraphBlocks` ends a paragraph
+ * on each. That exclusion is structural and needs no grammar. The imperative is
+ * the one that sits in paragraph prose, and it is what neither parser could
+ * separate out.
  *
  * A paragraph under the floor is skipped rather than scored. A two-sentence
  * configuration note has no spread worth reading, and the opener rule is

package/standards/tasks.md

@@ -207,7 +207,9 @@ Why this task exists and what it depends on.
 
 Every task names where it came from, through a `Plan:`, `Groundwork:`, `Intake:`, or `Issue:` line under the title. Include each only when the file, folder, or issue it names exists.
 
-A task with no origin is either lost context or work nobody decided to do. The invariant runs both ways, and the second direction is the one that bites: a groundwork track or an open issue that no task points at is work already decided and on its way to being forgotten. An intake folder is exempt from that direction, since it dispositions many items at once and most of them close without ever becoming a task.
+A task with no origin is either lost context or work nobody decided to do. The invariant runs both ways, and the second direction is the one that bites: a groundwork track, an intake folder, or an open issue that no task points at is work already decided and on its way to being forgotten.
+
+An intake folder answers that direction at folder scope rather than item scope, since one dump dispositions many items and most close without ever becoming a task. What names a folder is every item answered and no task citing it, on the board or in the archive. That is a dump nobody acted on. Counting the archive beside the board is what separates it from one already promoted and shipped, and a check reading the board alone calls every finished folder abandoned.
 
 `Plan:`, `Groundwork:`, and `Intake:` name their target as a markdown link whose text is the file or folder stem, so the line resolves on a ctrl-click the way `priority.md` rows already do. Write the path relative to `.claude/tasks/`, which makes it `../plans/`, `../groundwork/`, and `../intake/`. A path written from the project root renders as a link and resolves to nothing in an editor rooted at the project. `Issue:` stays a bare `#NNN`, since an issue number is not a path and a full URL would write the remote into a gitignored file.