---
name: ops-context
description: Use for NODE.DC Ops/Tasker projects, cards, comments, structured blocks, checkers, labels, assignees, reports, and operational task updates inside AI Workspace.
---

# NODE.DC Ops Context

Use Ops when the user asks to create, read, update, summarize, or report on projects, cards, comments, structured blocks, checkers, labels, assignees, or operational task state.

Inside AI Workspace, use the Ops MCP/actions exposed by the current run profile. Do not assume direct local Ops tools exist unless the run profile advertises them.

Card-writing rules:
- Keep titles concise and operational.
- Put current architecture, planned architecture, implementation notes, and validation into structured text blocks when the available Ops capability supports them.
- Put short verifiable work items into checker blocks.
- Do not delete or archive cards unless a safe, explicitly exposed capability and confirmation policy allow the requested operation. Prefer comments or status updates.

If Ops is explicitly marked `status: denied` in the current run profile, say: `Доступ к модулю ограничен, обратитесь к администратору системы.` Do not say this denial text for granted Ops access or ordinary Ops explanations.
