Knowledge

Most AI builders keep everything in the chat transcript. Ask a question three weeks later and the answer has scrolled away; ask the builder to change something and it has forgotten the reason you decided the opposite last month.

Pikku Studio Cloud doesn't work that way. Every decision made in Chat is written down, the moment it's made, as a note in your project's knowledge base. That base is not a summary of the conversation — it is the specification. When something gets built, it gets built from these notes.

Annotated screenshot of the Knowledge screen: a list of notes on the left grouped into Milestones, Entities and Decisions, and one note open on the right showing its title, description, a status dot, a "Resources" list of the real functions it maps to, and a "Linked from" backlinks list. Callout: "The written record of what your app is — and what it's made of."

Why it's written down

A decision that only exists in a chat transcript is lost the moment the conversation scrolls. Writing it down buys you four things:

• The app can be rebuilt from it. The notes are the brief. Nothing is built from a vibe you can't inspect.
• You can read what you agreed to. In plain language, at any time, without scrolling back through a conversation.
• Contradictions surface. When a note and the real code disagree — the app lets anyone delete a booking, the note says only the owner can — that's a question you get asked, not a silent drift.
• It survives the session. New conversation, new teammate, six months later: the record is still there.

What's in it

Notes are grouped into sections. Three are load-bearing and appear first; anything else your project grows sits after them.

• Milestones — the buildable pieces of your app, each with the user journey it has to satisfy. See Milestones.
• Entities — the things your app is about. An entry, an order, a booking: what it's made of, and how it ends.
• Decisions — one note per decision, carrying the reason rather than the implementation. Two sub-groups accumulate over a project's life: design decisions (how the app looks and behaves) and security decisions (who may reach what, and why).

You'll also see Questions — things that were asked and never answered, kept so they don't quietly vanish — and Wishlist, ideas you liked when the project was starting. The wishlist is deliberately never built from; it's there so that when your thinking heads somewhere you already liked, the record knows it.

It's a graph, not a folder

Notes link to each other with ordinary links, and the console follows them both ways. Open a note and you see:

• Resources — the real functions, routes, tables and workflows this note is about. That's the join between the written record and the running code, and it's checked: a note pointing at a function that no longer exists fails the project's checks rather than rotting quietly.
• Linked from — every other note that references this one. So from "health data stays out of measurement" you can see each milestone and entity that decision governs.

A story links the people in it and the things it touches; a rule links the person and the thing it governs. That's what makes the base answer questions a folder of documents can't.

Who writes it

The planning conversation does — and only it. That's a hard boundary rather than a convention: the planning agent is allowed to write knowledge notes and nothing else, and the build agent writes code. Neither can wander into the other's job.

That's also why you don't edit notes by hand from the console. The Knowledge screen is a reading surface: moving a note yourself would put the written record out of step with what's actually being built. To change what a note says, say so in chat — the same conversation that wrote it will rewrite it.

If you want to know what your app is supposed to be, read the knowledge base. If you want to know what it is, read the Weave. When those two disagree, that's the most useful conversation you can have.

Where to go next

• Milestones — the notes that turn into working software.
• Chat — the conversation that writes all of this.
• The Weave — the other half of the picture: what actually got built.