{
 "version": "https://jsonfeed.org/version/1.1",
 "title": "Geenius App blog",
 "home_page_url": "https://geenius.app/blog/",
 "feed_url": "https://geenius.app/blog/feed.json",
 "description": "Posts from the team building Geenius App: why the AI asks before it acts, and why a site is a validated spec.",
 "language": "en",
 "items": [
  {
   "id": "https://geenius.app/blog/a-site-is-a-spec/",
   "url": "https://geenius.app/blog/a-site-is-a-spec/",
   "title": "A site is a spec, not a pile of code",
   "summary": "Why the AI in Geenius App writes a checked spec and our generators build the site from it, so the result is predictable.",
   "date_published": "2026-10-24T09:00:00Z",
   "authors": [
    {
     "name": "The Geenius App team"
    }
   ],
   "tags": [
    "spec",
    "ai"
   ],
   "content_text": "When you say what you do, the AI does not write your website line by line. It writes a spec: a description of your site, with its pages, its blocks and its design choice. The spec is checked against a schema before anything uses it.\nWhy not write the site directly\nFree-hand code from a model is hard to check. A spec is small and typed, so it can be validated, shown to you as a change before it applies, and stored as a version.\nSame spec, same site\nOur generators build the site from the spec. The same spec gives the same files, so a build is predictable and a change can be compared with the version before it.\nThe AI is a plug-in\nBecause the AI only has to write a spec, the model behind it is a plug-in. That is what Bring your own AI means for us: the AI is yours to choose, not a lock-in. How your own AI connects to Geenius App is still being decided; tell us what you use."
  },
  {
   "id": "https://geenius.app/blog/why-the-ai-asks-first/",
   "url": "https://geenius.app/blog/why-the-ai-asks-first/",
   "title": "Why the AI asks before it acts",
   "summary": "In Geenius App the AI asks, shows and does, and anything that publishes, spends money, registers a domain or sends something out waits on an approval card.",
   "date_published": "2026-10-24T09:00:00Z",
   "authors": [
    {
     "name": "The Geenius App team"
    }
   ],
   "tags": [
    "approval",
    "ai"
   ],
   "content_text": "A person who has never built a website should not have to guess what an AI is about to do. So in Geenius App it asks first, shows what it proposes, and only then does it.\nOne rule\nFour kinds of action wait for a yes: publishing your site, spending money, registering a domain and sending something out. Each one shows up as an approval card that names the exact action. Where money is involved, it names the exact total, quoted again at that moment.\nWhy a card\nA card is small, it says one thing, and it can be answered with a yes. It also leaves a record of what you agreed to.\nAnd the rest\nA safety check runs on every site before it can go public. Every publish is a version, so a change can be undone. Geenius App is in early access and not open to the public yet; this is how it is built to behave. Join the waitlist to see it."
  },
  {
   "id": "https://geenius.app/blog/publishing-waits-for-your-yes/",
   "url": "https://geenius.app/blog/publishing-waits-for-your-yes/",
   "title": "Publishing waits for your yes",
   "summary": "How Geenius App lets its AI ask, show and do, while anything that publishes, spends money or sends something out waits for your yes on an approval card.",
   "date_published": "2026-10-24T09:00:00Z",
   "authors": [
    {
     "name": "The Geenius App team"
    }
   ],
   "tags": [
    "approval",
    "publishing"
   ],
   "content_text": "When an AI helps you build a site, the useful question is not only what it can do. It is who decides. In Geenius App the answer is simple: you do. This post explains the idea and where it stands today.\nThe AI asks, shows and does\nGeenius App is built around a short journey. You say what you do, in a card, a sentence or by speaking. The AI asks at most about ten questions, you choose a design, and a calm timeline shows the build. In the preview you can talk to the site or tap a section, and every change is shown to you before it applies.\nA spec, not free code\nThe AI does not write your site by hand. It writes a spec, a small description of your site that is checked against a schema before anything is built. The generators then build the site from the spec, so the same spec always gives the same site. A spec with a missing or wrong field is refused with the field named, so it can be fixed and tried again.\nWhat waits for you\nSome steps matter more than a change to a headline. Anything that publishes, spends money, registers a domain or sends something out waits for your yes on an approval card. The card says what will happen, and nothing happens until you agree.\nPublishing, version by version\nWhen you say yes, your site goes to a free address, your-name.geenius.site, and you get an email when it is live. Every publish is a version. If you change your mind, &quot;undo that&quot; brings back the one it replaced.\nA domain of your own, later\nLater, you will be able to search for a name and see the exact total on an approval card before anything is bought. Today this runs in a sandbox: no real domain is bought.\nYour AI, your choice\nGeenius App follows Bring your own AI. The model sits behind a port, so a provider can be swapped without changing the product. How your own AI connects to your account is still being decided, and the waitlist form is where you tell us which AI you use.\nWhere it stands\nThe journey, the generators and the approval cards are built and tested in our code. The live service is not open to the public yet. To be let in when it opens, join the waitlist."
  }
 ]
}
