How it works
One small model reads. Plain code plans, checks, and defends the plan.
The model reads
Every message in the pack - English, Urdu script or Roman Urdu - goes through one small model (gpt-oss-20b) in a single call. It extracts structured facts: students, venues, prices, judges, committed costs, requirements. It never does arithmetic and never decides.
Code plans
Teams, judges needed, people to feed, the cheapest venue that fits, food within the cap, a schedule that sums exactly to the event length - all computed in code, where arithmetic cannot hallucinate. Newer dated messages replace older ones; renamed items are matched, never double-counted.
Validators guard
Six checks run after every build: budget, venue fit, food, judges, schedule, coverage. A quantity scan - digits, spelled-out numbers, even Urdu digits - catches messages that would starve the plan, and updates are transactions: if an update would break a check that currently passes, it is rolled back and the reason is printed.
What makes it different
- Fact ledger. Every figure in the plan names the message it came from. Click any number on the plan to see its source.
- Risks and recommendations. The agent reads its own plan for thin headroom - budget, venue seats, spare judges, squeezed hacking time - and names the lever that fixes each one.
- Agent chat. After a plan is built you can talk to the agent: send updates in plain words, or ask "budget kitna bacha?" - questions are answered from the plan, with no model call.
- Try to break it. Tricky messages - wrong quantities, unapproved requests, outdated prices - can be fired at the live plan to watch it defend itself.
- Token-lean. One model call for a whole pack, at most two for an update, and every call is printed in the trace with the tokens the API reported.
Two ways to run it
This website runs the same logic in your browser: upload a messages file, add your own API key, and the plan, the chat and the trace all happen on the page. The terminal version in the repository runs the identical design from one command - python3 main.py messages.txt - and writes plan.txt, trace.txt and the same plan page to disk.