Our mandate is narrow on purpose.
Make continuous, policy-governed participation in onchain distribution events available to serious desks — without asking them to surrender custody, control, or the ability to explain themselves afterwards.
Everything we have declined to build follows from that sentence. We do not manage anyone's assets. We do not take discretion over anyone's balance sheet. We do not publish the methods behind the standard we hold. And we do not expand scope into adjacent businesses that would put us on the other side of our customers' interests.
A narrow mandate, held for a long time, compounds. A broad one rarely survives contact with the first conflict of interest.
What we kept running into.
The pattern was the same at every desk we spoke to. The opportunity was understood. The analysis was not the hard part. The hard part was that capturing it required someone to be present, attentive and consistent at hours no organisation can reliably staff — and then to reconstruct, weeks later, what had been decided and why.
So the work got done heroically or not at all. Results depended on who happened to be awake. Reconciliation was archaeology. And the honest answer to “why did we skip that one?” was usually that nobody saw it.
None of that is a strategy problem. It is an infrastructure gap. We built the system we wanted those desks to have: always present, identically disciplined, and incapable of forgetting what it did.
“Presence is not a virtue you can hire for. It is a property you have to build.”
The founding observation, and still the sentence the roadmap is measured against.
Six commitments we will not trade.
Each of these has already cost us something. That is how we know they are real.
Custody is never ours
We do not hold customer assets and have built nothing that would let us. This is structural, not a policy we could revise when it became inconvenient.
The record is not optional
If an action cannot be recorded, attributed and exported, it does not ship. Evidence is a feature of the same rank as capability.
Declines are outputs
A system that only reports what it did is hiding half the story. We treat a documented no as a deliverable.
Reticence by default
We describe commitments and evidence, never mechanisms. Our customers benefit from a standard that stays proprietary.
Limits are enforced, not advised
A posture that can be quietly overridden is decoration. Breaches are declines, every time.
Jurisdiction is respected
Where something is not available to a customer, we do not pursue it for them. This costs us revenue and we consider that correct.
How we expect to be held to it.
A platform asking to operate continuously inside someone else's mandate should state the standard it holds itself to — in terms that can be checked.
Availability is a commitment, not a target
Coverage is the product. Interruptions are treated as defects of the highest severity, not as expected operating noise.
Every change is reversible by the operator
Whatever we enable, you can revoke — immediately and without discussion. Authority flows one way.
No silent behaviour changes
Anything that alters how your mandate is executed is visible to you before it takes effect, and recorded when it does.
Support speaks to operators, not tickets
Escalation goes to people you can name. We do not route desk-level questions into a queue.
Hired for temperament.
We are deliberately quiet about individuals. What matters to a customer is the disposition of the people on the other side of the mandate.
Operators
People who have carried a number on a desk and know what a defensible answer looks like.
Risk
People whose instinct is to ask what the limit is before asking what the upside is.
Reliability
People who treat an interruption as an incident with a root cause, not an inconvenience.
Controls
People who care that the record would survive an auditor reading it line by line.
A short history, honestly dated.
Thesis
The pattern is identified across a dozen desks: the constraint is presence, not analysis.
First coverage
Continuous observation runs end to end for a single mandate, with a complete record.
Policy engine
Qualification becomes operator-configurable, with declines recorded as deliberately as actions.
Mission Control
The operator surface consolidates coverage, exposure, settlement and exceptions into one view.
Institutional controls
Role separation, session governance and export-grade reporting reach general availability.
Operator mandates
Accepting new mandates with scope and controls confirmed before anything is enabled.
Part of Ventureship.
AutoAirdrops operates inside Ventureship, which means shared identity, shared security standards and shared governance across every platform in the group.
Practically, an operator authenticates once and carries that identity — with its roles and its limits — wherever they are entitled to go. Credential policy, session governance and access review are group-level concerns, held to one standard rather than reinvented per product.
Talk to the teamWhat we refuse to do.
A platform that operates autonomously should be unusually clear about its own limits.
We decline business we should not take
Where a mandate cannot be operated within a customer's jurisdiction, we say so and walk away from it.
We do not market urgency
There is no countdown, no scarcity theatre and no implied return on this website. The case either stands on its own or it does not.
We state risk plainly
Digital assets can lose value. Participation can fail. Nothing we operate changes either fact, and we never suggest otherwise.
If presence is your constraint, we should talk.
Scope, controls and settlement arrangements are confirmed in writing before anything is enabled.