x-pulse-xint-complementary-not-replacement
Replacing X-Pulse with xint loses X-Pulse’s superior 3-phase research pipeline, Jaccard dedup, entity follow-up, and geo-proxy routing — xint’s x_search is single-phase only. The correct architecture keeps X-Pulse as the research workhorse and adds xint for its 50+ orthogonal capabilities (direct API metrics, streaming, analytics, engagement). A single unified skill abstracts routing so the agent never needs to know which tool handles each task.
Related
- x-intelligence-dual-tool-architecture-decision
- xint-xpulse-complementary-dual-tool-architecture
- xint-vs-xpulse-capability-gap-56-commands
- 2026-04-04-oracle-001-self-architecture-analysis
- enterprise-capability-expansion-5-pillars-from-digital-employee-analysis
- xint-xai-geo-proxy-via-base-url-env-override
- xint-phase1-deploys-with-existing-xai-key
- xpulse-vs-xint-capability-routing-split
- xint-geo-proxy-via-xai-base-url-override
- xint-phase1-health-shows-error-without-bearer-token
- xpulse-xint-complementary-not-replacement-architecture
- xpulse-xint-complementary-not-replacement
- xpulse-and-xint-complementary-not-replacement
- dual-tool-architecture-xpulse-plus-xint-routing-via-skill
- xpulse-xint-complementary-dual-tool-routing
- xint-complementary-dual-tool-routing-architecture
- x-pulse-and-xint-are-complementary-not-interchangeable
- xpulse-xint-complementary-not-competitive-architecture
- xint-complementary-dual-tool-architecture