Senova documentation

How to fly the whole platform — from a sentence to a live, examined, verifiable site.

The platform

Senova started as a builder: describe an app, get a working product. It has grown into something with a stricter job — the integrity layer of the AI-era web. Anyone can generate a website now. The hard part is a website that holds: design that stays inside a considered system, claims that can be checked by anyone, pages that pass a real inspection before and after they ship.

Senova's answer is a set of instruments that fly with every site — Design Rules, Personalization, Clarity Check, the Agent Sales desk, and sealed claims — plus an examiner, Site Check, that tests the result the way a picky human would.

You work in three places. The Builder is where you build. The Hangar is where your fleet lives. Site Check is where it gets examined. And Artificial Horizon is the showroom.

Getting started

Senova turns a plain-English description into a working web app — with its database, sign-in, and hosting already wired together. You describe what you want, Senova asks a few clarifying questions, and it builds it.

Create an account with your email or with Sign in with Google. Once you are in, you land on your dashboard: a grid of your projects and a prompt box to start a new one.

Credits. Every account gets a monthly pool of build credits. Each AI action spends credits based on how much work it is: a chat is 1 credit, a quick edit is 3, a complex edit is 8, a full new build is 15, and an agent build is 30. The Free plan includes 25 credits a month with up to 5 builds per day; Pro includes 500 credits; Team includes 2,000. When you run out, your existing projects keep running and your published apps stay live — you just can't run new AI actions until your credits refresh or you upgrade.

Plans. Free ($0), Pro ($29/mo), Team ($79/mo). You can start and ship on Free; move up when a project earns it.

Creating a project

There are three ways to start:

• Describe it. Type what you want in the prompt box (for example, "a booking tool for my pottery studio with class schedules and seat limits"). This is the fastest path.
• Start from a template. Pick a ready-made starting point and customize it with chat.
• Start from a page layout. Choose a designed layout from the gallery as your foundation.

Each project shows up as a card on your dashboard. You can rename a project, search your projects, duplicate one to branch off an idea, and move projects you no longer need to the trash (you can restore them for a limited time before they're permanently removed).

The Builder

Where you build.

The Builder is the builder's shell: a ribbon (Home / Insert / Design / View), a live canvas where clicking is editing — click any element, double-click text to type — and an assistant that leaves receipts: every action is logged and undoable.

How to use it

• ⌘K searches every tool.
• The instrument chips live on the top panel.
• Replay a build, or fork from any frame.
• Focus hides everything but the page.

Where it lives /live-build-demo.html

Plan mode

Plan mode lets you agree on what Senova will build before it writes any code. When you describe an app, Senova interviews you — asking about the audience, the key screens, and the data you need — and then drafts a plan: the data model, the pages, and how they connect.

You'll see the plan as a card you can read and refine. Not quite right? Tell Senova what to change in plain language and it updates the plan. When you're happy, click Build this and Senova turns the agreed plan into a working app.

Plan first when the app is non-trivial or you want to lock down the shape before spending a build. Skip straight to building when the idea is small and clear.

Build mode

During a build you'll see progress stream in: the decisions being made, the files being written, and a live preview when it's ready. A first build produces a complete app — pages, styling, data, and navigation — not a stub.

To keep improving it, just send another message. Every follow-up modifies the existing app: "make the hero darker," "add a testimonials section," "add a status field to bookings." You can stop a generation in progress if you want to change course.

Be specific, one change at a time. Small, clear requests apply more reliably than a paragraph of mixed changes. If you want three things, it's often better to ask for them in three messages.

Editing your app

You can shape your app two ways:

• Chat edits. Describe the change and Senova applies it. This is the primary way to work.
• Code view. Open any file, edit it directly, and save. The file tree on the left shows every file in your project; the pages navigation lets you jump between screens.

You can also adjust your palette and animations from their own views, and bring in your own images to use across your pages.

Preview

The preview tab shows your app live as you build and edit it. You can navigate between pages inside the preview and check different device sizes to see how it responds.

The preview URL is a private, in-workspace view — it is not your public address. When you're ready for the world to see it, publish (below), which gives you a separate public URL.

Design Rules

The design constitution, held in flight.

Every project carries a taste constitution — one type pairing, a bounded palette, a spacing rhythm, motion limits — that every build and every edit answers to. The chip reads Design Rules held; a change that would break the constitution gets snapped back and logged.

How to use it

• Open the Design ribbon — six art directions, Warm Editorial → Luxe Noir, all bounded.
• Ask in plain language ("try noir").
• Press Try to break it and watch it hold.
• The Hangar shows Held or Snapped ×2.

Where it lives TASTE chip · Builder taste gauge on every Hangar card

Personalization

One page, every visitor.

Personalization builds per-visitor variants — skimmer, comparison, ready-to-buy, skeptic — recomposed from the same sections under the same constitution. It personalizes the arrangement, never the facts.

How to use it

• Say "per visitor", or click COMPOSE → a lens bar appears.
• Preview any visitor with their arrival context.
• It composes in preview and ships nothing until you say.

Where it lives COMPOSE chip · Builder lens bar over the canvas

Clarity Check

The checklist before anyone else sees it.

Clarity Check inspects links, contrast, breakpoints, weight, and forms in one pass, then scores the result — so you catch the obvious failures before a visitor (or an agent) does.

How to use it

• Say "run pre-flight" — the chip reads "not run" until flown.
• Each item comes back pass/fail with a fix.
• The Hangar shows the last score and marks it stale when content changed.

Where it lives PRE-FLIGHT chip · Builder PRE-FLT gauge on Hangar cards

Agent Sales

A desk on your site that can actually answer.

The Agent Sales is a counter where serious buyers — human or agent — get structured answers, quotes, and offers you authorized in advance. It is closed by default and only ever quotes what you stocked.

How to use it

• Arm it from the STOREFRONT chip.
• Stock what may be quoted, and at which tiers.
• Every visit is logged to the Tower ("Partner-tier buyer · quoted $6k/mo — shortlisted").

Where it lives STOREFRONT chip · Builder desk readout on Hangar cards Tower

Verifiable Claims

Statements that can prove themselves.

Any fact — a certification, a rating, a count — can carry a seal: a signature over the claim plus a pointer to its source. Anyone, or any software, can check it, and Senova re-verifies it over time.

How to use it

• Mark a claim and attach its source; Senova seals it and ships it with the page.
• If the source changes, the claim is re-checked — re-sealed or flagged.
• Unbacked claims are called out before shipping.
• The Hangar counts them ("claims 5 verified", "1 unbacked").

Where it lives Claims · Builder Hangar cards Tower

Site Check

The examiner for your website.

Site Check flies a live site like a picky human and files a Report — an airworthiness score plus issues, each one carrying a screenshot and a fix.

How to use it

• Watch a real one at /checkride — a 40-second audit, measured live.
• Request one for your site — join the flight line; Senova sites board first.
• From the Hangar, use Run a Site Check.
• Nightly monitoring (preview) re-flies and issues on a broken deploy.

Where it lives /checkride Run a Site Check · Hangar

The Hangar

Home base for your fleet.

Sign in and every site is on the floor with a tail number and four gauges — Health Score, Design Rules, Squawks, Clarity Check — plus desk and claims readouts. A brief points at the one that needs you, and The Tower collects overnight events.

How to use it

• Filter GO / CAUTION / NO-GO / STANDBY, in Grid or Board.
• + New site, Run a Site Check, or ⌘K fleet search.
• Walk the sample fleet if you're signed out.

Where it lives /hangar — this is where Sign in lands.

Artificial Horizon

Flight Demonstration Nº 01.

The showroom: one HTML file showing what motion feels like with the constitution holding the stick. Shove the instrument and it comes back level; a crosswind of slop arrives and is denied.

How to use it

• Scroll to fly; drag the indicator; double-tap for a roll.
• Read the page's own constitution.
• Reduced motion is honored throughout.

Where it lives /horizon see also /effects.html

Database

Every project has its own built-in database. When you describe your app, Senova creates the tables it needs from your description — you don't write schema by hand.

The Data view lets you browse tables, view and edit rows, and see each table's schema. Power users can run queries in the SQL view. The Users view shows the accounts that sign up inside your app (your app's end users, separate from your Senova account). You also get storage for files and a place to set secrets (environment values your app needs).

Branches & history

Branches let you try a direction without touching your main app. Create a branch, make changes on it, and merge it back to main when you're happy — or throw it away if you're not.

Two kinds of history keep you safe: build history lists every build and edit you've run, and version history lets you see what changed and restore an earlier version if a change didn't land the way you wanted.

Publishing

When your app is ready, open the Publish view. Senova hosts it for you with HTTPS and gives you a public URL of the form /p/your-app. Update a live app any time by publishing again; unpublish to take it offline.

On paid plans you can connect a custom domain. Senova applies sensible security and caching headers for your published app automatically. You can also enable a PWA option so users can install your app.

Templates & starting points

If you'd rather start from something designed, browse the template categories and the page-layout gallery. Pick one as a foundation and customize it with chat. There's also a marketplace view and ready-made email templates you can adapt for your app's notifications.

Export & GitHub

Your code is yours. You can download your entire project as a ZIP archive at any time, or connect GitHub and sync your code to a repository you control. The export includes all of your project's files, so you're never locked in.

Troubleshooting & FAQ

My change didn't apply the way I wanted

Be specific and make one change per message. "Change the primary color to forest green" applies more reliably than a paragraph listing five different edits. If a change went wrong, restore the previous version from version history and try again with a tighter request.

The preview looks stale

Use the refresh control on the preview. If you just published, give the public URL a moment to update.

I ran out of credits

Everything you've already built keeps working and your published apps stay live. You only need credits to run new AI actions — wait for your monthly refresh or upgrade your plan.

How do I report a bug?

Email [email protected]. You can also check the changelog for recent changes and system status for live service health.

What's a squawk?

An examiner's word for a filed defect. Site Check flies your site, finds a problem, and files it as a squawk — with a screenshot of exactly where it is and a concrete fix.

What does "Design Rules held" mean?

Your site is inside its constitution. An edit that would break the type, palette, spacing, or motion rules is snapped back and logged — you'll see Snapped ×N in the Hangar. "Held" means nothing has tried to break it.

Can the Agent Sales desk promise something I didn't approve?

No. It only quotes what you stocked, at the tiers you set. Every visit is logged to the Tower, so you can see exactly what was said and to whom.