Governance
Governance at AlphaPing defines decision boundaries, change control, and accountability for mandate-driven vault operation.
It specifies what can be configured, what is fixed, how changes are executed, and how exceptions are handled, without relying on discretionary overrides or custodial control.
Governance Scope
This governance framework applies to the definition and maintenance of vault mandates, permitted configurations, and operational processes used to execute those mandates.
It does not introduce discretionary investment decision-making. Vault behavior is determined by mandate constraints, protocol mechanics, and on-chain execution.
Decision Boundaries
Governance distinguishes between parameters that are configurable per mandate, parameters that are fixed by protocol mechanics, and actions that are explicitly out of scope.
The table below summarizes these boundaries at a high level. Exact values and permitted ranges are defined per mandate and implemented through protocol configuration.
| Category | What This Covers | Governance Treatment |
|---|---|---|
| Configurable (Per Mandate) | Asset eligibility, market eligibility, allocation bands, collateral constraints, liquidity posture | Defined in advance; changes require explicit mandate update and documented configuration |
| Fixed (Protocol-Defined) | Execution sequencing, settlement mechanics, liquidation execution logic, on-chain accounting rules | Not overridden by AlphaPing; outcomes follow protocol and network behavior |
| Explicitly Out of Scope | Custody, discretionary overrides, guarantees, loss absorption, manual outcome modification | Prohibited; not provided as part of AlphaPing operation |
Roles and Responsibilities
AlphaPing operates the mandate enforcement and operational operation layer. This includes deployment, configuration within mandate bounds, monitoring, and execution coordination consistent with predefined constraints.
Third-party protocols define execution logic, settlement behavior, liquidation mechanics, and on-chain accounting rules. Protocol governance and smart contract behavior remain external dependencies and are not controlled by AlphaPing.
Where relevant, AlphaPing interfaces with ecosystem participants such as asset issuers and institutional counterparties to support mandate-defined execution and operational coordination, without assuming custody or discretionary control.
Change Control
Mandate changes are treated as explicit governance events. Changes that affect eligibility, constraints, or allocation behavior must be defined in advance, reviewed for consistency with the operating model, and implemented through controlled configuration updates.
Changes that cannot be safely expressed through permitted configuration require redeployment or a new mandate instance. AlphaPing does not apply ad hoc changes intended to influence outcomes after execution.
Escalation and Exceptional Conditions
Exceptional conditions are handled through predefined processes rather than discretionary overrides. Where escalation is required, actions remain constrained by mandate permissions and protocol mechanics.
There is no separate “stress mode” or hidden intervention layer. Under stress, enforcement and accounting continue according to the same rules that govern normal operation.
What Governance Does Not Do
Governance does not provide guarantees or assurances of performance, liquidity, pricing, or outcomes.
It does not introduce custody, discretionary investment decision-making, manual liquidation control, or override of protocol execution and on-chain settlement. It does not provide insurance, loss absorption, or compensation.