Glossary

Terms are grouped by where they belong in the system. Business records are defined in more depth in Shared business records.

The shape of the system

Work loop — The single loop every piece of work moves through: Trigger → Context → Capability → Execution → Artifact → Review → Learn → Measure, with results feeding the next trigger. See The work loop.

Station — One of the eight places in the loop. Each answers one question and has machinery behind it.

Foundation (also plane) — One of three cross-cutting concerns every station rests on: identity and access, data governance, connections. See Foundations.

Product area — One of five scope groups the workspace is organised into: conversations and coordination; work and deliverables; capabilities and automation; business performance; learning and improvement. They line up with the five steps in How it works.

The WilsonOS Five — The five measurable promises the system is built to keep. See What is WilsonOS? § What you get.

Agents

Agent — A long-running assistant with an identity, a boot contract, and a lane. Brand agents act as the chief operating officer of one brand; cross-cutting agents work across brands or on the platform itself.

Brand agent — The agent assigned to one brand. Scout runs Code Pineapple; Prime runs RiseBlox. Each loads its brand’s context at the start of every session.

Boot contract — The exact set of context an agent loads when a session starts: identity, the operator’s profile, the brand essence, its own recent memory, and its open plate. Defined per agent; nothing else loads “just in case”.

Lane — The area of the system an agent is responsible for. Brand agents deliver business assets; a platform agent builds the app; cross-cutting agents coach and steward.

Run — One execution of a capability against a task: what was invoked, with what inputs, producing which artifacts. A task can involve multiple runs.

Capabilities

Skill — An atomic, reusable capability: a method an agent masters right before performing a task (write a Pinterest post, render a brand book). Brand-agnostic; loads the brand stack at run time.

Flow — A multi-step orchestration of skills that produces an outcome (take a brand from “no Pinterest presence” to “posting weekly”). Agents execute flows; flows call skills.

Brand stack (also brand context) — A brand’s products, audience, voice, visual rules, customer language, and constraints. Loaded by skills and flows so the same capability produces on-brand work for different brands.

Connection — An external system reached through an API, MCP server, CLI, or equivalent connector, with its own account scope, permissions, and supported read and action capabilities.

Attribution — The chain linking a task to the skill and version that ran, the run, the artifact it produced, and the review and rating it received. What makes “show me everything this skill produced and how it was rated” answerable.

Memory and context

Context — Everything an agent knows before it acts: memory, brand canon, and the boot contract. The second station of the loop.

Memory — What persists across sessions: the operator’s profile, brand truth, capability knowledge, operational facts, and each agent’s working notes. Layered, scoped, and loaded on need rather than all at once.

Canon — The authoritative version of a fact or document. Each class of data has exactly one place it canons and exactly one path that writes it.

Recall — The search and boot path that surfaces the right memory for a task without loading everything.

Work and artifacts

Goal / project / task — Intent, the body of work toward it, and one unit of planned work. Chat messages reference tasks without becoming their storage location.

Deliverable — An artifact marked as a result someone should review, use, or publish — as opposed to a by-product of getting there.

Artifact — A durable output: a file, page, image, video, document. Identified by a stable reference, not by its file name or location.

Version — One explicit state of an artifact. Feedback attaches to a version; a new version does not overwrite the old one’s history.

Registry — The record of what artifacts exist and which version is current. The registry owns identity; storage holds bytes; a name is a label.

Workbench — The review surface: where tasks, deliverables, and artifacts of every type are opened, commented on, rated, approved, and published.

Publish — Moving an approved artifact version out through a connection (a channel, a store, a site) and recording the external identifier that came back.

Measurement and learning

Signal — An observed external event with a source, a date range, and a freshness: an impression, a click, a sale, a rating.

Attribution limit — A stated boundary on what a signal can prove. A funnel stage is not proof of a causal conversion.

Capability evaluation — Comparing versions of a skill or flow against explicit criteria, recording which version and inputs produced each result.

Promotion — Deliberately making an improved version the current one, with the evidence and reasoning preserved. Never automatic.

Sharpening — The nightly and weekly processes that distil what was written during work into durable memory and improved capabilities. They cannot capture what was never written.

Status vocabulary

Live — Deployed and verified. Direction — Agreed design, not a certification. Proposed — Discussed, not scheduled. See How to read these docs.