| 5e61968c993b0d63… | The business-facing experience includes governed dashboards and an AI-agent workspace with human-in-the-loop review for Marketing, eCommerce, Retail, Media, and Brand Health teams. | active | contextual | yes | |
| b4c7b97d74eeea9a… | The recommended architecture is defined as a Fabric foundation with a Pyrana agentic layer so that a single coherent stack operates inside Azure with Fabric as the base and Pyrana as the documented exception. | active | contextual | yes | |
| 79f014a73cef1268… | A single Azure-resident, pre-governed platform is presented as the lower-risk way to meet the project requirements that the exception clause is meant to protect. | active | contextual | yes | |
| bb52fc524146bee6… | Hand-building agent governance inside Fabric would increase scope, lengthen the timeline, and place provenance and safety responsibility on Summer Fridays’ team, making the alternative less favorable. | active | contextual | yes | |
| fdb776cffcab65c9… | The RFP allows exceptions as long as they are documented and justified, so an exception for Pyrana is acceptable when supported by a strong rationale. | active | contextual | yes | |
| b2edbc8d33e747d7… | Pyrana provides supporting architecture, data-flow, and security documentation to back approval of the written exception so that IT can justify the deployment formally. | active | contextual | yes | |
| f115b8d5e0af23ce… | Fabric remains the data foundation, dashboard surface, and governance authority of record so that Pyrana augments rather than replaces the core Microsoft data platform. | active | contextual | yes | |
| 0a2a24b2dcc2743a… | Pyrana adds agent-grade governance through source-to-AI citations, fact-versus-recommendation typing, human-in-the-loop approvals, prompt-injection defenses, and agent telemetry because these controls are required and not natively provided by Fabric Data Agents. | active | contextual | yes | |
| 14655cfac4ee60ed… | Pyrana consumes governed data from OneLake and writes no data outside Azure so that data movement remains confined to the approved cloud boundary. | active | contextual | yes | |
| 277be754eebd892a… | The AI-agent capability is defined as being delivered by Pyrana, an Azure-native agentic-application platform deployed in the customer tenant, so that the agent layer remains resident within Azure infrastructure. | active | contextual | yes | |
| ddbff523c0cb85fe… | The platform uses no model training on Summer Fridays data and instead provides private inference with per-tenant isolation so that customer data remains segregated and not reused for training. | active | contextual | yes | |
| c5fc478956e07104… | Pyrana reads from governed Fabric data, and raw confidential or customer-level data is not exposed through dashboards or agents unless explicit approval is granted so that sensitive data access remains controlled. | active | contextual | yes | |
| 35d766421bf12011… | Pyrana runs inside Summer Fridays' Azure tenant using Azure OpenAI or Foundry models, Azure Postgres, Entra ID, and AKS so that the platform remains within the Microsoft estate. | active | contextual | yes | |
| 842a8561c42ce67a… | Purview continues to own the data catalog, lineage, sensitivity labels, and DLP functions so that governance authority remains with Microsoft Fabric’s established controls. | active | contextual | yes | |
| d91bda58d26df36f… | Dashboards must reconcile to approved Fabric logic and Power BI reports so that business-facing analytics remain aligned with the governed reporting foundation. | active | contextual | yes | |
| 8ca5a3978a33687b… | The head-to-head capability comparison scores the agentic-application capabilities required by the project, while Fabric’s data and BI strengths are treated as already stipulated and covered separately in Section 7. | active | contextual | yes | |
| cc5998f0038c7f6a… | A security rail spans all layers using Entra ID identity, Azure Key Vault, AES-256 encryption at rest, TLS 1.2 or higher in transit, private networking, and per-tenant isolation, consistent with Pyrana’s production Azure architecture. | active | contextual | yes | |
| cb3bf9940d9d31d1… | Fabric Data Agents do not natively provide the cited Context Unit coverage described for Pyrana’s knowledge path, indicating a capability gap in native Fabric agent support. | active | contextual | yes | |
| 1e4777af1323a846… | The unstructured knowledge path sends recap documents, launch and marketing calendars, claim libraries, and brand-health and competitive PDFs into the Pyrana Context Engine, which extracts atomic cited Context Units that agents retrieve and cite. | active | contextual | yes | |
| d827626243b2ec84… | The structured data path flows from sources through Fabric pipelines to OneLake or a warehouse and then to a governed semantic model so that Power BI dashboards and Pyrana agents query the same governed model and reconcile to one source of truth. | active | contextual | yes | |
| 422330eb4307e86f… | The source systems include Shopify, Amazon, Sephora portals, TikTok Shop, affiliates, paid media, influencer and EMV data, reviews and sentiment, competitive intelligence, and calendars, budgets, and recap documents. | active | contextual | yes | |
| 65925a539231ea2a… | The data foundation layer includes OneLake, a governed data model, a business metrics layer, Purview labels and DLP, and optional Fabric Data Agents for question answering. | active | contextual | yes | |
| 1c7ec202c051ff3c… | The orchestration and governance layer consists of PyranaHarness with Temporal for durable HITL workflows, Cortex Context Units that are cited and versioned, a tiered code interpreter, OTel or Langfuse telemetry, and audit plus approvals. | active | contextual | yes | |
| 027914acdc1ed7f5… | The user-facing components include Power BI for BI dashboards, a Pyrana custom frontend for agent UX and HITL, and Entra ID SSO for identity access. | active | contextual | yes | |
| 8ea1cbcb4f13c7a1… | The business-facing layer serves Marketing, eCommerce, Retail, Media, and Brand Health teams through governed dashboards and an AI-agent workspace with human-in-the-loop review. | active | contextual | yes | |
| 9a2147178de18889… | The recommended architecture is a Fabric foundation with a Pyrana agentic layer, forming a single coherent stack inside Azure where data gravity stays in Fabric and the agentic application sits on top as the documented exception. | active | contextual | yes | |
| 6f54b43c23b98e0f… | A single Azure-resident, pre-governed platform is presented as the lower-risk way to meet the requirements protected by the exception clause so that compliance and delivery risk are reduced. | active | contextual | yes | |
| 6ff6b2e738e0f47a… | Hand-building agent governance inside Fabric would increase scope, lengthen the timeline, and place the burden of provenance and safety on Summer Fridays' own team, making it a less favorable alternative. | active | contextual | yes | |
| f4684eabb632961c… | The RFP anticipates exceptions and requires only that they be documented and justified, making the proposed exception acceptable when supported by a strong rationale. | active | contextual | yes | |
| 1d3654a7ef63c456… | Fabric remains the data foundation, dashboard surface, and governance authority of record while Pyrana supplies supporting architecture, data-flow, and security documentation to back the approval. | active | contextual | yes | |
| e4f82ab1f0165636… | Pyrana adds agent-grade governance features including source-to-AI citations, fact-versus-recommendation typing, human-in-the-loop approvals, prompt-injection defenses, and agent telemetry because the project requires capabilities that Fabric Data Agents do not natively provide. | active | contextual | yes | |
| eea7874f3029169e… | The written exception rationale states that Pyrana is an Azure-native agentic-application platform deployed in the tenant that consumes governed OneLake data and writes no data outside Azure so that the exception can be formally approved. | active | contextual | yes | |
| fa56e5c8015da58e… | Pyrana is intended to be the single platform that IT documents and approves rather than a sprawl of external tools so that governance and approval remain centralized. | active | contextual | yes | |
| 907ea9cb045d140a… | The platform uses no model training on Summer Fridays data and instead provides private inference with per-tenant isolation so that customer data remains segregated and not used for training. | active | contextual | yes | |
| b6efab79b3761c88… | Pyrana runs inside Summer Fridays' Azure tenant using Azure OpenAI or Foundry models, Azure Postgres, Entra ID, and AKS so that the platform remains inside the Microsoft estate. | active | contextual | yes | |
| a99c6357a358dce5… | Purview continues to own catalog, lineage, sensitivity labels, and DLP so that governance authority remains with Microsoft Fabric’s native governance system. | active | contextual | yes | |
| 52f69e44aabf15bf… | Dashboards must reconcile to approved Fabric logic and Power BI reports so that business-facing outputs remain aligned with the sanctioned Microsoft Fabric data foundation. | active | contextual | yes | |
| 256043e03b3e3c0a… | The written exception rationale should describe Pyrana as adding agent-grade governance features including source-to-AI citations, fact-versus-recommendation typing, human-in-the-loop approvals, and prompt-injection protections. | active | contextual | yes | |
| d4e5efc9ceab3e56… | The written exception rationale should state that Pyrana consumes governed data from OneLake and writes no data outside Azure so that data residency remains within the approved Microsoft environment. | active | contextual | yes | |
| 12fd356bb0bb6204… | A written exception rationale can state that the AI-agent capability is delivered by Pyrana as an Azure-native agentic application platform deployed in the organization's tenant. | active | contextual | yes | |
| d357ececf0e3931f… | IT documents and approves Pyrana as the single platform so that the organization avoids a sprawl of external tools. | active | contextual | yes | |
| 7337e3deec1255e9… | Pyrana does not train models on Summer Fridays data and instead uses private inference with per-tenant isolation so that customer data remains isolated and not used for model training. | active | contextual | yes | |
| a6ac0c58c6a06f76… | Pyrana runs inside Summer Fridays' Azure tenant using Azure OpenAI or Foundry models, Azure Postgres, Entra ID, and AKS so that the agentic layer remains within the Microsoft estate. | active | contextual | yes | |
| 9aec8058fb3bac90… | Dashboards must reconcile to approved Fabric logic and Power BI reports so that reporting remains aligned with sanctioned business logic. | active | contextual | yes | |
| e14de6ffaf4a49e4… | The governed data model and business metrics layer reside in the Fabric lakehouse, warehouse, and semantic models so that analytical logic remains in approved Fabric components. | active | contextual | yes | |
| bb2a6ae75a2c9efb… | Ingestion, transformation, refresh, and reconciliation processes run in Fabric pipelines so that core data operations remain within the Fabric environment. | active | contextual | yes | |
| d2e4d5363157d777… | Company data remains in OneLake as the system of record so that the authoritative enterprise data location stays inside Fabric. | active | contextual | yes | |
| 40bf75d56c03b8c2… | Pyrana is designed to comply with the Fabric mandate rather than bypass it, so its deployment approach is intended to satisfy the RFP's approval conditions. | active | contextual | yes | |
| 65fd9ca84a54a416… | The RFP requires the solution to be built within Summer Fridays' approved Microsoft Fabric environment unless IT grants a written exception, and any non-Fabric platform must be documented and approved before use. | active | contextual | yes | |
| a6774fb2794d5c3f… | Path B can satisfy the RFP governance threshold, but it becomes a do-it-yourself integration program layered on top of the data project, creating scope, timeline, and maintenance risk. | active | contextual | yes | |