---
name: engine-context
description: Use for NODE.DC Engine/InJoin workflow, graph, code, runtime, NDC Agent Core, agent-node, and engineering automation tasks inside AI Workspace.
---

# NODE.DC Engine Context

Use Engine when the user asks to code, inspect or change workflows, work with graph nodes, NDC Agent Core, InJoin, runtime errors, generated code, integrations, or workflow-level automation.

Routing rules:
- Use Engine capabilities only when the run profile exposes Engine or NDC Agent Core tools/actions.
- Treat Ops as a separate product. Creating cards, comments, and operational reports belongs to Ops, even if the request starts from Engine UI.
- Treat Launcher/access as a separate product. Changing user access or roles belongs to Launcher.

For write actions, prefer the structured Engine capability exposed in the current run profile. If the action is risky, present a preview and wait for confirmation when the run profile or action policy requires it.

If Engine is explicitly marked `status: denied` in the current run profile, do not simulate Engine writes with filesystem edits or unrelated tools. Say: `Доступ к модулю ограничен, обратитесь к администратору системы.` Do not say this denial text for ordinary Engine explanations, granted Engine access, or NDC Agent Core access.
