Docs/How Neuron works

Rules & SOPs

Data explains what happened. SOPs explain what should happen.

Bring the rule to the object

A purchase order can state an amount and an approver. A policy explains whether that approval is appropriate. Joining the facts to the relevant rule is what makes a compliance question meaningful.

Illustrative purchase order
Amount: ₹8,50,000
Approver: Manager

Illustrative approval policy
Above ₹5,00,000 → Director approval required

One rule, two behaviors

In the architecture design, Ask could identify purchase orders that do not follow the approval policy. A Run could apply the same rule whenever a new purchase order becomes available. Both would depend on the same governed-by relationship and source provenance.

Architecture example · One rule, two behaviors
  1. Purchase Order
  2. Governed by → Approval Policy
  3. Ask / Run
  4. Evidence

Available now

SOPs are saved as searchable text. Supported invoice checks use fixed ID, reference and amount comparisons. They do not derive logic from uploaded policy documents, interpret contracts or certify compliance. Review a policy excerpt alongside the original records.