# business logic

Business logic is the software layer that encodes domain-specific rules, constraints, validations, and workflows governing an enterprise's data and operations.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Prompt engineering won't make enterprise AI trustworthy. Data engineering will.

DevFeed: [Prompt engineering won't make enterprise AI trustworthy. Data engineering will.](<https://devfeed.tech/articles/prompt-engineering-won-t-make-enterprise-ai-trustworthy-data-engineering-will-146812.md>)

Original publisher: [Read original article](<https://sdtimes.com/data/prompt-engineering-wont-make-enterprise-ai-trustworthy-data-engineering-will/>)

Author: Arjun Danda Sureshbabu

Published: 2026-11-20T16:50:33Z

Content type: opinion

Language: en

Sources: [SD Times](<https://devfeed.tech/sources/sd-times.md>)

Topics: [data-engineering](<https://devfeed.tech/topics/data-engineering.md>), [Prompt Engineering](<https://devfeed.tech/topics/prompt-engineering.md>), [data-governance](<https://devfeed.tech/topics/data-governance.md>), [metric-standardization](<https://devfeed.tech/topics/metric-standardization.md>), [knowledge-engineering](<https://devfeed.tech/topics/knowledge-engineering.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [enterprise data protection](<https://devfeed.tech/topics/enterprise-data-protection.md>), [trust](<https://devfeed.tech/topics/trust.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assistant](<https://devfeed.tech/tags/ai-assistant.md>), [ai-projects](<https://devfeed.tech/tags/ai-projects.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [column](<https://devfeed.tech/tags/column.md>), [context](<https://devfeed.tech/tags/context.md>), [data](<https://devfeed.tech/tags/data.md>), [data-engineering](<https://devfeed.tech/tags/data-engineering.md>), [data-engineers](<https://devfeed.tech/tags/data-engineers.md>), [data-layer](<https://devfeed.tech/tags/data-layer.md>), [database](<https://devfeed.tech/tags/database.md>), [definition](<https://devfeed.tech/tags/definition.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-ai](<https://devfeed.tech/tags/enterprise-ai.md>), [enterprise-data](<https://devfeed.tech/tags/enterprise-data.md>), [finance](<https://devfeed.tech/tags/finance.md>), [prompt](<https://devfeed.tech/tags/prompt.md>), [prompt-engineering](<https://devfeed.tech/tags/prompt-engineering.md>)

### AI overview

The excerpt argues that confident wrong answers often come from missing business meaning and controls in enterprise data, not from poorly worded prompts. It describes a finance query that summed amounts without accounting for reversals, remapped region codes, or the narrower definition of "bookings." Its proposed approach is to give models a maintained semantic layer with agreed business definitions, allowed values, synonyms, and accurate joins; enforce row- and column-level access in the database; route common or consequential questions to reviewed queries; and show the query, definitions, and filters used for new answers. Test sets with known answers help check changes. The article says this puts definitions and policies under engineering review and monitoring, while prompts still provide context and guide follow-up questions. This is based on the supplied excerpt.

### Source excerpt

A few months into building an AI assistant for our finance teams, someone asked it what bookings looked like for one region last quarter. It answered in a few minutes, with a table and a summary explaining how it got there. The number was inaccurate. My first instinct was to blame the prompt, and we'd... ... continue reading The post Prompt engineering won't make enterprise AI trustworthy. Data engineering will. appeared first on SD Times.

## Agentic AI repeats same old enterprise adoption cycle

DevFeed: [Agentic AI repeats same old enterprise adoption cycle](<https://devfeed.tech/articles/agentic-ai-repeats-same-old-enterprise-adoption-cycle-146087.md>)

Original publisher: [Read original article](<https://www.infoworld.com/article/4249734/agentic-ai-repeats-same-old-enterprise-adoption-cycle.html>)

Author: David Linthicum

Published: 2026-11-20T09:00:00Z

Content type: opinion

Language: en

Sources: [InfoWorld](<https://devfeed.tech/sources/infoworld.md>)

Topics: [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [Enterprise Architecture](<https://devfeed.tech/topics/enterprise-architecture.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [API Governance](<https://devfeed.tech/topics/api-governance.md>), [observability](<https://devfeed.tech/topics/observability.md>), [LLM security](<https://devfeed.tech/topics/llm-security.md>)

Tags: [adoption](<https://devfeed.tech/tags/adoption.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [apis](<https://devfeed.tech/tags/apis.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [artificial-intelligence-emerging-technology-generative-ai](<https://devfeed.tech/tags/artificial-intelligence-emerging-technology-generative-ai.md>), [automate](<https://devfeed.tech/tags/automate.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [cost](<https://devfeed.tech/tags/cost.md>), [costs](<https://devfeed.tech/tags/costs.md>), [data](<https://devfeed.tech/tags/data.md>), [decision](<https://devfeed.tech/tags/decision.md>), [emerging-technology](<https://devfeed.tech/tags/emerging-technology.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [exception-handling](<https://devfeed.tech/tags/exception-handling.md>), [generative-ai](<https://devfeed.tech/tags/generative-ai.md>), [guardrails](<https://devfeed.tech/tags/guardrails.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [logging](<https://devfeed.tech/tags/logging.md>), [observability](<https://devfeed.tech/tags/observability.md>), [production](<https://devfeed.tech/tags/production.md>), [project](<https://devfeed.tech/tags/project.md>), [storytype-opinion](<https://devfeed.tech/tags/storytype-opinion.md>)

### AI overview

A distributor's agentic AI sales system ran successfully, but after supporting integration, governance, security, testing and operational costs were included, it cost roughly 20 times as much as a traditional architecture for about the same ROI. The article argues that agents are most useful when work requires interpretation, adaptation and semi-autonomous action; stable, rules-based or highly regulated workflows may be served more economically by conventional applications, workflow engines, rules or API integration. It recommends starting with measurable business value and assessing production costs and governance needs rather than adopting an architecture because it is fashionable. The text compares this adoption pattern with SOA, microservices and cloud-native systems, each of which can deliver benefits but also impose complexity when used without a fitting need or organizational maturity.

### Source excerpt

The pitch sounded perfect. A large regional distributor needed to build a new sales transaction management system. The goal was straightforward: automate parts of order intake, discount approvals, exception handling, customer communications, and inventory checks. It was not a trivial system, but it was also something the industry had built before. Then the vendor presentations began. Every software provider seemed to have a new agentic AI story. Their platforms had agents that could make decisions, orchestrate workflows, interpret customer intent, route exceptions, and learn from business context. One vendor described its offering as a common LLM brain that could make decisions as if the company had hired 10,000 experts, except those experts were not on the payroll. That line was from an actual sales pitch, and it landed well in the boardroom. The company decided to go agentic. The architecture would use AI agents to manage decision flows, invoke tools, check policies, interact with enterprise systems, and escalate only when needed. It looked modern. It looked strategic. It looked like the future. Then reality arrived. Building the system required far more integration work than expected. Each agent needed access to clean data, governed APIs, business rules, security controls, observability, exception handling, and human override mechanisms. The team had to build guardrails around decisions, logging around reasoning, test harnesses for unpredictable outcomes, and new operational processes for things traditional systems handled more predictably. Costs ballooned. Security reviews took longer. Operational complexity increased. The project ultimately ran fine once in production, but six months later, the company realized the uncomfortable truth: the system cost roughly 20 times more than a traditional architecture would have cost when all supporting complexity was included, and it delivered about the same ROI. I am hearing versions of this story once or twice a week from

## What AI-First Engineering Means for the Future of Software Quality

DevFeed: [What AI-First Engineering Means for the Future of Software Quality](<https://devfeed.tech/articles/what-ai-first-engineering-means-for-the-future-of-software-quality-145967.md>)

Original publisher: [Read original article](<https://testgrid.io/blog/ai-first-engineering/>)

Author: Ankita Nandi

Published: 2026-11-19T10:55:22Z

Content type: article

Language: en

Sources: [TestGrid](<https://devfeed.tech/sources/testgrid-blog.md>)

Topics: [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [mutation-testing](<https://devfeed.tech/topics/mutation-testing.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-generated-tests](<https://devfeed.tech/tags/ai-generated-tests.md>), [ai-testing](<https://devfeed.tech/tags/ai-testing.md>), [ai-workflow](<https://devfeed.tech/tags/ai-workflow.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [automation](<https://devfeed.tech/tags/automation.md>), [bank](<https://devfeed.tech/tags/bank.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [billing](<https://devfeed.tech/tags/billing.md>), [block](<https://devfeed.tech/tags/block.md>), [browser](<https://devfeed.tech/tags/browser.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [credit-card](<https://devfeed.tech/tags/credit-card.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [quality](<https://devfeed.tech/tags/quality.md>), [rules](<https://devfeed.tech/tags/rules.md>), [software](<https://devfeed.tech/tags/software.md>), [system](<https://devfeed.tech/tags/system.md>), [tests](<https://devfeed.tech/tags/tests.md>)

### AI overview

AI-first workflows can accelerate software delivery, but when an agent derives code, tests and documentation from the same incomplete requirement, they can all reinforce one mistaken assumption. The excerpt distinguishes tests that confirm behavior inferred from buggy code from tests that correctly enforce a flawed or underspecified business rule; either can leave a green build that fails users. It recommends agreeing on expected behavior and edge-case examples before implementation, having an accountable domain expert approve them, and generating business-rule tests from those approved expectations. Validate AI-generated tests by planting known bugs. For high-risk changes, add independent security review, hands-on human testing and sign-off. Use execution evidence such as video, screenshots, logs and network traffic to investigate failures, and measure customer bugs, pre-release risks and diagnosis time rather than test counts alone. The excerpt also calls for junior engineers to practice questioning requirements and explaining conclusions. Its example is hypothetical, and the overview reflects the supplied excerpt.

### Source excerpt

Let's say you oversee a bank's credit-card billing-error system. Your product team gives an AI agent a requirement: "Accept written billing-error notices within 60 days." The agent implements the rule, generates 40 tests, and reports that every test passes. But it has started the clock on the transaction date. Under US federal billing-error rules, the [...]

## OfficePrism: Benchmarking Agents on Single-Domain Operations Across Enterprise Business Functions

DevFeed: [OfficePrism: Benchmarking Agents on Single-Domain Operations Across Enterprise Business Functions](<https://devfeed.tech/articles/officeprism-benchmarking-agents-on-single-domain-operations-across-enterprise-business-functions-139600.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.22262>)

Author: Hanfeng Liu, Zhenyu Luo, Dongchao Zhang, Zexi Liu, Zulong Chen, Jinxin Hu, Jia Xu, Zeyi Wen

Published: 2026-11-18T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>), [arXiv: Machine Learning](<https://devfeed.tech/sources/arxiv-machine-learning.md>), [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Agent Harness](<https://devfeed.tech/topics/agent-harness.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [automated](<https://devfeed.tech/tags/automated.md>), [benchmarking](<https://devfeed.tech/tags/benchmarking.md>), [business](<https://devfeed.tech/tags/business.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-cl](<https://devfeed.tech/tags/cs-cl.md>), [cs-lg](<https://devfeed.tech/tags/cs-lg.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [curation](<https://devfeed.tech/tags/curation.md>), [dispatch](<https://devfeed.tech/tags/dispatch.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [environment](<https://devfeed.tech/tags/environment.md>), [full](<https://devfeed.tech/tags/full.md>), [grounded](<https://devfeed.tech/tags/grounded.md>), [operations](<https://devfeed.tech/tags/operations.md>), [organization](<https://devfeed.tech/tags/organization.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [reference](<https://devfeed.tech/tags/reference.md>), [response](<https://devfeed.tech/tags/response.md>), [rules](<https://devfeed.tech/tags/rules.md>), [schemas](<https://devfeed.tech/tags/schemas.md>), [synthetic](<https://devfeed.tech/tags/synthetic.md>), [tasks](<https://devfeed.tech/tags/tasks.md>), [ticket](<https://devfeed.tech/tags/ticket.md>)

### AI overview

OfficePrism evaluates agents on 420 single-domain enterprise tasks across seven business functions, separating function-specific operations from cross-function coordination. Tasks use benchmark-defined L1-L3 structure levels and fresh environments built from a shared synthetic organization and one function-specific domain. The pipeline constructs Chinese-language tickets, hidden executable reference witnesses, and expected responses from grounded records, business rules, and tool schemas, then filters and curates them. Results across 124 model-harness-package configurations show joint natural-language and database pass rates of 22.6%-76.4% (median 67.9%). L1 scores highest in every configuration; L2 exceeds L3 in 122. For 50 matched model and harness labels, search-and-dispatch scores higher than full-schema in 30, ties in one, and scores lower in 19.

### Source excerpt

arXiv:2611.22262v1 Announce Type: cross Abstract: Broad workplace scores can mix competence within one business function with the extra cost of coordinating across functions and systems, making failures hard to localize. OfficePrism evaluates this prerequisite through 420 single-domain enterprise tasks spanning seven business functions under shared, benchmark-defined L1--L3 task-structure levels. Each task runs in a fresh environment combining a shared synthetic organization with one function-specific domain and yped state access. Our pipeline uses grounded records, business rules, and tool schemas to jointly construct a Chinese-language ticket, a hidden executable reference witness, and an expected response, followed by automated filtering and human curation. The same task set is evaluated through full-schema and search-and-dispatch packages. Across 124 model--harness--package configurations, the per-case joint natural-language-and-database pass rate ranges from 22.6% to 76.4%, with a median of 67.9%. L1 is highest in all 124 configurations, and L2 exceeds L3 in 122. Among 50 configurations sharing the same harness and model labels across both packages, search scores higher in 30, ties in one, and scores lower in 19.

## Getting AI out of the demo and into businesses globally

DevFeed: [Getting AI out of the demo and into businesses globally](<https://devfeed.tech/articles/getting-ai-out-of-the-demo-and-into-businesses-globally-138419.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/getting-ai-out-of-the-demo-and-into-businesses-globally/>)

Author: Dr. Asa Kalavade

Published: 2026-11-17T19:05:22Z

Content type: article

Language: en

Sources: [Artificial Intelligence](<https://devfeed.tech/sources/artificial-intelligence.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [knowledge-engineering](<https://devfeed.tech/topics/knowledge-engineering.md>), [Automation](<https://devfeed.tech/topics/automation.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [AI Context Management](<https://devfeed.tech/topics/ai-context-management.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agentcore](<https://devfeed.tech/tags/agentcore.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-platform](<https://devfeed.tech/tags/agentic-platform.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [aws](<https://devfeed.tech/tags/aws.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [demo](<https://devfeed.tech/tags/demo.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineers](<https://devfeed.tech/tags/engineers.md>), [enterprises](<https://devfeed.tech/tags/enterprises.md>), [forward-deployed-engineering](<https://devfeed.tech/tags/forward-deployed-engineering.md>), [foundation](<https://devfeed.tech/tags/foundation.md>), [foundational-100](<https://devfeed.tech/tags/foundational-100.md>), [gap](<https://devfeed.tech/tags/gap.md>), [governance](<https://devfeed.tech/tags/governance.md>), [production](<https://devfeed.tech/tags/production.md>), [sprints](<https://devfeed.tech/tags/sprints.md>), [teams](<https://devfeed.tech/tags/teams.md>), [value](<https://devfeed.tech/tags/value.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

AWS Forward Deployed Engineering (FDE) helps commercial and public sector customers move AI prototypes into production through 45-day sprints in the customer's AWS account. Its approach builds a reusable foundation for identity, security, business context, and operations; automates high-volume workflows by surfacing rules held in systems and employee judgment; and embeds governance, monitoring, and audit controls from the start. AWS teams work alongside customer engineers using an opinionated stack, AI-Driven Development Lifecycle, and task-specific accelerators, with the goal of leaving customers able to operate and extend the systems themselves. The article reports examples including a governed platform for Samsung Life Insurance built in 45 days and a Marsh use case reaching production about two months after work began. FDE is available in 15 countries, with each sprint priced under FDE Terms and billed through the customer's AWS account.

### Source excerpt

Most enterprises have AI that works in a demo but stalls before production. AWS Forward Deployed Engineering closes that gap. AWS engineers embed with customer teams to take high-value workflows to production in 45-day sprints, leaving a foundation, workflows, and governance the customer owns.

## The knowledge layer for enterprise AI: Domain Ontology

DevFeed: [The knowledge layer for enterprise AI: Domain Ontology](<https://devfeed.tech/articles/the-knowledge-layer-for-enterprise-ai-domain-ontology-139351.md>)

Original publisher: [Read original article](<https://neo4j.com/blog/developer/the-knowledge-layer-for-enterprise-ai-domain-ontology/>)

Author: Jocelyn Hoppa

Published: 2026-11-17T08:57:00Z

Content type: tutorial

Language: en

Sources: [Neo4j](<https://devfeed.tech/sources/graph-database-technology-neo4j-blog.md>)

Topics: [semantic-layer](<https://devfeed.tech/topics/semantic-layer.md>), [knowledge-engineering](<https://devfeed.tech/topics/knowledge-engineering.md>), [data-governance](<https://devfeed.tech/topics/data-governance.md>), [Neo4j](<https://devfeed.tech/topics/neo4j.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [developer](<https://devfeed.tech/tags/developer.md>), [domain](<https://devfeed.tech/tags/domain.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-ai](<https://devfeed.tech/tags/enterprise-ai.md>), [enterprise-architecture](<https://devfeed.tech/tags/enterprise-architecture.md>), [genai](<https://devfeed.tech/tags/genai.md>), [knowledge](<https://devfeed.tech/tags/knowledge.md>), [knowledge-layer](<https://devfeed.tech/tags/knowledge-layer.md>), [ontology](<https://devfeed.tech/tags/ontology.md>), [semantic-layer](<https://devfeed.tech/tags/semantic-layer.md>)

### AI overview

The article presents a Neo4j domain ontology as a governed graph layer that lets enterprise agents resolve business terms by context and trace who owns each meaning and which rule enforces it. Its churn example preserves distinct enterprise, Retention, Customer Insight, and Credit Risk definitions instead of merging them; role-based stewardship and validity intervals let users identify the applicable meaning and recover historical definitions. Candidate terms and links extracted from wikis or report code retain source, extraction date, and confidence, remain proposed until a steward approves them, and can be checked against evaluable graph rules. The model links concepts, attributes, rules, roles, and process tasks, including separating changeable affordability thresholds into rules. The described build requires Neo4j 2026.02 or later, Enterprise Edition, and Cypher 25, with chapters 1 and 2 loaded first. It establishes definitions and rules; the article says the later data-products layer is needed to supply consumption-ready data and numbers.

### Source excerpt

This series is the practical build companion to Jesús Barrasa's knowledge layer manifesto. This chapter is built on the previous chapter 2: Processes. Building this at enterprise scale? Neo4j Context Engine is the new Neo4j product for building a knowledge... Read more ->

## What the !@#$% is Ontology?

DevFeed: [What the !@#$% is Ontology?](<https://devfeed.tech/articles/what-the-is-ontology-136528.md>)

Original publisher: [Read original article](<https://dataengineeringcentral.substack.com/p/what-the-is-ontology>)

Author: Daniel Beach

Published: 2026-11-16T14:43:28Z

Content type: article

Language: en

Sources: [Data Engineering Central](<https://devfeed.tech/sources/data-engineering-central.md>)

Topics: [semantic-layer](<https://devfeed.tech/topics/semantic-layer.md>), [AI Context Management](<https://devfeed.tech/topics/ai-context-management.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [Data Management](<https://devfeed.tech/topics/data-management.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2006](<https://devfeed.tech/tags/2006.md>), [2025](<https://devfeed.tech/tags/2025.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [absolute](<https://devfeed.tech/tags/absolute.md>), [acceptance](<https://devfeed.tech/tags/acceptance.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-context](<https://devfeed.tech/tags/agent-context.md>), [agentcore](<https://devfeed.tech/tags/agentcore.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-tooling](<https://devfeed.tech/tags/agentic-tooling.md>), [agentic-world](<https://devfeed.tech/tags/agentic-world.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-search](<https://devfeed.tech/tags/ai-search.md>), [data](<https://devfeed.tech/tags/data.md>), [data-mesh](<https://devfeed.tech/tags/data-mesh.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [ontology](<https://devfeed.tech/tags/ontology.md>)

### AI overview

The article frames ontology as a machine-readable model of domain concepts, relationships, and rules that gives AI agents business context. It argues that this extends a longstanding data problem: encoding institutional knowledge so technology can use it consistently. Its examples show different approaches. NVIDIA Auto-Ontology scans SQL data sources, proposes business terms, metrics, and joins for human review, then answers questions with SQL and supporting steps; the author sees it as infrastructure-heavy and notes its apparent lack of document ingestion. AWS's Context Ontology Accelerator is tightly integrated with AWS services and costly to run, but can build knowledge graphs from PDFs and Word files. Databricks Genie Ontology combines human-authored context with knowledge extracted from data, then ranks and delivers relevant information to agents. The article says open-source options are scarce and treats the distinction between ontology and semantic layers as unsettled; it calls for evaluations showing whether the added infrastructure improves results enough to justify its cost.

### Source excerpt

the new Data Mesh?

## Kotlin Multiplatform Networking with Native Android and iOS ViewModels

DevFeed: [Kotlin Multiplatform Networking with Native Android and iOS ViewModels](<https://devfeed.tech/articles/kotlin-multiplatform-networking-with-native-android-and-ios-viewmodels-134271.md>)

Original publisher: [Read original article](<https://proandroiddev.com/kmp-networking-native-viewmodels-cf6fb357b012?source=rss----c72404660798---4>)

Author: Ravi Rawal

Published: 2026-11-14T14:49:33Z

Content type: tutorial

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Ktor](<https://devfeed.tech/topics/ktor.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [coroutine-testing](<https://devfeed.tech/topics/coroutine-testing.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [api](<https://devfeed.tech/tags/api.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [business-logic](<https://devfeed.tech/tags/business-logic.md>), [cancellation](<https://devfeed.tech/tags/cancellation.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [coroutine](<https://devfeed.tech/tags/coroutine.md>), [domain](<https://devfeed.tech/tags/domain.md>), [error](<https://devfeed.tech/tags/error.md>), [http](<https://devfeed.tech/tags/http.md>), [http-client](<https://devfeed.tech/tags/http-client.md>), [ios](<https://devfeed.tech/tags/ios.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [kmp](<https://devfeed.tech/tags/kmp.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>), [native](<https://devfeed.tech/tags/native.md>), [networking](<https://devfeed.tech/tags/networking.md>), [published](<https://devfeed.tech/tags/published.md>), [software-architecture](<https://devfeed.tech/tags/software-architecture.md>)

### AI overview

The article recommends sharing Ktor networking, serialization, repositories, domain models, and meaningful use cases in Kotlin Multiplatform while Android and iOS retain native ViewModels and presentation state. Callers own coroutine or task lifecycles: Android can launch through `viewModelScope`; iOS can bridge Kotlin suspend functions to Swift `async`/`await` with KMP-NativeCoroutines or SKIE and cancel its Swift `Task`. Ktor requests are suspending and need no automatic dispatcher switch when they are main-safe; truly blocking or CPU-heavy work should use an appropriate injected dispatcher. Preserve cancellation, reuse the HTTP client, and keep DTO-to-domain and domain-to-UI mapping at their respective boundaries. The article notes that Swift interop adds generated types and conversions, and shared unit tests do not verify platform HTTP engines or the Kotlin-to-Swift bridge.

### Source excerpt

Share Ktor networking, repositories, and use cases while Android and iOS keep control of their native ViewModels, UI state, threading, and cancellation. Kotlin Multiplatform allows us to share networking and business logic between Android and iOS. When an API call is made from the shared Kotlin module to the native app there are a number of things we need to make a decision on. Who creates the coroutine? Who handles where the work is executed? Will the ViewModel be the same for Android and iOS? How do we get the use cases from the shared module onto each platform? The decisions here are more important than the actual HTTP client. A good KMP architecture will not have all the layers shared between both platforms. We can leave the repositories and use cases in Kotlin, have Android use its Jetpack ViewModels and iOS use SwiftUI with its native Swift ViewModels. Both platforms will call the same business functions but each will have control over their own presentation lifecycle. It's important to make sure the work that needs to be consistent is shared. Let's look at how we can create this architecture using a simple example of fetching articles from a REST API. 1. Decide what belongs in shared code Lets start with two native applications and one shared KMP module. The Android and iOS applications will not need or have identical ViewModels. But they should access to the same business operation. The shared module can own: HTTP client configuration and API requests. DTOs and serialization. Repository implementations and data-to-domain mapping. Use cases that represent application operations. Shared validation, business rules, and error classification. Android can use using Jetpack ViewModel, viewModelScope, and StateFlow. iOS may use SwiftUI, ObservableObject, @Published, and Swift concurrency. This is one of the architecture options described in the Kotlin Multiplatform ViewModel documentation: sharing the repository and data layers while keeping platform-specific ViewMo

## New in Symfony 8.2: Validator Improvements

DevFeed: [New in Symfony 8.2: Validator Improvements](<https://devfeed.tech/articles/new-in-symfony-8-2-validator-improvements-131817.md>)

Original publisher: [Read original article](<https://symfony.com/blog/new-in-symfony-8-2-validator-improvements>)

Author: Javier Eguiluz

Published: 2026-11-13T08:16:00Z

Content type: release

Language: en

Sources: [Symfony](<https://devfeed.tech/sources/symfony-blog.md>)

Topics: [Symfony](<https://devfeed.tech/topics/symfony.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>)

Tags: [arguments](<https://devfeed.tech/tags/arguments.md>), [array](<https://devfeed.tech/tags/array.md>), [arrays](<https://devfeed.tech/tags/arrays.md>), [boolean](<https://devfeed.tech/tags/boolean.md>), [callback](<https://devfeed.tech/tags/callback.md>), [closure](<https://devfeed.tech/tags/closure.md>), [collection](<https://devfeed.tech/tags/collection.md>), [collections](<https://devfeed.tech/tags/collections.md>), [comparison](<https://devfeed.tech/tags/comparison.md>), [component](<https://devfeed.tech/tags/component.md>), [constraint](<https://devfeed.tech/tags/constraint.md>), [custom](<https://devfeed.tech/tags/custom.md>), [fields](<https://devfeed.tech/tags/fields.md>), [financial-applications](<https://devfeed.tech/tags/financial-applications.md>), [message](<https://devfeed.tech/tags/message.md>), [numbers](<https://devfeed.tech/tags/numbers.md>), [php](<https://devfeed.tech/tags/php.md>), [precision](<https://devfeed.tech/tags/precision.md>), [rules](<https://devfeed.tech/tags/rules.md>), [symfony](<https://devfeed.tech/tags/symfony.md>)

### AI overview

Symfony 8.2 adds several validator improvements: `Callback` can create a violation from a boolean result using a `message` option, enabling inline rules with PHP 8.5 static closures. `Unique(fields: ...)` now checks selected fields on object collections, reading public properties directly and other values through PropertyAccess. `Range` and comparison constraints support PHP 8.4 `BcMath\Number`, converting limits to preserve precision. Violation `setParameter()` now accepts numeric, stringable, and date/time values for formatted translations. Group sequences can use `Class::class`; `cascadeCurrentGroup` validates `Valid` objects in the sequence's current group. `Valid(restrictGroups: false)` uses groups only to trigger cascading, while nested constraints receive all validated groups. `Valid` also works in `Sequentially`, with its groups configured on the outer constraint.

### Source excerpt

Inline Rules with the Callback Constraint Contributed by Javier Eguiluz in...

## Best Tools for AI Agent HITL (Human-in-the-Loop) Workflows

DevFeed: [Best Tools for AI Agent HITL (Human-in-the-Loop) Workflows](<https://devfeed.tech/articles/best-tools-for-ai-agent-hitl-human-in-the-loop-workflows-131246.md>)

Original publisher: [Read original article](<https://www.lyzr.ai/blog/best-tools-for-ai-agent-human-in-the-loop-workflows/>)

Author: Lyzr Team

Published: 2026-11-13T05:53:59Z

Content type: comparison

Language: en

Sources: [Lyzr.ai](<https://devfeed.tech/sources/lyzr-ai.md>)

Topics: [human in the loop agent](<https://devfeed.tech/topics/human-in-the-loop-agent.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [AI for customer service automation](<https://devfeed.tech/topics/ai-for-customer-service-automation.md>)

Tags: [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agent-governance](<https://devfeed.tech/tags/ai-agent-governance.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [approval-workflows](<https://devfeed.tech/tags/approval-workflows.md>), [human-in-the-loop](<https://devfeed.tech/tags/human-in-the-loop.md>), [tools](<https://devfeed.tech/tags/tools.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

HITL workflows should pause an agent before consequential actions and resume only after an authorized human decision. The article recommends risk-based checkpoints with context-rich requests, role-based routing, support for approval, rejection or changes, persistent state, and an audit trail. Tool choices depend on where agents run and what needs approval: LangGraph and the OpenAI Agents SDK provide developer controls over execution or tool calls, while n8n and Microsoft Copilot Studio integrate approvals into visual workflows and existing business processes. Temporal supports durable, long-running approvals; HumanLayer supplies approval infrastructure for existing agents. Lyzr's GitAgent Approval Flows govern promotion of agent versions between environments and are distinct from runtime approval of individual actions. The article emphasizes that HITL is one part of broader security and agent governance, not a substitute for them.

### Source excerpt

An AI agent can identify a customer refund request, check the transaction history, validate the refund policy, and prepare the transaction in seconds. But should...

## Operational Ontology on Snowflake: From Business Meaning to Governed AI Action

DevFeed: [Operational Ontology on Snowflake: From Business Meaning to Governed AI Action](<https://devfeed.tech/articles/operational-ontology-on-snowflake-from-business-meaning-to-governed-ai-action-131048.md>)

Original publisher: [Read original article](<https://medium.com/snowflake/operational-ontology-on-snowflake-from-business-meaning-to-governed-ai-action-6f3ef270d3f2?source=rss----34b6daafc07---4>)

Author: Tianxia Jia

Published: 2026-11-12T21:36:38Z

Content type: article

Language: en

Sources: [Snowflake Builders](<https://devfeed.tech/sources/snowflake-builders.md>)

Topics: [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [knowledge-engineering](<https://devfeed.tech/topics/knowledge-engineering.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [semantic-layer](<https://devfeed.tech/topics/semantic-layer.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [function calling](<https://devfeed.tech/topics/function-calling.md>), [schema design](<https://devfeed.tech/topics/schema-design.md>), [AI-Ready Data](<https://devfeed.tech/topics/ai-ready-data.md>)

Tags: [acting](<https://devfeed.tech/tags/acting.md>), [actions](<https://devfeed.tech/tags/actions.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-reasoning](<https://devfeed.tech/tags/ai-reasoning.md>), [also](<https://devfeed.tech/tags/also.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [article](<https://devfeed.tech/tags/article.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [best](<https://devfeed.tech/tags/best.md>), [bottleneck](<https://devfeed.tech/tags/bottleneck.md>), [business](<https://devfeed.tech/tags/business.md>), [governed-ai](<https://devfeed.tech/tags/governed-ai.md>), [meaning](<https://devfeed.tech/tags/meaning.md>), [ontology](<https://devfeed.tech/tags/ontology.md>), [operational](<https://devfeed.tech/tags/operational.md>), [snowflake](<https://devfeed.tech/tags/snowflake.md>)

### AI overview

The proposed Snowflake Operational Ontology architecture links governed business definitions to live operational state, domain rules, decision services, AI reasoning, and controlled execution. Its lifecycle is Observe -> Understand -> Evaluate -> Decide -> Execute -> Verify: Cortex Agents investigate and explain options, while specialized services validate or simulate plans; an authorized human approves actions before procedures dispatch them to external systems. Versioned snapshots, isolated simulation results, idempotency, and observed outcomes support traceability and verification. The article stresses that a system's acknowledgement does not prove an action completed. Snowflake Business Ontology governs concepts and relationships but does not execute rules or actions. Standard tables are the default for history and events; hybrid tables can serve selected indexed transactional workloads, with regional availability and quotas, but do not support streams. Applications therefore need another supported event source or dispatcher for hybrid-table state changes. The examples are illustrative synthetic reference implementations, not production integrations.

### Source excerpt

A reference architecture for AI agents to reason over operational state, simulate decisions, execute governed actions, and verify real-world outcomes. From Enterprise Knowledge to Operational Decisions At 1:30 PM, packing station PB-04 goes offline in a distribution center. Orders begin accumulating, and a carrier scheduled to depart at 5:00 PM may leave before its shipments are ready. An AI agent connected to warehouse data can identify the failed station, trace affected orders, and explain the shipping risk. But the warehouse manager needs to decide what to do. Can qualified workers move to another station? Can orders be rerouted? Which recovery plan has the best chance of meeting the deadline without creating another bottleneck? Answering these questions requires current operational state, resource capabilities, business constraints, and a way to evaluate proposed changes. Acting on a decision also requires authorization and confirmation that the intended changes occurred. In the earlier Ontology on Snowflake series, I explored how ontology definitions, enterprise data, semantic models, and AI reasoning establish a shared understanding of business information. Snowflake now has a product of Business Ontology for governed business definiton (Public Preview soon). This article builds on that foundation by introducing a Snowflake Operational Ontology Reference Architecture. It connects governed business meaning to operational state, constraints, simulation, AI reasoning, and controlled actions. The goal is to establish a reusable pattern. A warehouse, supply chain network, and data center require different operational models, but they can share architectural contracts and a common decision lifecycle. 1. What Makes an Ontology Operational? An ontology defines the concepts, relationships, and semantics of a domain. In our warehouse example, the ontology defines Packing Station, Worker, Order, and Carrier Commitment, along with relationships such as workers operating s

## Your re:Invent 2026 guide to mainframe modernization with AWS Transform

DevFeed: [Your re:Invent 2026 guide to mainframe modernization with AWS Transform](<https://devfeed.tech/articles/your-re-invent-2026-guide-to-mainframe-modernization-with-aws-transform-131161.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/migration-and-modernization/your-reinvent-2026-guide-to-mainframe-modernization-with-aws-transform/>)

Author: Rickey Bijlani

Published: 2026-11-12T11:15:16Z

Content type: article

Language: en

Sources: [Migration & Modernization](<https://devfeed.tech/sources/migration-modernization.md>)

Topics: [AWS Transform](<https://devfeed.tech/topics/aws-transform.md>), [Legacy Modernization](<https://devfeed.tech/topics/legacy-modernization.md>), [it modernization](<https://devfeed.tech/topics/it-modernization.md>), [Kiro](<https://devfeed.tech/topics/kiro.md>), [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [Mainframe](<https://devfeed.tech/topics/mainframe.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>), [Service fabric](<https://devfeed.tech/topics/service-fabric.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agentic-coding](<https://devfeed.tech/tags/agentic-coding.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-powered](<https://devfeed.tech/tags/ai-powered.md>), [ai-powered-development](<https://devfeed.tech/tags/ai-powered-development.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-re-invent](<https://devfeed.tech/tags/aws-re-invent.md>), [aws-re-invent-2026](<https://devfeed.tech/tags/aws-re-invent-2026.md>), [aws-transform](<https://devfeed.tech/tags/aws-transform.md>), [business-logic](<https://devfeed.tech/tags/business-logic.md>), [coding](<https://devfeed.tech/tags/coding.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [kiro](<https://devfeed.tech/tags/kiro.md>), [mainframe](<https://devfeed.tech/tags/mainframe.md>), [mainframe-legacy](<https://devfeed.tech/tags/mainframe-legacy.md>), [mainframe-migration](<https://devfeed.tech/tags/mainframe-migration.md>), [mainframe-modernization](<https://devfeed.tech/tags/mainframe-modernization.md>), [migration-solutions](<https://devfeed.tech/tags/migration-solutions.md>), [modernization](<https://devfeed.tech/tags/modernization.md>), [re-invent](<https://devfeed.tech/tags/re-invent.md>)

### AI overview

The guide presents AWS Transform and Kiro as a modernization workflow: AWS Transform analyzes legacy applications, extracts traceable business rules and requirements, and Kiro helps forward engineer services and production code. Its re:Invent sessions describe customer examples ranging from United Airlines' crew operations and Bank Hapoalim's mortgage application to enterprise-scale programs at Experian and Itaú Unibanco; Nissan and Bread Financial discuss preparing modernized systems for agentic workflows. Hands-on sessions cover turning batch processing into event-driven microservices and building an application with an agentic layer on Amazon Bedrock and Bedrock AgentCore. The guide also lists partner roundtables, invitation-only receptions, product talks, and AWS Village demos. Breakouts are walk-up; workshops and builders' sessions require reservations, and participants need a laptop for hands-on sessions. The claims about customer outcomes and compressing modernization from years to months are presented by the source as event descriptions, not independently assessed results.

### Source excerpt

Mainframe modernization has entered the agentic era. At AWS re:Invent 2026, customers will show how AWS Transform, the agentic AI service for migration and modernization, makes decades of business logic visible across mainframe, midrange, and distributed systems. Kiro, the AI-powered development environment from AWS, brings agentic coding to forward engineering. Together, they compress a journey [...]

## Announcing GA of Genie Ontology

DevFeed: [Announcing GA of Genie Ontology](<https://devfeed.tech/articles/announcing-ga-of-genie-ontology-129966.md>)

Original publisher: [Read original article](<https://www.databricks.com/blog/announcing-ga-genie-ontology>)

Author: Ken Wong; Paul Roome; Richard Tomlinson

Published: 2026-11-11T15:00:00Z

Content type: release

Language: en

Sources: [Databricks](<https://devfeed.tech/sources/databricks.md>)

Topics: [knowledge-engineering](<https://devfeed.tech/topics/knowledge-engineering.md>), [semantic-layer](<https://devfeed.tech/topics/semantic-layer.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>)

Tags: [1-6](<https://devfeed.tech/tags/1-6.md>), [about](<https://devfeed.tech/tags/about.md>), [access-controls](<https://devfeed.tech/tags/access-controls.md>), [accessible](<https://devfeed.tech/tags/accessible.md>), [account](<https://devfeed.tech/tags/account.md>), [admin](<https://devfeed.tech/tags/admin.md>), [administrator](<https://devfeed.tech/tags/administrator.md>), [advanced](<https://devfeed.tech/tags/advanced.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [business](<https://devfeed.tech/tags/business.md>), [domain](<https://devfeed.tech/tags/domain.md>), [genie](<https://devfeed.tech/tags/genie.md>), [genie-ontology](<https://devfeed.tech/tags/genie-ontology.md>), [ontology](<https://devfeed.tech/tags/ontology.md>), [platform](<https://devfeed.tech/tags/platform.md>), [useful](<https://devfeed.tech/tags/useful.md>), [work](<https://devfeed.tech/tags/work.md>)

### AI overview

Genie Ontology is generally available as a shared business context layer for agents. It combines continuously learned Ontology Snippets from Databricks assets with explicitly governed Unity Catalog semantics such as Metric Views, Domains, and Pages; OntoRank weighs authority, certification, expertise, popularity, and recency to select context while respecting permissions. Genie MCP makes that context available to external agents. The release also includes generally available Genie Search, Snippets, organizational directories, Domains, and Pages; external BI knowledge sources are in Beta, currently supporting Power BI, while Ontology Manager is planned for Beta. In a Turing-developed benchmark simulating a Databricks workspace, Genie answered correctly in 91% of runs--1.6 times the stronger of two frontier agents--using less than half the tokens and finishing three to four times faster. The article says this reflects an established deployment with accumulated knowledge; it does not establish results for other workspaces.

### Source excerpt

AI agents are only as useful as their understanding of the business in which they work. Within a given domain...

## The work between the tasks: why business orchestration is now enterprise infrastructure

DevFeed: [The work between the tasks: why business orchestration is now enterprise infrastructure](<https://devfeed.tech/articles/the-work-between-the-tasks-why-business-orchestration-is-now-enterprise-infrastructure-129319.md>)

Original publisher: [Read original article](<https://www.uipath.com/blog/product-and-updates/maestro-orchestrate>)

Author: Arun Mehta

Published: 2026-11-10T00:00:00Z

Content type: article

Language: en

Sources: [UiPath RSS Feed](<https://devfeed.tech/sources/uipath-rss-feed.md>)

Topics: [workflow automation](<https://devfeed.tech/topics/workflow-automation.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [least privilege](<https://devfeed.tech/topics/least-privilege.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [about](<https://devfeed.tech/tags/about.md>), [access-control](<https://devfeed.tech/tags/access-control.md>), [account](<https://devfeed.tech/tags/account.md>), [actor](<https://devfeed.tech/tags/actor.md>), [agents](<https://devfeed.tech/tags/agents.md>), [business](<https://devfeed.tech/tags/business.md>), [complex](<https://devfeed.tech/tags/complex.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-infrastructure](<https://devfeed.tech/tags/enterprise-infrastructure.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [maestro](<https://devfeed.tech/tags/maestro.md>), [orchestration](<https://devfeed.tech/tags/orchestration.md>), [people](<https://devfeed.tech/tags/people.md>), [processes](<https://devfeed.tech/tags/processes.md>), [product-and-updates](<https://devfeed.tech/tags/product-and-updates.md>), [robots](<https://devfeed.tech/tags/robots.md>), [systems](<https://devfeed.tech/tags/systems.md>), [tasks](<https://devfeed.tech/tags/tasks.md>), [uipath](<https://devfeed.tech/tags/uipath.md>), [work](<https://devfeed.tech/tags/work.md>)

### AI overview

UiPath Maestro Orchestrate is presented as a coordinating layer for long-running business processes that span agents, robots, systems, and people. It holds work across waits and failures, provides shared process visibility, governance, recovery, version management, and audit history, and can incorporate existing tools and third-party agents without replacing underlying systems. Orchestrate offers BPMN for structured regulated processes, Case for flexible work that can remain open for weeks, and Flow for system-facing steps; these can call one another on the same engine. The article illustrates their combined use in an insurance claim and reports customer results including provisioning reduced from 10 days to 10 minutes and dispute resolution from 97 hours to 4.8. It recommends baselining cycle time, cost, quality, judgment, or control for 30 days on a critical process. The text is promotional and supplies no independent validation of the claims or reported results.

### Source excerpt

Discover how UiPath Maestro Orchestrate coordinates the work between tasks, managing complex processes across agents, robots, systems, and people.

## MCP on raw data is just Excel hell again

DevFeed: [MCP on raw data is just Excel hell again](<https://devfeed.tech/articles/mcp-on-raw-data-is-just-excel-hell-again-124273.md>)

Original publisher: [Read original article](<https://dlthub.com/blog/mcp-on-raw-data-is-excel-hell-again>)

Author: Adrian Brudaru

Published: 2026-11-09T00:00:00Z

Content type: opinion

Language: en

Sources: [DLT Hub](<https://devfeed.tech/sources/dlt-hub.md>)

Topics: [semantic-layer](<https://devfeed.tech/topics/semantic-layer.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [Analytics Pipeline](<https://devfeed.tech/topics/analytics-pipeline.md>), [data analyst](<https://devfeed.tech/topics/data-analyst.md>), [reproducibility](<https://devfeed.tech/topics/reproducibility.md>), [Data Management](<https://devfeed.tech/topics/data-management.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [analyst](<https://devfeed.tech/tags/analyst.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [code](<https://devfeed.tech/tags/code.md>), [crm](<https://devfeed.tech/tags/crm.md>), [customer](<https://devfeed.tech/tags/customer.md>), [data-warehouse](<https://devfeed.tech/tags/data-warehouse.md>), [databricks](<https://devfeed.tech/tags/databricks.md>), [definition](<https://devfeed.tech/tags/definition.md>), [department](<https://devfeed.tech/tags/department.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [excel](<https://devfeed.tech/tags/excel.md>), [finance](<https://devfeed.tech/tags/finance.md>), [governance](<https://devfeed.tech/tags/governance.md>), [harness](<https://devfeed.tech/tags/harness.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [rules](<https://devfeed.tech/tags/rules.md>), [semantics](<https://devfeed.tech/tags/semantics.md>), [warehouse](<https://devfeed.tech/tags/warehouse.md>)

### AI overview

The article argues that agents connected directly to raw MCP data can produce conflicting business answers across departments, and may change data when given write access. It proposes two layers: an ontology in the platform catalog that maps business terms to data and definitions, and tested code that applies business rules consistently across sources. Agents can then use MCP tools mapped to the meaning layer. It names Databricks Unity Catalog Business Semantics and Genie Ontology, and Snowflake Semantic Views and governed MCP servers as platform examples. The text says raw MCP may work for individual use, but offers no shared precision for company-wide answers. It also describes dltHub as building pipelines, models, ontology, and metric views from business definitions, storing meaning in existing catalogs, with work done at build time.

### Source excerpt

Agents replaced the analyst, not the warehouse. Why MCP on raw data repeats the Excel mistake, and the two layers that fix it: semantics in your catalog, rules in code.

## Recognizing Policy

DevFeed: [Recognizing Policy](<https://devfeed.tech/articles/recognizing-policy-122371.md>)

Original publisher: [Read original article](<https://ryanharter.com/blog/2026/11/recognizing-policy/>)

Published: 2026-11-07T14:55:43Z

Content type: article

Language: en

Sources: [Blogs on Ryan Harter](<https://devfeed.tech/sources/blogs-on-ryan-harter.md>)

Topics: [Dynamic authorization rules](<https://devfeed.tech/topics/dynamic-authorization-rules.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [policy-as-code](<https://devfeed.tech/topics/policy-as-code.md>), [Functional programming](<https://devfeed.tech/topics/functional-programming.md>)

Tags: [business-logic](<https://devfeed.tech/tags/business-logic.md>), [chat](<https://devfeed.tech/tags/chat.md>), [cross-platform](<https://devfeed.tech/tags/cross-platform.md>), [feature](<https://devfeed.tech/tags/feature.md>), [file-permissions](<https://devfeed.tech/tags/file-permissions.md>), [functional-programming](<https://devfeed.tech/tags/functional-programming.md>), [policy](<https://devfeed.tech/tags/policy.md>)

### AI overview

Policy is changeable business logic based on explicit business decisions, such as who may use a feature. The article traces commenting access from being available to everyone with file access, to depending on file permissions, and then being restricted for minors in certain jurisdictions. Keeping these checks in multiple platform codebases makes consistent behavior harder as rules accumulate. The author describes centralizing feature access decisions in a testable service: a `decide()` function takes defined inputs and returns a decision, which supports isolated testing and cross-platform code sharing. For server-side policies, Cedar offers a policy language and evaluation specification; its runtime implementations are described as fast, and its definitions can be analyzed for dead paths and conflicts. The article presents centralization and shared definitions as ways to reduce risk and accommodate policy changes.

### Source excerpt

When writing apps, we often talk about "business logic" and treat it like special code. We work hard to isolate our business logic from other parts of the code, like the view layer or framework-specific code, and we say that if you have limited test resources, testing your business logic is the first priority. Business logic is the core behavior of your app, but there's a certain class of business logic that I believe warrants extra attention: Policy.

## Case Study: Connecting the pipes: Building Dixon scalable B2B platform on Symfony and Drupal

DevFeed: [Case Study: Connecting the pipes: Building Dixon scalable B2B platform on Symfony and Drupal](<https://devfeed.tech/articles/case-study-connecting-the-pipes-building-dixon-scalable-b2b-platform-on-symfony-and-drupal-121164.md>)

Original publisher: [Read original article](<https://symfony.com/blog/case-study-connecting-the-pipes-building-dixon-scalable-b2b-platform-on-symfony-and-drupal>)

Author: Eloïse Charrier

Published: 2026-11-06T13:30:00Z

Content type: article

Language: en

Sources: [Symfony](<https://devfeed.tech/sources/symfony-blog.md>)

Topics: [Symfony](<https://devfeed.tech/topics/symfony.md>), [Drupal](<https://devfeed.tech/topics/drupal.md>), [Legacy Modernization](<https://devfeed.tech/topics/legacy-modernization.md>), [scalable-architecture](<https://devfeed.tech/topics/scalable-architecture.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>)

Tags: [apis](<https://devfeed.tech/tags/apis.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [async](<https://devfeed.tech/tags/async.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [b2b](<https://devfeed.tech/tags/b2b.md>), [backend](<https://devfeed.tech/tags/backend.md>), [blocking](<https://devfeed.tech/tags/blocking.md>), [business-logic](<https://devfeed.tech/tags/business-logic.md>), [canada](<https://devfeed.tech/tags/canada.md>), [case](<https://devfeed.tech/tags/case.md>), [case-study](<https://devfeed.tech/tags/case-study.md>), [drupal](<https://devfeed.tech/tags/drupal.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-operations](<https://devfeed.tech/tags/enterprise-operations.md>), [global](<https://devfeed.tech/tags/global.md>), [international](<https://devfeed.tech/tags/international.md>), [platform](<https://devfeed.tech/tags/platform.md>), [scale](<https://devfeed.tech/tags/scale.md>), [scale-across](<https://devfeed.tech/tags/scale-across.md>), [symfony](<https://devfeed.tech/tags/symfony.md>)

### AI overview

Dixon's platform had frequent 503 timeouts under peak load, while Drupal Commerce modules proved too rigid for its B2B pricing, order logic, and multi-ERP needs. Americaneagle.com moved hosting to Pantheon and used Drupal as an administrative shell, with Symfony handling business logic through isolated services in its dependency injection container. Custom ERP adapters connect the application with a PIM, marketing tools, and Pronto and DDS systems. Symfony Messenger queues handle work such as order transmission, catalog imports, and abandoned-cart triggers asynchronously; Symfony routing and security also support REST JSON APIs for decoupled front ends. The excerpt reports improved scalability and developer workflow, but gives no measured performance results.

### Source excerpt

Dixon is a global US manufacturer and supplier of hose fittings, valves, and fluid transfer products operating across more than a dozen international domains. To scale across these multi-regional enterprise operations, Americaneagle.com re-architected...

## Why Enterprise AI Needs Less Guesswork and More Structure

DevFeed: [Why Enterprise AI Needs Less Guesswork and More Structure](<https://devfeed.tech/articles/why-enterprise-ai-needs-less-guesswork-and-more-structure-118810.md>)

Original publisher: [Read original article](<https://hackernoon.com/why-enterprise-ai-needs-less-guesswork-and-more-structure?source=rss>)

Author: ShaoTung Lien (練紹彤)

Published: 2026-11-05T06:23:17Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [semantic-layer](<https://devfeed.tech/topics/semantic-layer.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [added](<https://devfeed.tech/tags/added.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [business](<https://devfeed.tech/tags/business.md>), [can](<https://devfeed.tech/tags/can.md>), [connect](<https://devfeed.tech/tags/connect.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-ai](<https://devfeed.tech/tags/enterprise-ai.md>), [generate](<https://devfeed.tech/tags/generate.md>), [help](<https://devfeed.tech/tags/help.md>), [layers](<https://devfeed.tech/tags/layers.md>), [less](<https://devfeed.tech/tags/less.md>), [more](<https://devfeed.tech/tags/more.md>), [natural-language-to-sql](<https://devfeed.tech/tags/natural-language-to-sql.md>), [needs](<https://devfeed.tech/tags/needs.md>), [rag-pipeline](<https://devfeed.tech/tags/rag-pipeline.md>), [retrieval-augmented-generation](<https://devfeed.tech/tags/retrieval-augmented-generation.md>), [semantic](<https://devfeed.tech/tags/semantic.md>), [semantic-data-modeling](<https://devfeed.tech/tags/semantic-data-modeling.md>), [semantic-search](<https://devfeed.tech/tags/semantic-search.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [sql](<https://devfeed.tech/tags/sql.md>), [structure](<https://devfeed.tech/tags/structure.md>)

### AI overview

Semantic layers reduce the business logic an analytics agent must infer: they expose approved metrics, dimensions, relationships, aggregation rules, and time logic so the model can map a request to established concepts, while the query system applies those rules and the database executes the query. This can prevent valid SQL from answering the wrong business question, provided definitions are agreed, mapped to physical data, validated, owned, versioned, and updated as needed; unclear underlying data models remain a limitation. The excerpt also distinguishes this from RAG: system design defines relevant context and retrieval scope, retrieval ranks evidence within that space, and the LLM synthesizes source-grounded answers. Retrieval representations may be enriched for discovery while returned evidence remains faithful to the source.

### Source excerpt

AI agents can generate valid SQL and still deliver wrong answers. Discover how semantic layers help connect AI to approved business definitions.

## Your Business, Always Current. Streamhouse - The Data Architecture for the Age of AI.

DevFeed: [Your Business, Always Current. Streamhouse - The Data Architecture for the Age of AI.](<https://devfeed.tech/articles/your-business-always-current-streamhouse-the-data-architecture-for-the-age-of-ai-117675.md>)

Original publisher: [Read original article](<https://www.confluent.io/blog/streamhouse-your-business-always-current/>)

Author: Yashwanth Dasari

Published: 2026-11-04T15:52:47Z

Content type: article

Language: en

Sources: [Confluent: Data in motion](<https://devfeed.tech/sources/confluent-data-in-motion.md>)

Topics: [data-engineering](<https://devfeed.tech/topics/data-engineering.md>), [stream-processing](<https://devfeed.tech/topics/stream-processing.md>), [semantic-layer](<https://devfeed.tech/topics/semantic-layer.md>), [data-governance](<https://devfeed.tech/topics/data-governance.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [Apache Kafka](<https://devfeed.tech/topics/apache-kafka.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [streaming data analytics](<https://devfeed.tech/topics/streaming-data-analytics.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [about](<https://devfeed.tech/tags/about.md>), [account](<https://devfeed.tech/tags/account.md>), [age-of-ai](<https://devfeed.tech/tags/age-of-ai.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [applications](<https://devfeed.tech/tags/applications.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [business](<https://devfeed.tech/tags/business.md>), [confluent-cloud](<https://devfeed.tech/tags/confluent-cloud.md>), [context](<https://devfeed.tech/tags/context.md>), [data](<https://devfeed.tech/tags/data.md>), [data-architecture](<https://devfeed.tech/tags/data-architecture.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [making](<https://devfeed.tech/tags/making.md>), [processes](<https://devfeed.tech/tags/processes.md>), [state](<https://devfeed.tech/tags/state.md>), [systems](<https://devfeed.tech/tags/systems.md>)

### AI overview

A Streamhouse is presented as an architecture for keeping reusable business state and context current across distributed systems so applications, AI agents, and analytics can act on it. It combines historical data with ongoing operational changes, maintains state incrementally, and supports replay, correction, and recomputation. Its three requirements are freshness with history, decentralized sharing without consolidating onto one platform, and mission-critical correctness, availability, security, recovery, and traceability. The described components include connectors, a durable event backbone, stateful processing, shared semantics and governance, and serving through streams, queries, APIs, or tables. Operational systems still authorize transactions; warehouses and lakehouses still support historical analysis and training. The architecture does not guarantee a globally synchronized "now," and implementations trade off latency, consistency, replay, cost, and operational complexity. The text gives examples including Siemens Healthineers, Neuron Systems, and Yelp, and presents Confluent's platform as one implementation; its claims about platform completeness are vendor claims.

### Source excerpt

A Streamhouse is a data architecture that continuously captures, processes, governs and serves current business state and context across distributed systems, making them available to applications, AI agents, and analytics.

## Build vs. buy: How to decide for your orchestration layer

DevFeed: [Build vs. buy: How to decide for your orchestration layer](<https://devfeed.tech/articles/build-vs-buy-how-to-decide-for-your-orchestration-layer-118917.md>)

Original publisher: [Read original article](<https://www.twilio.com/en-us/blog/insights/build-vs-buy-orchestration-layer>)

Author: Jesse Sumrak

Published: 2026-11-04T00:00:00Z

Content type: comparison

Language: en

Sources: [Twilio](<https://devfeed.tech/sources/twilio-blog.md>), [Twilio Blog](<https://devfeed.tech/sources/twilio-blog-2.md>)

Topics: [Orchestration](<https://devfeed.tech/topics/orchestration.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [AI Architecture](<https://devfeed.tech/topics/ai-architecture.md>), [build vs buy database solutions](<https://devfeed.tech/topics/build-vs-buy-database-solutions.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [advice](<https://devfeed.tech/tags/advice.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agent-runtime](<https://devfeed.tech/tags/ai-agent-runtime.md>), [all](<https://devfeed.tech/tags/all.md>), [api](<https://devfeed.tech/tags/api.md>), [build](<https://devfeed.tech/tags/build.md>), [build-vs-buy](<https://devfeed.tech/tags/build-vs-buy.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [industry-insights](<https://devfeed.tech/tags/industry-insights.md>), [layer](<https://devfeed.tech/tags/layer.md>), [one](<https://devfeed.tech/tags/one.md>), [orchestration](<https://devfeed.tech/tags/orchestration.md>), [platform](<https://devfeed.tech/tags/platform.md>), [right](<https://devfeed.tech/tags/right.md>), [vs](<https://devfeed.tech/tags/vs.md>)

### AI overview

The article recommends deciding separately for each orchestration layer: keep the decision engine that encodes business logic under your control, and assess whether to buy context, channel transport, or agent runtime based on your needs. Nova Gestões used documented APIs to integrate communications while retaining its decision logic; Eltropy consolidated communications onto one platform; Sweetwater moved off homegrown infrastructure after rising interaction volumes exposed technical limits, while keeping its CRM and workflow logic. The article suggests unifying real-time customer data before scaling AI, checking staffing and tenfold-volume capacity, and securing a data export path before buying. It describes channel compliance and deliverability as ongoing specialist work, while recommending control over business-specific models, prompts, and guardrails. These are examples and guidance from the supplied text, not a universal build-or-buy rule.

### Source excerpt

One CIO built his own orchestration layer. Another consolidated onto a platform. A third moved off homegrown. And...all three were right.

## Before You Model a Single Table: Data Modelling Questions to Ask for AI Agents in Snowflake

DevFeed: [Before You Model a Single Table: Data Modelling Questions to Ask for AI Agents in Snowflake](<https://devfeed.tech/articles/before-you-model-a-single-table-data-modelling-questions-to-ask-for-ai-agents-in-snowflake-116418.md>)

Original publisher: [Read original article](<https://medium.com/snowflake/before-you-model-a-single-table-data-modelling-questions-to-ask-for-ai-agents-in-snowflake-0ac71edf8172?source=rss----34b6daafc07---4>)

Author: Cesar Segura

Published: 2026-11-03T19:31:02Z

Content type: article

Language: en

Sources: [Snowflake Builders](<https://devfeed.tech/sources/snowflake-builders.md>)

Topics: [schema design](<https://devfeed.tech/topics/schema-design.md>), [semantic-layer](<https://devfeed.tech/topics/semantic-layer.md>), [JOIN](<https://devfeed.tech/topics/join.md>), [text2sql](<https://devfeed.tech/topics/text2sql.md>), [Data Quality](<https://devfeed.tech/topics/data-quality.md>), [knowledge-engineering](<https://devfeed.tech/topics/knowledge-engineering.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [AI Architecture](<https://devfeed.tech/topics/ai-architecture.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [aggregation](<https://devfeed.tech/tags/aggregation.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [analyst](<https://devfeed.tech/tags/analyst.md>), [architect](<https://devfeed.tech/tags/architect.md>), [article](<https://devfeed.tech/tags/article.md>), [business](<https://devfeed.tech/tags/business.md>), [business-analyst](<https://devfeed.tech/tags/business-analyst.md>), [column](<https://devfeed.tech/tags/column.md>), [cortex](<https://devfeed.tech/tags/cortex.md>), [cortex-agent](<https://devfeed.tech/tags/cortex-agent.md>), [data](<https://devfeed.tech/tags/data.md>), [data-modelling](<https://devfeed.tech/tags/data-modelling.md>), [generative-ai-tools](<https://devfeed.tech/tags/generative-ai-tools.md>), [governance](<https://devfeed.tech/tags/governance.md>), [model](<https://devfeed.tech/tags/model.md>), [modelling](<https://devfeed.tech/tags/modelling.md>), [ontology](<https://devfeed.tech/tags/ontology.md>), [questions](<https://devfeed.tech/tags/questions.md>), [snowflake](<https://devfeed.tech/tags/snowflake.md>), [table](<https://devfeed.tech/tags/table.md>)

### AI overview

AI agents infer query logic from schemas, so ambiguous grain, joins, dates and metric meanings can produce incorrect SQL. The article recommends documenting and testing each fact table's grain, exposing clear business columns, defining relationships and metric logic explicitly, and using scoped Snowflake Semantic Views over curated data. It distinguishes the executable query and metric layer (Semantic Views) from governed business definitions (Business Ontology) and AI-inferred context (Cortex Sense); ontology formulas document meaning, while Cortex Analyst executes the Semantic View expression, so they must stay aligned. It also advises profiling performance under realistic workloads and repeatedly evaluating representative business questions, including join, double-counting, ambiguity and permission cases. Business Ontology and Cortex Sense are noted as preview features as of October 2026.

### Source excerpt

A Snowflake Architect's guide to designing data that AI agents can actually understand Questions prior to modelling in Snowflake for your agents Every few weeks someone asks me the same thing: "We want a Cortex Agent on top of our data. How should we model it?" The honest answer is that most of the questions behind that sentence are not about the agent. They are modelling questions we should have answered years ago, and an agent now exposes them in public. A business analyst carries a lot of tacit knowledge: which date really means "sale", which orders are cancelled, what "revenue" means for Finance versus Sales. An agent has none of that. It reads your schema, infers, and writes SQL. Every ambiguity becomes an inference, and every inference is a chance for a wrong join, filter or aggregation. In this article we will walk through the six questions I ask teams before they start modelling: grain, shape, semantic views, business meaning, performance and evaluation. We will close with a checklist you can take to your next design session. Index 1. Why agents change the rules 2. Question 1: What is the grain, and does every column mean one thing? 3. Question 2: Star, snowflake or wide table, and how many joins are too many? 4. Question 3: How big should a Semantic View be? 5. Question 4: Who owns the meaning of a metric? 6. Question 5: Does physical performance still matter? 7. Question 6: How will we know it works? The Big Picture Conclusions References About Me 1. Why agents change the rules The first thing I explain is that an agent solution is not one model; it is a stack of layers, each with a different job. Confusing them is the root of most disappointing proofs of concept. Curated physical model: tables, views, facts, dimensions, types, keys and quality tests. It represents the data faithfully and consistently. Semantic View: the executable semantic layer. It describes how to query a domain and how to calculate its metrics: logical tables, relationships, dimensions

## Why Your LLM Keeps Matching the Wrong Products (And Why a Better Prompt Won't Fix It)

DevFeed: [Why Your LLM Keeps Matching the Wrong Products (And Why a Better Prompt Won't Fix It)](<https://devfeed.tech/articles/why-your-llm-keeps-matching-the-wrong-products-and-why-a-better-prompt-won-t-fix-it-114862.md>)

Original publisher: [Read original article](<https://hackernoon.com/why-your-llm-keeps-matching-the-wrong-products-and-why-a-better-prompt-wont-fix-it?source=rss>)

Author: Oleg Kokorin

Published: 2026-11-03T11:25:53Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Entity resolution](<https://devfeed.tech/topics/entity-resolution.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [AI-driven information retrieval](<https://devfeed.tech/topics/ai-driven-information-retrieval.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [Enhancing AI model performance](<https://devfeed.tech/topics/enhancing-ai-model-performance.md>), [llm-reasoning](<https://devfeed.tech/topics/llm-reasoning.md>)

Tags: [abbreviation](<https://devfeed.tech/tags/abbreviation.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [algorithm](<https://devfeed.tech/tags/algorithm.md>), [algorithms](<https://devfeed.tech/tags/algorithms.md>), [alternatives](<https://devfeed.tech/tags/alternatives.md>), [approach](<https://devfeed.tech/tags/approach.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [automate](<https://devfeed.tech/tags/automate.md>), [automated](<https://devfeed.tech/tags/automated.md>), [business](<https://devfeed.tech/tags/business.md>), [candidate](<https://devfeed.tech/tags/candidate.md>), [catalog-matching](<https://devfeed.tech/tags/catalog-matching.md>), [facets-of-likelihood](<https://devfeed.tech/tags/facets-of-likelihood.md>), [fine-tuning-llms](<https://devfeed.tech/tags/fine-tuning-llms.md>), [llm](<https://devfeed.tech/tags/llm.md>), [llm-prompting](<https://devfeed.tech/tags/llm-prompting.md>), [llms](<https://devfeed.tech/tags/llms.md>), [matching](<https://devfeed.tech/tags/matching.md>), [product-catalog-ai-prompts](<https://devfeed.tech/tags/product-catalog-ai-prompts.md>), [product-matching](<https://devfeed.tech/tags/product-matching.md>), [products](<https://devfeed.tech/tags/products.md>), [prompt](<https://devfeed.tech/tags/prompt.md>), [rag-architecture](<https://devfeed.tech/tags/rag-architecture.md>), [rules](<https://devfeed.tech/tags/rules.md>), [search](<https://devfeed.tech/tags/search.md>), [similarity](<https://devfeed.tech/tags/similarity.md>), [text](<https://devfeed.tech/tags/text.md>)

### AI overview

Product matching errors often come from retrieval, missing data, attribute handling, or business rules rather than prompt quality. The article recommends a staged system: retrieve candidates with lexical and semantic search, extract and normalize relevant attributes, then rank pairs using structured features and category specific rules. Evaluate candidate retrieval separately, since a correct product omitted from the candidate list cannot be selected later. Use configuration for changing rules and synonyms, and retrieve validated historical examples for difficult cases; irrelevant or outdated examples can mislead. Before changing models, check candidate coverage, input completeness, attribute normalization, and rule application. Applying LLMs only to retrieved candidates can lower processing costs but risks missing valid matches; broader processing may improve recall at higher cost. Cloud models have usage fees, while local inference requires infrastructure and maintenance, so compare total costs at the required quality.

### Source excerpt

Why do LLMs match the wrong products? Learn why text similarity falls short and how candidate search, attribute checks, and business rules improve matching.

## From Stories to Bugs: Story-Based Semantic Fuzzing of Interactive Systems

DevFeed: [From Stories to Bugs: Story-Based Semantic Fuzzing of Interactive Systems](<https://devfeed.tech/articles/from-stories-to-bugs-story-based-semantic-fuzzing-of-interactive-systems-113499.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.01173>)

Author: Yeshayahu Weiss, Achiya Elyasaf, Gera Weiss

Published: 2026-11-03T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Fuzzing/Fuzz testing](<https://devfeed.tech/topics/fuzzing.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [race-condition](<https://devfeed.tech/topics/race-condition.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>)

Tags: [ablation](<https://devfeed.tech/tags/ablation.md>), [apis](<https://devfeed.tech/tags/apis.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [business-logic](<https://devfeed.tech/tags/business-logic.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [deep](<https://devfeed.tech/tags/deep.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [fuzzing](<https://devfeed.tech/tags/fuzzing.md>), [interactive](<https://devfeed.tech/tags/interactive.md>), [interface](<https://devfeed.tech/tags/interface.md>), [magento](<https://devfeed.tech/tags/magento.md>), [model](<https://devfeed.tech/tags/model.md>), [openapi](<https://devfeed.tech/tags/openapi.md>), [ordering](<https://devfeed.tech/tags/ordering.md>), [ranking](<https://devfeed.tech/tags/ranking.md>), [reproduction](<https://devfeed.tech/tags/reproduction.md>), [rest-apis](<https://devfeed.tech/tags/rest-apis.md>), [semantic](<https://devfeed.tech/tags/semantic.md>), [stories](<https://devfeed.tech/tags/stories.md>), [systems](<https://devfeed.tech/tags/systems.md>)

### AI overview

Story-based semantic fuzzing searches constrained compositions of behavioral stories to reach deep valid states and expose concurrency-sensitive failures. In Behavioral Programming, semantic bindings and state constraints preserve legal prefixes, while event eligibility, schedule selection, and replay explore relevant interleavings. On Magento, overlap-aware ranking raised reproduction of a sporadic Shipping Fee race from 3.6% to 41.2%; a controlled ordering intervention reduced another failure signature from 100/100 initial executions to 0/200 constrained executions. In a REST API study, a pipeline generated stories, dependencies, and bindings from frozen public OpenAPI contracts. Under a shared black-box evaluation, Basic and Complex confirmed 0/11 and 11/11 semantic fault classes, compared with RESTler's 2/11 and EvoMaster's 0/11. Binding yielded 250/250 valid dependent operations versus 0/250 without it; prefix controls attributed the difference to preserving legal relational state.

### Source excerpt

arXiv:2611.01173v1 Announce Type: new Abstract: Complex interactive systems hide business-logic failures along two complementary axes: deep state-dependent behaviors that require long valid prefixes and concurrency-sensitive failures that depend on the ordering of otherwise legal operations. We present story-based semantic fuzzing, a methodology that treats semantically constrained compositions of behavioral stories as primary search objects. Implemented through Behavioral Programming, semantic binding and state constraints preserve legal prefixes, while event eligibility, schedule selection, and replay expose failure-relevant interleavings. We evaluate the methodology on Magento and four stateful REST APIs. On Magento, overlap-aware ranking increased reproduction of a sporadic Shipping Fee race from 3.6% to 41.2%; a controlled ordering intervention reduced a second failure signature from 100/100 initial executions to 0/200 constrained executions. For the REST study, a versioned end-to-end pipeline took each frozen public OpenAPI contract as its sole benchmark-specific model-generation input and automatically generated the Basic and Complex stories, dependency structure, and interface bindings. Under a shared black-box task and sequence-local evaluation contract, Basic and Complex confirmed 0/11 and 11/11 semantic fault classes, while RESTler and EvoMaster confirmed 2/11 and 0/11. A paired binding ablation produced 250/250 valid dependent operations with binding and 0/250 without it, while supplementary prefix controls localized the difference to preservation of legal relational state. Together, the studies show that searching admissible semantic compositions provides a unified and effective representation for reaching deep states and exposing concurrency-sensitive business-logic failures.

## The middle layer will make or break enterprise AI agents

DevFeed: [The middle layer will make or break enterprise AI agents](<https://devfeed.tech/articles/the-middle-layer-will-make-or-break-enterprise-ai-agents-112549.md>)

Original publisher: [Read original article](<https://www.cio.com/article/4242744/the-middle-layer-will-make-or-break-enterprise-ai-agents.html>)

Author: Bob Venero

Published: 2026-11-02T09:00:00Z

Content type: opinion

Language: en

Sources: [CIO](<https://devfeed.tech/sources/cio.md>)

Topics: [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [middleware](<https://devfeed.tech/topics/middleware.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [API Economy](<https://devfeed.tech/topics/api-economy.md>), [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [workflow automation](<https://devfeed.tech/topics/workflow-automation.md>), [AI Models](<https://devfeed.tech/topics/ai-models.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [apis](<https://devfeed.tech/tags/apis.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [artificial-intelligence-enterprise-architecture](<https://devfeed.tech/tags/artificial-intelligence-enterprise-architecture.md>), [business](<https://devfeed.tech/tags/business.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [cios](<https://devfeed.tech/tags/cios.md>), [contributor](<https://devfeed.tech/tags/contributor.md>), [data](<https://devfeed.tech/tags/data.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-ai](<https://devfeed.tech/tags/enterprise-ai.md>), [enterprise-architecture](<https://devfeed.tech/tags/enterprise-architecture.md>), [enterprises](<https://devfeed.tech/tags/enterprises.md>), [environment](<https://devfeed.tech/tags/environment.md>), [example](<https://devfeed.tech/tags/example.md>), [execution](<https://devfeed.tech/tags/execution.md>), [financial](<https://devfeed.tech/tags/financial.md>), [financial-data](<https://devfeed.tech/tags/financial-data.md>), [financial-services](<https://devfeed.tech/tags/financial-services.md>), [identity](<https://devfeed.tech/tags/identity.md>), [identity-management](<https://devfeed.tech/tags/identity-management.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [storytype-opinion](<https://devfeed.tech/tags/storytype-opinion.md>)

### AI overview

The article argues that enterprise agents' value depends on the integration and engineering layer that connects model reasoning to reliable action across business systems. For precise calculations, it recommends deterministic code such as Python or Node.js, with the model interpreting the results. Agents also need dependable APIs or MCPs, accessible data, documented business logic, identity management and connections to systems of record. MCP adoption does not remove the need for API/MCP management. Organizations with point-to-point technical debt may need integration modernization; agents expose gaps that people have been bridging manually, while one-off fixes can add further complexity. Because agent behavior is probabilistic and can vary with context, enterprise use requires dedicated engineering for testing, monitoring, maintenance, observability and recovery. The excerpt identifies four capabilities for scaling: mature integration practices, dedicated software engineering teams, strong technical leadership and a culture comfortable with software, data and calculated risk. Leaders should also distinguish workflows suited to agents from those better handled by conventional or,א

### Source excerpt

The hype around AI agents and the models that power them is warranted. But while they can give organizations a real competitive advantage, in reality, how much value they deliver ultimately depends on something much less glamorous: the middleware and integrations that connect agents to systems across enterprise workflows. Enterprises have used AI in various forms for decades, but agents represent a significant shift in how we put AI to work and what we ask it to do. The first phase of AI largely focused on generating, summarizing, analyzing and recommending information. Agents go a step further by executing actions and this is where the middle layer often gets overlooked. Without the right APIs, MCPs, data streams, tools, deterministic logic, identity management and systems of record, agents and models essentially operate in a sandbox. As enterprises adopt agents into real-world workflows, the question CIOs need to ask isn't simply, "Which AI agent should we deploy next?" It's, "Can our enterprise faithfully support software action on our behalf?" The model is becoming the commodity layer After decades of leading a technology organization and countless implementations, I've seen firsthand how important it is to align technology with the business problems it is meant to solve. When it comes to AI agents, one of the biggest mistakes I see organizations make is setting unrealistic expectations for how a model will operate within their existing enterprise environment. AI agents and models are often touted for what they can accomplish, which naturally focuses attention on their reasoning and execution capabilities. But we cannot simply layer them onto existing workflows and expect them to make decisions or take consistent, repeatable action reliably. Financial services make for a great example of this. Think about an investing agent who evaluates companies using financial data. When they need it to calculate something precise, like a company's cash burn ratio or runway,

[Next page](<https://devfeed.tech/topics/business-logic.md?cursor=WyIyMDI2LTExLTAyVDA5OjAwOjAwKzAwOjAwIiwgIjBlZWNhNjEwLWQyMTYtNGIyNC1iNTU5LTY0Zjg5YmZmYzc2NiJd>)