Channel Relays & Notifications

Niyatna keeps company participants aligned by routing important events back to the channels where work happens.

A notification should not dump noise. It should explain what changed, what proof exists, and whether someone needs to approve, revise, or respond.

Relay event types

• Intent accepted: A request has been converted into owned work.
• Work assigned: A human, agent, or mixed path now owns the next step.
• Review needed: A staged action requires approval before completion.
• Proof ready: Evidence is available for inspection.
• Blocked: The work hit a missing permission, unclear context, or boundary constraint.
• Reported back: The requester receives the final result and proof summary.

Alert structure

Every useful notification should answer:

intent → owner → status → proof → action required

Relay rule

Send the smallest message that lets the right person act. If the channel cannot show the proof directly, link to the proof surface instead of pasting noisy logs.