Marc-André Bombeck ebf032158e Give the intake toast one decision, and stop admitting two writes nothing calls ...

Three surfaces record a dose and all three had to reach the same two
conclusions inside somebody else's record: name the record, and drop an
Undo the server refuses. Two learned it and the dose ledger did not,
because the ternary was written out three times. It is written once now,
in the file the other two already share, with its own test.

POST /api/allergies and POST /api/family-history leave the frozen
delegable write set. The argument that admitted them still stands — an
allergy is the single most useful thing a caregiver can contribute — but
the only surface that posts to either lives in Settings, which a switch
closes, so no delegate could reach the form at any level. That is a
permission frozen ahead of the caller for it, and the list is built the
other way round on purpose.

Both delegable READ arms stay. A caregiver reading the allergy list is
what the feature is for; only the contribute step waits, and it comes
back in the same diff as the surface that offers it.

2026-08-03 18:47:42 +02:00

..

[id]

feat(sharing): open the lab and clinical-record reads to a delegate

2026-08-02 16:38:39 +02:00

route.ts

Give the intake toast one decision, and stop admitting two writes nothing calls

2026-08-03 18:47:42 +02:00