— Zeki Akgül — home
TRContact

01 / Living plan workspace

Change the plan once. See the impact before the work changes.

Role
Independent product design and full-stack engineering
Status
Live public demo
Year
2026
Nexus living plan editor with requirements and impact graph.

Decision flow

A plan change stays reviewable before it becomes delivery work.

Nexus is not another writing surface. Its product is the authority boundary between an accepted baseline and a proposed change.

  1. 01Accepted plan
  2. 02Proposed revision
  3. 03Impact analysis
  4. 04Human decision
  5. 05Audit trail

Signature flow / 01

The system finds the change. It never inherits authority.

Proposals remain visible, affected work stays traceable, and only the selected set is applied.

01Accepted baselineNever silently overwritten
02Review proposalLikely impact stays visible
03Human approvalApply / reject / relink
IMPACT

Requirement · Work · Test · Link

Plans change. The trace stays.

Nexus keeps plan and delivery in one change trace. It compares revisions, surfaces impact, and leaves the decision with a person.

REVISION TRACEV03 / REVIEW
  1. 01PLANbaseline.v2
  2. 02IMPACTimpact.review
  3. 03APPROVALhuman.approval
plan.v3  /  affected work  /  apply decision

Authority stays human.

AI flags likely impact; execution waits for human approval.

This constraint shaped the interface: baseline and proposal are visually separate, impact is explicit, and approval is a real state rather than a decorative confirmation dialog.

From analysis to audit.

Temporal holds workflow state; PostgreSQL, Yjs, and audit events stay in one trace. The public demo uses quota-limited server access and honest unavailable states.

The result is intentionally narrow: one difficult workflow, implemented end to end and available to verify.

Product evidence

When the decision stays visible, the product becomes explainable.

Nexus dashboard showing plans, workflow history, and priority work.
01 / Operational surface

Plans, workflow state, and delivery priorities remain in one workspace.

Nexus landing page showing a controlled plan-change workflow.
02 / Live demo

The public surface presents one difficult flow as a narrow, verifiable product demo.

System boundaries

A durable workflow and a visible decision are two halves of the same product.

  1. 01Next.js 16
  2. 02React 19
  3. 03TypeScript
  4. 04PostgreSQL + pgvector
  5. 05Drizzle
  6. 06Temporal
  7. 07Yjs
  8. 08Gemini
  9. 09Docker
Engineering notes
31
Unit test files
02
End-to-end specs
01
Approval gate

Boundary

Where the claim stops

Nexus is a focused portfolio demo, not a production-scale SaaS. The public workspace is isolated and deliberately limits external provider behavior.

Open live demoView source