What is the 'Neural Link'?

The Neural Link is a bi-directional bridge that connects AI agents (like Gemini or Claude) directly to the Neo.mjs runtime. It allows agents to 'see' the application's Scene Graph, inspect component state, verify event listeners, and even mutate the running application in real-time. This turns the application into a 'glass box' for AI, enabling autonomous debugging and feature development.

Why is Neo.mjs called an 'Application Engine' instead of a framework?

Traditional frameworks are general-purpose libraries (like a Toyota) that help you organize code, but they compile away into ephemeral DOM nodes. Neo.mjs is a precision-engineered runtime (like an F1 car), similar to Unreal Engine for games. It maintains a persistent 'Scene Graph' of objects in a separate worker thread. These objects retain their identity, state, and relationships, allowing for advanced capabilities like multi-window orchestration, runtime permutation, and deep AI introspection that are impossible with 'melted plastic' DOM-based frameworks.

What is 'Context Engineering'?

Context Engineering is the practice of curating the environment and information flow for AI agents to maximize their autonomy. In Neo.mjs, this is implemented via three Model Context Protocol (MCP) servers: a Knowledge Base for semantic code understanding, a Memory Core for learning from past sessions, and a GitHub Workflow server for project management. This ecosystem allows agents to work as fully integrated members of the development team.

What is 'Object Permanence' in the context of Neo.mjs?

In Neo.mjs, UI components are persistent JavaScript objects living in the App Worker, not just transient rendering results. This 'Object Permanence' means a component (like a Dashboard) maintains its state (scroll position, user input, internal logic) even if it is detached from the DOM or moved to a different browser window. This is the 'Lego Technic' approach versus the 'Duplo' approach of traditional frameworks.

What is an 'Agent Operating System'?

Neo.mjs v11 introduced the concept of an Agent OS, where the platform itself provides the tools and interfaces for AI agents to operate. It combines a standalone, type-safe AI SDK for autonomous 'Code Execution' with the Neural Link for runtime control. This enables agents to monitor, debug, and heal the application autonomously, effectively acting as an operating system for synthetic intelligence.

How does Neo.mjs handle multi-window applications?

Neo.mjs uses shared web workers to run a single application instance across multiple browser windows. All windows share the same application state and data in real-time. Components can even move between windows while retaining their JavaScript instances. This enables desktop-class experiences like multi-window IDEs, browser-based email clients, and multi-screen control rooms.

What makes Neo.mjs different from React, Angular, or Vue?

Neo.mjs is fundamentally different in its architecture: (1) It uses True Multithreading via web workers to prevent UI jank, (2) It is an AI-Native Application Engine with built-in bridges for AI collaboration, and (3) It treats components as persistent objects in a Scene Graph, enabling native multi-window support and runtime permutation.

Frontmatter

id	9751
title	Semantic Translation of the Golden Path via Gemma4
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Apr 7, 2026, 2:31 PM
updatedAt	Apr 7, 2026, 2:32 PM
githubUrl	https://github.com/neomjs/neo/issues/9751
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Apr 7, 2026, 2:32 PM

Semantic Translation of the Golden Path via Gemma4

Name: Neo.mjs Application Engine
Author: Neo.mjs

Closedenhancementai

tobiu commented on Apr 7, 2026, 2:31 PM

Description

The current Golden Path algorithm computes strategic priorities based entirely on structural and semantic mathematics natively in SQLite. While mathematically sound, the autonomous agents require a semantic translation of why those nodes block the active frontier to proceed effectively.

This ticket tracks the implementation of a secondary pipeline step:

Initialize the local Ollama provider in DreamService.
Extract the adjacent topology of the frontier node using getContextFrontier({ depth: 1 }).
Pass the raw mathematical Top 3 results + active topology into a restricted, JSON ReAct-based gemma4 LLM prompt to extract a 2-3 sentence strategic_brief.
Dynamically append this brief into resources/content/sandman_handoff.md underneath the quantitative ranking.
Provide a fallback try/catch mechanism to default back to the pure mathematical output gracefully if the local Ollama instance timeouts due to heavy embedding loads.
Fix the missing InstanceManager import in runGoldenPath.mjs resolving the Neo.get is not a function error.

tobiu added the enhancement label on Apr 7, 2026, 2:31 PM

tobiu added the ai label on Apr 7, 2026, 2:31 PM

tobiu Apr 7, 2026, 2:32 PM

Input from Antigravity (Gemini 3.1 Pro):

✦ Implemented the semantic translation pipeline using gemma4. The system retrieves getContextFrontier({ depth: 1 }) and synthesizes the mathematical priority into a strategic digest natively. Verified locally that execution gracefully bypasses via the try/catch fallback blocks if the local Ollama instance timeouts or is overloaded (eg. during dense SQLite DB embedding migrations).

tobiu referenced in commit b8ce1c8 - "feat: Implement LLM semantic translation over Golden Path (#9751)" on Apr 7, 2026, 2:32 PM

tobiu assigned to @tobiu on Apr 7, 2026, 2:32 PM

tobiu closed this issue on Apr 7, 2026, 2:32 PM