An open source design system that's fully customizable and agent ready
TypeScript
docs: writing rubric for specification records (#6917)
Cindy Zhanga17467599d08
diff --git a/.github/PULL_REQUEST_TEMPLATE/specification.md b/.github/PULL_REQUEST_TEMPLATE/specification.mdindex 5ac9892cc3..ff573598cf 100644--- a/.github/PULL_REQUEST_TEMPLATE/specification.md+++ b/.github/PULL_REQUEST_TEMPLATE/specification.md@@ -14,7 +14,7 @@## Rejected alternatives-<!-- Record only consequential alternatives likely to recur. -->+<!-- Record only consequential alternatives likely to recur. The reasoning may live here; in the record itself each one is at most one line inside the decision that rejects it. -->## Claim scope and non-goals@@ -22,7 +22,18 @@## Evidence and implementation relationship-<!-- Evidence supporting the decision; linked implementation PR if one exists. The specification must remain valid without it. -->+<!-- Evidence supporting the decision; linked implementation PR if one exists. Research (surveys, option comparisons, benchmarks, test scores) is linked here as an artifact, not written into the record. The specification must remain valid without it. -->++## Writing rubric results++<!-- Run the rubric in docs/contributing/spec-writing.md over every record this PR touches. One line per item: what you found and what you did with it. "None" is a result; "two found, collapsed into DEC-3" is a better one. A record PR without these lines is incomplete. -->++- R1 narration:+- R2 research in the record:+- R3 evidence naming a change:+- R4 rejected alternatives over one line or outside a decision:+- R5 pull request or issue references remaining:+- R6 ruled open questions still listing options:## Scope@@ -30,7 +41,7 @@- [ ] It records observable behavior and preserves equivalent internal implementations.- [ ] Any named internal mechanism is intentionally public, names its dependent caller/system, and explains why an equivalent implementation would not satisfy the contract.- [ ] Verification states the evidence layer and failure signal without prescribing CI job/workflow topology.-- [ ] It records one intentional durable decision, not a review transcript or rescue for a separable tagalong.+- [ ] It records one intentional durable decision, not a rescue for a separable tagalong.- [ ] The canonical knowledge owner, affected current claims, and overlapping open work are named; any ownership collision is resolved or called out for human decision.- [ ] Adjacent API, visual, accessibility, composition, and implementation facts remain outside scope unless this exact decision depends on them.- [ ] Public text and artifacts contain no internal Meta context.diff --git a/.github/REVIEW_GATE.md b/.github/REVIEW_GATE.mdindex 5a56e27a8a..f79be3bc6b 100644--- a/.github/REVIEW_GATE.md+++ b/.github/REVIEW_GATE.md@@ -71,6 +71,10 @@ A PR changes only spec records when every changed path is one of:- a colocated Core/Lab `<Name>.spec.md`.Draft-only spec records can merge after validation without owner approval.+Approval reads the record against the `## Writing rubric results` the author+reports in the pull request description (`docs/contributing/spec-writing.md`);+a record pull request without them is incomplete. That is a review convention,+not a status this gate publishes.Pure spec-record PRs do not add Changesets because they do not release packages;CI rejects a PR containing only spec records and `.changeset` entries.That classification fails closed on an empty or truncated file list and checksdiff --git a/AGENTS.md b/AGENTS.mdindex 5cf97fac87..a41562a4b0 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -41,6 +41,13 @@ nested `AGENTS.md`.applicable design spec under `docs/design/`, and current architecture under`docs/architecture/`.- Consequential shared-system changes: use a record under `docs/specs/`.+- Writing or reviewing any knowledge record: run the rubric in+ `docs/contributing/spec-writing.md` over the record and put its results in+ the pull request description under `## Writing rubric results`. A record+ describes the system in the present tense; proposals, history, pull+ requests, and research stay out of it. When reviewing, read the record+ against the reported results; a record pull request without them is+ incomplete, so ask for them before reviewing the content.- Integration contribution work: read `docs/specs/AST-039/spec.md`. Every newdiscoverable item owns a strongly typed, same-stem `.doc.mjs`; root manifestslocate directories and never catalog their items. No catalog file (likediff --git a/docs/architecture/interaction-modality.md b/docs/architecture/interaction-modality.mdindex 711ba66107..cfac1d6f5e 100644--- a/docs/architecture/interaction-modality.md+++ b/docs/architecture/interaction-modality.md@@ -238,9 +238,9 @@ ownership, scrolling, clipping, hit testing, or whether an essential control remperceivable in the supported presentation. Unit tests prove event routing, DOM state,and deterministic intent ordering but do not replace those browser outcomes.-[PR #5648](https://github.com/facebook/astryx/pull/5648) is a verification-benchmark for the record, not an authority for it. Its ChatComposer fixture-covers keyboard-owned editor focus, pointer suppression, clearing an existing-keyboard indicator on pointer press, and keeping internal action focus owned by-the action. The benchmark also verifies programmatic editor focus after both-keyboard and pointer input before the behavior is treated as complete.+A composed editor surface is the record's verification benchmark: it covers+keyboard-owned editor focus, pointer suppression, clearing an existing keyboard+indicator on pointer press, and keeping internal action focus owned by the+action. The benchmark also verifies programmatic editor focus after both+keyboard and pointer input before the behavior is treated as complete. A+benchmark demonstrates the invariants; it does not carry authority for them.diff --git a/docs/architecture/knowledge-contracts.md b/docs/architecture/knowledge-contracts.mdindex d7fc705af5..5fb41b1020 100644--- a/docs/architecture/knowledge-contracts.md+++ b/docs/architecture/knowledge-contracts.md@@ -155,10 +155,14 @@ Every record is either:record states durable requirements, prohibitions, compatibility, ownership, andevidence independently of any one implementation change. It never exists toapprove a pull request and never approves, rejects, classifies, designates, or- authorizes a specific one. Pull requests and issues may appear only as clearly- non-authoritative examples, historical evidence, or references; the rule must- remain complete without them. The reviewer owns each change's disposition- against current authority.+ authorizes a specific one. Pull requests and issues are not standing content:+ a record states the fact a change established, not the change, and remains+ complete without any pull request or issue it once cited. Research that+ supports a decision — a survey, an options comparison, a benchmark, a test's+ design or scores — is an artifact linked from the pull request, not record+ content; the record keeps the conclusion inside the decision that rests on+ it. A fact owned elsewhere is delegated by linking the record that owns it.+ The reviewer owns each change's disposition against current authority.- **INV11 — Every public delta has an authority result.** Every public API updateand every public behavior change is matched to current committed authoritybefore acceptance. Package-export shape is not the only trigger: reachable@@ -332,6 +336,10 @@ for a clause that has no stable heading or explicit anchor.Then write the authoritative body:+- Describe the system in the present tense, not the project that produced it.+ `docs/contributing/spec-writing.md` turns this rule and INV10 into a rubric;+ a pull request that creates or changes a record reports that rubric's results+ in its description before review.- Use familiar words and short, direct sentences.- State each rule fully once, beside the conditions and exceptions that control it.Later sections cite its ID or canonical owner instead of restating the prose.diff --git a/docs/architecture/template-authoring.md b/docs/architecture/template-authoring.mdindex 8a7c33db41..a773d823e5 100644--- a/docs/architecture/template-authoring.md+++ b/docs/architecture/template-authoring.md@@ -274,13 +274,6 @@ An exact-source audit at `067b176` found:## Decision log-### Recovered draft — 2026-09-02--This record recovers the architecture half of [#5915](https://github.com/facebook/astryx/pull/5915)-without copying the rubric or changing `design:template-composition`. It replaces-that draft's proposed stable-slug invariant with the accepted-`spec:AST-017/DEC-2` boundary.-### Catalog convergence direction — 2026-09-05One validated catalog owns template membership. Source-specific authoring shapes maydiff --git a/docs/contributing/README.md b/docs/contributing/README.mdindex 811ea24e16..44d00736cc 100644--- a/docs/contributing/README.md+++ b/docs/contributing/README.md@@ -10,3 +10,6 @@ contracts, or component contracts.public component API.- [CLI conventions](cli-conventions.md): propose, implement, and review a changeto the `packages/cli` command surface.+- [Writing specification records](spec-writing.md): the six-month test, the+ rubric an author runs over a record before review, and the results a record+ pull request reports.diff --git a/docs/contributing/pull-requests.md b/docs/contributing/pull-requests.mdindex 49f06ceba4..e045c8718d 100644--- a/docs/contributing/pull-requests.md+++ b/docs/contributing/pull-requests.md@@ -4,15 +4,17 @@ A pull request should make one reviewable change for one reason. Choose the tempGitHub uses the default template automatically. To choose another, add `?template=<file>.md` to the new-pull-request URL, or copy the matching file from `.github/PULL_REQUEST_TEMPLATE/` into the description.-| Primary intent | Template | Minimum evidence |-| ---------------------------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------- |-| Restore broken behavior | `bug-fix.md` | reproduction, expected authority, before/after result, unchanged representative path |-| Correct or intentionally change appearance | `visual-update.md` | current visual authority or owner decision, real-browser before/after pixels, relevant state matrix |-| Add a capability | `new-feature.md` | user need, current specification, complete public delta, behavior and compatibility evidence |-| Correct contributor or consumer documentation | `documentation.md` | reader impact, source of truth, rendered or generated result |-| Record a durable decision | `specification.md` | exact unresolved claim, existing authority searched, decision, rejected alternatives, explicit non-goals |-| Change tooling, tests, CI, or repository maintenance | `maintenance.md` | operational problem, failure proof, success proof, unchanged product behavior |-| Anything else | `other.md` | primary intent, user or maintainer impact, authority, evidence |+Any pull request that creates or changes a knowledge record — a `docs/specs/<id>/spec.md`, a family, design, theme, or architecture record, or a colocated `<Name>.spec.md` — reports the results of the rubric in [Writing specification records](spec-writing.md) in its description, whichever template it uses. `specification.md` carries the `## Writing rubric results` section; copy it into another template when that pull request also touches a record.++| Primary intent | Template | Minimum evidence |+| ---------------------------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------- |+| Restore broken behavior | `bug-fix.md` | reproduction, expected authority, before/after result, unchanged representative path |+| Correct or intentionally change appearance | `visual-update.md` | current visual authority or owner decision, real-browser before/after pixels, relevant state matrix |+| Add a capability | `new-feature.md` | user need, current specification, complete public delta, behavior and compatibility evidence |+| Correct contributor or consumer documentation | `documentation.md` | reader impact, source of truth, rendered or generated result |+| Record a durable decision | `specification.md` | exact unresolved claim, existing authority searched, decision, rejected alternatives, explicit non-goals, writing rubric results |+| Change tooling, tests, CI, or repository maintenance | `maintenance.md` | operational problem, failure proof, success proof, unchanged product behavior |+| Anything else | `other.md` | primary intent, user or maintainer impact, authority, evidence |## Explain only what authority does not already saydiff --git a/docs/contributing/spec-writing.md b/docs/contributing/spec-writing.mdnew file mode 100644index 0000000000..6bdc69d03b--- /dev/null+++ b/docs/contributing/spec-writing.md@@ -0,0 +1,191 @@+# Writing specification records++A specification record describes the system as it is meant to be. It is read by+someone deciding whether an implementation conforms, long after the pull+requests that shaped it are closed. Every sentence in a record has to survive+that reader.++This guide applies to every knowledge record that states what the system does:+`docs/specs/<id>/spec.md`, family, design, theme, and architecture records, and+colocated `<Name>.spec.md` component and module contracts. An implementation+plan (`plan.md`) tracks work and is outside it. It projects+`architecture:knowledge-contracts` (INV2 and INV10) and the templates under+`docs/templates/knowledge/` into a pass an author runs and a reviewer checks. It+does not create policy; when it disagrees with a current record, the record wins+and the guide needs fixing.++## The test++> In six months, when every pull request mentioned in this record is closed and+> forgotten, does this sentence still say something true about the system?++A sentence that passes describes behavior, a boundary, a default, an owner, or a+piece of evidence. A sentence that fails describes the project: what a change+proposed, what the team considered, what the owner ruled against, what used to+be the case. That is narration. It was true the day it was written and it ages+into noise that a future reader has to step around to find the rule.++## The rubric++Run the items in order. The order is how often each one goes wrong, not where it+sits in the template. Each item is a question with a yes-or-no answer that a+reviewer can check by reading the record; a `no` is a pass. Report what the pass+found, not a tick.++| ID | Question | When the answer is yes |+| --- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |+| R1 | Does any sentence describe what a change proposed, decided, replaced, ported, or used to do, rather than what the system does? (Scan for `proposes`, `we decided`, `previously`, `a port of`, `now`.) | Rewrite it in the present tense as a statement about the system, or delete it. |+| R2 | Does the record contain research: a survey of other systems, an options comparison, a benchmark run, or a test's design and scores? | Delete it from the record. Publish it as an artifact linked from the pull request. Keep the conclusion it supports as one or two sentences inside the decision resting on it. |+| R3 | Does any evidence, basis, or verification cell name a pull request, issue, or commit instead of the fact it established? | Replace the reference with the fact: `real-device touch feedback`, `current source`, `WAI-ARIA 1.2 combobox pattern`. |+| R4 | Is any rejected alternative longer than one line, or recorded anywhere other than inside the decision that rejects it? | Collapse it to one `Rejected:` line in that decision. Keep the line only when naming the alternative prevents the mistake recurring; otherwise delete it. |+| R5 | Searching for `#` followed by digits, `/pull/`, and `/issues/`: does any pull request or issue remain as standing content? | Delete it, or replace it with a link to the record that owns the fact. Links to other records are encouraged; they are canonical owners. |+| R6 | Does any open question whose answer is already recorded still list its options? | Collapse the options into the decision. Only an unanswered question keeps its options side by side. |++Report one line per item in the pull request description, under+`## Writing rubric results`. State what was found and what was done with it:++```text+R1 narration: Intent opened with the proposal history; rewritten as two present-tense sentences.+R2 research: none in the record; the comparison lives in a linked artifact.+R3 evidence: FR4 basis cited a pull request; now "real-device touch feedback".+R4 rejected alternatives: one, DEC-2, one line.+R5 change references: none.+R6 open questions: OQ1 is unanswered and keeps its two options.+```++A finding is not a defect in the author. "Two found, moved into DEC-3 as one+line" is a clean result. A record whose results all read `none` on the first+pass is rarer than one that found something, and a reviewer reads it with that+in mind.++## Why each item++### R1 — State the system, not the project++A record is a description of behavior that happens to have a history, not a+history that happens to describe behavior. Present tense, declarative, what the+thing does. "The pull request proposes", "we decided to change", "previously+this was", and "a port of" all describe the project. They tell the reader how+the sentence came to exist and nothing about what the system does.++Narration is the most common failure because it is the natural way to write+while the decision is fresh. The fix is mechanical: find the behavior the+sentence is circling and state it.++Narration:++> An open pull request proposed revealing row actions on hover. The owner ruled+> against it, so this record settles that actions are always visible.++The same fact as a record sentence:++> Row actions are always visible. They do not depend on hover or focus.++The second version is shorter, needs no context, and is still true when the pull+request is forgotten.++### R2 — Research is an artifact++A competitive survey, an options comparison, a benchmark, or the design and+scores of a test are how a decision was reached. They are valuable and they+belong somewhere durable, which is an artifact linked from the pull request. A+record states the conclusion the research supports, in a sentence or two inside+the decision that rests on it, with a citation only where a reader might+reasonably doubt the claim.++Research in a record fails the six-month test twice. The comparison stops being+true as the surveyed systems change, and the reader has to find the decision+inside a table of alternatives the decision already closed. A record also reads+as though the decision was always the decision; a survey reads as a debate.++The template's own line about audit data is the same rule applied to+measurements: "Current measurements belong in the audit record; this subsection+owns only durable constraints and their verification target."++### R3 — Evidence cites facts, not changes++An evidence cell answers "how do we know?" A pull request number does not+answer it; it points at a place where the answer once lived. "#NNNN's device+test" tells a future reader nothing once the pull request is closed, and tells+the present reader only that someone tested something somewhere. "Real-device+touch feedback" says what the evidence is.++The same applies to a basis column in a draft requirement table. `proposal` is a+valid basis while a row is unsettled; a pull request number in its place is not,+because the basis of a rule is a reason, and a change is not a reason.++### R4 — Rejected alternatives: one line, inside the decision++The record describes the specific behavior wanted, not every option considered.+A rejected alternative earns one line, inside the decision that rejects it, when+naming it prevents the same mistake from being proposed again. That is a+guardrail, not a history.++A rejected alternative that takes a paragraph is research (R2). A rejected+alternative in the Intent section is narration (R1). A rejected alternative that+no one would propose again is noise; delete it.++> **DEC-2 — Actions are caller-rendered nodes.** The caller supplies the control+> and owns its handler; the component places it and never inspects it.+> Rejected: a declared `{label, icon, onClick}` object, because the component+> would then render a control it does not own.++### R5 — No pull request or issue as standing content++A record outlives every change that touched it. A pull request referenced in+the body is a dependency on something that will close, merge, or be superseded,+and the sentence that references it fails the six-month test by construction.+`architecture:knowledge-contracts` INV10 states the rule: pull requests and+issues are not standing content, a record states the fact a change established+rather than the change, and it never exists to approve, reject, classify, or+authorize one.++Links to other records are the opposite case and are encouraged. A record is a+canonical owner; linking `component:Selector/FR3` or `spec:AST-002/DEC-1`+delegates a fact to the place that owns it, which is exactly what INV2 asks for.++Checking this item is a text search, which is why it is phrased as one.++### R6 — Open questions are the exception++An unanswered question genuinely has options, and the owner needs them side by+side to rule. An open question may therefore list its alternatives, with the+consequence of each. Once ruled, the alternatives collapse: the chosen one+becomes the behavior, and the rejected ones become at most one line inside the+decision (R4). A ruled question that still carries its options is a record+describing a debate that is over.++## Where the pass happens++The author runs the rubric before requesting review and reports the results in+the pull request description. The reviewer reads the record against the+results: an item reported `none` with a finding still in the record is a review+comment, and a record pull request with no results section is incomplete before+review starts. This applies to any pull request that creates or changes a+record, under whichever pull request template it uses; `specification.md`+carries the results section, and other templates add it when they touch a+record.++The templates under `docs/templates/knowledge/` carry a one-line reminder at the+sections where these failures usually land (Intent, evidence, decision log, open+questions) and point here. The reminder reaches an author editing the file; the+results section reaches the reviewer. Neither replaces the other.++## What is checked mechanically++`pnpm check:knowledge` validates record structure: frontmatter, required+sections, schema and template versions, relationship links, and metadata blocks.+It does not check any rubric item, by design:++- Whether a sentence is narration (R1), research (R2), or a ruled question (R6)+ is a judgement about meaning, and a check that guesses at it would be argued+ with and then ignored.+- A pull request reference (R3, R5) is detectable, but records approved before+ this rule carry references that were permitted when they were written, and+ the file cannot tell which of those a future edit is responsible for. A hard+ check would fail every one of them; a grandfather list would drift, which is+ the failure this guide exists to stop. The reviewer's text search is the+ honest check, and the rubric applies to the records a pull request touches.++Rubric results in the pull request description are a convention backed by+review, not a status check.diff --git a/docs/templates/knowledge/architecture.md b/docs/templates/knowledge/architecture.mdindex d12f3992e8..188a008388 100644--- a/docs/templates/knowledge/architecture.md+++ b/docs/templates/knowledge/architecture.md@@ -1,6 +1,6 @@---schema_version: 1-template_version: 2+template_version: 3kind: architectureid: architecture:<surface>authority: draft@@ -16,6 +16,8 @@ deciding_specs: [spec:AST-000/DEC-0]# <Surface> architecture+<!-- Describe the system, not the project: present tense, what it does. No proposals, history, pull requests, or research in the record; see docs/contributing/spec-writing.md and report its rubric results in the pull request. -->+## Contract at a glance| Area | Contract |diff --git a/docs/templates/knowledge/component-spec.md b/docs/templates/knowledge/component-spec.mdindex f85dc2b8ee..f44ac8d9ec 100644--- a/docs/templates/knowledge/component-spec.md+++ b/docs/templates/knowledge/component-spec.md@@ -1,6 +1,6 @@---schema_version: 3-template_version: 6+template_version: 7kind: componentid: component:<Name>authority: draft@@ -21,6 +21,8 @@ system_specs: [spec:AST-000/DEC-0]# <Name> component contract+<!-- Describe the system, not the project: present tense, what it does. No proposals, history, pull requests, or research in the record; see docs/contributing/spec-writing.md and report its rubric results in the pull request. -->+## Contract at a glance| Area | Contract |@@ -181,7 +183,7 @@ edit an existing component contract merely to backlink to those drafts.## Decision log-<!-- Record a durable boundary or requirement, not a review transcript. Keep a rejected alternative only when it is consequential and likely to recur. -->+<!-- Record the boundary or requirement, not how it was reached. A rejected alternative is at most one line here, kept only when it is consequential and likely to recur. -->### DEC-1 — `<component-local decision>`diff --git a/docs/templates/knowledge/design-spec.md b/docs/templates/knowledge/design-spec.mdindex 9ca71cc839..580f75e62f 100644--- a/docs/templates/knowledge/design-spec.md+++ b/docs/templates/knowledge/design-spec.md@@ -1,6 +1,6 @@---schema_version: 1-template_version: 1+template_version: 2kind: designid: design:<surface>authority: draft@@ -19,6 +19,8 @@ deciding_specs: [spec:AST-000/DEC-0]# <Surface> design specification+<!-- Describe the system, not the project: present tense, what it does. No proposals, history, pull requests, or research in the record; see docs/contributing/spec-writing.md and report its rubric results in the pull request. -->+## User intent<!-- Who is affected, in which state, and what they should understand or do. -->diff --git a/docs/templates/knowledge/family-contract.md b/docs/templates/knowledge/family-contract.mdindex af9dea49c9..a4673c3ba1 100644--- a/docs/templates/knowledge/family-contract.md+++ b/docs/templates/knowledge/family-contract.md@@ -1,6 +1,6 @@---schema_version: 1-template_version: 1+template_version: 2kind: familyid: family:<family-name>authority: draft@@ -19,6 +19,8 @@ deciding_specs: [spec:AST-000/DEC-0]# <Family name> contract+<!-- Describe the system, not the project: present tense, what it does. No proposals, history, pull requests, or research in the record; see docs/contributing/spec-writing.md and report its rubric results in the pull request. -->+## Intent## Membership rulediff --git a/docs/templates/knowledge/module-spec.md b/docs/templates/knowledge/module-spec.mdindex 37ad86f0be..4c75889211 100644--- a/docs/templates/knowledge/module-spec.md+++ b/docs/templates/knowledge/module-spec.md@@ -1,6 +1,6 @@---schema_version: 3-template_version: 3+template_version: 4kind: moduleid: module:<ParentComponent>/<PublicName>authority: draft@@ -17,6 +17,8 @@ references: [architecture:<surface>, design:<surface>, spec:AST-000/DEC-0]# <PublicName> module contract+<!-- Describe the system, not the project: present tense, what it does. No proposals, history, pull requests, or research in the record; see docs/contributing/spec-writing.md and report its rubric results in the pull request. -->+## Contract at a glance| Area | Contract |diff --git a/docs/templates/knowledge/system-spec.md b/docs/templates/knowledge/system-spec.mdindex 31e8f68d88..eba018cedc 100644--- a/docs/templates/knowledge/system-spec.md+++ b/docs/templates/knowledge/system-spec.md@@ -1,6 +1,6 @@---schema_version: 4-template_version: 1+template_version: 2kind: system-specid: spec:AST-000authority: draft@@ -18,6 +18,8 @@ affects_consumer_docs: [<doc-id>]# <Change> system spec+<!-- Describe the system, not the project: present tense, what it does. No proposals, history, pull requests, or research in the record; see docs/contributing/spec-writing.md and report its rubric results in the pull request. -->+## Intent<!-- State the person/task and the durable observable outcome this spec owns. -->diff --git a/docs/templates/knowledge/theme-spec.md b/docs/templates/knowledge/theme-spec.mdindex 7b953a8482..0d192a25da 100644--- a/docs/templates/knowledge/theme-spec.md+++ b/docs/templates/knowledge/theme-spec.md@@ -1,6 +1,6 @@---schema_version: 2-template_version: 1+template_version: 2kind: themeid: theme:<package-theme-name>authority: draft@@ -15,6 +15,8 @@ references: [architecture:<surface>, design:<contrast-methodology>]# <Theme name> theme specification+<!-- Describe the system, not the project: present tense, what it does. No proposals, history, pull requests, or research in the record; see docs/contributing/spec-writing.md and report its rubric results in the pull request. -->+## Intent and audience## Inheritance and basediff --git a/docs/templates/knowledge/versions.json b/docs/templates/knowledge/versions.jsonindex e1fba65ceb..474f7de24b 100644--- a/docs/templates/knowledge/versions.json+++ b/docs/templates/knowledge/versions.json@@ -1,10 +1,10 @@{- "architecture": 2,- "component": 6,- "design": 1,- "family": 1,+ "architecture": 3,+ "component": 7,+ "design": 2,+ "family": 2,"implementation-plan": 1,- "module": 3,- "system-spec": 1,- "theme": 1+ "module": 4,+ "system-spec": 2,+ "theme": 2}diff --git a/scripts/check-knowledge.test.mjs b/scripts/check-knowledge.test.mjsindex 089ca2309b..da0ad4455d 100644--- a/scripts/check-knowledge.test.mjs+++ b/scripts/check-knowledge.test.mjs@@ -2055,10 +2055,10 @@ describe('knowledge validation', () => {fs.mkdirSync(directory);fs.writeFileSync(path.join(directory, 'Button.spec.md'),- componentRecord({template_version: '7'}),+ componentRecord({template_version: '8'}),);expect((await validateKnowledgeRoot(root)).join('\n')).toMatch(- /template_version 7 is newer than 6/,+ /template_version 8 is newer than 7/,);});