flagship · the thesis
klip
Every mini-app feeds klip. One button replaces like / save / comment; every klip is a piece of signal that lands on a klip profile. The constellation exists to acquire, qualify, and route audience to klip.
What's left to do — klip
no live PRD-equivalent in repo · derived from PITCH.md + README.md 2026-05-15 · marked needs brief where uncertain
- klip-button protocol spec — events, payload shape, auth model. Without this, no mini-app can adopt cleanly.
-
RN SDK — consumable by bpm, knead, tape. Single
<KlipButton/>+useKlip(). - klip profile ingest — cross-app klips land on one feed
- Attribution — track which mini-app drove each klip
- bpm pilot — first mini-app to adopt the protocol (run summary klips)
- Public launch criteria needs brief — what does "klip is live" mean?
Where it lives
Building| Main repo | open ↗~/Documents/Walle-codes/klip |
| PITCH | open ↗klip/PITCH.md |
| README | open ↗klip/README.md |
| Expo app | open ↗klip/app/ |
| Native iOS | open ↗klip/ios/ |
| Web / TV | web ↗tv ↗ |
| Backend | open ↗klip/supabase/ |
| Marketing | Marketing ↗designs ↗command-center ↗ |
| Pitch deck | open PDF ↗ |
| Screenshots | open ↗ |
| Vault notes | klip/ ↗raw/klip-saves/ ↗ |
| Ideation | open ↗ |
The klip-button protocol
Standing rule: every Lino Labs mini-app replaces its native engagement primitive with a single klip button. The mini-app keeps the audience; klip keeps the signal.
- Klip-button protocol spec (events, payload, auth)
- RN SDK consumable by bpm, knead, tape
- Klip profile ingests cross-app events into one feed
- Attribution: which mini-app drove the klip
Adoption across the portfolio
- bpm — run summary klipsbpm status →
- knead — TBD (HIPAA boundary; design carefully)knead status →
- tape — TBD (concept stage)tape status →
Lino Labs · klip · status · the thesis