How do processes and decisions run on GilbPlatform?
Short answer
Programs move a process on one step when its conditions hold, and run decisions against a policy; each move and new decision is kept.
Deeper
This answer is for developers, people who write programs that work with GilbPlatform; GilbApp has no screen that runs a process or a decision. A process is a standard that holds work, with entry conditions, steps and exit conditions. A policy is a standard that holds principles for people who decide later. A decision here is one choice GilbPlatform works out for a subject, the thing decided about, by a policy's rules.
Reading: GET /lws/vault/<vault>/processes lists a vault's processes, and GET /lws/process/<id>/steps gives one process with its steps in their stored order. Each other kind of standard has the same pair: /lws/vault/<vault>/ followed by rulesets, checklists, policies, templates, lookups, references or procedures lists them, and /lws/ruleset/<id>/rules, /lws/checklist/<id>/questions, /lws/policy/<id>/statements, /lws/template/<id>/specimens, /lws/lookup/<id>/entries, /lws/referencedocument/<id>/exhibits or /lws/procedure/<id>/proceduresteps gives one with its parts. Each part comes back only if the caller may read it. A list that names no vault is refused.
Moving a process on: POST /base/process/advance with the body { instance } moves a process instance, one run of a process, by one move. It moves only when the exit conditions of the current step hold and the entry conditions of the next step hold. A move writes a transition, a record of that move, and answers 201. A blocked move writes nothing and answers 200, with the condition that failed in blockedReason; an instance that has finished also answers 200 and does not start again. The current step is the latest transition, so the run's whole path is a log that is never overwritten.
Running a decision: POST /base/decision/operate with the body { subject, policy } works out one decision for the subject against the policy, from the subject's state at that moment: which band, or range, each measured value falls in, the regime, or operating mode, chosen, a sizing level and an option, as the policy's rules give them. A decision that differs from the subject's last one is written as its own record and answers 201; an unchanged one writes nothing and answers 200. A decision's history is at /base/e/<id>/history.
Both need a signed-in caller with the right to write: a caller who is not signed in gets 403 before anything is read. How a process instance is first made is not part of these two calls.
Source: GilbPlatform 4d008a55367a6e7453920c463a8923df37de62e9 (https://id.gilb.com/version 2026-11-10), code read at 4d008a55; every cited file unchanged at the live 498d29a0dec9a15d167f4b6b5d731382a6bcede0 (the diff from 4d008a55 to 498d29a0 over src/lws src/process src/decision src/routes/process.ts src/routes/decision.ts: no change, 2026-11-11): src/lws/routes.ts:751-759 (GET /lws/vault/:vaultId/processes), :795-800 (GET /lws/process/:id/steps; each returned step authorized EXACTLY as GET /lws/r/<step>), :656-690 (one loop over the families: GET /lws/<segment> 400 vaultRequired; GET /lws/vault/:vaultId/<segment>; GET documentPath(id), each unit authorized as GET /lws/r/<unit>); src/lws/standard-family-registry.ts:105-125 (rulesets, checklists, policies, templates, lookups, references, procedures); src/lws/rulesets.ts:61-62, checklists.ts:61-62, policies.ts:59-60, templates.ts:89-90, lookups.ts:28-29, references.ts:33-34, procedures.ts:34-35, process-steps.ts:67 (the paths); src/routes/process.ts:1-19, :28-35 (body { instance }), :48-69 (anon 403 an authenticated writer is required before the engine reads; 201 when a transition was written, 200 blocked or done); src/process/engine.ts:1-40 (current step = latest transition; both gates; blocked writes nothing; done does not restart), :70-83 (outcome opened | closed | blocked | done; blockedReason); src/routes/decision.ts:1-14, :21-31 (body { subject, policy }), :44-63 (anon 403; 201 changed, 200 unchanged no-op); src/decision/engine.ts:1-45 (bands, regime, level, option; write only on a change; append-only history; GET /base/e/<id>/history). GilbApp ebd9415e: the code at ebd9415e has no process/advance or decision/operate (no screen runs either). GilbVeda public read 2026-11-10: t:Process (Approved), t:ProcessInstance (Suggested: A single running enactment of a Process), t:Transition (Suggested: One append-only move of a Process Instance between steps), t:Decision (Suggested: "A single operating determination the decision engine wrote for a subject at an instant ... bands, regime, level and option"), t:Policy. GilbPlatform.StandardRules.Kinds (a Process holds work, with entry conditions, steps and exit conditions; a Policy holds principles for people who decide later). Capability rows: CapabilityTags-GilbPlatform:44, :78, :79, :84; inventory Capability-GilbPlatform-GilbSupport.md:95, :160, :161, :166.
Checked against GilbApp d529620.