Blog

Why the Best Way to Govern an Agent is to Treat It Like a Human

Labels
AI(12) AJAX(112) App Studio(10) Apple(1) Application Builder(245) Application Factory(207) ASP.NET(95) ASP.NET 3.5(45) ASP.NET Code Generator(72) ASP.NET Membership(28) Azure(18) Barcode(2) Barcodes(3) BLOB(18) Business Rules(3) Business Rules/Logic(140) BYOD(13) Caching(2) Calendar(5) Charts(29) Cloud(14) Cloud On Time(2) Cloud On Time for Windows 7(2) Code Generator(54) Collaboration(11) command line(1) Conflict Detection(1) Content Management System(12) COT Tools for Excel(26) CRUD(1) Custom Actions(1) Data Aquarium Framework(122) Data Sheet(9) Data Sources(22) Database Lookups(50) Deployment(22) Designer(178) Device(1) Digital Workforce(3) DotNetNuke(12) EASE(20) Email(6) Features(101) Firebird(1) Form Builder(14) Globalization and Localization(6) HATEOAS(3) How To(1) Hypermedia(2) Inline Editing(1) Installation(5) JavaScript(20) Kiosk(1) Low Code(3) Mac(1) Many-To-Many(4) Maps(6) Master/Detail(36) Micro Ontology(5) Microservices(4) Mobile(63) Mode Builder(3) Model Builder(3) MySQL(10) Native Apps(5) News(18) OAuth(9) OAuth Scopes(1) OAuth2(13) Offline(20) Offline Apps(4) Offline Sync(5) Oracle(11) PKCE(2) Postgre SQL(1) PostgreSQL(2) PWA(2) QR codes(2) Rapid Application Development(5) Reading Pane(2) Release Notes(185) Reports(48) REST(29) RESTful(30) RESTful Workshop(15) RFID tags(1) SaaS(7) Security(81) SharePoint(12) SPA(6) SQL Anywhere(3) SQL Server(26) SSO(1) Stored Procedure(4) Teamwork(15) Tips and Tricks(87) Tools for Excel(3) Touch UI(93) Transactions(5) Tutorials(183) Universal Windows Platform(3) User Interface(338) Video Tutorial(37) Web 2.0(100) Web App Generator(101) Web Application Generator(607) Web Form Builder(40) Web.Config(9) Workflow(28)
Archive
Blog
Monday, December 1, 2025PrintSubscribe
Stop Teaching AI to Write SQL. Give It a User Interface.

The obsession with "Text-to-SQL" is a strategic error. Across the enterprise, teams are burning millions of dollars trying to teach Large Language Models (LLMs) to query databases directly. The dream is a "Chat with your Data" bot that can answer anything.

The reality is a nightmare of hallucinations, security risks, and broken schemas.

Why? Because you are asking the AI to do a job you wouldn't even trust your smartest human employees to do.

The Sales Clerk Paradox

Imagine you hire a new sales clerk for your retail store. A customer walks up and buys a t-shirt.

Option A (The SQL Way): You give the clerk a command-line console and say: "To record this sale, please write an INSERT statement into the Orders table, then an UPDATE to decrement Inventory, and don't forget to JOIN the TaxRates table to calculate the VAT. Oh, and please don't accidentally DROP TABLE Customers."

This is absurd. It requires the clerk to be a Computer Science major. It is slow, error-prone, and dangerous.

Option B (The UI Way): You give the clerk a Cash Register (User Interface).

The screen presents three buttons: [Checkout], [Return], [Exchange].

The clerk doesn't need to know the schema. They simply look at the goal ("Sell T-Shirt") and classify which button matches that goal.

The Insight: The UI acts as a Cognitive Compressor. It collapses the infinite complexity of the database into a finite set of safe, valid choices.

AI is Just a Fast User

Why do we treat AI Agents differently?

When you force an LLM to write SQL, you are treating it like the clerk in Option A. You are forcing a probabilistic engine to perform a deterministic, high-risk task.

You should be treating the AI like Option B.

If you give the AI a User Interface, you turn an "Infinite Generation Problem" (writing code) into a "Finite Classification Problem" (clicking a link).

  • The Human looks at the screen and thinks: "I need to sell this. I will click 'Checkout'."
  • The AI looks at the API and thinks: "The prompt is 'Sell Item'. The available links are create-order, return-item. It classifies create-order as the match."

The AI doesn't need to be a genius. It just needs to be a fast sales clerk.

The Dual-Interface Advantage

This is the core philosophy behind the Code On Time platform. We believe that the best way to control an AI is to give it the exact same tools you give your humans.

When you build an application with App Studio, you are building two interfaces simultaneously:

  1. The Visible UI: A professional-grade, fluid, and responsive interface for your Human workforce.
  2. The Invisible UI: A self-describing HATEOAS API for your Digital Workforce.

They are mirror images. Every time you add a validation rule, hide a button, or filter a grid for your human users, you are instantly training your AI Agent.

Don't want to replace your existing human apps? You don't have to. You can configure the Micro-Ontology to run in "Headless Mode." In this configuration, you restrict the full Visible UI (forms and grids) to Administrators and Developers only. When your standard workforce logs in, they are greeted by a clean, fullscreen AI Prompt—a secure, corporate gateway similar to ChatGPT. This interface allows them to query data and execute workflows using natural language, while the underlying app enforces all security and logic. Your team can even interact with this agent via Email and Text Message, allowing you to keep your existing legacy applications for manual tasks while layering a modern Digital Workforce on top.

The "Micro-Ontology" Revolution

This approach transforms your application into a Micro-Ontology.

We call it "Micro" because you don't need to model your entire enterprise at once. You don't need a multi-year "Digital Transformation" budget or a massive Data Lake project. You just need to build one app.

  • Start Small: Build a "Sales App." It automatically creates a secure, intelligent Micro-Ontology for customers and orders.
  • Grow Fast: Build an "Inventory App." It creates a Micro-Ontology for products and stock.
  • Federate: Use our built-in Federated Identity Management (FIM) to link them together.

Suddenly, you have a Federated Mesh of intelligence. Your AI Co-Worker can "hop" securely from the Sales App to the Inventory App, carrying the user's identity and permissions across the boundary. You achieve total AI enablement without the massive financial investment of a monolithic system.

You Are Now an AI Developer

Stop building "AI Bots" in a silo. Start building Apps. By focusing on the Visible UI, you solve the hardest problems in AI—Security, Context, and Hallucination—without writing a single prompt.

You aren't just building software. You are curating the reality for your Digital Workforce. The App IS the Ontology. Learn about the Micro-Ontology Factory.
Labels: AI
Monday, December 1, 2025PrintSubscribe
The Living Ontology: Refactor Intelligence at the Speed of Thought

For decades, the "Enterprise Ontology"—the definitive map of your business data and rules—has been treated as a static artifact. It’s usually a massive documentation project or a rigid Data Warehouse schema that takes months to build and years to update. By the time it’s finished, the business has already moved on.

At Code On Time, we believe the Ontology shouldn’t be a document. It should be Software.

With the Micro-Ontology Factory, we are introducing a radical shift: The App IS the Ontology.

From Static Schema to Living Application

When you build a database web app with App Studio, you aren't just building screens for humans. You are simultaneously generating a self-describing HATEOAS API that serves as the cognitive map for your AI Agents.

This tightly coupled architecture unlocks capabilities that static data lakes can never match:

  • Infinite Refactoring: Need to track a new metric or enforce a new business rule? Don't file a ticket with the Data Team. Just update the app in App Studio. Your AI Co-Workers instantly "see" the new logic and adapt their behavior.
  • Unified Operations & Analytics: Stop separating "doing work" (OLTP) from "measuring work" (OLAP). Build analytical dashboards directly into the visible UI to give your Agents explicit "thinking paths" for complex questions.
  • Disposable Intelligence: Because Micro-Ontologies are fast and cheap to generate, you can spin up a temporary, single-purpose "Headless App" to solve a specific problem (like a merger or audit) and discard it when the job is done.
  • Real-Time Governance: Control the economics of your digital workforce. Instantly switch user roles from expensive "Reasoning" models to fast "Flash" models, or cap daily spending limits across the enterprise—all without a deployment cycle.

The Future is Agile

Intelligence is no longer a capital expenditure; it is a flexible operational expense. It’s time to stop treating your data model like a museum piece and start treating it like a living, breathing business asset.

Ready to see how it works?

Read the full vision: The Agile Ontology
Tuesday, November 25, 2025PrintSubscribe
Expanding Your Toolkit: The Strategic Value of SqlText

The SQL Business Rule has long been the superpower of the Code On Time developer. It allows you to inject validation, logging, and custom data processing directly into your application using the language you know best—SQL. For high-performance, database-specific tasks, it remains the gold standard.

But as the Code On Time platform evolves with the Digital Workforce, Builder Edition, and AI Scaffolding, there are specific scenarios where you might need a different kind of tool.

This is where the [ProjectNamespace].Data.SqlText utility class shines.

It isn't about replacing the SQL rules you love; it's about extending your reach to platforms and technologies where raw T-SQL or PL/SQL cannot go.

1. The Key to the Builder Edition (SQLite)

The Builder Edition allows you to build unlimited commercial applications for free and accelerated by the Digital Workforce. To make this portable and lightweight, it defaults to using SQLite.

While SQLite is a powerful database engine, it does not support the rich procedural languages (like T-SQL or PL/SQL) that drive standard SQL Business Rules.

  • The Challenge: How do you write server-side validation logic (e.g., "Check if Customer exists") in an app running on SQLite?
  • The Solution: Type: Code business rules using the SqlText class. This allows you to write standard SQL queries wrapped in C# or VB.NET, which the framework automatically translates for SQLite. It is the only way to build complex server-side logic for Builder Edition apps.

2. A Blueprint for AI Scaffolding (GEN)

We are introducing GEN (Scaffolding) capabilities that allow you to "export" your application logic to completely different technology stacks, such as Next.js, Python, or standard ASP.NET Core APIs.

  • The Challenge: An AI agent cannot easily translate a block of raw T-SQL into a Node.js API route because the logic is "locked" inside the database dialect.
  • The Solution: Logic written with SqlText acts as a "White Box" for the Axiom Engine. The AI can read your C# code, understand the intent, and natively re-implement it in the target language. If you plan to use your app as a specification for a custom build, SqlText ensures your business rules travel with you.

3. Debugging with "Pro Code" Tools

For complex logic, nothing beats a real debugger.

  • The Advantage: Unlike SQL scripts, Type: Code rules live in your project's source files. You can use the "Edit Code" action to open your rule in Visual Studio, set breakpoints, and step through your logic while the app runs. It combines the speed of the App Studio with the precision of a professional IDE.

Learn the Pattern

We have released a comprehensive tutorial to help you add this tool to your belt. Whether you are building a portable app for the Builder Edition or preparing a specification for the Digital Workforce, this guide shows you how to write secure, database-agnostic logic.

Read the Tutorial: Using the SqlText Class in "Code" Business Rules
Master the tools that let you build anywhere, for any platform.
Labels: Business Rules