Fliki
What Flash's product team knows, kept as linked notes that their AI agents read first.
April 2026 to now · Built at Flash, for the product team
Fliki is Flash plus wiki. I built it for the product team at Flash: product managers, designers and researchers. It holds what the team knows (people, projects, product lines, metrics, meetings) as typed notes that link to each other, and the team's AI agents read them while they help with the work.
Every chat starts with context. The agent first reads three short notes: who you are, and two maps of what's in Fliki. Then it walks. It opens one note and follows its links only as far as the question needs. Every note has a one-line description, so the agent can tell from one line whether a note is worth opening.
People use it for all kinds of product work: writing PRDs, drafting tickets, research, saving a meeting, or asking who owns something and what was decided.
---
type: project
description: Onboarding v2, the shorter sign-up. Open for decisions.
product_lines: [growth]
status: in-progress
owners: [amira]
squad: growth
started: 2026-03-01
updated: 2026-03-17
---
# Onboarding v2
## Summary
Sign-up goes from five steps to three. Owned by [[people/amira]],
built by [[squads/growth]], measured by [[metrics/sign-up-rate]].
## Decisions
- 3 Mar: drop the second ID photo. See [[meetings/2026-03-03-kickoff]]
- 17 Mar: keep the phone number step. See [[meetings/2026-03-17-review]]Before 1.0
The first versions worked like a code project. Every note was a pull request, people waited on each other to review, and you had to pull your teammates' notes in by hand. For a team that's mostly not engineers, that was too much.
For 1.0 I put the ownership rules into GitHub's checks. A change to a note you own merges by itself. A change to someone else's note waits for them, and they get a message asking. Everyone's copy updates every five minutes. Nobody sees Git words. They see messages like these:
- Saved by Amira with /fliki-save.
- Waiting for Omar to approve.
- 3 things to fix before this can go live
Where it is
The whole product team uses it, and six teammates add to it. In April, when it started, they made one change between them. In September they made 81. Adoption is growing day by day, and next we're opening it to people outside the product team.
Most of what I learned building it was about how knowledge scales and how agent context works. That's why every note has a type, an owner and at least one link in.
I built it starting from research on how other teams give AI shared knowledge, and I still run it.