Operational brief
Dash
Process Street's shared Slack and Teams teammate for reports, connected-tool work, and approval-gated writes.
Choose it when
You want a shared operations teammate in team chat that can prepare recurring reports and hold every send, post, write, or spend for approval.
Skip it when
You need to host the runtime and credentials yourself, or you do not work in Slack or Microsoft Teams.
01 / Classification
Autonomy evidence
This is our classification, not a vendor badge. The record says what the product normally does. The gaps stay visible.
02 / Operations
Control reality
Useful agents eventually touch something real. This is the operational picture we have, not a promise hidden in a sales page.
03 / Receipts
Evidence ledger
Here is what this brief is built on. “Documented” means we found a source. “Tested” means this desk actually ran it. Those are different things.
Sources on file
Corrections
Not recorded yet. If we change a material claim, the correction belongs here.
04 / Change log
Related coverage
The brief tells you what the product is. Payloads track the changes that may alter the decision.
No linked change coverage on file yet.