Glossary: cat-harness
The glossaries cat-harness owns: Folio Assistant platform terms (cat-harness) (14 terms, SKOS). Terms extracted from its assets: Skills (245) · Tools (171) · BPMN activities (483) · DMN decisions (10) · Schema fields (2140). Every other instance’s terms, the counts and the sources are on the glossary index.
Size: this page holds 14 terms and is 17 KB before compression, within its budget of 1.0 MB. There is no search index: the filter below runs over this page, and the A–Z bar jumps within it.
14 shown
A
- actor
-
A concrete participant, human, agentic or mechanical, that persists across every process and takes on roles. Which login is which actor is the data store's to know.
- closeMatch: www.w3.org/ns/prov#Agent
- associated harness
-
A harness this one knows by name, site and repository, and never loads, builds or copies. The fourth relation beside depends (needs), references (remoteGraphs) and utilizes (dependencies).
B
- bean
-
One item of the agent work plan, held by the beans CLI in the committed beans/ store, with a status, a parent and the beans it blocks.
E
- external schema
-
A record of a specification the platform depends on but does not hold: which authority publishes it, which version is conformed to, and the operative terms used from it.
J
- JSON Schema
-
A JSON document that describes the shape of other JSON documents. In the platform, a node schema and a skill's input and output contracts are each a JSON Schema file.
- closeMatch: json-schema.org/draft-07/schema#
K
- KG QA report
-
A committed QA sidecar recording, for one knowledge-graph subject such as a process, role or skill, which of its references fail to resolve under each audit criterion.
P
- permission
-
One ODRL rule allowing an assignee an action, optionally on a target and within constraints. A permission to a broader action permits every action included in it.
- exactMatch: www.w3.org/ns/odrl/2/Permission
- policy
-
Which Actor may do which action, and where, written as W3C ODRL 2.2 permission and prohibition rules scoped by Process, Task and Role.
- exactMatch: www.w3.org/ns/odrl/2/Policy
R
- role
-
The swimlane: a persona an actor takes on because of the lane it is acting in, carrying the skills that lane's activities need.
T
- task run
-
One performance of a BPMN task by an Actor in a Role under a policy, recorded as a W3C PROV-O activity whose plan is the task.
- closeMatch: www.w3.org/ns/prov#Activity
- test run
-
One measurement of a Skill: which skill it tests, the cases it exercised, and a hash of the data and a hash of the process that produced the result, so a third party can redo it. Its cases are checked against the skill's input and output contracts.
- todo
-
One person's outstanding work, as a content node the folio owns, tagged with the roles, processes and tasks it concerns. Not the agent work plan, which is beans.
U
- user story
-
What a reader acting in a Role is trying to do, told as that role: as a <role>, I want <want>, so that <so that>. The story points at its role; the role names no story.
V
- voice
-
A named set of writing rules for prose, active in the roles and processes it names. The voice points at the role it is written for; the role names no voice.