CARAKA · README

Animasi di GitHub, tanpa GIF

GitHub membuang <script> dan <style> dari markdown, tapi gambar dilewatkan apa adanya. Jadi animasinya dititipkan di dalam SVG, pakai SMIL — <animate> dan <animateTransform>, markup gerak bawaan SVG yang tidak butuh stylesheet sama sekali. Ukurannya kecil, tajam di layar retina, dan tidak ada GIF 4 MB yang harus di-render ulang tiap ganti kata.

Satu batasan yang menentukan bentuknya: font eksternal tidak ikut termuat — SVG dirender pakai font milik pembaca. Makanya aksara ꦕ tidak dipakai di dalam banner (di Windows sering jadi kotak kosong); lambangnya dibangun dari geometri cincin yang sudah jadi motif situs, dan teksnya cuma mono dan sans generik. Aksara tetap ada di badan README, tempat GitHub menanganinya sebagai teks biasa.

TIGA BERKAS

assets/banner.svg.txt
Gerbang membuka, cincin berputar, utusan menelusuri lemniskat.

assets/flow.svg.txt
Paket berjalan Telegram → caraka → agent, dan progres balik lagi.

org-profile/assets/banner.svg.txt
Dua utusan berjalan saling mendekat, gerbang approval naik di tengah.

Ketiganya berakhiran .txt karena editor ini membuang markup gerak dari berkas .svg. Buang akhiran .txt-nya saat commit — isinya sudah final, tidak ada yang perlu diubah.

01 · BANNER REPOassets/banner.svg.txt · 1280×440

02 · DIAGRAM ALURassets/flow.svg.txt · 1280×380

03 · BANNER ORGANISASIorg-profile/assets/banner.svg.txt · 1280×340

Loop delapan detik: dua utusan berjalan saling mendekat, berhenti di gerbang yang naik di tengah, gerbang menyala hijau ✓ human, lalu keduanya lewat. Legendanya berakhir dengan dua mayat; animasinya berakhir dengan dua yang selamat. Itu seluruh tesis organisasinya, tanpa satu kalimat pun.

04 · TAMPAK DI GITHUBCarakaDev/caraka · README.md

github.com/CarakaDev/caraka

📖CarakaDev/carakaPublic★ Star⑂ Fork

npmv1.0.0licenseMITnode≥22protocolACPstatusv1.1

caraka.dev · Blueprint · Install · Threat model · Roadmap · 🇮🇩 Bahasa Indonesia

v1.1. Telegram, Discord, and WhatsApp, on one contract, with seven agent presets, memory, more than one workspace, a read-only dashboard on loopback, and a policy-mode gate that leaves a room read-only until someone opts it in. Claude Code is the only agent that has ever answered here, and no field gate has been answered by anyone but the author.

What it is

Coding agents are locked to one terminal on one machine. Caraka is the missing transport — a thin bridge, not another assistant.

It has no agent loop, no tools, no model provider, and no plugin marketplace. Your coding agent already has all of those, and its versions are better. Caraka adds only what chat needs — identity, sessions, approvals, and audit.

▸ Same thing, as plain text

Try it

npx caraka init      # guided setup — checks Node, finds your agent, pairs the bot
npx caraka start     # start the envoy

No agent installed? Init takes any one of the seven presets it finds on PATH, and an authenticated Claude Code is the one route proven here.

05 · PROFIL ORGANISASICarakaDev/.github · profile/README.md

ꦕCarakaDev2 repositories

Tools for coding agents that can be interrupted, questioned, and asked to explain themselves.

The name

In the Javanese script, the first four letters are not letters. They are a sentence.

ꦲꦤꦕꦫꦏ · hana caraka — there were two envoys

ꦢꦠꦱꦮꦭ · data sawala — they disagreed

ꦥꦝꦗꦪꦚ · padha jayanya — they were equally strong

ꦩꦒꦧꦛꦔ · maga bathanga — both became corpses

Both obeyed perfectly. Both were right according to the instructions they held. Both died — killed not by disloyalty but by loyalty without context. Every project here is a different answer to that failure.

Projects

carakaThe envoy. A thin bridge from Telegram, Discord, or WhatsApp to the coding agent already on your machine — sessions as topics, threads, or a header, approval before every write, nothing executed without a human in between.v1.1, unproven

titenThe memory. Agent memory that never flattens a conclusion into its evidence — claims cite their observations, extraction is deterministic.active

One is sent. One remembers.

TARUH DI MANA

di sini                    →  di repo

assets/banner.svg.txt      →  assets/banner.svg
assets/flow.svg.txt        →  assets/flow.svg
README.md                  →  README.md
README.id.md               →  README.id.md

                              (repo CarakaDev/.github)
org-profile/README.md      →  profile/README.md
org-profile/assets/
  banner.svg.txt           →  profile/assets/banner.svg

Profil organisasi butuh repo publik bernama persis .github di bawah CarakaDev. Isinya muncul otomatis di halaman depan organisasi.

YANG PERLU DIINGAT

Buang akhiran .txt saat menaruh berkasnya di repo. Markdown-nya sudah menunjuk ke assets/banner.svg, jadi tidak ada yang perlu disesuaikan lagi.

Pakai path relatif di markdown, bukan URL raw.githubusercontent — path relatif ditulis ulang GitHub jadi URL satu origin dan disajikan langsung, sehingga animasinya jalan. URL ke host lain lewat proksi gambar camo, dan animasinya tidak selamat.

Kartu ini gelap di kedua tema GitHub, jadi tidak perlu dua berkas <picture>.

Animasi mulai ulang tiap gambar dimuat, jadi bagian intronya selalu terlihat oleh pengunjung baru — sisanya loop pelan supaya tidak mengganggu saat orang membaca.

npm tidak menampilkan gambar berpath relatif. Diagram teks polos sengaja disimpan di <details> supaya pembaca npm tetap kebagian.