Notifications & Updates
Send high-signal status, proof, and approval requests back to the right company channels.
Niyatna keeps everyone aligned by sending important updates back to the places where work already happens.
A notification should not dump noise. It should explain what changed, what proof exists, and whether someone needs to approve, revise, or respond.
What gets sent
- Request accepted: A request has been turned into owned work.
- Work assigned: A human, agent, or mixed path now owns the next step.
- Review needed: A staged action needs approval before it can finish.
- Proof ready: Evidence is available for inspection.
- Blocked: The work hit a missing permission, unclear context, or a boundary.
- Reported back: The requester receives the final result and proof summary.
What a good update says
Every useful notification should answer:
request → owner → status → proof → action requiredThe rule
Send the smallest message that lets the right person act. If the channel cannot show the proof directly, link to it instead of pasting noisy logs.