AAA vs manual allocation
Manual allocation is a default, not a strategy. It works until it doesn't — until a key person leaves, a governance vote is disputed, or an auditor asks why a specific decision was made. AAA is built for the environments where those questions are inevitable.
Head-to-head comparison
| Dimension | Manual allocation | Sagitta AAA |
|---|---|---|
| Consistency | Decisions vary with the individual, their stress level, and the prevailing narrative. The same situation on two different days may produce two different decisions. | Identical inputs always produce identical outputs. Policy constraints are enforced mechanically, not interpreted situationally. |
| Auditability | Decisions are hard to document retroactively. Meeting notes, chat messages, and spreadsheets are not audit trails. | Every allocation produces a structured decision record: portfolio snapshot, policy version, constraint evaluation log, and resolved output — all machine-readable and timestamped. |
| Governance alignment | Policy documents don't constrain execution. Treasury operators or fund managers may deviate from ratified mandate without realizing it. | Policy is encoded as machine-checkable constraints. The allocator cannot produce outputs that violate active policy. Alignment is structural. |
| Continuity across personnel changes | When a key person leaves, institutional memory about allocation rationale often leaves with them. | Policy is versioned and explicit. Decision records are persistent. New operators work within the same documented constraint set. |
| Stress testing | Manually modeling how different policies perform under regime changes is slow, inconsistent, and rarely done before capital is exposed. | A/B policy comparison and regime simulation are built-in. Multiple allocation strategies can be tested against the same portfolio state before any commitment. |
| Defensibility under scrutiny | Explaining a decision under governance review or to a regulator requires reconstructing reasoning that may not have been documented at the time. | The decision record contains all the justification required: what constraints were active, what the portfolio state was, and why the allocation resolved as it did. |
| Custody exposure | Manual allocation requires operators who can actually execute — often with signing permissions or direct access to execution infrastructure. | Non-custodial by design. Decision authority and execution authority are fully separated. AAA never holds keys or requests signing permissions. |
When manual allocation is adequate
Manual allocation is adequate when decisions are low-stakes, infrequent, and made by a single person with no governance obligations. As soon as allocation decisions involve multiple stakeholders, require accountability to token holders or committees, must be explainable under audit, or happen at any meaningful frequency — manual processes become a liability. AAA is built for the second environment.
Observer access is free. See how policy-driven allocation compares to what you're doing today — without any commitment or custody requirement.
Launch evaluation