read-only · never writes to your code

See your product, not your code.

AI builds. Frooqie reconstructs and verifies.
AI fills in the blanks. Frooqie shows you which blanks it filled in.

Bring in your product
Built for founders who ship with
GitHubReplitLovable · Bolt · v0Claude CodeCursor · VS CodeChatGPT · Codex
your-name/your-product · read once6 areas · 16 features · 24 rules
What your product is, in your words
Discovery
3 features
Stories
3 features
Requests
2 · 1 question
Meal drops
2 · 1 break
Messaging
3 · 1 question
Trust & safety
3 features
Does this loop close? · Reserve a portion
Reserved
Accepted
Ready
Collected
Cook told
Frooqie noticedA customer can cancel after the cook has accepted, but nothing tells the cook. Should it?
Yes, tell themNo, that’s fineNot sure
kept with your name and the date · checked again on the next read
The problem

AI built it. But did you decide it?

AI doesn't only follow your instructions — it fills in what you didn't specify. Four things Frooqie catches, from real products.

AI assumption
Your pricing page uses GBP (£).Frooqie couldn’t find a decision where you chose GBP.
Frooqie asks: Is this intentional?
YesNo, use USDNot decided
app/pricing.tsx · Intl.NumberFormat(…, { currency: “GBP” })
Missing scenario
Your product has 3 user roles.Cancellation behaviour is defined for only 2.
Frooqie asks: What should happen for Admin?
Same as customerCannot cancelNot decided
3 roles · 2 cancel paths · traversal complete
Contradiction
You confirmed: seller cancellations receive a full refund.Current implementation issues store credit.
Frooqie asks: Previously verified intent may have been violated. Which is right?
The code is wrongMy decision changedNeeds review
confirmed 14 June · changed 3 Sept · server/refunds.ts
Reconstructed decision
Admins can post a story as a cook.This exists in your product, but Frooqie found no evidence you explicitly chose it.
Frooqie asks: Review the assumption before it becomes product behaviour.
Meant itRemove itNot sure
app/(admin)/post-as-chef.tsx · absent from your chats and decisions
AI fills in the blanks. Frooqie shows you which blanks it filled in.
Bring it in

Wherever you build, one path in.

A GitHub repository Frooqie can read again, or a folder your AI tool built that it reads once. Pick your tool; the steps are written in that tool’s own words.

github.com/your-name/your-productconnection
  1. 01Enter the repository that ships to production.
  2. 02Pick the branch. Frooqie reads it read-only and tells you the version it read.
  3. 03Push again later and Frooqie tells you what changed in the product, not the files.
  4. the only path Frooqie can read again — change memory works from the second read
01 · See

Understand what your AI actually built.

Areas, features, who does what, what leans on what — named the way you say them. Frooqie separates what it can prove from what it infers — and says unknown when the evidence isn’t sufficient.

Discovery3 features
Customers find cooks near them.
Find cooksLocal feedMap
Stories3 features
Cooks post what they are making; it expires on a timer.
Create a storyView a storyStory lifecycle
Requests2 features
Customers ask for a dish; cooks answer in a thread.
Ask for a dishRespond
Meal drops2 features
Cooks sell portions; customers reserve and collect.
Create a dropReserve a portion
Messaging3 features
Both sides settle pickup; pushes when the app is closed.
ConversationNotificationsBlock & report
Trust & safety3 features
Your team reviews reports and every decision is audited.
ReportReview & decideSafety watch
02 · Discover

Find the scenarios nobody thought to specify.

Frooqie follows each journey as far as the code lets it, and marks the two kinds of break apart: steps that exist but nothing joins, and steps with no code at all. Different fixes — so it never says just “broken”. Where a journey can’t be followed, it says that too.

Reserved
Accepted
Ready
Collected
Cook told
✓ connected · ✗ unlinked — both steps exist, no edge joins them · ? missing — no step in the code · ○ described by you, not detected yet
Who can do what

Every way in, and what stands in front of it.

Customer, cook, admin — which reaches each feature. The number that matters is the smallest one: the ways in that change something and have nothing guarding them.

No guard, and it changes something8 of 158
No guard, read only36 of 158
Behind a session check5 of 158
Behind the admin guard107 of 158
a guard applied centrally would not show here — unguarded is inferred, never observed
03 · Remember

Frooqie asks. You decide. It remembers.

Where the code is unclear, where two things exist but nothing joins them, where something looks unasked-for — Frooqie asks in one sentence. Your answer becomes a requirement with your name and the date — and if a later read contradicts it, Frooqie raises the conflict.

unlinkedMeal drops · Reserve a portion
A customer can cancel after the cook has accepted, but nothing tells the cook. Should it?
Yes, tell themNo, that’s fineNot sureboth steps exist; no edge joins them
did you mean thisTrust & safety · admin console
An admin can post a story as a cook. Nobody asked for this in your chats. Keep it?
Meant itPlumbingNo ideafound in code; absent from your decisions
your wordsyour Cursor chat · 28 Aug
“Stories are approved-cooks only, no exceptions.” The code agrees. Still true?
YesAlmost — here is the wordingNobuilt as you said · canPostStory
04 · Verify

Don’t trust “done.”

Frooqie compares what you requested, what the AI claimed, and what actually exists in the code — and holds all three against what you intended.

Requested“Make every scan route rate-limited.”your Cursor chat · 2 Sept
AI claimed“Done. All scan routes are protected.”assistant turn · 2 Sept
Built2 of 3 scan routes carry the rate limiter.server/scan-routes.ts · read at 9c1e4f2
IntendedAll scan routes must be rate-limited.your decision · 2 Sept · not yet met
Frooqie verifies what your AI actually built — not what it says it built.
05 · Protect

Know when your product stops doing what you intended.

You said“Viewers are read-only.”
Claude built itConfirmed — viewers cannot create or edit.
Three months laterCursor refactors Projects.
Frooqie⚠ Viewers can now create Projects. This conflicts with your confirmed decision from 14 June.

Six areas, sixteen features, every screen placed or waiting for you. Dots read by tint and weight: understood, a question for you, an approved rule the code disagrees with.

understoodDiscovery — customers find cooks near them3 features · loop closes
questionRequests — an unanswered request never expires. Should it?2 features · 1 question
mismatchMeal drops — cancel exists after accept; nothing tells the cook2 features · 1 break
understoodTrust & safety — your team reviews and decides3 features · 39 of 48 actions audited
06 · Portability

Your AI changes. Your product memory shouldn’t.

Build in Replit today and Codex tomorrow. Git remembers the code. Frooqie remembers what you decided, why you decided it, and whether the next agent quietly changes it.

Chatstell Frooqie what you asked for.
Gittells Frooqie what changed.
Codetells Frooqie what exists.
Youtell Frooqie what you actually meant.
Frooqie reconstructs your product history from all four.
Replitbuilt authentication
phone sign-in, one-time codes
Claude Codechanged onboarding
cook approval before selling — you confirmed it
Codexfixed permissions
admin guard moved to the top of two files
Cursorrefactored reservations
⚠ cancel-after-accept no longer tells the cook — conflicts with your 12 Aug decision
Whatever comes next
Frooqie remains.
Each agent saw the code. None of them owned what you meant. Frooqie does — across all of them.
Trust

Understand your product without changing your code.

Read-only, alwaysNo write scope is ever requested. Frooqie cannot open a pull request, commit, or change a file — on GitHub or in a folder you give it.
Sensitive files are excludedFiles that look like keys or passwords are never opened. How many were skipped is shown, not hidden.
Your code is never storedFrooqie reads your code and releases it. No copy of your repository survives the read.
Your customers’ data is not neededFrooqie reads how your data is shaped, never what is in it. Your product’s records are neither required nor read.
Evidence, inference, or unknownEvidence stays evidence. Inference stays inference. Unknown stays unknown. Every statement says which it is, and none is rounded up.
“Why does Frooqie believe this?”One click on any finding shows what it was read from, and the version it was read at.
Your decisions outlive the codeAn answer you gave keeps your name and the date. If the code later contradicts it, Frooqie raises the conflict and quotes you.
You decide what becomes memoryWhat your AI proposed in a chat is shown as proposed. It joins your Product Memory only when you say so.
Self-hosting, when you need itToo large or too sensitive to leave your network? The same read runs inside it, with no outbound calls.
FROQIE

“A founder shouldn't need a developer to explain their own startup.”

the sentence Frooqie is built on
Built for software today. Designed for fragmented reasoning anywhere.the same loop — observe, reconstruct, ask, confirm, verify, remember — works wherever intent and evidence have drifted apart

See what was built. Decide what was meant. Remember why. Know when it changes.

Get started