You operate a DAO treasury and want an agent that reallocates idle stablecoins toward the best risk-adjusted yield, subject to mandate constraints. Alterscope provides the data and the signals; the agent makes the call; your existing executor signs the transaction.
Alterscope does not execute transactions on your behalf. This recipe ends at the decision; the actual write to chain is your codebase.
What you build
A loop that, on each tick or on each vault.cap.changed event:
- Pulls the candidate opportunity universe.
- Scores each candidate against the current portfolio.
- Picks the top reallocation that satisfies your mandate.
- Emits a signed proposal to your executor.
1. Discover candidates
2. Score each candidate against the current book
3. Apply mandate constraints
Encode your policy as code, not as prose. Common constraints:
- Per-protocol cap: no more than 30% of treasury in a single protocol.
- Oracle-provider cap: no more than 50% of treasury behind a single oracle provider.
- Reject any candidate whose
meta._agentic.freshness.status is not fresh.
- Reject any candidate whose
risk.dominant_factors[0] is oracle.stale_risk or peg.deviation.
4. Emit a signed proposal
5. Audit trail
Log every decision, including the ones that were rejected and why. The request_id in meta.request_id ties the proposal to the exact API responses that produced it.
6. Tier requirements
Factor attribution and stress scenarios require the Analyst tier or higher (the read:yield:detail scope). WebSocket triggers (a tighter feedback loop than polling) also require the Analyst tier or higher. Custom factors and per-route uplift require Enterprise.