2
5 Comments

Building an AI Engineering Operating System, not another AI coding tool.

Hi everyone 👋

I'm an indie builder from Indonesia, and over the last few months I've been working on a project called NAEOS (Nusantara AI Engineering Operating System).

After experimenting with tools like Cursor, Claude Code, GitHub Copilot, Gemini CLI, and Codex, I noticed the same pattern:

AI can generate code incredibly fast.

But every new project still requires rebuilding the engineering foundation:

  • Project structure

  • Architecture decisions

  • Coding standards

  • Documentation

  • Security rules

  • Testing strategy

  • AI prompts

  • Team conventions

The AI is powerful.

The engineering context is often missing.

So instead of building another AI coding assistant, I'm trying to build something different:

An open AI Engineering Operating System that provides the standards, workflows, governance, and knowledge layer for AI coding agents.

The long-term vision is to make AI agents work more like experienced software engineers rather than autocomplete tools.

I'm building everything in public:

  • Documentation first

  • Open architecture

  • Modular design

  • AI-native workflows

  • Vendor-neutral approach

This is still an early-stage project, and I'm looking for honest feedback.

Some questions I'd love to hear your thoughts on:

  • Do you think AI development needs an "operating system" layer?

  • What's the biggest engineering problem you've faced while using AI coding tools?

  • Would an open standard for AI software engineering be valuable?

I'd really appreciate your feedback, criticism, or ideas.

Thanks for reading!

posted toAvatar for product naeos
naeos
  1. 1

    What stood out to me is that you're describing a gap that exists before code is ever written.

    The quality of the output often depends less on what the AI knows than on what the surrounding environment has already decided.

    1. 1

      Exactly. That's the layer I'm most interested in.

      Before an AI writes a single line of code, the engineering environment should already define the architecture, constraints, standards, and decision-making boundaries. At that point, the model isn't inventing the process—it's executing within one.

      To me, that's the difference between using AI as a code generator and using AI as an engineering system.

      1. 1

        I appreciate you taking the time to explain your thinking.

        I'd be interested in continuing the conversation by email if you're open to it. What's the best email to reach you on?

        1. 1

          Thank you—I appreciate that.

          I'd be happy to continue the conversation. You can reach me at bayupriatno007@gmail.com

          I'm particularly interested in discussing where protocol-level engineering ends and broader engineering systems begin. I think there's a lot of unexplored ground there, and I'd enjoy exchanging ideas.

          1. 1

            Thanks! I’ve just sent it over.

            Looking forward to hearing your thoughts whenever you have a chance.