Home / Method
How the record and the check are made
The method, in plain words
One reviewed record drives the pages, the check and the kit. The public facts carry a retrieval date. The practices carry a basis label. The check is arithmetic on the reader's own answers.
One record, every output
data/rule.json holds the public facts, the 40 practices, the 18 defined terms, the six groups and the check. Every page, the kit and the check read from it. A change to one row changes every output, and the smoke tests fail if they disagree.
The record carries a hash. The refresh script re-downloads the public record, compares the fields with the record and fails loudly on any change. The same diff is what the change watch sends. Nothing on the site is written from memory or from a search snippet.
What each label means
- public-record: the ISO abstract or scope states the point, and the page cites the abstract section. The 25-person limit, the non-critical limit and the parallel-project situation are in this group.
- series-structure: the process area is named in the public abstract, and the practice is our reading of how a VSE works it. Most of the project, system and acquisition practices are in this group.
- our-reading: the practice is our practical recommendation. It is not attributed to the text and the page says so.
The FDIS body is not public. No unit states a draft clause number, a clause heading or a quotation. When the published text appears, the register is re-baselined and the labels are revisited.
Tailoring. A very small entity may apply a practice at less than full weight for a particular project. Tailoring is allowed here only when the decision, the reason and the approver are recorded. Silent tailoring is treated as a gap, because the assessor cannot see what was left out or why.
How the free check decides
The check applies the public scope first: the size of the entity, the criticality of the systems, and whether more than one project runs with more than one team. A firm outside the scope gets a scope verdict, not an action plan. A critical system stops the check and names the route out. A firm on one project and one team is pointed to the Basic profile.
Inside the scope, the check adds a starting-point score from five facts: the profile in use, the state of the templates, the state of the evidence, whether acquisition is part of the work, and whether a decision has been recorded. The score picks one of three verdicts and three actions from the register. The result prints the rule it used. It is not a compliance score and not a legal opinion.
What the method does not do
- It does not assess a real project. It states practices and evidence; the firm supplies the facts.
- It does not classify a system as critical. That is a competent engineering judgement.
- It does not quote or paraphrase the draft body, because the body is not public.
- It does not certify, audit or create a presumption of conformity.
- It does not predict the publication date. The planning date is arithmetic and is labelled as such.