# /platforms/konnaxion/kollective-intelligence/kintsugi

> Canonical HTML: https://initkoa.org/platforms/konnaxion/kollective-intelligence/kintsugi
> Markdown mirror: https://initkoa.org/platforms/konnaxion/kollective-intelligence/kintsugi/index.html.md
> Route: /platforms/konnaxion/kollective-intelligence/kintsugi
> Source: app/platforms/konnaxion/kollective-intelligence/kintsugi/page.mdx
> Generated: 2026-04-09T23:01:26.288Z

[Open the HTML page](https://initkoa.org/platforms/konnaxion/kollective-intelligence/kintsugi)

'Operate Smart Vote + EkoH “under one roof” to run legitimate decisions under complexity: baseline voting + domain-bounded advisory readings + publishable accountability.',

# Kintsugi (Kollective Intelligence)

**Kintsugi** is the “operate layer” for **Smart Vote + EkoH** inside Konnaxion.

It turns voting into a **governance-grade decision workflow**: a process with phases, clear publication rules, and outcomes that remain **legible and contestable**—even when expertise matters.

## What it enables (for citizens and communities)

### 1) Decisions that stay democratic
Konnaxion’s goal is to **raise decision quality without reallocating decision rights**.

So every decision can be viewed as:
- a **baseline result** (one-person-one-vote), and
- an **advisory reading** that incorporates **domain-bounded competence signals**.

The baseline is never hidden.

### 2) A dual view: opinion vs credibility
Large groups have two real “shapes”:
- how opinions cluster (what people want), and
- how credibility is distributed (who has demonstrated competence and integrity for *this* domain).

Kintsugi preserves both views instead of collapsing everything into popularity.

### 3) A complete lifecycle (not a thread)
A decision is not a comment section. It has a lifecycle:
- setup → decision window → tally → publication → follow-up.

Kintsugi makes that lifecycle explicit so communities can actually **finish** decisions.

## The two pillars

The decision interface: time-boxed votes, clear results, and multiple readings that can be compared side-by-side.
Open Smart Vote →

The domain-based expertise and ethics ledger (with privacy and audit context). It makes advisory readings explainable and reviewable.
Open EkoH →

## What users actually get

### Transparent outcomes (not “black box governance”)
Every published result should come with:
- the **baseline** outcome (one-person-one-vote),
- an **advisory** outcome (domain-bounded reading),
- and a **public explanation surface** that shows *why* the advisory reading differs (without exposing private data).

### Domain-bounded competence (not a global score)
Competence is treated as **domain-specific**:
- being strong in one domain does not grant authority in unrelated domains,
- competence can decay unless renewed by recent evidence,
- integrity can adjust influence (as a bounded modifier).

This keeps merit usable without becoming technocracy.

### Accountability after the vote
A decision is incomplete until it is linked to follow-up:
- what happens next,
- who is responsible,
- when updates are due.

Kintsugi treats publication as the beginning of accountability—not the end.

## Typical workflow (end-to-end)

1. **Define the decision**
- set phases (open/close windows), eligibility, and publication rules.

2. **Open the decision window**
- people participate;
- the system can show both a baseline view and an advisory view.

3. **Publish outcomes**
- official result + transparency views (baseline + advisory reading).

4. **Link execution**
- adopted outcomes connect to implementation tracking and updates elsewhere in Konnaxion.

## Where this connects in Konnaxion

- **ethiKos** can feed structured deliberation into decision-ready proposals.
- **KonnectED** can support verifiable competence evidence (when communities choose to use it).
- **keenKonnect** can coordinate execution and preserve outputs so decisions don’t disappear.

## Next