Sexy
Documentation
Show how it works.
One skill for clear system maps, useful examples, and documentation people can actually follow.
Where does the number come from?
Follow a sale through the rules to a reviewed payout.
Ticket desk
Sales and refunds
order H-104 · $1,000
Rate workbook
Approved business rules
net revenue × 10%
Access: operations admin
Warehouse
Join the sale to its rule
$1,000 − $200 = $800
Payout report
Calculated, not approved
$800 × 10% = $80
Access: data platform admin
Payroll review
Reconcile and approve
review $80 for H-104
A report refresh does not mean the payout is approved.
Access: payroll admin
Step through to follow one record.
A negative adjustment can be correct.
A $1,000 eligible sale creates $100 in commission.
See the commission rule
Eligible change × 10% = commission change
A refund reverses the commission on that refund at the same 10%. It is not a second charge for the original sale.
Automation changes the handoffs.
Same approved report. Review still belongs to a person.
Manual release
- AnalystExport the approved file
- AnalystUpload to the target workspace
- AnalystCheck settings and refresh
- Report ownerReview the published result
Each handoff depends on someone repeating the procedure.
Pipeline release
- AnalystCommit the approved change
- PipelineValidate and deploy to the target
- PipelineApply configured checks
- Report ownerReview the published result
Repeatable deployment; business acceptance stays explicit.
The method behind the examples.
Get the complete skill ↗- Show the source
- A product name needs a role and an example record.
- Keep the useful detail
- A good dropdown reveals a rule. A bad one hides the answer.
- Make interaction earn its place
- A control changes the model, not just the decoration.