مرکز اسناد در حال تکمیل است — وضعیت حقوقی هر سند را پیش از استناد بررسی کنیدمشاهده اسناد
لوگوی رسمی ارث‌کوپ مرکز دانش ارث‌کوپشناخت · راهنما · اسناد بنیادین
فاتغییر زبان
فارسیفعال Englishراهنماهای انگلیسی العربيةترجمه موجود نیست
EarthCoop.ir

English Product Guides

NajmHoda: Your AI Support Assistant on EarthCoop

NajmHoda is EarthCoop's AI assistance and orchestration subsystem. The Current product includes a real member chat path, conversation history, policy-aware orchestration, conditional support escalation, and selected context-aware assistance flows. Other specialist, knowledge, and action capabilities are still evolving / In development and should not be treated as uniformly available merely because the architecture anticipates them.

Current product

For an authenticated ordinary member, the current chat path routes the conversation through the Steward mode. The controller records the conversation under that member, validates the request, passes it through the entry-policy and execution layers, and can return suggestions or escalation information when the applicable services provide them.

Current code also supports owner-scoped conversation retrieval, listing, archiving, and deletion. These are real application capabilities; exact placement or styling in the user interface may evolve independently of the underlying controller contract.

Assistance is not authority

NajmHoda can explain, draft, suggest, summarize, and in some explicitly authorized contexts help invoke a product workflow. It does not gain authority simply because a user asks it to act.

The current execution boundary is deliberately server-controlled:

  • browser-provided page context is informational only;
  • the server resolves the authenticated user and trusted page/domain context again;
  • client-supplied fields cannot grant action authority;
  • mutating actions require the applicable server authorization, entry policy, role/ownership checks, and domain service;
  • NajmHoda cannot legislate new rules or override EarthCoop law, policy, permissions, or monetary safeguards.

A conversational answer is not itself an approval, election result, legal decision, financial authorization, or completed system mutation. The underlying domain must independently authorize and record the operation.

Context-aware assistance

Some current flows are page-aware. For example, the implementation contains dedicated assistants for selected private group/action-item and secretariat contexts. Those helpers are constrained by their server-resolved context and domain rules.

The secretariat drafting assistant provides a useful example of the boundary: it may preview or save a Draft, but it is explicitly not allowed to submit, register, dispatch, or publish merely because the chat requested that outcome. A later formal workflow must perform those actions under its own authority.

Knowledge and support

NajmHoda can use EarthCoop knowledge sources and support infrastructure through the configured orchestration path. The exact retrieval sources, ranking strategy, indexing state, and availability can change as the subsystem evolves, so this documentation does not promise that every answer follows one fixed search recipe.

When the current escalation policy determines that a conversation should move to human support, the chat flow can ask the support service to create or link the relevant ticket information. Escalation is conditional and should not be read as a guarantee that every uncertain answer automatically creates a ticket.

Evolving / In development capabilities

NajmHoda is a central long-term component of EarthCoop, but several areas remain under active development, including parts of the knowledge pipeline, broader specialist orchestration, and additional authorized actions across product domains.

The safe documentation rule is:

architectural intention ≠ current capability
assistant suggestion ≠ system authority
successful domain mutation = trusted authorization + domain execution + audit record

Explore NajmHoda

Chat with NajmHoda

Learn the verified member chat flow, conversation boundary, and server-side authorization rules.

Knowledge Base

Understand the knowledge sources and the limits of freshness and retrieval guarantees.

Support Tickets

Use the support system when a matter requires human handling or a formal ticket workflow.