Skip to content
Ocean-Atlasv0.1.0Canonical Knowledge

Run the First Example

Everything in this guide happens inside Ocean App. You do not need to install a CLI, clone a repository, or use a terminal.

Ocean App presents Onboarding: Task Manager specifically for this first experience. It is a small but complete application that persists tasks, applies lifecycle rules, exposes a REST API, and provides a UI. Its model is documented in Ocean-Atlas as the Task Manager example.

Go to app.ocean-lab.ai and access Ocean App.

From Ocean App’s available examples, open Onboarding: Task Manager. Choose the provided example rather than creating a project from scratch.

The example opens the Bundle used throughout this path: ten small DSL files that together model Task Manager.

00-todo-info.ocn
app-todo-api.ocn
app-todo-config.ocn
app-todo-dashborad.ocn
app-todo-db.ocn
app-todo-deploy.ocn
app-todo-dt.ocn
app-todo-expression.ocn
app-todo-service.ocn
app-todo-ui.ocn

You don’t need to understand them yet — Understand the First Bundle walks through each one next. For now, just look around.

Use Ocean App’s generation action for the example. Ocean App validates the Bundle as part of this workflow and generates its concrete implementation.

The current Task Manager model targets a Go API using Gin, PostgreSQL persistence, and an HTMX/Bootstrap/Go-template UI, as documented by the example’s Voyage.

Run the generated application from within Ocean App. The app manages this first execution experience; no local runtime or database setup is required for the onboarding flow.

Once the application is running, explore its generated UI. In particular, look for the behavior backed by these two API operations:

  • getInfo — the simplest operation, with no dependencies: a good first thing to try.
  • listItems — reads persisted tasks back, exercising the Database-Backed CRUD pattern this example demonstrates.

The Bundle declares deployment details such as API and UI ports, but Ocean App handles those runtime details for this in-app experience.

7. Downloading the Generated Project Is Optional

Section titled “7. Downloading the Generated Project Is Optional”

You may download the generated source when you want to inspect or run it outside Ocean App. Local prerequisites are target-specific; follow the generated project’s own README for its required runtime, dependencies, configuration, build, and execution steps.

Downloading or running the source locally is not required to complete this Getting Started path.

You have opened a real Ocean Bundle, generated its implementation, and run it inside Ocean App. Understand the First Bundle explains what you just looked at, in detail.