Building an Engineering AI Ecosystem with Replit

Hi team

Over the last few months, I’ve been building something much bigger than a single AI app.

Instead of creating isolated projects, I’ve been trying to build an ecosystem around one core idea:

Engineering reasoning should become interactive, visual, and accessible.

That vision became ORION-TEK.

One of its main products is NEXIA, an AI assistant focused on engineering reasoning. It doesn’t just generate text—it explains concepts, creates interactive demonstrations, visualizes ideas, and helps transform reasoning into something users can explore.

The web version is now online, and I’d really appreciate feedback from the Replit community.

Website ORION-TEK — Penser, décider, construire

NEXIA Web NEXIA Web

I’m particularly interested in your thoughts on:

The overall user experience.

The technical demonstrations.

Whether the concept is clear.

What you would improve before a broader public launch.

Many parts of this project were built with Replit, so I’d like to thank the team and the community. Your discussions and feedback have been valuable throughout the process.

I’m looking forward to hearing your honest opinions. Every suggestion helps improve the next version of NEXIA.

This is an ambitious and compelling direction. NEXIA’s focus on making engineering reasoning visible, interactive, and explorable separates it from assistants built mainly around text generation.

I’m the founder of TrustStak and Fortress Apps. We build AI-powered platforms, business automation systems, and customer-facing digital products. I see several areas where we could support NEXIA:

  • Refining the user experience for first-time and nontechnical users

  • Clarifying NEXIA’s value proposition and target markets

  • Testing demonstrations with real-world users

  • Developing industry-specific applications and pilot programs

  • Supporting commercialization, partnerships, and broader market positioning

I’d be interested in learning more about your roadmap, the industries you plan to serve first, and the type of partnership you’re seeking. There could be a strong opportunity to combine your engineering-reasoning technology with our experience building practical AI platforms and bringing them to market.

Congratulations on getting the web version online. I’d be glad to connect and explore whether our teams can build something valuable together.

What makes this different / better than using a paid Gemini AI account, or Claude Cowork?

Good question. The practical difference is in what happens after you give the AI a task.

With a general-purpose AI like Claude or Gemini, you usually have to guide the conversation, choose what to ask for, refine the prompts, request calculations or diagrams separately, and decide yourself when the work is complete.

NEXIA is designed to take a task and carry it through as a structured workflow.

For example, if a student wants to understand a mathematical or engineering exercise, NEXIA can explain the reasoning, solve the equations, plot the functions, and generate simulations or visual explanations as part of the same work.

For an engineer or technician, NEXIA can frame the technical problem, work according to relevant standards and assumptions, perform calculations, generate technical diagrams and preliminary 2D/3D design sketches, and produce structured technical documents.

There is another difference that is less visible: NEXIA has its own behavioral framework. Its “personality” is defined by a set of technical and normative rules, combined with principles inspired by moral philosophy. These rules influence how it analyzes uncertainty, distinguishes facts from assumptions, approaches responsibility, and decides what should remain a human decision.

So I don’t see NEXIA as a replacement for Claude or Gemini at the model level. Those models can actually be components inside NEXIA. NEXIA is the system around them: the reasoning framework, rules, tools, verification processes and workflows that turn a general AI model into a more specialized working environment.

A simple way to put it is: with a general AI, you manage the AI to get the work done; with NEXIA, the goal is to describe the work and let the system manage the process.

You can see practical examples here: