X/Twitter Status
X/Twitter is not an active Hub Signal Source surface in the current public product direction. Do not treat it as a trading command channel, reply bot, or guaranteed social automation product.
For active source workflows, use:
Current positioning
| Capability | Public-doc status |
|---|---|
| Source ingestion | Not active unless a future verified implementation exposes it. |
| Mention monitoring | Do not promise. |
| Reply posting | Do not promise. |
| Proactive posting | Do not promise. |
| Trading execution | Not a direct execution surface. |
X/Twitter API access, rate limits, and write permissions are controlled by X's developer platform. Balchemy cannot bypass those constraints.
If X/Twitter returns later
If a future architecture decision enables X/Twitter, it should follow the Signal Source model:
- source health,
- CA/token-signal detection,
- allowed/blocked/trusted submitters,
- attribution metadata,
- no auto-response chat bot behavior,
- no direct trade execution bypass.
Trading would still pass through Hub rules, runtime mode, risk, scope, replay, approval, and reconciliation gates.