How to Chat with NajmHoda and Get Help on EarthCoop

NajmHoda has a real authenticated chat flow in the current EarthCoop application. You can ask questions in natural language and continue an existing conversation. Ordinary members are routed through the Steward mode by the current web controller.

Asking a question

The current web chat request accepts a message under the controller's current validation rules. A conversation can be continued through the product's existing conversation context. Conversations are owner-scoped: one member must not be able to retrieve or operate on another member's conversation simply by knowing an ID.

NajmHoda may return an answer, suggestions, and other response metadata produced by the current orchestration path. The exact wording and knowledge sources can vary with the active model, policy, available sources, and subsystem state.

Conversation history

The current web controller supports owner-scoped conversation operations including listing, opening, archiving, and deletion state. The user interface around those operations may evolve, so this guide documents the verified capability rather than promising a particular icon position or menu label.

Page context and action safety

NajmHoda can receive page context to make assistance more relevant, but browser context is informational, not a source of authority. The server resolves the authenticated member and trusted page/domain context again before an action-capable helper can proceed.

All mutating actions require trusted server authorization plus the applicable role, ownership, policy, and domain checks. A client cannot grant itself permission by sending actor, role, target, or page identifiers in chat context.

Asking NajmHoda to perform an action does not make that action authorized. The underlying EarthCoop service remains responsible for permission, validation, execution, and audit.

Draft assistance vs formal action

Selected contexts have dedicated assistance. In the secretariat context, for example, the current helper can preview or save a Draft. It is deliberately constrained: it does not submit, register, dispatch, or publish the draft on its own.

A draft, recommendation, or conversational confirmation is not a formal governance, economic, or administrative act until the responsible workflow executes it under its own rules.

Support escalation

The current chat flow includes a support-escalation service. Escalation is conditional: the policy/service evaluates the message and response and may create or link support-ticket information when the criteria are met. It is not a guarantee that every failed or uncertain answer creates a ticket.

When you need a formal support case, see Support Tickets.

Native/client API boundary

EarthCoop now has a real versioned native/client NajmHoda endpoint at:

/api/v1/najm-hoda/message

That endpoint is part of the current first-party/native /api/v1 contract. It does not automatically expose the entire web conversation-history controller or every specialized NajmHoda helper as a v1 endpoint, and it is not a blanket third-party automation API.

Authentication and action authority remain enforced on the server in both web and native/client flows.