The action path
- The AI prepares a typed action with the proposed inputs.
- OpenNeko evaluates the action against deployment policy.
- The request runs automatically, waits for approval, or is denied.
- A connector or solution pack performs the approved change.
- OpenNeko records the request, decision, result, and available evidence.
Set policy by consequence
| Policy | Use it when | Example |
|---|---|---|
| Allow | The change is narrow, reversible, and safe within fixed limits. | Update an internal record field. |
| Require approval | A person should confirm the target, amount, audience, or timing. | Publish a catalog change or send a customer message. |
| Human-only | The action moves money, carries legal consequence, or should never be delegated. | Approve a refund or change payout settings. |
| Deny | The connector capability should not be available in this deployment. | Any write outside the approved operating scope. |
Use explicit limits for bulk work: maximum rows, fields that may change, required preview, and whether a safe inverse change-set exists.
Review an action
- Confirm the target system and affected records.
- Compare the proposed values with the source evidence.
- Check whether the change is reversible and how partial failure is handled.
- Approve only the displayed request; do not treat approval as blanket permission for later runs.