Integrations
Nexus is the authority; integrations are adapters and gateways around it.
| Integration | Direction | Status |
|---|---|---|
| Taiga | Nexus board → Taiga user stories (+ webhooks back) | First external board adapter |
| Telegram | Telegram commands → Nexus goals/tasks | Command gateway |
| Solana DeFi | HARVEST module ↔ Squads / Kamino / MarginFi / Jupiter Metis + Trigger / Pyth / Jito stake pool / Orca Whirlpools / Meteora DLMM via nexus-solana | Live |
| Jira | Nexus board → Jira | Later (same BoardProvider trait) |
| GitHub / GitLab | PR creation, CI polling | Via nexus-git |
Design stance
- External boards are projections through
BoardProvider— swapping Taiga for Jira is implementing one trait. - The command gateway (Telegram) never bypasses approvals; sensitive actions
still route through the UI approvals
queue. HARVEST is the exception by design: its sell/CEX/fallback approvals
are Telegram-native (
/pending,/approve <id>,/reject <id>) overoperator_digestsrows, so the operator can act from the phone.
See Board sync for the projection mechanics.