VERAGENLearn

Chimp

The other steps, and settings

Each step shows exactly where it is, under the steps across the top of an app.

Not startedIt starts when the step before it is approved.
WorkingThe AI is at it (the designer, or the engineer). You can leave the page; the work carries on.
Waiting for youIt needs an answer, an approval, or a person to look at a change that failed its checks.
ApprovingAn approval has started and is being finished.
ApprovedDone; the next step has started.
Waiting for the apps platformThe step runs on the apps platform and cannot start yet; the step says why. Your approved spec and its stories are ready for it. Nothing is charged.
SkippedA prototype stops after Design, so its later steps are skipped. A prototype made before Chimp also skips the spec until it continues to build.

Each step says what happens in it, and whether anyone approves it. Build and Live have no approval: they move on when their checks pass.

Live

Once a version is published, Live starts: the app is live at its address, and every version is kept, so you can roll back from Release → Versions. Monitoring and visitor numbers for live apps are not part of Chimp yet. To be told when the address stops working, add a test for it in Site Pulse.

Domain and Data

  • Domain shows the app's free address (such as yourapp.veragen.app), with Copy. Where your account can connect a domain of its own, Domain is also where you connect it: the DNS records to add, and each domain's status.
  • Data shows what the spec says the app stores. Browsing and editing an app's data isn't available yet. A website without sign-in stores nothing of its own.

Settings

Settings, at the top right of an app:

NameThe app's name in Chimp.
What Chimp readsEverything Chimp uses for this app: the Brand Kit (colours, fonts and logo), the business name, the project's Context (with anything that did not fit), the pages you chose, your imported website, and the project's Skills with a tick for each one it follows. Tick or untick skills (up to five) and press Save; the spec writer, the designer and the engineer follow the new choice from their next piece of work. What Chimp reads
Chat on the siteOne of your Tellagent chatbots, or No chat. After the app is built, changing it adds one change to Build that puts the new chatbot on every page (or takes the chat off), checked like any other change. QA has to pass again before the next release. Pressing Save with nothing changed adds nothing.
Who approvesWho approves The spec, The design and Releases. Owners and admins can narrow each one (for example, releases by owners only); it can never be widened. Everyone else sees the choices but cannot change them.
HistoryEvery step: who did it, the AI's work, approvals and changes, with times.
Publish without paymentsOnline stores only. Make it a web app turns the store into a web app, which is released without taking payments. Nothing already built changes.
Delete this appThe app leaves Chimp. Its specification, documents and Skunk Works items are kept. Only the person who started it, owners and admins can delete it, and a live app has to be taken offline first (Release → Versions → Take it offline).

Developer tools

The Developer tools switch at the foot of Chimp's menu adds Code, Repository, Tests and Logs to each app: the app's files, every change in its repository, its tests with their latest results (the unit tests in the repository, the acceptance tests QA wrote, the latest checks and QA run; to run or confirm them, use QA), and each change's checks. They fill in as the app is built. It is your own setting and changes nothing for anyone else. See Build.