KASA
The Decision Engine

Decisions, on a clock.Nothing stalls.

Pending--:--:--

The neutral engine between whoever decides and whoever acts — every decision classified, routed to whoever must own it, and held to a deadline. Built for anyone with an inbox full of decisions.

The co-equal engine

The problem

Two roles. One organization. And a handoff where everything stalls.

Every organization runs on a split that no software respects: someone decides, someone else acts — and the moment between them is where issues sit for weeks, authority gets murky, and accountability evaporates.

KASA is the co-equal engine that sits in that gap. It never takes a side. It classifies every decision, derives who actually holds authority, and routes it — with a clock attached.

The Approver
Decides collectively. Votes, ratifies, sets the threshold.
The Operator
Acts within authority. Executes, assigns, gets it done.
Industries

Anyone with an inbox full of decisions.

If it arrives by email and someone has to decide, KASA fits. The engine is identical — only the vocabulary changes.

Settlements, retainers, filings — the calls only a partner can make, routed in seconds.

Inbox
OC
Opposing counsel
counsel@bryant-llp.com
9:14 AM
RE: Settlement offer — Henderson matter
Our client will accept $85,000 to resolve all claims, provided we have a response by Friday…
KASA routes it
Settlementhigh-stakes$85,000
Approval-required→ Supervising partner
2d 00h
Supervising partner decidesAssociate acts
The loop

One decision, start to close — and it never leaves the rail.

Report to resolution runs through seven stages. Each one is owned, timed, and recorded. Nothing falls between the decider and the doer because the engine holds the thread.

  1. 01
    Report
    Anyone files an issue with a few facts.
  2. 02
    Classify
    Category, urgency, cost, budgeted — four axes.
  3. 03
    Route
    Five gates derive who holds authority.
  4. 04
    Act · Decide
    The operator executes, or the approvers decide.
  5. 05
    Track
    An SLA clock runs against every owner.
  6. 06
    Escalate
    Misses climb the ladder to the chair.
  7. 07
    Close
    Minutes, work order, financials — logged.
The invariant, enforced in code: nothing exits the engine without a clock and an owner.
The engine

Pure, deterministic, and built to be audited.

A side-effect-free decision core, surfaced through a KASA-branded app. The same interface that classifies today swaps to AI tomorrow — the router never changes.

Deterministic classifier

Scores every issue across category, urgency, cost and budget. It records the raw facts and applies no policy of its own — the engine stays explainable.

Five-gate router

One ordered decision tree, first match wins. The sole consumer of the approval threshold — and the only place authority is ever decided.

SLA clock & escalation

Urgency drives the deadline; a route-aware ladder climbs from owner to chair to full agenda when a deadline slips. Time is always injected, never assumed.

Immutable audit log

Every routing decision and authority derivation is appended — the gate that matched, the owner assigned, the clock that started. The record is the proof.

Co-equal dashboard

An approver / operator split with live status and escalation pills, decision intake, and per-row actions that drive the whole loop — approve, assign, ratify, close.

AI classifier, ready

Phase two drops an AI classifier behind the identical interface — confidence scores and human override included. The routing contract is untouched.

On the roadmap
The logic contract

Five gates. Evaluated in order. First match wins.

Authority isn't a guess or a setting buried in a menu — it's derived. The order is load-bearing, and every gate is independently testable.

IncomingProduction outage — region 2Incident · emergency · $6,800
1IF the category is a configured emergency category
2ELSE IF an always-approve flag fires — contract, spend commitment, policy, legal, precedent
3ELSE IF the spend is unbudgeted and cost ≥ the threshold T
4ELSE IF it's a governance or compliance category
5OTHERWISE — within the operator's standing authority
RoutedEmergency-override→ Operator, act now
Emergency-override is bounded: only configured categories qualify. The urgency axis never grants override authority — so no reporter can seize unilateral action by tagging an item “emergency.” Urgency is free to drive the deadline instead.
The co-equal dashboard

Both sides of the decision, on one screen.

The approvers' decisions and the operators' actions, side by side — each row carrying its status, its owner, and the clock it's running against.

kasa.app / acme-operations / decisions

Acme Operations

Org-wide · 6 teams · approval threshold $5,000
0
Open decisions
0
Awaiting approval
0
With operators
0
Escalated
Approversmust decide
Capital expenditure — new line
Capex · unbudgeted · $48,200 · Gate 3
4 / 7 approved2d 4h
Change customer refund policy
Governance · Gate 4
Open5d 1h
Vendor contract renewal
Procurement · $31,000 · Gate 2
RatifyOverdue 6h
Operatorsact within authority
Production outage — region 2
Incident · emergency · $6,800 · Gate 1
Override2h left
Replace field sensor unit
Maintenance · budgeted · $1,150 · Gate 5
Assigned1d 3h
Onboard a new contractor
Operations · budgeted · $900 · Gate 5
ClosedOn time
The approach

Build the engine natively. Integrate only the money.

KASA owns the decision layer end to end — its own system of record, its own audit trail. It doesn't sit on top of your existing tools, and it doesn't try to be your system of record for everything. It does the one thing they can't: hold authority and time.

Native where it matters

Classification, routing, SLAs and the audit log are ours — pure, deterministic, and proven by the test suite.

Rent the financial seam

Accounting and payments write back through a single port — your existing systems, not a rebuild.

Not another portal

We don't replace your CRM, ticketing or ERP. We resolve the decision they leave stranded between approver and operator.

Put it on the clock

Every decision owned. Every clock running.

Stop losing weeks in the handoff between whoever decides and whoever acts. KASA routes the decision, starts the clock, and closes the loop.