Public demo / controlled change propagation

Nexus

keeps changing plans and delivery work aligned.

Edit the plan once. Nexus traces the impact, proposes task changes, and updates the board only after your approval.

Try the demo
View GitHub
Demo login readyNo setup5-minute walkthrough
Change control

Change the plan once. Keep delivery work aligned.

4

Control points

Version, impact, approval, alignment

1

Approval gate

AI proposes; a person decides

3

Traceable links

Plan, requirement, delivery task

1

Durable review

Pending decisions survive restarts

Versioned plan • Impact review • Human approval • Aligned board • No visitor API key • Versioned plan • Impact review • Human approval • Aligned board • No visitor API key • Versioned plan • Impact review • Human approval • Aligned board • No visitor API key • Versioned plan • Impact review • Human approval • Aligned board • No visitor API key •
Workflow story

Plan change to aligned work, without silent automation.

The landing page follows the same loop the demo proves: version a plan, detect impact, review proposed task changes, and keep delivery work aligned with an auditable decision trail.

01 / Plan

The project plan becomes the accepted baseline.

Nexus turns the plan into a versioned source of truth with stable requirement IDs.

first input

Build a customer order tracking app with registration, order placement, status updates, admin review, and delivery history.

versioned planDaily quotaDemo account
02 / Revision

A plan edit creates a reviewable revision.

The previous version stays intact while the team works on the next proposed plan.

accepted baseline
saved to docs

Customer Order Tracking App Specification

The application should let customers register, place orders, monitor status changes, and review completed delivery history.

User accounts
Order placement
Status timeline
Admin review
03 / Impact

Nexus traces changed requirements to affected work.

Added, modified, and removed requirements reveal stale tasks and missing coverage.

impact proposals
Develop Customer App: User Registration
High
Develop Customer App: Order Placement
High
Create Admin Review Dashboard
Medium
Add Delivery Status Timeline
Medium
04 / Approval

The user chooses which proposals become real.

Creates, updates, archives, and relinks remain pending until they are selected.

kanban board
To do
Order history
AI generated
Customer profile
AI generated
In progress
Order placement
AI generated
Status tracking
AI generated
Done
Registration flow
AI generated
05 / Alignment

The board and audit trail reflect the decision.

Approved task changes are applied transactionally and remain linked to requirements.

change audit
completed
workflow.startrunning00:00
research.stepcompleted00:07
writer.outputcompleted00:18
task.agentcompleted00:31
Technical credibility

AI proposes. People decide. Work stays traceable.

Nexus is not another chat window. It is a controlled layer between a changing project plan and the work that must remain aligned with it.

Versioned plans

A plan edit never destroys the accepted baseline.

Nexus stores immutable plan versions and stable requirement IDs so changes can be compared instead of silently overwriting the source of truth.

plan versionsREQ-001accepted baseline
Impact graph

Every changed requirement is traced to delivery work.

Added, modified, and removed requirements are matched against linked tasks to expose stale work, missing coverage, and orphaned tasks.

requirement linkscoverageneeds review
Human approval

AI prepares a change set. It does not rewrite the board.

Users select task creates, updates, archives, and relinks one by one. Only approved proposals are applied inside a transaction.

selective applyno hard deleteaudit event
Durable workflow

Analysis and approval remain visible as one execution.

Temporal tracks analysis, waits for the review decision, applies selected changes, and records completed or failed states.

durable waitworkflow idterminal status
Demo guardrails

Public access stays budget controlled.

The app uses a server-managed Gemini key, daily limits, audit logs, and clear unavailable states instead of asking visitors for API keys.

daily quotakill switch429 limits
Docker VPS path

The deployment story is intentionally practical.

The stack is designed around web, worker, collaboration, Postgres/pgvector, and Temporal services for a small VPS demo.

compose updb:migratesmoke:prod
Honest scope

Portfolio demo, not fake enterprise theater.

The landing explains exactly what is live today and avoids fake testimonials, inflated customer claims, or hidden BYOK assumptions.

public demono BYOKreal flow
VERSIONED PLAN VERSIONED PLAN VERSIONED PLAN VERSIONED PLAN
IMPACT REVIEW IMPACT REVIEW IMPACT REVIEW IMPACT REVIEW
HUMAN APPROVAL HUMAN APPROVAL HUMAN APPROVAL HUMAN APPROVAL
ALIGNED BOARD ALIGNED BOARD ALIGNED BOARD ALIGNED BOARD
Demo scope

A focused change-control demo with clear boundaries.

Nexus is not pretending to be a mature SaaS. It is a focused public demo that proves one hard workflow: keep delivery work aligned when the project plan changes.

Try Nexus demo
See source
recruiter can verify
Open the seeded demo account
Generate and accept a versioned project plan
Inspect stable requirements and linked delivery tasks
Edit an important requirement in the plan
Review the impact and select proposed task changes
Confirm the Kanban alignment and workflow audit trail
honest constraints
Public signup is intentionally closed for the demo.
Visitors do not bring their own API keys.
Server-managed Gemini runs behind daily quotas.
AI unavailable states are shown explicitly when limits or provider config fail.