Lightforce Sketch

Describe your app. Get a sketch.

Tell us what you want to build in plain words. A few questions later, Sketch writes the blueprint of your app, and a Software Architect signs it before anything is built.
Every Lightforce product starts here.
What is in a sketch

Five parts, in plain words

DomainsThe parts of the app.
JobsWhat each part gets done.
RulesWhat must always hold.
ProcessesHow the work flows.
ScenariosWhat a user does and sees, step by step, written GIVEN, WHEN, THEN.
Three levels
01 · Map: every domain as a tile, with its jobs and counts.
02 · Domain: purpose, language, boundaries, and the jobs as cards.
03 · Job: rules, processes and scenarios, written as GIVEN, WHEN, THEN.
A sketch job, with its rules, processes, and scenarios written as GIVEN, WHEN, THEN.
The same sketch job on a phone, with its rules and its first scenario.
The sketch map, with every domain as a tile and its jobs listed underneath.
Signed

Signed before anything is built

Every sketch is reviewed and signed by a Lightforce Software Architect. The Architect checks that the rules hold together, flags what needs investigation before money is spent, and only then lets the sketch enter the factory.
Portable

Yours, and portable

Your sketch belongs to you. Export it as a PDF, or as markdown with one feature file per job that a test tool can run as written. Take it to any builder or to the coding agent you already use. Lightforce Forge was built to read it.
Lightforce

Start with a sketch

Describe the app you have in mind, and read the sketch before anything is built.