The agent assembled a workable explanation of Soul as Emplifi's internal design system by relying heavily on web search results and documentation fetches from soul.emplifi.io, since the primary target domain (soul.dev.emplifi.io) returned only a Storybook component showcase with limited accessible content. The site is poorly navigable for agents: the dev subdomain blocks documentation access (403 errors), the main site uses heavy client-side rendering that hides content in static HTML, and the relationship between the two domains is unexplained. The agent had to work around these barriers using prior knowledge and search to construct an answer that was partially complete but missing key details like pricing, commercial availability, and the purpose of the 'Alpha' designation.

• ›soul.dev.emplifi.io returned only a Storybook shell with no substantive content; attempts to fetch documentation (/docs/overview) were blocked with 403 Access Denied, forcing the agent to pivot entirely to soul.emplifi.io
• ›Web search (steps [5], [6]) was essential: the search results snippet lists from Supernova pointed the agent to the working documentation URLs, which the agent then fetched directly (steps [10], [11]). The agent did not discover these URLs from the site itself
• ›soul.emplifi.io uses client-side rendering; fetched HTML contained only meta tags and redirect scaffolding, not the actual page content. The agent could not extract substantive information from static HTML and had to rely on search results and prior knowledge to fill gaps
• ›The agent correctly identified that pricing, commercial model, and access policies were not publicly documented anywhere. This represents a genuine information gap, not a navigation failure
• ›The agent cited three working documentation URLs in its sources ([10], [11], and a Medium article from search), but these were discovered via search routing, not by navigating the site interface itself