Maestro splits in two, MCP goes stateless, and an e-invoice deadline lands
Issue one: the architectural split behind UiPath FUSION, Gartner’s warning on vendor-built agents, the new MCP spec, the EU AI Act calendar, Türkiye’s 1 January 2027 e-Arşiv rule and IXP’s new pricing unit.
As this is the first issue, the window is wider than a week. Six items from recent weeks that could change the budget, the architecture or the calendar of an automation programme. They share a thread: as the tools mature, the question moves from “can it do this?” to “who will own it, and what will it cost?”
UiPath FUSION 2026: Maestro is now two products
At FUSION 2026 UiPath split Maestro in two. Maestro Orchestrate is for long-running processes that cross teams and systems; Maestro Automate is for small, fast, high-volume tasks. Several things went generally available in the same announcement: Cartographer, which drafts and maintains a “Map of Work” from documents, systems and people; UiPath for Coding Agents, which lets developers build with the coding agent they already use; and Delegate, a desktop agent. Dark Testing Factory is in preview and the Map of Work itself is on the roadmap.
Why it matters. The split turns a decision teams already make into a product boundary. A case that stays open for weeks waiting on human approval and a queue item that finishes in seconds shouldn’t be governed by the same rules. Make that distinction in your architecture documents now: which processes hold state, and which only carry volume? I’d treat Cartographer as a way to keep the PDD current, not as a replacement for writing one. My first test would be a small process that already has documentation, comparing the output against what’s on file.
Gartner: most vendor-built agents will be abandoned
Gartner’s 29 September release predicts that 70% of enterprises will abandon agentic AI built by a vendor’s forward-deployed engineers by 2028. The published summary points to rising costs and to organisations being unable to evolve these systems on their own. Gartner’s page blocks automated access, so this item rests on the release title and its published summary.
Why it matters. Outsourcing an agent build isn’t the problem. Being unable to maintain what you received is. I would put three things in the contract: versioned prompts and tool definitions, the evaluation sets used in acceptance testing, and at least one change made by the internal team alone after go-live. If the third can’t happen, what you have is a dependency, not a product.
Model Context Protocol 2026-07-28: the protocol is now stateless
The 28 July release moves MCP’s core to a stateless request-response model. The initialisation handshake and session IDs are gone; each request carries its own version and capability information. When a server needs input mid-call it now uses Multi Round-Trip Requests, and method and tool names travel in HTTP headers (Mcp-Method, Mcp-Name). Authorisation was tightened, and Tasks, MCP Apps and Enterprise Managed Authorization became official extensions. Roots, Sampling and Logging are deprecated, with at least twelve months to migrate.
Why it matters. If you run MCP servers in-house there is good news on two fronts. Servers scale horizontally without sticky sessions, and a gateway can see which tool is being called and apply policy without opening the request body. That gives you something concrete to discuss with the security team. The work is clear too: list which of your servers use the deprecated features now. Twelve months is short if you don’t have an inventory.
EU AI Act: high-risk delayed, transparency not
Regulation (EU) 2026/1744, the Digital Omnibus on AI, entered into force on 27 July, three days after publication. Obligations for high-risk systems under Annex III move to 2 December 2027, and those for systems embedded in products under Annex I to 2 August 2028. The Article 50 transparency duties did not move; telling people they are dealing with an AI system has applied since 2 August 2026. Providers whose generative systems were on the market before that date get a four-month transition for machine-readable marking of outputs, which ends on 2 December 2026.
Why it matters. For Turkish companies serving the EU, or with EU customers, the order of work has changed. There’s breathing room on high-risk classification, but if a chatbot talks to customers or a flow generates text for them, the disclosure duty is current. I’d start with an inventory: in which flows is a person corresponding with a model without knowing it?
Türkiye e-Arşiv: the last quarter for small taxpayers
General Communiqué No. 589 on the Tax Procedure Law gave taxpayers on the simplified method or business-account basis, who are outside e-Fatura and e-Arşiv, one extra year. Until 31 December 2026 they may issue invoices up to 3,000 TL including taxes on paper; anything above must be issued as e-Arşiv through the GİB portal. From 1 January 2027 every invoice they issue, whatever the amount, must be e-Arşiv. For other taxpayers the same rule has applied since 1 January 2026.
Why it matters. Companies that buy from many small suppliers still see paper or scanned invoices in accounts payable. Expect that channel to shrink in 2027. If you run an OCR flow for paper invoices, redo next year’s volume forecast with this change in mind. I’d move the freed capacity to integrations that take e-document data straight into the ERP.
IXP: priced per operation, not per page
Since 8 July, UiPath meters IXP extraction from unstructured and complex documents per operation rather than at a flat rate per page, and IXP and Document Understanding licences can be used together without extra per-page cost. On 23 July an option to deploy a model version straight to an Orchestrator folder entered preview. On 14 September Bring Your Own Subscription opened in preview: IXP can run on an organisation’s own Gemini or GPT subscription, eligible projects get discounted consumption, and AI Trust Layer policies still apply.
Why it matters. Document-processing business cases are usually built on page counts. Change the unit and the maths changes, and only your own sample will show which document types it helps and which it hurts. Re-run the business case on a real month of documents. For organisations that already hold a model subscription, BYOS adds an option in conversations about data residency and price. It’s still a preview, though.
Over the coming weeks I’ll be watching two things: availability dates for Maestro Orchestrate and Automate, and what model providers publish as the 2 December marking date approaches.
Sources
- The biggest product announcements from UiPath FUSION 2026
UiPath, September 23, 2026 · Accessed October 7, 2026 - Gartner Predicts 70% of Enterprises Will Abandon Agentic AI Built by Vendor Forward-Deployed Engineering by 2028
Gartner, September 29, 2026 · Accessed October 7, 2026 - Regulation (EU) 2026/1744 (Digital Omnibus on AI)
EUR-Lex, Official Journal of the European Union, July 24, 2026 · Accessed October 7, 2026 - Yes, August 2 Still Matters: The EU Approved a High-Risk AI Delay, but Most Transparency Obligations Remain
Jones Walker LLP, July 16, 2026 · Accessed October 7, 2026 - E-Arşiv invoicing obligation for taxpayers outside e-Fatura and e-Arşiv, revised for simplified-method and business-account taxpayers (Legislation Circular 02.01.2026/16, in Turkish)
TÜRMOB, January 2, 2026 · Accessed October 7, 2026 - IXP Release notes — Unstructured and Complex Documents, July 2026
UiPath Documentation, July 8, 2026 · Accessed October 7, 2026 - IXP Release notes — Unstructured and Complex Documents, September 2026
UiPath Documentation, September 14, 2026 · Accessed October 7, 2026
This radar is compiled by an AI-assisted research pipeline in which every item links to its primary source. The commentary is mine. If you spot a mistake, write to me and I will fix it.