King Klown Logo
King Klown& KOA

Konnaxion – Technical Architecture & Services

This page collects the technical details of Konnaxion: service code‑names, core models, configuration parameters, routing invariants, and cross‑module infrastructure. It complements:

Use this page as the reference for development and integration work.


1. Platform overview

1.1 KOA module map

Konnaxion’s architecture is organized into six top‑level modules:

Each KOA module is implemented as one or more Django apps with:

1.2 Shared technology stack

Across modules, the technical stack is consistent:


2. Cross‑module infrastructure

2.1 Service code‑name convention

Every sub‑module defines named services that are stable integration points. Examples:

Code‑names map 1‑to‑1 to service modules (e.g. services/dynamic_weighted_vote.py), and are referenced by tasks, API endpoints, and configuration.

2.2 Routing invariants

Top‑level routes are owned by specific modules and treated as invariants. Namespacing is enforced for consistency:

No other module should claim these top‑level paths.

2.3 Storage and media

Storage is typically an object store (S3/MinIO) behind the media path.

2.5 Realtime and background jobs


3. Module–by–module technical summary

3.1 KonnectED

3.1.1 Knowledge – Collaborative Learning Library

Services

Core models

Key configuration

Routes

3.1.2 CertifiKation – Skills & Certification

Services

Core models

Key configuration


3.2 Ethikos

3.2.1 Korum – Structured Debates

Services

Core models

Key configuration

Routes

3.2.2 Konsultations – Public Consultations & Feedback

Services

Core models

Key configuration

Routes


3.3 Kreative

3.3.1 Konservation – Creative Content & Cultural Preservation

Services

Core models

Key configuration

Routes

3.3.2 Kontact – Collaboration & Networking

Services

Core models

Key configuration

Routes


3.4 keenKonnect

3.4.1 Konstruct – Project Collaboration Spaces

Services

Core models

Key configuration

Routes

3.4.2 Stockage – Secure Repository & Versioned Storage

Services

Core models

Key configuration

Routes


3.5 Kollective Intelligence

3.5.1 EkoH – Reputation & Expertise

Services

Core models

Key configuration

Runtime

3.5.2 Smart Vote – Weighted Voting System

Services

Core models

Key configuration

Runtime & analytics


4. Data flows and integration

4.1 Reputation‑weighted voting

4.2 Projects and documents

4.3 Culture, archives, and networks

4.4 Learning and certification


5. Analytics and insights


6. Contribution guidelines and invariants (technical)

When extending or integrating with Konnaxion, the following invariants should be respected (all documented above):

  1. Do not change top‑level route ownership (/learn, /certs, /ethikos/korum, /ethikos/consult, /projects, /kreative, /connect, /kollective/konsensus, /reports/smart-vote) without updating all dependent modules.
  2. Preserve service code‑names (e.g. dynamic_weighted_vote, multidimensional_scoring); treat them as public, versioned integration points.
  3. Respect frozen parameter values when relying on thresholds, caps, or schedule timings, or introduce new configuration entries in a documented way.
  4. Reuse shared infrastructure (Channels+Redis, Celery, /app/media/, PostgreSQL tsvector) to keep behavior consistent and predictable.

This page, together with the module‑specific wiki entries, should provide enough technical context to navigate, extend, and integrate the Konnaxion codebase.