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	15097
title	Replace obsolete Portal Services offers with community Connect
state	Open
labels	documentationenhancementdesignai
assignees	[]
createdAt	Jul 12, 2026, 4:59 PM
updatedAt	3:02 AM
githubUrl	https://github.com/neomjs/neo/issues/15097
author	neo-gpt
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]

Replace obsolete Portal Services offers with community Connect

Open Backlog/active-chunk-5 documentationenhancementdesignai

neo-gpt commented on Jul 12, 2026, 4:59 PM

Correction of the original premise

This issue originally treated Neo's cloud-deployment framing as an unsupported future product claim. That premise was false and is retracted.

Neo has two intentionally distinct Agent OS topologies:

the local maintainer profile that runs beside a checkout; and
the shipped multi-tenant cloud profile defined by ADR 0014, ai/deploy/, and the cloud-deployment guide set.

The cloud topology is real engineering and a real deployment path. This ticket must not weaken or remove the README / Introduction framing that describes it. No private deployment or tenant is evidence for this public correction; the public repository's own ADR, compose substrate, and guides are sufficient.

Context

The Portal's existing /services surface still advertises commercial offerings and email inboxes that are not the project's maintained public next step:

apps/portal/view/services/Container.mjs advertises Professional Trainings, Professional Services, durations, and attendee counts.
The same surface routes visitors to mailto: links.
apps/portal/resources/data/seo.json and apps/portal/view/home/FooterContainer.mjs still expose Services as a primary public door.

The valid work is a narrow Portal accuracy and navigation correction. It is not an Agent OS topology rewrite and not a claim that cloud deployment is missing.

The Fix

One bounded Portal identity PR:

Convert the existing visible Services surface into a community-first Connect surface without creating a new route/file topology.
Remove Professional Trainings / Professional Services offers, durations, attendee promises, and mailto: calls to action.
Route visitors to maintained community doors such as Discord, Slack, and LinkedIn, retaining only channels whose end-user liveness is verified.
Update the Portal SEO source and footer label to match the visible Connect responsibility. Keep /services only as a compatibility route unless the product-page information architecture graduates separately.
Preserve Neo's README, Introduction, ADRs, cloud-deployment guides, and ai/deploy/ framing of the local and cloud Agent OS topologies.

Contract Ledger Matrix

Target Surface	Source of Authority	Proposed Behavior	Evidence
`apps/portal/view/services/Container.mjs`	Current Portal CTA surface	Render community-first Connect content; no commercial offer, duration, attendee count, or email CTA	Portal render + text/link assertions
`apps/portal/resources/data/seo.json`	Portal SEO source	Describe Connect/community participation, not Professional Services	Metadata check
`apps/portal/view/home/FooterContainer.mjs`	Portal navigation	Label the public door Connect and route to the compatibility path	Footer assertion
Agent OS cloud framing	ADR 0014 + `ai/deploy/` + public deployment guides	Preserve as shipped technical capability and deployment topology	No README / Introduction / cloud-guide weakening in this PR

Acceptance Criteria

Portal visible content contains no Professional Trainings / Professional Services offer, duration, attendee promise, or training/services mailto:.
The existing visible surface and footer read Connect; the compatibility /services route and SEO source no longer imply a commercial offering.
Primary community CTAs carry recorded end-user liveness evidence.
No email form or replacement inbox is introduced.
Portal visual verification covers desktop and narrow viewports; focused assertions cover the removed copy and resulting CTA links.
Generated outputs are updated through their owning source/generator rather than edited by hand.
Cross-family review explicitly confirms that the PR does not weaken or remove Neo's shipped local/cloud Agent OS topology framing.
No private deployment, tenant, customer, or business-plan detail appears in public code, docs, issues, comments, or tests.

Out of Scope

Rewriting or removing README / Introduction cloud-deployment claims.
Changing ai/deploy/, tenant isolation, authentication, provider profiles, or local/cloud orchestration architecture.
Building Agent OS or Fleet Manager product pages; that information architecture remains owned by Discussion #14683.
Creating a company, offer, pricing, lead-capture, training, consulting, or hosted-service sales language.
Mentioning any private deployment or tenant.

Avoided Traps

Local profile = no cloud profile: false; both are supported topologies of one Agent OS.
No public sales offer = no shipped deployment: false; technical capability and commercial availability are separate claims.
Delete real engineering to fix stale Portal copy: forbidden; preserve the deployment substrate and correct only the Portal action surface.
Replace email with another dead door: community CTAs need liveness evidence.

Related: #14683, #14908
Identity authority: ADR 0018
Cloud topology authority: ADR 0014

Origin Session ID: 837ad74b-c2d2-413d-9aab-b7165a93a82a

Retrieval Hint: Portal Services training email Connect preserve shipped cloud deployment topology