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	8936
title	Fix: RecordFactory mapping logic not triggering for missing source keys
state	Closed
labels	bugcore
assignees	tobiu
createdAt	Feb 1, 2026, 5:25 PM
updatedAt	Feb 1, 2026, 5:33 PM
githubUrl	https://github.com/neomjs/neo/issues/8936
author	tobiu
commentsCount	1
parentIssue	8930
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 1, 2026, 5:33 PM

Fix: RecordFactory mapping logic not triggering for missing source keys

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

Closed v12.0.0 bugcore

tobiu commented on Feb 1, 2026, 5:25 PM

This task fixes a bug in Neo.data.RecordFactory where model fields using the mapping configuration are not populated if the field name itself is missing from the input data object.

The Issue

Currently, setRecordFields iterates over Object.entries(fields) (the input data). If a field like y2025 relies on a mapping years.2025, but y2025 is not in the input data, setRecordFields never processes it, and the mapping logic inside parseRecordValue is never triggered.

The Fix

Modify Neo.data.RecordFactory.assignDefaultValues to also handle mapped fields.

Iterate over the model's fields.
If a field has a mapping and the field key is missing in the data object:
- Explicitly set data[fieldName] = undefined (or the default value).
This ensures that setRecordFields will visit the field, triggering parseRecordValue, which then correctly resolves the mapping from the source data.

Acceptance Criteria

Fields with mapping are correctly populated even if their key is missing in the source data.
The DevRank grid correctly displays data for the mapped yearly columns.

tobiu added the bug label on Feb 1, 2026, 5:25 PM

tobiu added the core label on Feb 1, 2026, 5:25 PM

tobiu added parent issue #8930 on Feb 1, 2026, 5:25 PM

tobiu assigned to @tobiu on Feb 1, 2026, 5:26 PM

tobiu referenced in commit 33c939e - "fix: RecordFactory mapping logic not triggering for missing source keys (#8936)" on Feb 1, 2026, 5:32 PM

tobiu Feb 1, 2026, 5:32 PM

Input from Gemini 3 Pro:

✦ I have implemented the fix for RecordFactory mapping logic.

The Fix

I modified assignDefaultValues in src/data/RecordFactory.mjs. It now iterates over mapped fields and, if the field is missing from the input data object, it attempts to resolve the value using the mapping path from the data object itself.

This effectively "pre-populates" the mapped fields in the config object before setRecordFields iterates over them, ensuring that the mapping is applied and the value is set on the record.

Verification

This change ensures that y2025 (mapped to years.2025) in the DevRank model will be correctly populated from the source JSON, even though y2025 is not a key in the source JSON.

I have pushed the changes to dev.

tobiu closed this issue on Feb 1, 2026, 5:33 PM