Skip to content

Business Rules (v1)

This page captures high-impact behavioral rules that are stable enough for product/domain understanding.

Ownership and scope

  • Most data and operations are user-scoped.
  • Write operations enforce user ownership checks before persistence changes.

Onboarding behavior

  • New users start with onboarding required.
  • Onboarding is disabled once key setup actions are completed (for example adding a credential, wallet, or first manual transactions).

Connexion rules

  • Credential and wallet names must be unique per user.
  • Wallet address duplication is blocked for existing user wallets on supported chain groups.
  • Import jobs are emitted when connexion status is IMPORTING.

Synchronization rules

  • Credentials/wallets in IMPORTING state are rejected for direct synchronization calls.
  • Bulk synchronization only processes eligible auto-sync connexions.
  • Reconciliation may add, update, convert, or cancel transactions to restore consistency.

Coherence and consistency rules

  • Transaction add/update/delete is coherence-checked.
  • If an operation would create insufficient holdings, it is rejected.
  • Negative holdings are not allowed.

Strategy execution rules

  • Strategy completion happens when:
  • a stop-on-execution action triggers, or
  • all actions are executed.
  • Strategy-generated orders create tracks and events for auditability.

Calculation and valuation rules

  • Position and portfolio metrics use multi-quote values (EUR, BTC, ETH, USD by default).
  • Missing price data does not always stop processing; partial outputs may be produced with warnings.

Service boundary rules

  • UI apps consume webservice-facing APIs.
  • Worker handles async execution and record jobs.
  • Portfolio SOA owns portfolio/position/coherence calculations.
  • Findata SOA owns market/news ingestion and retrieval.
  • Webservice acts as gateway/orchestrator, not as owner of all downstream logic.

Subscription and quota rules

  • Connexion and related limits depend on the user’s subscription tier and configured quotas in the webservice; usage is tracked and enforced on adds (and comparable write paths).
  • The agent enforces per-user monthly agent call limits by tier and chooses the LLM model from tier for user-scoped jobs.

Details and operations guidance: Subscriptions and quotas.

Related: