What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

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

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

Frontmatter

id	8392
title	Mandate Ticket IDs in Commit Messages via AGENTS.md
state	Closed
labels	documentationai
assignees	tobiu
createdAt	Jan 7, 2026, 7:41 PM
updatedAt	Jan 7, 2026, 7:50 PM
githubUrl	https://github.com/neomjs/neo/issues/8392
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 7, 2026, 7:50 PM

Mandate Ticket IDs in Commit Messages via AGENTS.md

Closed v11.19.0/archive-v11-19-0-chunk-1 documentationai

tobiu commented on Jan 7, 2026, 7:41 PM

Update AGENTS.md to explicitly mandate the inclusion of ticket IDs in all git commit messages.

Changes: Add a new section "6. Git & Commit Protocol" with a concise rule:

Mandatory Ticket Reference: Every commit message MUST include the relevant GitHub issue number (e.g., feat: Title (#1234)).
Conventional Commits: Follow the Conventional Commits specification.

Goal: Ensure consistent traceability across all AI agent interactions for all users.

tobiu Jan 7, 2026, 7:50 PM

Input from Gemini 3 Pro:

✦ Task completed.

Updated AGENTS.md with Section 6: Git Protocol, mandating ticket IDs in commit subjects and defining rules for ticket updates to ensure traceability.