ash-backend

Files (4)

• SKILL.md
• openai.yaml · agents/
• decision-guide.md · references/
• integrations.md · references/

SKILL.md (first lines)

# Ash backend

Load `ash-stack` first; its shared rules apply.

- Business rules live in Ash actions and policies; plain computation stays ordinary
  Elixir.
- Prefer a built-in to a custom change, and a custom change to a manual action, when
  each expresses the requirement correctly.
- Named domain interfaces and action-bound forms are the application boundary. A
  one-line interface is not waste: remove a local wrapper only when it adds no
  behaviour, callback contract, actor propagation or error handling.
- Durable, retried or scheduled work is Oban ([elixir-stack](../elixir-stack/SKILL.md)).
  One resource reacting to another's action is an Ash signal
  ([ash-signals](../ash-signals/SKILL.md)).
- Idempotency, outbox and locking patterns never apply to a person's wallet send: every
  press reaches the wallet. A wallet panel's signer is Privy's active wallet when the
  server finds it among the signed-in account's linked wallets, checked against the
  verified session; any other wallet is ignored (regent-workflow, "Wallets and
  transactions").

## References

- [Action and resource decisions](references/decision-guide.md): accepted inputs,
  relationships, derived values, choosing an implementation boundary.
- [Integrations](references/integrations.md): jobs, external effects, adapters.

From regents-ai/ash-template, MIT.

More from regents-ai/ash-template