{"id":26480,"date":"2026-06-03T17:00:40","date_gmt":"2026-06-03T15:00:40","guid":{"rendered":"https:\/\/www.regestaitalia.eu\/genai-and-agentic-ai-how-to-turn-data-into-operational-decisions\/"},"modified":"2026-06-08T17:40:08","modified_gmt":"2026-06-08T15:40:08","slug":"genai-and-agentic-ai-how-to-turn-data-into-operational-decisions","status":"publish","type":"post","link":"https:\/\/www.regestaitalia.eu\/en\/genai-and-agentic-ai-how-to-turn-data-into-operational-decisions\/","title":{"rendered":"GenAI and Agentic AI: how to turn data into operational decisions"},"content":{"rendered":"

GenAI and Agentic AI offer the ability to transform data into operational decisions, if and when they work on trusted business sources<\/strong>, structured knowledge bases, and integrated workflows. GenAI interprets and generates content; Agentic AI uses this content to plan activities, interact with business systems, and support controlled process execution. <\/p>\n

Artificial intelligence is moving beyond the experimental stage and gaining consistency in business processes. After the spread of generative tools used to write text, synthesize documents, produce images or answer questions, the focus of companies is shifting to a more operational focus: using AI to intervene in processes, automate repetitive tasks, support rapid decisions and transform business knowledge into executed work.<\/strong> <\/p>\n

This is where the relationship between GenAI and Agentic AI becomes particularly relevant. Generative AI enables the interpretation, generation and reprocessing of content. Agentic AI adds another layer: the ability to plan actions, use tools, interact with business applications, and carry out complex tasks with a controlled level of autonomy. IBM\u00b9 describes Agentic AI as a system capable of achieving a specific goal with limited supervision through AI agents coordinated by orchestration mechanisms.<\/strong> <\/p>\n

For CIOs, IT managers, operations and innovation managers, the question is no longer whether artificial intelligence can generate plausible content. The issue is figuring out how to connect it to the right data, real processes, and core business systems<\/strong>. Without this connection, AI remains an isolated tool. Instead, when it works on reliable data, structured knowledge bases, process rules, and application integrations, it becomes an operational tool capable of reducing the distance between information and decision. <\/p>\n

For us at Regesta<\/strong>, this is the most important step: taking artificial intelligence out of experimentation and into business flows<\/strong>, where data becomes knowledge, knowledge becomes decision, and decision becomes action.<\/p>\n<\/div>

What are GenAI and Agentic AI<\/h2>\n

From an architectural point of view, GenAI and Agentic AI operate on different levels of the information value chain. GenAI primarily presides over the interpretation and generation level<\/strong>: it receives an input, retrieves context from document or knowledge base sources, processes a probabilistic response, and produces an output in the form of text, summary, classification, code, or other content. <\/p>\n

Instead, Agentic AI adds a goal-oriented level of execution<\/strong>: it does not just generate an output, but breaks down a task into steps, selects tools, interacts with external systems, applies process rules, and coordinates actions with a defined degree of autonomy and supervision.<\/p>\n

It is the shift, from content generation to workflow management, tool calling, orchestration and contextualized decision<\/strong> making, that makes Agentic AI an operational extension of GenAI, particularly relevant when the goal is to support controlled process execution on trusted data, application integrations and governance policies.<\/p>\n<\/div><\/div><\/div>

\"what<\/span><\/div><\/div><\/div><\/div>

Definition of GenAI<\/h3>\n

Generative AI is a technology capable of producing text, summaries, responses, images, code and other content from data, instructions and context. In the enterprise, it becomes useful when working on controlled, up-to-date, process-linked sources.
\nThe NIST profile dedicated to Generative AI, published in 2024 as part of the AI Risk Management Framework, frames GenAI as a technology with specific risks that must be managed throughout the entire system lifecycle, from design to operational use. <\/p>\n

In business, this capability is useful when there is a need to transform unstructured knowledge into readable content, synthesize documents, query information bases, generate contextualized responses, classify queries, or support document-intensive activities.<\/strong> GenAI can reduce search time, simplify access to knowledge, and make the production of information outputs faster.
\nHowever, GenAI alone does not guarantee better decisions. It can explain, propose, synthesize, or suggest, but it often remains confined to assistive logic. A generative model can produce a useful answer, but it does not always know the application context, does not always distinguish the authoritative source, does not always know which business system to update, and cannot always execute an action. <\/p>\n

Definition of Agentic AI<\/h3>\n

Agentic AI is an application model in which AI agents plan and execute goal-oriented activities using enterprise data, tools, applications, and workflows with defined levels of autonomy, control, and oversight.<\/p>\n

This distinction is fundamental. GenAI works primarily on information production and interpretation; Agentic AI works on the sequence from information to action through decision.<\/strong> For a business, it means moving from an assistant responding to an operator to a system that can read a request, retrieve data from ERP or CRM, verify conditions, propose a decision, compile a document, open a transaction, or initiate an approval workflow. <\/p>\n

GenAI vs Agentic AI: the operational differences<\/h3>\n

The difference between GenAI and Agentic AI is not only about the underlying technology. It depends on the role artificial intelligence takes in the process.<\/strong> A GenAI can generate a response. An AI agent can use that response as part of a larger operational sequence.<\/p>\n<\/div>\n

\n\n\n\n\n\n\n\n\n\n\n
Size<\/th>\nGenAI<\/th>\nAgentic AI<\/th>\n<\/tr>\n<\/thead>\n
Main objective<\/td>\nGenerate content, summaries, responses, and classifications<\/td>\nAchieve an operational goal through coordinated actions<\/td>\n<\/tr>\n
Typical input<\/td>\nPrompts, documents, data, knowledge base<\/td>\nGoal, context, data, tools, rules, workflow<\/td>\n<\/tr>\n
Output<\/td>\nText, summary, analysis, classification, draft<\/td>\nTask executed, ticket, update, document, alert, approvable proposal<\/td>\n<\/tr>\n
Relationship to business systems<\/td>\nQueries or uses information sources<\/td>\nInteracts with core systems, APIs, workflows, applications<\/td>\n<\/tr>\n
Level of autonomy<\/td>\nLimited to generation of output<\/td>\nDefined by policies, permissions, controls, and supervision<\/td>\n<\/tr>\n
Prevailing value<\/td>\nIndividual efficiency and access to knowledge<\/td>\nProcess efficiency, scalability, traceability, controlled automation<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

This evolution is particularly important because many companies have already experimented with generative AI tools but struggle to turn them into measurable productivity. McKinsey notes\u00b2 that Agentic AI scales on a solid data foundation and that companies must modernize information architectures, data quality, and operating models<\/strong> to produce value at scale. The same analysis points out that many enterprises have already experimented with AI agents, but few have scaled them with tangible results; data limitations remain among the main obstacles. <\/p>\n

From assistive AI to operational AI<\/h2>\n

The difference between assistive AI and operational AI is one of the most important issues for those who need to evaluate artificial intelligence projects in the enterprise.
\nAssistive AI helps a person work better.<\/strong> It can answer questions, summarize documents, draft papers, explain data or suggest alternatives. The value is real, but it often remains confined to individual productivity. <\/p>\n

Operational AI enters the process.<\/strong> It uses data, rules, workflows, and business tools to support repeatable, governed, and measurable activities. It doesn’t just produce a response: it helps turn the response into an action, maintaining traceability, permissions, and human control where needed.<\/p>\n<\/div>\n

\n\n\n\n\n\n\n\n\n\n
Appearance<\/th>\nAssistive AI<\/th>\nOperational AI \/ Agentic AI<\/th>\n<\/tr>\n<\/thead>\n
Main function<\/td>\nRespond, synthesize, generate content<\/td>\nPerform tasks, orchestrate steps, interact with systems<\/td>\n<\/tr>\n
Relationship to the data<\/td>\nUses context provided by the user or retrieved from an information source<\/td>\nAccesses data, systems, and process rules according to permissions and workflow<\/td>\n<\/tr>\n
Output<\/td>\nText, summary, suggestion, draft<\/td>\nAction, ticket, order, document, update, alert, approvable proposal<\/td>\n<\/tr>\n
Role of the user<\/td>\nFormulates requests and validates responses<\/td>\nOversees exceptions, monitors decisions, intervenes at high impact points<\/td>\n<\/tr>\n
Corporate value<\/td>\nIndividual efficiency<\/td>\nProcess efficiency, scalability, traceability, bottleneck reduction<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

This distinction helps avoid a frequent misunderstanding: introducing generative tools without rethinking data, processes and integrations.<\/strong> The result, in these cases, is a piecemeal use of AI: useful for some personal activities, but with little impact on the company’s ability to make faster, more consistent decisions.<\/p>\n

For us, however, value is built when artificial intelligence is designed as a component of enterprise architecture.<\/strong> This means connecting it to data, applications, processes, authorizations and operational responsibilities.<\/p>\n

Why data is the prerequisite for operational AI<\/h2>\n

When working with productive realities, AI does not start from the prompt. It starts from the data. <\/strong> A model can be very advanced, but if it operates on information that is inconsistent, duplicated, obsolete, or disconnected from processes, it will produce weak results. This is true for GenAI and even more true for Agentic AI, because an agent does not just propose an answer: it can trigger subsequent steps. <\/p>\n

For this reason, we consider data quality the first level of governance. In our approach to AI and Data Management, we work to transform data into strategic insights through artificial intelligence, advanced analytics, and process-oriented management models. AI and Data Management is in an area dedicated to transforming information into operational value<\/strong>, with application cases including GenAI, Visual AI, and document automation.
\nThe data-driven model should be read from this perspective. A data-driven company truly is when it is able to use data in day-to-day decision making: the amount of data available is almost a secondary parameter. We have previously addressed<\/a> the operational significance of the data-driven approach and highlighted three levels: availability of data, quality and consistency of information, and ability to integrate data into decision-making processes. <\/p>\n

For GenAI and Agentic AI, these three levels become even more binding. Data availability allows the system to access the information it needs. Quality avoids biased, inconsistent or unverifiable responses. Integration into processes allows moving from insight to action.
\nMany companies already have ERP, MES, CRM, logistics software, HR platforms, manufacturing systems, business intelligence tools and document repositories. The problem stems from the fact that these information sources do not always share the same language. The same customer, the same product, the same indicator or the same operational event may be described in different ways depending on the system. If this complexity is not governed, AI inherits the inconsistencies of the organization.<\/strong><\/p>\n

The Regesta model for operational AI: govern, structure, interpret, act, control<\/h2>\n

To transform GenAI and Agentic AI into truly usable tools in business processes, we adopt a progressive model. We do not start with the AI model, but with the process and the data.<\/p>\n<\/div>\n

\n\n\n\n\n\n\n\n\n\n
Phase<\/th>\nFunction<\/th>\nTechnology or approach<\/th>\nOperational output<\/th>\n<\/tr>\n<\/thead>\n
Governing<\/td>\nMaking data trustworthy<\/td>\nData management, data governance, application integration<\/td>\nConsistent, accessible and traceable data<\/td>\n<\/tr>\n
Structuring<\/td>\nMaking knowledge queryable<\/td>\nKnowledge base, business semantics, document intelligence<\/td>\nOrganized business context<\/td>\n<\/tr>\n
Interpreting<\/td>\nGenerating insights, responses and classifications<\/td>\nGenAI, LLM, RAG, prompt engineering<\/td>\nSynthesis, analysis, classifications, proposals<\/td>\n<\/tr>\n
Take action<\/td>\nBringing output into processes<\/td>\nAgentic AI, workflow, API, automation<\/td>\nTasks, alerts, documents, updates, transactions<\/td>\n<\/tr>\n
Check<\/td>\nEnsure oversight and auditability<\/td>\nHuman in the loop, logging, permissions, policy<\/td>\nTrackable, approvable, and governed actions<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

This sequence allows us to clarify the role of artificial intelligence in the enterprise. AI does not replace the process: it extends it. It does not eliminate governance: it requires it. It does not erase the human experience: it makes it more accessible, verifiable and scalable. <\/p>\n

The role of the corporate knowledge base<\/h3>\n

The knowledge base is where corporate knowledge stops being dispersed and becomes queryable. It can include technical manuals, procedures, quality documents, contracts, price lists, product sheets, internal regulations, historical emails, tickets, ERP data, MES data, bills of materials, drawings, reports, and expert-generated information. <\/p>\n

For GenAI, a well-constructed knowledge base makes it possible to generate responses that are more adherent to the business context. For Agentic AI, it becomes an operational base: the agent can use the knowledge to decide which step to perform<\/strong>, which document to produce, which information to verify, or which exception to report.
\nIn this architecture, Retrieval Augmented Generation (RAG) is often a crucial component.<\/strong> RAG allows the model to retrieve information from controlled business sources before generating a response. This reduces the risk of generic responses and helps keep the result adherent to available knowledge. <\/p>\n

However, RAG alone does not solve the problem. If sources are inconsistent, outdated, or lack structure, the system retrieves weak content.<\/strong> If the knowledge base is out of date, AI may produce answers that are formally correct but only partially operational. If there is a lack of shared semantics, the model may misinterpret acronyms, codes, roles or process states.
\nFor this reason, in enterprise AI projects the knowledge base must be designed as an enterprise asset.<\/strong> It is not a passive repository. It is an information layer that must be governed, updated, validated and linked to processes. <\/p>\n

How the transition from data to operational decisions works<\/h2>\n

The path that transforms a piece of data into an operational decision can be described as a technical sequence.
\nFirst the data is collected from ERP systems, MES, CRM, PLM, documents, emails, sensors or external information bases.<\/strong> Then it is normalized, classified, and linked to a shared business semantics. It then enters a knowledge base or governed data layer, where it can be queried by AI models. <\/p>\n

At that point, GenAI interprets the request, retrieves the relevant context, and produces an output. Agentic AI intervenes when that output needs to be turned into a task<\/strong>: update a card, prepare a bid, generate a bill of materials, open a request, produce a technical summary, send an alert, or trigger a workflow.<\/p>\n

For example, a customer request may come via email.<\/strong> An AI system can recognize customer, product, urgency and category of the request. It can retrieve commercial history, check contract terms, consult technical documentation, generate a draft response, and prepare an offer. In an agent scenario, it can also create a task in the CRM, update the status of the request, open an internal audit, or submit the draft to the salesperson for validation.
\nThe difference is substantial: it prepares the action rather than simply producing the text or other output on demand.<\/strong> <\/p>\n

Execution layer: the point at which AI enters processes<\/h2>\n

Many AI projects stop at the conversational interface stage. The user formulates a question, the model answers, and the user decides what to do. This approach may improve individual productivity, but it does not fundamentally change the operation of the business. <\/p>\n

The execution layer serves to overcome this limitation. It is the layer where artificial intelligence is connected to processes, permissions, applications, rules, controls, and operational responsibilities. In other words, it is the point at which AI stops being a side function and becomes part of the enterprise architecture. <\/p>\n

In a sales process<\/strong>, an agent can read a request received via email, recognize customer and product, retrieve trade terms, check availability or historical data, generate a draft offer, and forward it to an operator for validation.<\/p>\n

In procurement<\/strong>, it can classify supplier documents, identify contract anomalies, compare order and invoice data, and propose corrective actions.
\nIn production, it can analyze process anomalies, correlate IoT and management data, suggest interventions or trigger escalations.<\/p>\n

In service<\/strong>, it can read tickets, retrieve technical manuals, propose diagnoses, generate operating instructions, and prepare a response consistent with the corporate knowledge base.<\/p>\n

Value comes from reducing manual steps, standardizing procedures, tracking decisions, and making business know-how scalable.<\/p>\n<\/div>

Reggy: the digital worker to link knowledge and action<\/h2>\n

To make all these needs and best practices a reality, we developed Reggy, Regesta Group’s AI Digital Worker<\/a>. We designed it to integrate Generative Artificial Intelligence into the heart of business flows and transform every piece of information into value and action. Reggy was created to overcome data fragmentation, automate manual tasks, learn procedures and operate in core systems.<\/strong><\/p>\n<\/div><\/div><\/div>

\"reggy<\/span><\/div><\/div><\/div><\/div>

Its positioning is consistent with the evolution from assistive AI to operational AI. Reggy is not just a chatbot: it is the digital worker capable of connecting business knowledge and automation. It can support already defined tasks such as Tender Analyst<\/strong> for analysis of technical notices and standards, Inbound Document Processor<\/strong> for automated management of Bills of Lading and invoices on SAP, Sales & Offering Assistant<\/strong> for monitoring inquiries and generating draft offers, Technical & Quality Support<\/strong> for troubleshooting and root cause analysis of manufacturing defects. <\/p>\n

Most relevant is the integration with the corporate knowledge base. Reggy learns from documents, data, technical manuals, Excel files, CSV files, PDFs, and expert knowledge, turning operational knowledge into shared and scalable assets. <\/p>\n

This is a crucial step for manufacturing and industrial companies. Many processes still depend on the implicit experience of skilled people: technicians, operators, quality managers, buyers, salespeople, maintenance workers, product specialists. When this knowledge remains in the heads of individuals or dispersed in unquestionable documents, the organization becomes fragile. When it is codified, validated and linked to workflows, it can become a basis for controlled automation. <\/p>\n

Reggy interprets precisely this need: to transform corporate knowledge into an operational system to support daily activities. Its value lies in its ability to link GenAI, data, documents, procedures and core systems. <\/p>\n

GenAI and Agentic AI applications in business processes: some concrete examples<\/h2>\n

In manufacturing, GenAI can support technical, quality, maintenance, operations, and sales back offices. Agentic AI can add the executive component, integrating with ERP, MES, document management, CRM and business intelligence systems.
\nThe use cases most suitable for early adoption have common characteristics: available data, repetitive tasks, partially formalized rules, high document volume, need to reduce response time and presence of experienced operators to be involved in validation. <\/p>\n

Document management and back office<\/h3>\n

Bills of Lading, invoices, order confirmations, emails, attachments and administrative documents can be read, classified, compared and routed automatically. AI can recognize the document type, extract relevant fields, check for consistency with ERP or management systems, flag anomalies and prepare the next task. <\/p>\n

Customer service and sales support<\/h3>\n

GenAI can summarize requests, retrieve information from knowledge base and customer history, generate draft responses, and support bid preparation. Agentic AI can create tasks, update CRM, trigger internal workflows, and propose operational priorities. <\/p>\n

Production and quality<\/h3>\n

In manufacturing processes, AI can analyze non-conformity reports, compare production parameters, retrieve operating instructions, identify recurrences and suggest corrective actions. In more advanced systems, it can correlate MES data, IoT data, quality reports and maintenance information. <\/p>\n

Maintenance and troubleshooting<\/h3>\n

An agent can query technical manuals, historical tickets, procedures, and machine cards. It can help an operator identify probable causes, suggest controls, generate reports, and trigger escalations when the problem exceeds certain thresholds. <\/p>\n

Procurement and supply chain<\/h3>\n

AI can support document analysis of suppliers, verification of contract terms, comparison of order and invoice, classification of requests, preparation of summaries, and monitoring of risks or delays.<\/p>\n

Knowledge management<\/h3>\n

Corporate knowledge can be transformed into a queryable system useful for onboarding, technical support, internal training and business continuity. This reduces dependence on unformalized individual knowledge and makes skills transfer faster. <\/p>\n

Governance, security and human control<\/h2>\n

Agentic AI requires a higher level of governance than GenAI used individually. The reason is simple: when a system can act, risk also changes in nature.<\/strong> It is not just about an inaccurate response, but about a possible wrong action, an unauthorized update, an untracked decision, or a permission violation. <\/p>\n

The NIST Generative AI Profile\u00b3 calls out the need to manage risks across the lifecycle of AI systems, with governance, mapping, measurement and management actions.<\/strong>
\nFor us, this means designing operational AI with some minimum conditions<\/strong>: action traceability, role management, permissions consistent with business applications, audit trail, human in the loop in sensitive steps, secure data environments, separation of content generation and action validation.<\/p>\n

Human control is a component of architecture. In many processes, AI can prepare, sort, classify, and propose. The ultimate responsibility remains with people when the decision has economic, legal, production, or organizational impact.<\/strong>
\nA good Agentic AI design must therefore precisely define where the agent can act autonomously, where it must propose an action, and where it must seek approval. This distinction allows for efficiency without losing control. <\/p>\n

How we set up a GenAI + Agentic AI project.<\/h2>\n

An operational AI project should start with the process, not the choice of model.<\/strong> The most common mistake is to introduce a generic technology and then look for a use case. The most effective path proceeds in the opposite direction: identify a high-volume or high-complexity flow, measure the operational load, identify data sources and decision rules, define where AI can intervene, and determine which actions require human oversight. <\/p>\n

For us, the correct sequence is this: process, data, knowledge, model, agent, integration, control.<\/strong> Without process, AI remains experimental. Without data, AI remains approximate. Without structured knowledge, AI does not reflect the real workings of the business. Without integration, AI does not act. Without control, AI is not governable. <\/p>\n

In this perspective, we favor an incremental approach. We start with a circumscribed domain, measure the benefit, correct knowledge base and workflow, then extend the model to other processes. This reduces technology risk, makes it easier to transfer skills, and allows us to verify ROI on specific activities. <\/p>\n

    \n
  • Process selection<\/li>\n
  • Analysis of available data<\/li>\n
  • Knowledge base construction<\/li>\n
  • Agent design<\/li>\n
  • Integration with workflow and business systems<\/li>\n<\/ul>\n

    This scheme keeps the project adherent to operational objectives<\/strong> and avoids experimentation without measurable impact.<\/p>\n

    What metrics to use to measure value<\/h3>\n

    To measure a GenAI or Agentic AI project, it is not enough to count the number of prompts executed or active users. These metrics help understand adoption, but they do not explain operational value.
    \nThe most useful metrics relate to process<\/strong>, e.g., average time to handle a request, number of manual steps eliminated, reduction in errors, time to respond to the customer, percentage of documents classified correctly, reduction in backlog, number of exceptions handled, quality of output validated by operators, level of knowledge base reuse.<\/p>\n

    For agentic projects, governance metrics need to be added: number of actions performed automatically, number of actions proposed but not approved, reasons for rejection, frequency of escalations, audit trail of decisions, consistency of permissions, compliance with policies.
    \nThese metrics help distinguish a useful AI project from an AI project that is merely demonstrative<\/strong>. The goal is not to use AI, but to improve the way the business works. <\/p>\n

    Why GenAI and Agentic AI matter to CIOs, operations and innovation managers<\/h2>\n

    For CIOs and IT managers, GenAI and Agentic AI pose an architectural question. AI must be integrated with core systems, data, security, identity, APIs, governance and application control.<\/strong> It cannot be left to isolated initiatives of individual departments. For operations and production managers, value is measured in the ability to reduce decision-making time, standardize activities, support operators and improve visibility into processes. AI becomes useful when it enables faster action on anomalies, priorities, requests and bottlenecks. <\/p>\n

    For innovation managers, the issue is about scalability. Many AI experiments produce interesting results in the lab, but fail to become stable processes. Agentic AI therefore requires a method that holds together technology, organization, data, expertise and measurement.<\/strong>
    \nThis is where our approach focuses: building a bridge between technological potential and real-world application. GenAI and Agentic AI have value when they enter processes, respect corporate governance, and produce measurable effects. <\/p>\n

    From data to action: the new perimeter of enterprise artificial intelligence<\/h2>\n

    GenAI and Agentic AI are shifting the focus of enterprise artificial intelligence. The generic experimentation phase is giving way to more integrated projects in which models, data, knowledge base and core systems work together to produce measurable effects on processes.
    \nFor us at Regesta, this shift is consistent with an approach geared toward transforming data into operational decisions.<\/strong> Our goal is not to add one more tool to the enterprise application landscape, but to build a layer capable of smoothing the relationship between knowledge, decision and action. <\/p>\n

    The maturity of AI in the enterprise is measured in its ability to reduce the time between event and response, make know-how scalable, automate repetitive tasks, maintain control over data, and let people make decisions that require experience, accountability, and process vision.<\/strong>
    \nIn this operating space, GenAI and Agentic AI become useful, governable, and truly integrated technologies in everyday work. That’s why we work on data, processes, knowledge base, automation and digital worker: so that artificial intelligence produces value when it enters the point where the business decides, acts and measures its results. <\/p>\n

    Q&A on GenAI, Agentic AI and Operational AI.<\/h2>\n

    The following questions summarize the most relevant technical nodes for distinguishing between generative AI, agentic AI, and operational AI in the enterprise environment. The key point is that these technologies differ in their positioning in the application architecture<\/strong>: GenAI primarily presides over interpretation and content generation, while Agentic AI introduces capabilities for planning, orchestration, use of tools, and interaction with enterprise systems and workflows, always within constraints of governance, permissions, and human oversight. <\/p>\n<\/div>