About and research / Critiques we published Edit on GitHubMarkdown

Critiques we published

We asked hard questions about Cookwala and wrote the answers down. Each concern has an id in the action plan's concern register, along with our response and its status. Reviews from outside are welcome and will be listed here.

Is this going to work? (strategy) #

ConcernShort answerStatus
The market doesn't exist yet; the spec is ahead of productsSmall Core, demo first, no new spec without usersCore 0.2 done; device demo next
Nobody powerful has a reason to adoptLead with each adopter's gain; useful without robotsFood-bank pilot and device partner sought
The simulators prove what they assumeFair baseline, ranges, "illustrative" labels; pilots replace themOpen
Hunger is about poverty and conflict, not surplusCookwala contributes; it doesn't claim to end hunger aloneMessage changed
Safety, liability and attack surfaceLimits enforced on the device; refusal; recalls; incident reportsSpec done; certifier review open
Privacy (health and religion data, ledgers vs erasure)Local-first, selective disclosure, hash-only logs, consentSpec done; impact assessment open
Too complexCore 0.2; everything else marked experimentalDone
Founder dependencyGovernance path to a neutral homeGOVERNANCE.md

Is the technical design sound? #

ConcernWhat changed in Core 0.2
Operations had no physical meaningEnvelopes, heat levels, sensor ladders, altitude rule, test vectors
Unit and number bugs°C only, absolute tolerances, kitchen units, densities, decimal money
Schemas accepted typosStrict schemas with x- extensions; offline bundle
One mutable Mission documentEvent log + projection, single sequencer, transitions table
The ledger proved littleKey records with revocation, witnessed checkpoints, rewrite detection
Undefined event delivery; safety on the busSequence numbers, latency classes, heartbeats, "safety is local"
API surfaces driftCore OpenAPI; every reference checked in CI
No verifierReference library and 106 conformance vectors

Reviews we are asking for #

W3C TAG (identity, JSON-LD), IETF SCITT (event-log transparency), food scientists (envelopes), food-safety officers and dietitians (rule packs), a security audit, a data-protection review, and a certifier's gap analysis. See the external review program.