Decision log
The decisions that shape Float, and why
The handful of decisions most relevant if you're evaluating Float.
| Decision | Why |
|---|---|
| Float is non-custodial. It never disburses, holds or moves funds, and obligations are registered after a partner has financed. | Fewer moving parts, and no custody or lending risk sits with Float. |
| Reputation uses Float-verified evidence only. | Portable reputation has to be independently checkable, and it applies equally to good and bad outcomes. |
| A wallet proof is the only cross-partner identity link. | Hard to spoof, and no merging of business records to get wrong. |
| Private and public data are kept apart. Only fingerprints are ever public. | Partners and their customers keep control of what is shared, and with whom. |
| Credit lines share the invoice engine. They are a second kind of request on the same underwriting and reputation system. | One set of businesses, consent rules, events and reputation, not two. |
| Chain observation is enabled per environment. | Nothing silently depends on a network connection. |
Open decisions#
Still being decided, and not assumed anywhere in the product: production document retention, the final risk band taxonomy, and how reputation is banded. See the Roadmap.