CONEXIQ / ENTERPRISE INTELLIGENCE

Conexiq Knowledge

Enterprise Knowledge Assistant

Technical brief · document revision 1.0 · 18 October 2026

A reusable pattern for conversational access to organisational knowledge, adapted to the audience, sources and work channel.

Core capability

• Knowledge-source catalogue and retrieval boundaries
• Question, answer and source-reference experience
• Audience and identity integration
• Evaluation set and operational feedback

Interface responsibilities

• Inputs: user question, validated caller context and permitted knowledge scope
• Outputs: grounded response, source references and missing-evidence handling
• Connections: enterprise content sources and the selected employee channel

Example interface envelope

This reference envelope explains integration responsibilities. It does not prescribe a shared production endpoint; the schema and authentication contract are established for the deployment.

{
  "profile": "Conexiq Knowledge — reference interface",
  "documentRevision": "1.0",
  "scope": "An illustrative integration envelope. Endpoint, authentication, source access and schema are agreed for each implementation.",
  "request": {
    "correlationId": "example-001",
    "question": "Which guidance applies to this operational task?",
    "knowledgeDomain": "agreed-domain"
  },
  "response": {
    "correlationId": "example-001",
    "status": "answered | insufficient_evidence | access_denied | failed",
    "answer": "A response supported by the permitted sources.",
    "sources": [
      {
        "title": "Authoritative guidance",
        "reference": "source-reference",
        "location": "permitted source link"
      }
    ]
  },
  "serviceResponsibilities": [
    "Validate caller identity outside model-supplied text",
    "Enforce the permitted source scope",
    "Return source references",
    "Handle insufficient evidence explicitly"
  ]
}

Deployment configuration

• Authoritative collections and source ownership
• User groups, authentication and channel integration
• Representative questions and release acceptance

Extension paths

• Extend knowledge coverage through source review and evaluation
• Add work channels while preserving identity and source boundaries
• Introduce business actions as separately scoped, approved tools

Release acceptance

Agree the business scenarios, authorised users, source and tool boundaries, failure behaviour, evaluation set and support ownership. Record the acceptance evidence for the selected release.

Read the corresponding delivery story · Module overview · consult@conexiq.com.au