Venue adapters

An adapter declares what it can do and implements only that.

type VenueAdapter = {
  venue: string;
  kind: AccountKind;
  capabilities: { canReadBalances: boolean; canReadQuotes: boolean; canPlaceOrders: boolean };
  readBalances(request: ReadBalancesRequest): Promise<AdapterBalance[]>;
  readQuote(request: ReadQuoteRequest): Promise<AdapterQuote>;
  placeOrder?(request: PlaceOrderRequest): Promise<OrderReceipt>;
};

What ships

coingecko refuses balances rather than returning an empty list, because a price source does not know what you hold and an empty list reads as "you hold nothing".

Adding a keyed broker

1. Write a module in packages/node/src/adapters/.
2. Take the credential from the worker's environment.
3. Register it in defaultRegistry().

If you implement placeOrder

type PlaceOrderRequest = {
  // ...
  confirmation: OrderConfirmation;   // { confirmedBy, confirmedAt }
};

OrderConfirmation has no default. An order that no human confirmed cannot be constructed, which is a type error rather than a policy someone can forget.