Operation Board
This board is the entry point for the 18 YOps operations. Use it to choose the operation family first, then open the operation page for parameters, behavior, errors, and examples.
DDL: Structure
| Op | Use it when | Reference |
|---|---|---|
define | Create a new empty mapping path | Strict container creation |
drop | Remove a node or subtree that must exist | Strict deletion |
rename | Rename a key without moving its value | Same-parent key rename |
DML: Values
| Op | Use it when | Reference |
|---|---|---|
set | Set one scalar, list, or mapping value | Upsert with lazy mapping creation |
unset | Remove one key but keep the parent | Idempotent key cleanup |
populate | Fill several fields on the same existing mapping | Multi-field mapping write |
append | Add one item to a sequence | Sequence append |
DTL: Reshape
| Op | Use it when | Reference |
|---|---|---|
move | Relocate a subtree | Source removed, destination created |
clone | Copy an existing subtree | Deep copy |
nest | Group sibling keys under a new wrapper | Flat to nested |
split | Split one mapping into named children | One mapping to multiple groups |
fold | Collapse a single-child wrapper | Nested to flatter |
merge | Combine sibling mappings | Multiple mappings to one |
sort | Sort a sequence | Deterministic sequence ordering |
unique | Deduplicate a sequence | Keep first occurrence |
pick | Keep only specific keys | Mapping allowlist |
omit | Remove specific keys | Mapping denylist |
DCL: Check
| Op | Use it when | Reference |
|---|---|---|
assert | Verify state without changing it | Read-only guardrail |
How To Read The Board
Use DDL when the shape is wrong. Use DML when the values are wrong. Use DTL when the information is present but arranged badly. Use DCL when you need a guardrail before later operations continue.
yops:
- assert:
path: support_escalation_review/refund_policy/threshold
equals: Refunds above $100 require manual review
- append:
path: support_escalation_review/refund_policy/required_evidence
value: agent name
- unique:
path: support_escalation_review/refund_policy/required_evidence
This sequence says: first prove the current threshold is the one we expect, then add a new required evidence field, then dedupe the list.