App Studio — Nexus One AI

Step 1 · Idea

What should Nexus build?

Start with the business outcome. App Studio will turn it into a structured application project.

Application name

Describe the application

Step 2 · Spec Kit

Requirements and acceptance criteria

The generated specification remains editable and becomes the shared contract for the coding agent, visual builders, testing and approval.

✓

Vendor request intakeEmployees can submit company, contact, category, budget and supporting-document information.

✓

Role-based reviewFinance reviews budget details before procurement can make the final decision.

✓

Status dashboardAuthorized users can filter requests by owner, department, stage and decision.

✓

Governed actionsEvery submission, edit, approval and rejection is attributed and retained in the audit trail.

Additional acceptance criteria

Step 3 · Builder

Design and build

Compose the application visually, then use the VS Agent to implement the same versioned design contract in the governed repository.

Visual Builder + VS AgentEnterprise path

Design pages and data bindings visually, then refine the generated source with the appliance-local VS Agent.

OpenHandsPlanned

Delegate a complete implementation task and review the resulting commits and test evidence.

AppsmithIntegration

Import or connect an existing Appsmith application through the governed lifecycle.

LangflowAI Flow

Compose AI agents, retrieval pipelines and model-powered application workflows.

Visual application contract

Version 1 · unsaved

Step 4 · Build sandbox

VS Agent workspace

The agent implements the approved contract inside this project's isolated repository. Only source that passes the governed checks is committed and pushed.

vendor-approval-hub · mainSandboxed

$ nexus-agent implement specs/application.md

Step 5 · Preview

Review the running application

This exact verified commit is running in a constrained, authenticated preview container. Publishing requires explicit approval.

Preparing preview…

Step 6 · Governance

Approve publication

Nexus validates the release evidence and records the approving user before making the application available.

Publication approval required

Version 1.0.0 will be promoted from the preview sandbox to the internal Applications catalogue.

✓ Specification approved

✓ Automated checks passed

✓ No secrets detected

✓ Rollback point created

I reviewed the preview and approve this release.

✓

Published

Application is live

The application is available to authorized Nexus users and its release can be audited or rolled back.

/apps/vendor-approval-hub

Open Applications catalogue