01 / Evidence
What do we
know?
Package date, purchase date, storage and lifecycle events contribute different levels of evidence.
Freshness rescue / 4DK
USE THIS
FIRST.
The food closest to becoming a problem should get a louder vote. 4DK manages freshness as kitchen context so the next meal can rescue something before it turns into waste.
freshness should
change dinner.
change dinner.
Fresh / use soon / priority / check
Direct answer / freshness
A date is not the
whole story.
4DK keeps package dates, storage, opened or cooked states, estimates and confidence separate. Then freshness can influence what gets suggested without pretending an estimate is certainty.
What do we
02 / State
What needs
attention?
Useful states such as Fresh, Use Soon, Priority and Check are easier to act on than a fake precise expiry.
03 / Action
Cook the right
thing first.
Meal suggestions can promote ingredients that need using before novelty wins by default.
waste less.
without babysitting.
without babysitting.
The operating rule
4DK manages freshness.
You manage exceptions.
Most of the time, freshness should work quietly. Ask the user only when evidence is genuinely unresolved. The system should do the boring part.
Get 4DK →Quick answers.
Clear enough for humans. Structured enough to become useful search and answer-engine material later.
Will 4DK tell me food is spoiled?
Not from an estimate alone. Estimated freshness is treated as uncertainty, not a safety verdict.
Can it tell the difference between best-before and use-by dates?
That is the design. Date semantics remain distinct instead of being collapsed into one generic expiry field.
Does storage matter?
Yes. Fridge, freezer, pantry, opened, cooked and defrosted states can materially change the useful freshness context.
4DK.FOR D KITCHEN.
