SI ...engineered!
Our Intelligent Agents provide solutions to your needs. These Intelligent Agents are part of the LANai platform and tools. The Ground Control interface provides control and monitoring of the LANai resources. Every change runs an extensive automated test suite, is cross-tested on a second machine before it ships, and is checked again on the server after each deploy. The apps run on the web, iPhone and Android, and are built and tested on both macOS and Windows.
Once invited as a Guest, you will have access to each Application's demo and information. Log in to open each one and see what it does.
Apps
The platform behind them
Sign in to open the releases
What each app does, its demo and the theatre are for account holders. Accounts are by invitation.
How it’s built
A team of intelligent agents
Each session is an AI coding agent that writes, tests and ships one application or process. Every session is replicated on each machine used in the Lanai environment — today a Mac and a Windows PC — and the copies share their decisions through git.
Ground Control directs them
One coordinating session sets the priorities, hands out the work, checks every result and keeps the team inside its budget.
One standard for every app
Automated tests on every change, a deploy that refuses untested code, and a check after every release that proves what was deployed — watched by the myLanai hub.
How the apps are tested
The testing grew up with two of the apps. Pill Inspector's Automated Test Bed runs one library of scripted user journeys against the real app on Android and iPhone; AutoAppraisal turned that bed into an Automated Test System of its own that other apps can plug into. The same ideas now run through every release:
- Tests drive the real app. Scripted journeys tap and type through the actual screens, in emulators, simulators and real browsers — not just the code underneath.
- One set of journeys for every platform. Android and iPhone read the same scenario files, so a fix is tested the same way on both.
- Honest results. A failure, a crash and a stalled device are reported as different things, and a check that could not run never counts as a pass.
- The tests are tested. Deliberate faults are planted to prove each suite catches them; a green run is never trusted on its own.
- Evidence you can look at. Every run keeps its screenshots and logs, and someone looks at them.
- Two machines, one verdict. A Mac and a Windows PC each test every change before it ships. They pull their work from the server, and a new machine starts switched off until it is approved.
- Test data is fenced off. Test accounts are marked, hidden from everyone else and removable, and the test machines have their own secured way in, separate from people's.
- A gate before every deploy. Untested code is refused, and a check after each release proves exactly what was deployed.
> help_