MyJackfruit

Help
Browse topics · Words for standards

Words for standards

← Back to How do I write a new standard?

What is a standard, and why is each one unique?

Checked against GilbApp d529620.

A standard is a written procedure, rule set, form or other guide, kept in a vault, that people and agents follow as they work.

Deeper

Also asked:

What are the tabs in Standards (Policies, Processes, Procedures …)? Each tab lists one kind of standard: Policies principles for later decisions, Processes work with steps, Procedures agents, Rules rules for writing, Templates & Forms forms, Checklists questions, References facts, Lookups entries found by a key.

What is the difference between my plan and a standard? Your plan says what your project should deliver: its Values, Functions and Solutions, kept under Plan. A standard is a written way of working, such as a process or a rule, kept under Standards.

What is the difference between a policy, a process, a procedure and a rule? A policy holds principles for later decisions; a process, work with steps; a procedure, an agent and the steps it runs; a rule set, rules for writing.

A vault is the place where a person or a group keeps their records, and an agent is your AI following one written procedure, its standing instructions, for one kind of work. A standard is kept on GilbPlatform as data in a vault, so a person reads it in GilbApp under Standards, and an agent reads it as it works. GilbVeda, GilbPlatform's shared list of concepts, calls a standard an official, written specification that guides a defined group of people in doing a process: a best-known practice.

There are nine kinds, each for one sort of job. A Procedure holds an agent: who you call, and the steps that agent runs. A Process holds work, with entry conditions, steps and exit conditions: it starts only when its entry conditions are true and hands back when its exit conditions are true. A ProcessCard is one task: another standard hands off to it for that task, and it hands back when the task is done. A RuleSet holds rules for writing: what the writing must be; it does not run the work. A Checklist holds questions that ask whether the work followed a Process and its rules; each question points at the standard it asks about. A Policy holds principles for decisions other people make later, under conditions no one knew when it was written. A Template holds a form and a filled example. A LookupTable holds entries you look up by a key. A ReferenceDocument holds facts for reuse; it does not instruct.

In GilbApp, Standards has a tab for the kinds: Policies, Processes (where ProcessCard, beside Process, lists the process cards), Procedures, Rules (rule documents, GilbApp's name for a RuleSet), Templates & Forms, Checklists, References and Lookups.

A standard is made of points, each a record of its own: the steps of a process or a procedure, the rules of a rule document, the questions of a checklist, the statements of a policy, and so on. A point can hand off to another standard: a link to the standard, or the point in one, that does the job the point names.

Each standard is meant to be unique in two ways, by the rules for writing standards. It should be the one place where its job is written: a job that more than one standard needs is a standard of its own, and the others hand off to it instead of copying its steps. And by the same rules each point, and the standard itself, gets a tag, a short fixed name such as Bakery.Open, that nothing else in its vault may carry; a point's tag is the standard's tag, a dot and a short name for the point.

The same rules keep each standard short: a good template and a clear example do most of the work. A standard is built backwards from a finished example: first the example, then the template made from it, then the rules, then the process, then the agent. Before an agent reads or changes GilbPlatform's code or its live stored data, the standard GilbPlatform.Bind tells it to name the platform agent it loaded, load that agent's standard and follow its hand-offs, the links from one standard to the next.

Whoever may write in the vault a standard is kept in may change it, and an agent changes a standard only with the go of a person who may write in the vault the standard is kept in.

The standards Kai Gilb publishes on GilbPlatform belong to him; GilbPlatform customers (people and organisations with a current subscription), their apps, those apps' users and their AI may read, follow and run them inside GilbPlatform, but may not export them, keep a copy outside it or train an AI on them; the terms for them do not cover standards you write in your own vault. The answer on what you may do with the standards tells more.

This answer is written for a computer screen.

Source: Standards read 2026-11-10: Agent.Standard (J 06gew6pxehz9dexdcnmd5n5t6r) steps Type.Procedure (A Procedure holds an Agent. It is who you call, and the steps that agent runs.), Type.Process (It starts only when its entry is true, and it hands back when its exit is true.), Type.ProcessCard ("one task, with no entry or exit. Another standard hands off to it for that one task, and it hands back when the task is done."), Type.RuleSet (rules for writing ... It does not run the work), Type.Checklist ("questions ... whether the work followed a Process and its rules ... Every question points at the standard it asks about"), Type.Policy ("principles for decisions other people make later, under conditions that were unknown when it was written"), Type.Template (a form and a filled example), Type.LookupTable (keyed entries. You look one up by its key), Type.ReferenceDocument (facts for reuse. It does not instruct); GilbPlatform.StandardRules (J 06gew6ngqsvpd5wygjv0gp4gg0) Owner, Kinds, Short, OnePlace ("A job that more than one process needs is its own Process or ProcessCard: callers hand off to it and it hands back. Never copy its steps."), Tag ("Tag every point ... with a tag unique in the vault: <Standard>.<Point>. Document tags and point tags share one namespace."), Backwards; GilbPlatform.ChangeStandard.Go; GilbPlatform.Bind.Name; GilbPlatform.Licence.Copyright (These terms do not cover standards customers write in their own vaults), .Inside, .Use. GilbVeda (public read 2026-11-10): t:Standard a:does ("an official, written specification that guides a defined group of people in doing a process. It is a best-known practice"), a:handsOffTo ("X may be any point of a standard ... Y may be any standard document or any point in one"). GilbApp af0f04ee (https://gilb.com/app/version.json read 2026-11-10): components/process/standardsTabs.ts:9-24 (tab labels), lib/base/standardKinds.ts:108-120 (Process, ProcessCard), components/process/ProcessViewer.tsx:168-361 (the unit names per kind), components/process/StandardsSection.tsx:297-299 (Read live from GilbPlatform).