Answer Set Programming

The spreadsheet rule that never quite reaches the model Rules are everywhere in business software. An invoice total must match its line items. A loan file must contain the right documents before underwriting. A production schedule cannot assign the same machine to two jobs at the same time. A compliance workflow may tolerate uncertainty in OCR, but not uncertainty about whether a prohibited combination of fields has appeared. ...

Calendars are harmless until a computer has to reason about them. A human can say, “Ram has a dentist appointment in one hour, must pick up his insurance card from home, needs cash from the ATM, and travel takes 15, 20, 30, or 40 minutes depending on the route.” We see a small planning problem. A logic system sees actions, states, deadlines, durations, inertia, and a very annoying question: should every possible minute become a Boolean object? ...

Configuration sounds like the kind of problem declarative AI was born to solve. A customer specifies requirements. A system knows the rules. The machine fills in the valid product structure: modules into frames, frames into racks, capacities respected, incompatible combinations avoided, technical constraints satisfied. Nobody hand-codes every possible arrangement. Nobody manually enumerates the combinatorial swamp. Lovely. ...

Decisions Rarely Fail Because Everyone Disagrees Businesses are quite used to disagreement. Risk says no, growth says yes, legal says “only if we phrase it carefully,” and compliance brings a spreadsheet that somehow makes everyone sad. The hard part is not that these groups disagree. The hard part is that they often disagree using partly shared language. “Eligible,” “material,” “reasonable,” “high risk,” “recommended,” and “approved” may look like one vocabulary. In practice, they are local dialects wearing corporate badges. ...