| aa7b4feb98f1b393… | Ingestion, transformation, refresh, and reconciliation processes continue to run in Fabric pipelines under the proposed architecture. | active | contextual | yes | |
| 34d89d84f9970e20… | Company data remains in OneLake as the system of record under the proposed approach so that core enterprise data stays in Fabric. | active | contextual | yes | |
| 8a4109730f0c8245… | Pyrana is described as designed to satisfy the Fabric mandate rather than circumvent it. | active | contextual | yes | |
| 5df2461a4f782da1… | The RFP also requires that any platform outside Fabric be documented and approved by Summer Fridays IT before it is used. | active | contextual | yes | |
| 74cd3b42d96a2a98… | The RFP requires that the solution be built within Summer Fridays' approved Microsoft Fabric environment unless IT grants a written exception. | active | contextual | yes | |
| dd5ba37bdce6e4e4… | Pyrana is characterized as effectively being Path B already built, governed, and supported. | active | contextual | yes | |
| e3dd53846fcd32ea… | The document states that the scope, timeline, and maintenance risk of Path B are the very burdens a vendor is supposed to eliminate. | active | contextual | yes | |
| 1f1e77f886fa0550… | The document concludes that Path B can satisfy the governance bar, but only as a build-it-yourself integration program layered on top of the data project. | active | contextual | yes | |
| f393997b2ca1fcc5… | The document concludes that Path A is fast but too limited to satisfy the RFP's governance standard. | active | contextual | yes | |
| aa1125650e2c8ab3… | Path B also requires the organization to own integration, testing, security hardening, and lifecycle management for the custom agent solution. | active | contextual | yes | |
| 09dab346cf09dba0… | Under Path B, the organization must assemble and own runtime, orchestration, retrieval, provenance and citation governance, prompt-injection defenses, telemetry, and a custom frontend. | active | contextual | yes | |
| 2a8452c1b0953b51… | Path B uses Foundry and the Agent Framework with a custom application to provide full flexibility for building custom agents on Azure AI Foundry runtime grounded on Fabric. | active | contextual | yes | |
| e61f574f5088ed1c… | Path A does not provide agent-level monitoring, citations, human-in-the-loop controls, or a business user interface. | active | contextual | yes | |
| 46a443501e734ff7… | Path A supports single-turn question answering rather than durable multi-agent workflows, so it does not provide persistent agent orchestration. | active | contextual | yes | |
| 9cae9b9af37d07b9… | Path A is limited to structured Fabric data and does not natively support PDF or Word grounding, which constrains its usable knowledge sources. | active | contextual | yes | |
| 1466169b85ddc076… | Path A, called Fabric Data Agents only, provides conversational natural-language question answering over governed Fabric data while honoring Purview labels. | active | contextual | yes | |
| a03acab70ba15f66… | Building agents directly in Fabric is presented as two practical paths, and the document says IT should evaluate both paths honestly. | active | contextual | yes | |
| b0487d68fa16f836… | Pyrana delivers agentic capabilities as one governed, pre-integrated platform so that organizations do not need to assemble the same capabilities from several separate Microsoft services. | active | contextual | yes | |
| 056b74b831c277d0… | On the Microsoft stack, agentic capabilities are assembled from multiple services including Fabric, Foundry Agent Service, the Agent Framework SDK, and custom application code rather than delivered as a single integrated product. | active | contextual | yes | |
| 523430ecc7017ebe… | Pyrana and Microsoft Fabric operate at different layers because Fabric answers governed-data questions while Pyrana uses that data plus documents, policies, and tribal knowledge to generate traceable and trusted recommendations. | active | contextual | yes | |
| 48fbb0f279655a9d… | The document states that building agents directly in Fabric leads in practice to one of two paths and emphasizes that IT should see both paths honestly. | active | contextual | yes | |
| d023869459bc804a… | Pyrana is presented as delivering agentic capabilities as one governed, pre-integrated platform rather than as an assembly of separate services. | active | contextual | yes | |
| 08ea2e2d86ba6619… | On the Microsoft stack, agentic capabilities are assembled from Fabric, Foundry Agent Service, the Agent Framework SDK, and custom application code rather than delivered as a single integrated platform. | active | contextual | yes | |
| e04ffe4cb65462ba… | The document's key insight is that Fabric and Pyrana operate at different layers, with Fabric focused on governed data answers and Pyrana focused on deciding what to do using data plus documents, policies, and tribal knowledge with traceable and trusted recommendations. | active | contextual | yes | |
| 2c4840201cdbe1ba… | All layers of Pyrana are configuration-driven through versioned YAML, support multi-tenancy, and are governed and observable by design. | active | contextual | yes | |
| 18bfe086d29f4089… | Pyrana's experience layer provides custom Next.js and React frontends built on shared UI and SDK libraries and delivered per client in weeks. | active | contextual | yes | |
| 369d19e071b18787… | Pyrana's tools and tiered code interpreter provide sandboxed compute and connectors to systems, APIs, and other agents. | active | contextual | yes | |
| b9903112c820d9fc… | Pyrana's agent orchestration layer, using PyranaHarness and Temporal, provides durable multi-step and multi-agent plans with pause, resume, and human-in-the-loop capabilities. | active | contextual | yes | |
| 43ae91bf21367891… | Pyrana's Context Engine, also called Cortex, is a living, cited knowledge graph composed of Context Units with provenance and an approval lifecycle. | active | contextual | yes | |
| 3c75370f8c9bc96f… | Pyrana is defined as an enterprise platform for building agentic applications consisting of human-centered workflows powered by coordinated agents with shared memory, governance, and a custom user interface, and it runs on Azure. | active | contextual | yes | |
| 35a32a55ed403543… | For the dashboard portion of the project, Fabric is identified as the right tool, and Pyrana is not positioned as a replacement for that dashboard capability. | active | contextual | yes | |
| fcb5a526c9ec6016… | Microsoft Purview in the Fabric stack provides cataloging, lineage, sensitivity labels, and data loss prevention capabilities. | active | contextual | yes | |
| 85acb2069c243398… | Real-Time Intelligence in Fabric provides streaming and event analytics capabilities. | active | contextual | yes | |
| 87ba52d5946ed0e1… | Semantic models and Power BI in Fabric form the business metrics layer and dashboards. | active | contextual | yes | |
| 20bb6dcebc4d3c11… | The Lakehouse and Warehouse components in Fabric provide the governed, queryable data model. | active | contextual | yes | |
| c69d7ee10f3dfff8… | Data Factory, pipelines, and mirroring in Fabric are used for data ingestion and transformation. | active | contextual | yes | |
| efd71e40bfe80e31… | OneLake in Microsoft Fabric serves as a single, governed data lake that functions as the system of record. | active | contextual | yes | |
| 4eaa175be94a378e… | The analysis compares two different things that are often bundled together under the phrase build directly on Microsoft Fabric, and separating them is described as central to the analysis. | active | contextual | yes | |
| f3a2bcd80d9f175b… | Sections 6 through 9 cover build-versus-buy economics, areas where Fabric is genuinely the better tool, the five business capabilities, and an IT risk and governance summary. | active | contextual | yes | |
| d6bde524533ae7db… | Section 5 contains the requirement-by-requirement crosswalk mapped to the RFP and is identified as the core of the response. | active | contextual | yes | |
| 6aa404beaf5d7cc6… | Section 4 provides a head-to-head capability matrix comparing the platforms. | active | contextual | yes | |
| 615a5c62d076ecbb… | Section 3 presents the recommended architecture for the solution being evaluated. | active | contextual | yes | |
| 1077799fbd35df07… | Section 2 explains how Pyrana honors the Fabric mandate, positioning Pyrana as compatible with the requirement to use Fabric. | active | contextual | yes | |
| 76b5f9ccac5338a3… | Section 1 of the document defines the two platforms and explains what building directly on Fabric actually entails so readers can understand the basis of the comparison. | active | contextual | yes | |
| f8db862670b2e771… | Pyrana is presented as delivering the required governance layer within weeks inside Azure, with the audit trail that IT is requesting. | active | contextual | yes | |
| 3e80c6b44eaf716f… | The document concludes that dashboards should be built in Fabric, but building agents in Fabric alone would require Summer Fridays to hand-build and own governance scaffolding that Pyrana already provides and that the RFP explicitly requires. | active | contextual | yes | |
| 2e0d9b594791817c… | The Context Engine is designed to ground answers in unstructured sources such as recap documents, calendars, claim libraries, and reviews by extracting atomic, cited claims from those documents. | active | contextual | yes | |
| 93527307c4bbc291… | Fabric Data Agents currently lack built-in agent telemetry, evaluation harnesses, audit logging, approval workflows, prompt-injection protection, and agent-level observability, so teams must assemble their own testing, monitoring, and injection guardrails. | active | contextual | yes | |
| bbff84b25b1f5945… | Fabric Data Agents currently lack built-in agent telemetry, an evaluation harness, audit logging, approval workflows, prompt-injection protection, and agent-level observability, requiring users to assemble testing, monitoring, and injection guardrails themselves so that governance and safety capabilities are not native. | active | contextual | yes | |
| fb1ca1f96f4e45fd… | Fabric Data Agents are described as not natively grounding on PDF and Word documents, which distinguishes them from Pyrana’s Context Engine for document-based answer grounding. | active | contextual | yes | |