Products and services FAQ
Answers about working with me, buying IntelligenceOS and getting help with the setup.
I build role-specific assistants, connect business tools and automate recurring tasks. That might mean a weekly report, a content workflow or a dashboard for reviewing work. We choose a useful first project, build it and test it together. See how the service fits together.
No. IntelligenceOS is a separate self-serve project-context kit. You can discuss a service directly, and buying the kit does not include consulting, AI Workbench setup or implementation.
AI Workbench is my assistant implementation service. We start with your role and recurring tasks, then agree any tool connections or dashboard the setup needs. The Janet case study describes one implementation recorded in June 2026.
You get a written price and a clear description of the work before we start. I flag software, hosting and API costs upfront. Ongoing support is optional, with agreed hours and response times.
We decide that together before connecting anything. Some tasks can run automatically; others should wait for your review. The setup follows those agreed permissions.
A reusable project toolkit shaped by four years of my own AI-assisted development. It is aimed at solo founders and developers who want a clear starting point and a project they can keep improving.
IntelligenceOS connects the questions asked before the scan, Git-aware mapping, protected paths, structured files, reusable skills, local failure diagnosis, handoffs and future release updates. You are buying a tested system you can keep using, rather than spending your own time designing and maintaining one.
Both. On a new project, it records the purpose, intended users, definition of done and protected areas before the folder grows.
On an existing project, it maps supported local files, instructions, tests and release surfaces so your agent can propose a clean-up from current evidence. It does not silently rename, rewrite or restructure anything.
IntelligenceOS leaves a local diagnosis with what stopped, likely causes and repair steps. Give that file to your agent first so it can start with the named problem.
The diagnosis stays on your machine. It does not send project data anywhere or authorise a repair.
Start with IntelligenceOS Agent Setup when your agent can read an attached ZIP, inspect local files and run commands. Tell it to read AGENT_MODE_START_HERE.md.
Keep IntelligenceOS Complete for the guided app, browser instructions, Mac and Windows launchers, manual setup routes and privacy-safe support report. Both are included.
No. A capable coding or content agent can follow the documented files even when its platform does not support automatic skill discovery.
If you approve installation, IntelligenceOS adds five focused skills and .agents/INTELLIGENCEOS_START_HERE.md to the project. That gives later agents one stable file to reopen.
A readable Project Brief and Project Map, a browser report, SQLite database, JSON and CSV evidence, Markdown guidance, an agent handoff and the next safe prompt. It also records scan coverage and whether anything was omitted.
Yes. It can map the pages and local source material, topics already covered, obvious gaps, linking opportunities, claim rules and approval boundaries.
The included content workflow then helps the agent choose a real gap, research it, use your writing profile, check claims, prepare images and update the project record after you accept the work.
The writing-profile skill turns your accepted samples into practical voice, structure, terminology and avoid rules. The profile stays in your project. Accuracy, source and safety rules still take priority over style.
No. Replicate is an optional paid route for stronger editorial image backgrounds and uses your own API access. Pillow provides a local, more basic fallback for covers, quote cards and frames around real screenshots.
No. The current release works from local configuration and exported files. Live CMS writes, publishing, deployment, account changes and credentials stay outside the default product and need a separate approved workflow.
No. Its warnings help you and your agent notice missing context, weak connections and review needs. They are not specialist security, legal, medical, compliance or factual assurance.
Stripe returns you to a secure MorpheOS delivery page with both downloads. Use Agent Setup first, or open 00_OPEN_FIRST.html inside Complete.
The purchase includes a perpetual licence and buyer-visible IntelligenceOS product updates for the commercial lifetime of the product, plus one first-run troubleshooting review if a supported setup route is materially broken. I will review the local diagnosis and tell you what to try next. Custom implementation is separate.
Future buyer-visible IntelligenceOS product updates are included for the commercial lifetime of IntelligenceOS. Your original protected fulfilment link serves the current release. If you lose it, I can verify the original purchase and restore access, so you do not need to buy IntelligenceOS again.
From beta.4, the kit can check the public release record without sending project data and verify a new ZIP before you unpack it. Your agent can then preview any project update while preserving your existing rules. Read the update steps.
The local engine requires Python 3.11 or newer. The agent route works best when your coding or content agent can inspect local files and run commands. Mac and Windows launchers are included, but operating-system security settings vary.
IntelligenceOS is the self-serve product. The MorpheOS service brings review, implementation and ongoing improvement together for small teams, founders and agencies. See the services or tell me what you are building.
If you cannot access the downloads or a supplied file is materially broken, email within seven days and I will try to fix it; if I cannot, I will refund it. The immediate digital-supply terms and your statutory rights still apply.