app · health · HIPAA-bound
knead
A Lino Labs mini-app in the health space. Real codebase exists (mobile + backend + infra). Full brief from Sebastian is pending.
Waiting on Sebastian's full brief. This page is a scaffold — what's documented below was discovered by audit, not briefed. Treat as provisional until confirmed.
What's left to do — knead
stubbed — needs brief · derived from repo audit 2026-05-15, not from Sebastian
- Capture full brief from Sebastian — replaces this scaffold with real content
- Audit knead/tasks/ to surface real open work
- Design HIPAA-aware klip-feed (klip the routine, not the patient data)
- Pick a visual identity beyond the current warm-serif scaffold
Where it lives
Exploring| Repo | open ↗~/Documents/knead |
| Mobile | open ↗knead/mobile/ |
| Backend | open ↗knead/backend/ |
| Infra | open ↗knead/infra/ |
| Docs | open ↗knead/docs/ |
| Tasks | open ↗knead/tasks/ |
| Correspondence | open ↗knead/correspondence/ |
| HIPAA | knead/HIPPA signed with Wisper Flow.pdf |
| Vault notes | open ↗vault/Knead/ |
klip feed (to design)
HIPAA boundary will constrain what knead can ever klip publicly. Likely shape: klip the routine, not the patient data.
- Decide klip-button scope under HIPAA
- Patient/practitioner consent model for klips
- De-identification pipeline before klip-feed ingestion
Open questions for Sebastian
- Who is the user (patient, practitioner, both)?
- What's the current ship status of mobile + backend?
- Visual identity / brand direction for knead's umbrella page?
- How (if at all) does knead feed klip given HIPAA?
Lino Labs · knead · status · scaffold pending brief