DEVELOPERS

Stable boundaries for knowledge systems.

Jonex separates browser access, shared governance, business capabilities, domain orchestration, and atomic engines so each layer can evolve with a clear contract.

View GitHub Contact

QUICK START PATH

Follow the complete knowledge workflow.

The repository is the source of truth for setup and current implementation details. This sequence shows how the product pieces connect.

Run the platform

Start the required Docker Compose profile and verify the gateway and capability health checks.

Define the domain

Create or select a domain space, then create a knowledge base and choose its parser profile.

Connect sources

Upload files or configure a supported REST API, MinIO or S3 source, or signed inbound push.

Compile knowledge

Track parsing and ontology compilation through the document lifecycle.

Search and review

Query one or more knowledge bases, inspect structured references, and record feedback.

REQUEST PATH

One public API surface. Governed capabilities behind it.

The browser stays on the frontend origin, while gateway and governance layers protect internal service boundaries.

01 / Browser

Frontend gateway

Serves the shell and applications, and sends business requests only through /api/v1/**.

02 / Route

API Gateway

Aggregates HTTP routes and forwards calls without taking ownership of business composition.

03 / Govern

Sidecar

Handles authentication, tenant context, internal identity, metering, rate limits, resilience, and invocation.

04 / Execute

Capability service

Applies business rules through services and repositories with tenant-scoped data.

05 / Compose

Domain and atomic clients

Combine retrieval, parsing, ontology, language, and other technical engines behind stable boundaries.

GROUNDED RESPONSE

Evidence is part of the contract.

Ontology-aware search is available at POST /api/v1/knowledge-base/search/ontology. A knowledge response can carry structured reference data for the consuming application to show where the answer came from.

ILLUSTRATIVE RESPONSE SHAPEapplication/json

{
  "answer": "...",
  "references": [
    {
      "doc_id": "document-id",
      "file_name": "policy-manual.pdf",
      "media_type": "pdf",
      "raw_url": "signed-source-url",
      "locations": [
        { "type": "page", "page_no": 48 }
      ]
    }
  ]
}

IMPLEMENTATION RULES

Contracts that keep the system coherent.

Business APIs use one versioned browser-facing prefix.
Tenant identity comes from trusted authentication context, not an arbitrary request body.
Gateway routing stays separate from capability business rules.
Services own business decisions; repositories own persistence access.
Source files use abstracted object storage with controlled access URLs.
Retrieval paths return structured references consistently.

CONTACT

Design the right integration boundary.

Share the systems, data sources, and application workflow you need Jonex to support.

Contact