The owner's manual your codebase never came with.
Generate an evidence-linked manual from a repo snapshot before touching billing, auth, limits, or the flows your product depends on.
Free to generate and preview. $19 one-time unlock per repo snapshot/manual. GitHub read-only access · Open beta.
review readySample manual
Owner's Manual for an AI bookkeeping app
7 generated chapters from the reviewed repository snapshot. Generated from one anonymized repo snapshot, with evidence boundaries, attention cards, and owner decisions.
ai-bookkeeping-app
revision
7
chapters
17
attention
17
decisions
Comprehension debt
Could you answer these right now?
The dangerous moment isn't writing the code — it's coming back to change billing, auth, or usage limits and realizing you can't say what the code already does. That gap is comprehension debt.
Mid-cycle upgrade: do the new limits apply immediately, or next cycle?
Downgrade: what happens to data that's now over the limit — grace period, or gone?
Usage limit hit: soft block (warn and allow) or hard block (deny)?
Admin override: who can bypass it, and what checks does that skip?
Payment fails: retry, lock the account, or fail silently?
What the manual does about it
Stewie Reflect answers these from one snapshot of your actual repo — each behavior tied to the code that proves it. Where the repo doesn't settle the question, it says unknown instead of inventing a confident answer. So you change the risky part knowing what's really there, not what you hope is there.
Sample manual
Read product behavior with the evidence still attached.
Stewie Reflect does not hand you a confident summary and ask for trust. It writes claims in product language, then keeps the files and functions close enough to inspect.
Read the full sample manual
Owner's Manual
repo snapshot · evidence-linked
Paid users unlock the full manual after checkout.
Evidence: checkout success handler updates manual access and routes the owner back to the generated artifact.
src/routes/checkout.ts
Linked source for this claim
src/lib/manual-access.ts
Linked source for this claim
Attention cards
It highlights the parts an owner should not hand-wave.
Billing and unlock logic
What changes after payment, what remains gated, and which edge cases still need owner review.
Auth and permission paths
The user journeys that decide who gets access, where trust is assumed, and where the code enforces it.
Known unknowns
Places where the repo does not provide enough evidence, called out instead of smoothed over.
How it works
A short path from repo snapshot to readable manual.
Connect GitHub read-only
Install the GitHub App on only the repositories you choose. Access is read-only, and you can revoke it on GitHub at any time.
Free repository check
Pick one repository and branch; we pin the exact commit. If the repository can't be processed, the check tells you clearly — and why — before anything runs.
Generate the manual — free
Generation is asynchronous and runs through staged, evidence-based quality checks. A manual that fails the quality bar is not delivered, not even as a preview.
Read a free preview
One complete chapter plus every finding, generated from your own code — so you judge the quality before paying anything.
Unlock and export
Pay $19 once for that repo snapshot/manual, then keep the full manual and Markdown export. It stays in your account, tied to that exact commit.
Owner decisions
Read the manual before you change the product.
Is this behavior intended, or just what the implementation happens to do?
Can you change billing, auth, limits, or onboarding without breaking a hidden promise?
Which gaps need a founder decision before an engineer or agent touches the code?
Built for risky moments
Sound familiar?
Owning software isn't the same as understanding it.
“I vibe-coded my whole product with AI. It works… I think. I honestly couldn't tell you what happens when a payment fails.”
“My developer left. I own the code now — I just can't read it, and I don't know what I don't know.”
“Before I invest more in this codebase, I want an honest second opinion on what's actually in there.”
That gap between owning software and understanding it is exactly what an owner's manual closes.
Pricing
Preview first. Unlock only if the manual is worth keeping.
Stewie Reflect is separate from the broader Stewie workspace beta. This page is for one repo snapshot, one generated manual, one one-time unlock.
Free preview
Generate from your repo and inspect the sample before checkout.
$19
one-time unlock
Unlocks the full manual and Markdown export for that repo snapshot. Taxes may apply. Beta pricing may change later.
Honest scope: manuals are AI-generated and machine-reviewed against your code — no human review is included. Every manual must pass automated, evidence-based quality checks; one that fails is not delivered, not even as a preview. One snapshot, one manual — no continuous sync.
Trust & privacy
Your code stays yours. Your manual stays private.
Privacy & how we handle your code
- Access is read-only through a GitHub App, and only for the repositories you select. You can revoke it on GitHub at any time.
- Your manual is generated from one pinned commit snapshot — we don't watch or sync your repository afterwards.
- Your repository code is never executed.
- Instructions found inside a repository (prompts, agent configs, hooks) are treated as evidence to describe — never as instructions to follow.
- Only you can open your manual; it is tied to your account and not shared, published, or used as marketing material.
More detail: Privacy Policy.
Pricing, payment issues & support
- Generating a manual and reading the preview is free. You only pay US$19 to unlock the full manual and export — so you're never paying before you've seen real output from your own code.
- A manual that fails our automated quality checks is not delivered — not even as a preview. We don't show a weak manual just because generation finished.
- Because you review a real preview before paying, purchases are generally final after unlock. If you were charged twice, paid but could not access the unlocked manual, or hit a clear platform error, contact support and we'll review it.
- No human review of your manual is included. Any exceptional access needed to investigate a problem is handled under an explicit support and privacy process.
Support: hello@stewie.sh · Full terms: Beta Terms.
FAQ
Frequently asked questions
What exactly do I get?
An owner's manual generated from one snapshot of your repository: plain-language chapters with figures, attention cards ranked by consequence, explicit evidence boundaries, and a list of decisions only you can make. You read a free preview first — one full chapter plus every finding as a labeled hook — then unlock the full manual and its export for US$19. The sample manual on this site shows the format and the quality target we hold generated manuals to; output depth varies with your repository and the evidence available in it.
Do I have to pay before I see anything?
No. Connecting a repository, the repository check, generation, and the preview are all free. You only pay US$19 if you decide to unlock the full manual and its export — after you've judged a real preview of the selected repository snapshot.
How much does it cost?
Generating and previewing is free. US$19 is our current beta price — one-time — and unlocks the full manual and Markdown export for one repository snapshot. No subscription. Any applicable sales tax or VAT is calculated at checkout based on your location.
Who is it for?
Owners of software they can't fully read — founders who vibe-coded a product with AI, people who inherited a codebase, or semi-technical owners who want an honest second opinion. No code reading is required to use the manual.
Does this replace a developer?
No. A strong engineer still does the hard work better than any tool. The manual makes that engineer cheaper and faster to use: it gives a non-technical owner a map of what the product appears to do, where the important rules live, and which areas are risky — so you know what to ask and where not to step before someone touches billing, auth, or permissions. Where the code doesn't settle a question, it says so instead of guessing.
Is the sample manual real?
Yes. The sample on this site is a real generated manual — our engine produced it end-to-end from one snapshot of a real AI bookkeeping app, and it passed the same automated quality checks every customer manual must pass. We changed the app's name and removed source-identifying details before publishing it as an anonymized sample.
How long does it take?
Generation is asynchronous and runs through staged quality checks. It usually takes 30–60 minutes, and larger repositories can take longer. You can close the page and return from your dashboard while it runs.
Do you support private repositories?
Access goes through a read-only GitHub App that you install on selected repositories, which is designed to cover private repositories. We're verifying private-repo handling during the beta before advertising it as guaranteed.
What makes a repository ineligible?
Oversized repositories, repositories we can't access, unsupported formats, or obvious multi-project dumps. The repository check is free and shows reasons before generation starts.
Is my manual reviewed by a human?
No. Customer manuals are AI-generated and machine-checked against your code with evidence rules; anything that can't be supported is labeled or rejected, and a manual that fails the quality checks is not delivered. The sample on this site additionally went through human review because it's our own product's manual — that human pass is not part of the offer.
Does Stewie Reflect keep watching my repository?
No. One snapshot, one manual. There is no continuous sync, no webhooks into your repo, and no multi-repository analysis in this beta.
Stewie Reflect
Start with the product you already shipped.
Bring a repo snapshot. Read the preview. Unlock the manual when it earns its place in your workflow.