Talos
Four agents, twenty-three skills; you decide.
Talos is the layer of mind that works on the data of CENPRA products. Every morning it tells you in plain language whether your business is normal or not and shows why; it drafts orders, production and transfers; it asks before turning what it learned into a rule. It never invents a number; every figure has a source.
LiveRuns inside Brain.
Four agents
What each agent may do alone, what it may do only with approval, and what it must say when data is missing are all written down. None of them starts an outward-facing action on its own.
- Chef
- Synthesises and prioritises: today's single most important topic, where money is leaking, which item carries and which weighs. It applies none of the menu, price or campaign decisions; it proposes.
- Patrol
- Looks at the record itself: is the number right, is it consistent. Hunts negative balances, unreconciled tills, missing documents, duplicates. If a check did not run it says "not audited", never "clean"; it writes no correcting entry.
- Planner
- Prepares tomorrow: draft orders, production plans, transfer proposals, payment schedules. Computes days of cover and checks a sister branch's surplus before buying. Purchases, transfers, production orders and payments never go without approval.
- Reporter
- Tells what happened: end-of-day, weekly and monthly summaries with the source and time of every figure. Partial data is stamped partial; only summaries go out, and only to approved recipients.
Twenty-three skills
Every skill knows which data it works on, at which rhythm it checks (every morning, every evening, hourly, weekly, monthly or on an event), how it decides and what to say when data is missing.
Sales, menu and profitability
- Product sales analysis
- What sold how much, and where it stands against its own normal.
- Menu engineering
- Items that carry, items that weigh, items whose price or recipe needs a question.
- Recipe cost
- How an input price rise lands on plate cost; which recipes got expensive.
- Campaign evaluation
- Did the campaign bring sales, or did the discount eat them.
- Weekly business summary and period profitability
- Net profit after ingredients, staff and other costs; estimated figures are called estimates.
Operations
- Stock control
- Critical levels, days of cover; an item without a threshold counts as "threshold missing", not "zero".
- Count discipline
- Were counts done, are variances explainable, which item never reconciles.
- Production planning
- A production draft based on tomorrow's need.
- Inter-branch transfers
- A sister branch's surplus before a purchase.
- Waste and voids
- Waste and void patterns; one-day noise is separated from a persisting problem.
- Daily plan and end-of-day summary
- Plan in the morning, summary in the evening; against an eight-week baseline of the same weekday.
Money
- Till reconciliation
- Does the till match the records; a day that does not is named.
- Collections and cash flow
- Late collections, upcoming payments, the cash picture.
- Invoice control
- Price, quantity and supplier consistency on every invoice entry.
- Staff performance and labour ratio
- Payroll against net revenue; pseudonyms instead of names, and approval does not relax that rule.
External relations and conduct
- Supplier management
- On-time delivery, price changes, a supplier report card.
- Reviews and reputation
- Recurring topics in guest reviews.
- Culture distillation
- A pattern that holds in at least six of eight weeks becomes a culture candidate; one that stops holding is withdrawn. Culture is a list that can shrink, not only grow.
- Approval rules, scope and limits, tone, synthesis and prioritisation
- A proposal waiting longer than four hours expires and is reported; each user sees only the branches they are entitled to; full sentences, no blame; if everything is important, nothing is.
Principles
The system computes, Talos interprets.
Every number comes from live data tools; the model produces none. The risk of an invented figure is removed by design.
It asks before making a rule.
A habit it learns becomes a candidate first; it needs your approval to become a standing rule. It notices when a rule stops holding and withdraws it.
It says when data is missing.
The difference between "no data" and "truly zero" is kept; if a check did not run it says "not audited".
Nothing is done without approval.
Purchases, transfers, production orders and payments touch the outside world; all four wait in the approval queue. A proposal unanswered for four hours expires and is reported.
Start with one branch.
Talos starts inside Brain, in one branch; as it learns the rhythm, its proposals become rules only with your approval.