iKwath - a pod-based smart Kwatha (Kadha) maker that prepares a fresh, AFI/API-standardized decoction from coarse powder (yavaku?a c?r?a) on demand, in the shortest practical time without altering the decoctions quality or yield

The receipts 🧾

Every red flag on this statement, in full. These are the four places it bites.

1. Exhibit A

   The one thing that distinguishes this from a programmable kettle is proving the accelerated decoction matches the classical one chemically, and that needs HPTLC or HPLC comparison — arrange lab access in week one or accept that your central claim is unevidenced

2. It gets worse

   Raising temperature is the obvious way to go faster and the statement explicitly rules it out, so a team that quietly boils harder has answered the opposite of the question asked

3. Still reading?

   Extract density on a refractometer is measurable and cheap and is genuinely worth doing, but it evidences quantitative yield only — it says nothing about whether the constituent profile shifted, and you should say so rather than let it stand in for both

4. And the finisher

   Food-grade contact surfaces, boil-over and dry-run protection are stated requirements that hardware teams treat as polish, and a device that scalds a judge ends the presentation

The damage report 📉

Every score this statement earned, and what each one actually costs you.

• Feasibility

  3/5

  Buildable. Not comfortably. There is a week in here you have not planned for yet.

  The appliance itself is well within reach — a controlled heater, a load cell, a filter and a pump are cheap and the statement even fixes the volumes and temperature for you — but the central claim, that acceleration leaves the constituent profile unchanged, needs chromatographic comparison against a classically prepared control, and that requires a phytochemistry lab you must arrange rather than assume.

• Innovation scope

  4/5

  There is something genuinely new here. Do not bury it under another dashboard.

  The statement fixes the pharmacopoeial constraints deliberately and then leaves the actual engineering problem wide open, listing several acceptable acceleration routes without choosing one, so how you shorten the cycle while holding temperature and reduction endpoint constant is genuinely your contribution.

• Clarity

  5/5

  The ask is unambiguous, which quietly removes your favourite excuse.

  Unusually exact for a hardware statement — it gives the temperature band, the reduction ratio, the water and dose volumes, the chamber size, the pod-as-brew-bag design, the cleaning requirements, the safety interlocks, which acceleration methods are acceptable and which are not, and the five criteria it will be evaluated on.

• Acceptance potential

  4/5

  Strong footing before you have written a line. Try not to waste it.

  Physical, consumable output, a completely specified target, a mislabelled theme and a field almost nobody will enter all count strongly in its favour, but the equivalence claim that the statement puts at the centre needs lab analysis most teams cannot arrange, which caps how far the submission can honestly go.

• Effort

  Heavy

  Heavy. Somebody on this team is not sleeping in week three. Pick who, on purpose.

  Chamber and filter fabrication, heater and temperature control, load cell and density instrumentation, pod encoding and reading, dispensing, safety interlocks and cleaning design is a full appliance build, and the validation work against a classical control sits on top of all of it.

• Demo-ability

  Easy

  Easy to demo — and so is everyone else's. Working is the floor here, not the achievement.

  The judges watch it brew and then drink the result, and the side-by-side against a hand-prepared control makes the comparison the demo rather than a claim about the demo — very few statements let you hand the panel the actual output.

The demo they will have already seen 🪞

Somewhere around 70–160 teams are heading here, and the description is doing the choosing for most of them. They will read the same brief, reach the same architecture, and build a version of the same demo you are planning. Being correct is the floor. If your five minutes could be swapped with the team before you and nobody in the room would notice, you have not picked badly — you have built predictably, which costs exactly the same and hurts more.

What survives 🛡️

The ground worth standing on when the questions start.

• The pharmacopoeial specification defines correctness externally — temperature band, water proportion, reduction endpoint and dose are all given, so you are engineering to a published standard rather than to an invented one
• The judges can drink the output, which is about as direct a demonstration as exists, and brewing a classical control alongside turns the whole pitch into a comparison rather than an assertion
• The theme is filed under Fitness and Sports, so an Ayurvedic appliance is invisible to anyone browsing MedTech, hardware or AYUSH