Fliki

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, customer feedback) 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 whether a note is worth opening before it opens it.

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]]

How it's arranged

Every note has a type, an owner and at least one link in. Each type has its own folder and template, so the agent always knows what fields to expect.

How it connects

The links are what make it work. A project links to its product line, its squad and its metrics, so the agent can start anywhere and reach what it needs in a step or two. Press “Follow a question” to watch it answer one.

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 Slack message asking them to review it. Everyone's copy updates every five minutes, and nobody sees Git words.

Where it is

The whole product team uses it. Version 1.0 shipped on 29 September. In the 17 days after it, the team made 102 changes, more than the 79 they made in the five and a half months before.

I built it starting from research on how other teams give AI shared knowledge, and I still run it. 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.