This page guides you through the build lifecycle of a Pilot application, from ontology generation through seed data. For creating a new application, see Getting started. For deploying to production, see Deploy an application.
After you describe your application, Pilot analyzes your prompt and creates the data model for your application using the ontology architect agent. Pilot creates the following resources based on your prompt:
Task, Project, and Team Member object types with relevant properties.Create Task, Update Task Status, Assign Task, and Delete Task.Task and Project to indicate which project a task belongs to.The ontology architect documents design decisions in the chat panel, explaining the rationale for each entity. You can view the generated ontology graph by switching to the Ontology tab. For more details on the ontology graph, see the ontology tab documentation.
To refine the ontology, type instructions in the chat panel. For example, you might ask Pilot to add a new property, change a property type, or create a new relationship between object types.
If you attach existing ontology entities as context, Pilot will use them instead of creating duplicates. See Provide context and attachments for details.
Once the ontology is defined, the design agent creates a detailed design specification for your application. The design agent reads the ontology and your requirements, then produces a design specification with the following:
You can view a summary of the design specification in the chat panel. The design specification guides the front-end generation that follows.
The app builder agent implements the front end using the ontology and design specification. This agent performs the following tasks:
When the agent finishes, the Preview tab displays a live preview of your application running in the container. You can interact with the preview to test functionality, and the device selector lets you preview the application at different screen sizes.

In editor view, Pilot generates seed data in the container so that AI agents never access real enterprise data. This prevents Pilot from hard-coding production values into your application code. You can view generated records in the Ontology tab by selecting an object type node and opening the data preview panel. See the ontology tab documentation for details.
To validate your application against real ontology data, switch to the Deploy view. On a deployment branch, ontology schema changes are scoped to that branch and do not affect Main until you merge. On Main, any actions performed in the application are live ontology edits. For details, see Deploy an application.
After the initial build, you can refine your application through follow-up prompts.
If you encounter build errors in the Preview tab, you can select Fix with Pilot to prompt Pilot to diagnose and resolve the issue automatically.