Initializing KAEDE…

PT Koneksi Jaringan Indonesia

KAEDE .

A bridge between Trello and Koneksi's Agentic Development ecosystem — where teams unite, AI assists, and workflows run smoothly.

Get Started with Power-Up Learn Ecosystem
Scroll
About

What is KAEDE?

KAEDE is an integration project owned by PT Koneksi Jaringan Indonesia that connects Trello — where teams plan and track work — with the development ecosystem based on Agentic AI.

Starting as a Trello Power-Up for environment management (Production / Staging / Development), KAEDE has evolved into the core bridge between team planning on Trello and AI Agent execution via the OpenCode MCP protocol.

1 Trello Power-Up — Manage environments, badges, and authorization directly from Trello cards.
2 MCP Bridge — Exposes Trello data for reading and writing by AI Agents via OpenCode MCP.
3 Knowledge Hub — The central information hub of the Koneksi ecosystem for all team members.
K

KAEDE

Koneksi Automated Environment & Developer Engineering

v1.0.0 · Last updated June 2026
Ecosystem

Four Pillars of Koneksi Development

Every repository in the Koneksi organization can have all four components. Each has a distinct yet complementary role.

Playbook

Human-to-human guidance. Workflows, SOPs, quality standards, onboarding, ADRs. Stored in the {org}/playbook repository.

Human → Human

OpenKB

AI ↔ Human communication protocol. .openkb/ directory in each repo. SHARED (glossary, decisions) + PERSONAL (private notes).

AI ↔ Human

OpenCode

AI Agent configuration. .opencode/ directory in each repo. Agent types, permissions, project context, rules.

Agent Config

KAEDE

Trello ↔ MCP bridge. Trello Power-Up connecting team planning with agentic execution. Also the ecosystem's information hub.

Integration Bridge

How They Connect?

Playbook OpenKB OpenCode KAEDE Trello

Humans write guidelines in Playbook → AI reads context from OpenKB → Agent is configured via OpenCode → KAEDE connects everything to Trello.

Protocol

OpenKB

Open Knowledge Base — AI ↔ Human communication language

OpenKB is a protocol that enables AI Agents and humans to share context bidirectionally. Stored as a .openkb/ directory in each repository.

Two storage spaces:

Tracked SHARED/

Term glossary, external references, architectural decisions (decision-log). Committed to git — readable by everyone and AI.

Gitignored PERSONAL/

Personal notes, local preferences, experiments. Individual only — not in git, not readable by others.

Directory Structure

# Each repo can have this:
.openkb/
├── SHARED/
│   ├── glossary.md      # Terms & abbreviations
│   ├── references.md    # Links & references
│   ├── decision-log.md  # Architecture decisions
│   └── project-context.md # Project context
└── PERSONAL/
     └── .gitignore      # Not tracked

Communication Flow

→ AI reads OpenKB before assisting — understands context, terms, rules.
→ Humans write OpenKB — record decisions, update glossary, add references.
→ Bidirectional — AI can suggest updates to OpenKB, humans review and approve.
Guide

Playbook

Operational standards for humans

A Playbook is a collection of human-to-human documents containing standards, workflows, and SOPs for the Koneksi team. Stored in a separate repository: {org}/playbook.

📋 Philosophy & engineering principles
📋 Git & GitHub workflow (branching, PR, commit)
📋 Trello integration — from card to code
📋 New team member onboarding
📋 Quality standard & code review

Playbook vs OpenKB

Aspect Playbook OpenKB
Audience Humans AI Agent + Humans
Location Own repository Inside each repo
Format Narrative documentation Standard directory structure
Scope Org-wide Per repo
Configuration

OpenCode

AI Agent configuration per repository

OpenCode is the AI Agent tool used by the Koneksi team. Each repository can have an .opencode/ directory that configures how AI Agents behave in that repo.

Agent Types

Each repo has several agents with different roles: build (execution), plan (planning), review (review), docs (documentation). Each has different permissions.

Project Context

Files like SHARED/project-context.md and SHARED/agent-rules.md inform the AI about the tech stack, team, rules, and repo conventions.

Example Structure

.opencode/
├── opencode.json       # 4 agent types + permissions
└── SHARED/
     ├── project-context.md # Stack, team, repo
     └── agent-rules.md    # Agent rules

Integration with KAEDE

Through MCP (Model Context Protocol), OpenCode can call KAEDE to read and write Trello data — creating cards, updating labels, checking assignments — directly from conversations with the AI Agent.

Workflow

Team Agentic Coding Operation

Koneksi runs development with a Human In The Loop (HITL) approach — AI Agents assist execution, humans remain in control.

1

Planning Product + BA

Product Manager and Business Analyst define requirements in Trello: creating cards, setting priorities, attaching context. Each card can be assigned an environment label (Production/Staging/Development) via the KAEDE Power-Up.

2

AI Context OpenKB

Before starting, the AI Agent reads OpenKB and OpenCode in the repository to understand the context: project terms, architectural decisions, tech stack, rules. The Agent can also read related Trello cards via KAEDE.

3

Execution Developer + Agent

Developers (Frontend, Backend, UI/UX, Junior) work with the assistance of AI Agents. The Agent helps write code, check patterns, run tests. The Developer stays in control — AI is a pair programmer, not a replacement.

4

Review Senior (HITL)

Human In The Loop — Senior Developer reviews all changes before merging. Ensures quality, consistency, and security. AI Agents assist with review (static analysis, pattern check) but the final decision remains with the human.

5

Deploy & Report CI/CD

After merging, it is automatically deployed. Trello cards are updated — status, environment, deploy links. Everything is documented in the OpenKB decision-log for future context.

Guide

Using KAEDE Power-Up

How to install and use KAEDE on your Koneksi team Trello.

1

Install Power-Up

Open trello.com/power-ups/admin, click Create or add an existing KAEDE registration. Enter the URL: https://kaede-powerup.netlify.app

2

Enable on Board

Open your team Trello board → Power-Ups → search for "KAEDE" → Enable. The KAEDE button will appear in the board header.

3

Manage Environment

Open a card → click KAEDE: Environment → select Production / Staging / Development. A badge will appear on the card face.

MCP Integration Live

The KAEDE MCP Server is active. AI Agents in OpenCode can read and write Trello directly — all 22 tools are available via dist/mcp-server.js.

22 Tools Boards Lists Cards Members Labels Comments
bun dist/mcp-server.js