MyJackfruit

Help
Browse topics · Words for standards

Words for standards

← Back to How do I read a standard?

What are the standards packs?

Checked against GilbApp d529620.

A standards pack is a named group of standards kept together in one vault; in GilbApp it is a standards group.

Deeper

GilbVeda, GilbPlatform's shared list of concepts, calls it a standards group: the standards that govern one body of work, such as a project, a domain or a team's practice, gathered under one name so they can be reached, cited and found as a set. Pack is the word of the tool your AI uses to read standards; the standards themselves, and GilbApp, say group.

A group may hold standards of every kind. A standard belongs to a group only when it names that group itself. One standard may belong to several groups, and a group may sit inside another group. The standards stay where they are in the vault; the group only names a set of them.

The standards GilbPlatform's agents follow are kept in groups in GilbPlatform's own vaults. Kai-Zen, the group of the planning agent Kai-Zen and the agents it works with, is in kaizen.gilb.com/base. GilbPlatformAuthorStandard, which holds standards such as Agent.Standard, the agent that writes and changes standards, and GilbPlatform.Licence, and GilbVedaConcepts, which holds the standards for GilbVeda and for GilbLife, GilbPlatform's list of species, are in jackfruit.gilb.com/base. GilbPlatformCode, GilbPlatform Frontend and websites are in appbuilder.gilb.com/base. They can be read without signing in, and your agents read them as they work.

In GilbApp, open Standards and choose a group under STANDARDS GROUP on the right to see only its standards; All shows every standard of the vault on screen, and + New group, shown only where you may write in the vault, makes a group. In GilbApp today you see the groups of the vaults you have been given access to; GilbPlatform's own vaults above are not in the list under VAULT unless you have been given access to them, so their groups do not show there.

A standard is public unless it names something that must stay private: a secret, a key or where one is kept, a private address, a person's contact details, steps that would help an attacker, a security gap still open, or a client's unreleased information. Such a standard is kept in a private group. Some private rules answer only when your AI reads them with the key of the computer it runs on. If your AI finds no rule without that key, it has not shown that the rule is not there; if the key fails, it asks the vault's owner for a fresh one and stops. You do not need a terminal for any of this: GilbPlatform's standards do not require you to use one, and where one is unavoidable the standard names that step and says why; an agent runs the other steps.

The groups Kai Gilb publishes on GilbPlatform are his, under the terms in GilbPlatform.Licence; one group, GilbPlatformDeveloperGuide, is open under a licence of its own. Groups you make in your own vault are not covered by those terms. The answer on what you may do with the standards tells more.

This answer is written for a computer screen.

Source: GilbVeda t:StandardsGroup a:does (public read 2026-11-10: "A named grouping of the standards one pod holds — the standards that govern one body of work (a project, a domain, a team's practice), gathered under one name so they can be reached, cited and navigated as a set ... MEMBERSHIP is the Approved part-of edge ... written on each MEMBER standard ... The standards stay in the pod's flat registry; one standard may be part-of several groups ... a Standards Group may itself be part-of another Standards Group"). Packs and their vaults: scripts/kz-std/lib/access.mjs:104-118 (each pack's vault); Kai-Zen (Pack: Kai-Zen, vault https://kaizen.gilb.com/base), get Agent.Standard / follow GilbPlatform.Licence, .StandardRules, .Bind (Pack: GilbPlatformAuthorStandard, jackfruit.gilb.com), follow Rule_Code_gilb-name-and-search (Pack: GilbVedaConcepts); Agent.Standard.Where ("Standards that govern GilbVeda and GilbLife are in the GilbVedaConcepts group on https://jackfruit.gilb.com/base"). Standards: GilbPlatform.StandardRules.Public (the list of private reasons; A private standard sits in a private group), GilbPlatform.Bind.Rules ("Some rules are private to the team and answer only to this computer's key. A search with that finds nothing says nothing about them. If the key fails, ask the vault's owner for a fresh one; do not go on."), GilbPlatform.NoHumanTerminal.NoStep, .Agent, GilbPlatform.Licence.Copyright ("These terms do not cover standards customers write in their own vaults. A group Kai Gilb names as open carries its own licence standard instead; today only the GilbPlatformDeveloperGuide group, under Dev.Guide.Licence."). GilbApp af0f04ee: components/process/StandardsControls.tsx:101-151 (Standards group, All), :171-184 (+ New group), standardsGroupScope.ts:6-8 (membership only by a:partOf), AppShell.tsx:478 and GilbPlatform 4d008a55 src/authz/reachable-vaults.ts:242-243 (public vaults not listed).