A loaded playbook now decides a real task's workflow. The wiring point is the daemon's definition pin (Daemon.resolveWorkflowID, consumed by pinWorkflowFromCollection), not pollNATS/publishTask as the design doc assumed: routing moved out of the agent process when workflow definitions became database rows pinned before dispatch, so the pin is the one place a task's workflow is chosen. Precedence: an explicit Task.Workflow (the waiting_human -> approved requeue) still wins, then a matching playbook, then workflow.ResolveWorkflowID's existing label/kind bindings. A playbook naming an undefined workflow is a reported failure that parks the task rather than a silent fall-through to the binding's choice -- the operator bound that trigger deliberately. Store.Dispatch returns the selected workflow name plus the matching playbook's id and version, instead of a compiled workflow.Workflow: the production caller decides against the active definition collection, and the id/version are the first two components of the resolved gap-2 idempotency key. The playbook package no longer imports internal/domain/workflow. The shipped example's `when` read event.priority, a field no intake supplies, so it could never have fired once wired. Both examples now read the event surface playbookInput really builds, and label-trigger.yaml documents the axis an instance defines for itself: trigger.kind is the closed workintake vocabulary because a kind addresses a NATS subject, while trigger.labels is free-form and binds an operator's own taxonomy to a workflow. Module/Channel/Forge positions stay rejected at load; they need the playbook_dispatches ledger first (archie-core-t2db.24). Closes archie-core-t2db.23
20 lines
748 B
YAML
20 lines
748 B
YAML
# Example EDA playbook triggering on an instance-defined label.
|
|
#
|
|
# The kind axis (bug/feature/bootstrap/default) is archie's own closed
|
|
# classification. This file is the other axis: a label set of your own
|
|
# choosing, matched as a subset of the issue's labels. Every label listed here
|
|
# must be present on the issue for the playbook to fire.
|
|
#
|
|
# A matching playbook decides the task's workflow ahead of the
|
|
# workflow_routing_file, workflow_labels_file and playbook_dirs bindings. The
|
|
# workflow it names must be a defined workflow; naming one that is not parks
|
|
# the task with a reported error rather than quietly running a different one.
|
|
|
|
trigger:
|
|
labels:
|
|
- ops::security-review
|
|
|
|
actions:
|
|
- position: workflow
|
|
workflow: feasibility
|