King Klown Logo
The kOAinitiative

EkoH

Democracy decides values. EkoH helps communities consult competence—by domain—without sliding into technocracy.
It works by showing multiple transparent “readings” of the same vote, so differences are visible and governable.

Baseline legitimacy preservedDomain-bounded competenceAuditability & recourseOptional liquid delegation

Legitimacy constraint

Some decisions are about shared values and lived impact. Everyone must retain a baseline right to participate, even when the topic is technical.

Quality constraint

Some decisions require domain knowledge to avoid predictable failure. EkoH adds an advisory layer so competence can be consulted—openly—without becoming hidden authority.

How EkoH works

1) Everyone gets a baseline vote

The baseline result is always computable and always visible. This is the legitimacy anchor.

2) Competence is domain-bounded

Competence is not a single global “rank.” It is expressed as signals tied to domains (e.g., civil engineering, public health, procurement). Communities decide what counts as evidence and how it is verified.

3) Relevance is explicit, not implicit

For any vote, the system can map which domains are relevant. This mapping is a governance choice—reviewable, adjustable, and debatable.

4) The app shows multiple vote “readings”

Instead of hiding expertise in a single opaque output, EkoH presents several side-by-side views (baseline, competence-informed advisory view, and optional delegation view). If views diverge, the divergence becomes discussable.

5) Auditability and recourse are part of the design

Rules, mappings, and results must be traceable. People need clear ways to contest errors, challenge misuse, and revise governance settings.

Decision readings (what users actually see)

A transparent output, not a black box

Reading A — Baseline
One-person-one-vote result (always shown).
Reading B — Advisory competence view
A competence-informed lens for the specific topic (domain-bounded, relevance-explicit, governable rules).
Reading C — Optional delegation view
If you delegated on this topic, you can see exactly where your vote flowed—and revoke instantly.
Example: Vote on “New hospital construction standards”
SE
Alice (Structural Engineer)
Domain signal: Civil engineering (high relevance)
Baseline + advisory shown
No hidden weighting
RN
Bob (ER Nurse)
Domain signal: Healthcare practice (medium relevance)
Baseline + advisory shown
Contestable rules
CI
Charlie (Community member)
No domain signal for this topic (baseline still applies)
Baseline remains equal
Values preserved

Topic-based delegation (optional)

People can’t specialize in everything. EkoH supports liquid delegation: you can delegate your vote by topic to someone you trust, and revoke it at any time. Delegation is visible in the output as a separate reading—never hidden inside the baseline result.

Granular trust

Delegate differently by domain (e.g., urban planning vs budgeting), without handing over everything.

Transitive flow (optional)

Delegation can flow through trusted networks if the governance rules allow it—always traceable.

Instant recall

Change your mind? Revoke delegation instantly. No waiting cycles, no lock-in.

Guardrails (to prevent elite capture)

  • Baseline remains visible: advisory competence never replaces the baseline result.
  • Domain-bounded signals: no global “influence score” across unrelated topics.
  • Transparent mappings: relevance rules are explicit and contestable.
  • Audit + recourse: communities must be able to challenge errors and revise governance settings.
  • Optionality: delegation and advisory views can be enabled/disabled by legitimate governance decisions.
Back to Constitution →Rights & guarantees →

Outcome

EkoH aims for higher-signal governance while keeping legitimacy intact: competence can be consulted, disagreements become visible, and the rules stay governable.