When institutions evaluate new infrastructure, the first question is rarely "what can it do?" It is "what can it not do — and how do you know?" Here is our answer for Aros Financial Core.
1. Hold your money
AFC never takes custody. Funds in transit stay with licensed anchors — banks, payment institutions, licensed digital-asset firms — under their own licences and supervisors. There are no balances inside AFC.
2. Do your compliance for you — or skip it
KYC, AML and sanctions screening are done by the initiating institution before a request enters. Unverified flows cannot enter at all. AFC checks structure and conformity; it does not pretend to be a compliance function.
3. Route around the law
The contract does not override sanctions, currency controls or AML rules. They apply independently, and the process is designed to comply with them — never to work around them.
4. Merge liabilities
Every participant performs exactly one role in a process. No party can act as another, and no party can read another's internal systems. Responsibility stays with whoever holds the licensed function.
5. Expose what it does not need
Each participant sees only the data its role requires. The record of execution states is complete and auditable; private transaction content is fragmented and encrypted.
6. Change silently
Changing the contract requires consensus of the parties, a conformity check and a new version with a migration plan. Every process runs under a known, recorded version.
7. Leave a process half-finished
Every process instance ends in exactly one terminal state: settled, rolled back or failed. A deviation returns the process to its last consistent state, and the recovery itself is recorded.
Why publish this?
Because limits are easier to verify than promises. Our canon and its automated guards are public, and every claim on this site is meant to be traceable to a document you can check.