karass.dev●status: building itself·phase 1 · foundation·watch it build →

  ##  ##    ####    #####     ####    ######  ######
  ##  ##   ##  ##   ##  ##   ##  ##  ##      ##
  ## ##    ##  ##   ##  ##   ##  ##  ##      ##
  ####     ######   #####    ######   ####    ####
  ## ##    ##  ##   ## ##    ##  ##      ##      ##
  ##  ##   ##  ##   ##  ##   ##  ##      ##      ##
  ##  ##   ##  ##   ##  ##   ##  ##  ######  ######

karass is building itself

a self-driving product: it senses its own defects, picks the next block from the queue, builds it, and a verifier — never the builder — decides whether the block stands. this page is the construction site. what you see below is the actual work queue of the organism assembling itself, block by block.

customer #0 is karass. customer #2 is checkmyapp.dev — a sibling organism that gives karass its sense of touch. if it can build itself, it can build for you.

## the crane — what's building now

a tower crane over the structure it's assembling, live from Linear and GitHub. it carries the block it claimed, hangs it above the tower while checks run, and lowers it into place once a verifier — never the crane — says it stands.

[idle] no active session

→ raw queue cards
next in line
[ ].crane bookkeeping in the PR diff is the reviewer's most repeated P1 — it burned three blocksKARASS-247
[ ][gap:v7_self_hosted_from_terraform] V7 — self-hosted: the builder the organism runs on is provisioned from Terraform, not by handKARASS-256
[ ]Прокинуть id decision_point-события допуска до порождённого блокаKARASS-252
[ ]Headless browser screenshot capture utilityKARASS-250
[ ]Map PR diff to changed UI pages/routesKARASS-249
[ ]Route outside_diff verdicts to the new root-cause ticket instead of capping the PRKARASS-240

## roadmap

blocks placed: 20/31growing now: 0spores waiting: 11· Linear unreachable, showing last known snapshot (2026-08-22)
phase 0 · awakening████████████████████████4/4

the corpse was audited, the concept reborn: karass builds itself.

epic zero · research & rebirth
[x]autopsy: why v2 died without ever running its loop
[x]market sweep: everyone stops at "human approves merge"
[x]concept gate: a self-driving product that builds itself
[x]this roadmap, published on the front page
phase 1 · foundation███████████████████░░░░░7/9

the construction site gets ground to stand on. nothing autonomous without it.

epic A · foundation — github, ci, deploy
[x]push the repo to github, install the karass app, protect mainKARASS-97
[x]ci on every pr: typecheck + lint + buildKARASS-98
[x]auto-deploy: merge to main → cloud build → cloud runKARASS-99
[ ]agent merge policy: who merges what, and how it is enforcedKARASS-100
[ ]preview deploy per pr + post-deploy screenshotKARASS-101
epic B · mycelium — the event log
[x]event log schema: append-only, refs, meta-levelsKARASS-102
[x]writers everywhere: sessions, ci, deploys, tickets — log-firstKARASS-103
[x]read interface: mcp server over the event logKARASS-104
[x]organism self-health: liveness per limbKARASS-105
phase 2 · the crane██████████████░░░░░░░░░░3/5

a dispatcher that picks the next block, builds it, and hands it to the verifier.

epic C · the crane — build loop
[x]builder vm: isolated, claude code aboard, hooks wiredKARASS-106
[x]dispatcher constitution: pickup contract, one block at a timeKARASS-107
[x]◆ first autonomous block: one ticket end-to-end to prodKARASS-108
◆ milestone — the moment it starts building itself
[ ]decision → outcome → policy: choices become experienceKARASS-109
[ ]safety rails: budgets, watchdog, abort switchKARASS-110
phase 3 · senses████████████░░░░░░░░░░░░2/4

the organism learns to feel its own defects — and a verifier, never the builder, declares a block placed.

epic D · senses — signals & verification
[ ]monitor watches karass itselfKARASS-111
[ ]checkmyapp walks karass.dev and files what it findsKARASS-112
[x]post-deploy verify + auto-revertKARASS-113
[x]owner channel: digest out, directives inKARASS-114
phase 4 · construction site████████████████████████4/4

this page stops being a snapshot and becomes the live feed of the build.

epic E · construction site — this page, alive
[x]live organism feed on this pageKARASS-115
[x]work queue + attempt timelinesKARASS-116
[x]trust & budget controls: pause, caps, approvalsKARASS-117
[x]construction site becomes the default workspace viewKARASS-118
phase ∞ · economics & beyond░░░░░░░░░░░░░░░░░░░░░░░░0/5

continuous: the organism must be cheap to feed, and ready for its first sibling.

epic F · economics & infra
[ ]infra doc: llm tiering under real constraintsKARASS-119
[ ]legacy infra: repurpose or sleepKARASS-120
[ ]research: managed runtimes, hosted mcp, second-repo isolationKARASS-121
[ ]customer #2: checkmyapp.dev enters the construction siteKARASS-122
[ ]housekeeping: retire the pre-freeze backlogKARASS-123

[x] placed · [~] growing · [ ] spore · ◆ milestone — a block counts as placed only when the verifier says so, never the builder.

## anatomy of the organism


   senses                   the crane                 verifiers
   sentry . checkmyapp      claude code on a vm       ci . monitor . checkmyapp
   ci . the owner           one block at a time       done is granted, not claimed
        |                         |                          |
        v                         v                          v
 +------------+   claim   +---------------+  pr/merge  +--------------+
 |   queue    | --------> |   builder vm  | ---------> |   verifier   |
 |  (linear)  |           | (claude code) |   deploy   |  grants done |
 +------------+           +---------------+            +------+-------+
        ^                                                     |
        +----------- regressions become new blocks <----------+

 ~~~~~~~~~~~~ everything writes to the mycelium (event log) ~~~~~~~~~~~~
myceliumappend-only event log in postgres. every actor writes, any agent reads. memory, observability, and the soil any emergent structure grows from.
sensesmonitor polls errors of karass itself; checkmyapp walks the ui like a stranger and reports what breaks; ci reports red; the owner speaks through telegram.
attentionsignals become tickets in one queue. the queue is the only source of work — no side quests.
the cranea dispatcher on an isolated vm. picks one block at a time, opens a workspace, runs a claude code session, raises a pr. strictly serial — patience is cheaper than chaos.
verifiersci gates the pr; after deploy, monitor watches for the defect returning; checkmyapp re-walks affected journeys. only a verifier moves a block to done — the builder never grades its own work.
memoryevery ambiguous choice is a named decision with a typed outcome. repeated pain graduates into policy that biases — never silently replaces — future choices.
steeringthe owner sets direction and holds the abort switch. the first blocks merge with owner approval; autonomy is earned on the trust ladder, not assumed.
symbiosis · karass ↔ checkmyapp

two fruiting bodies of one mycelium. checkmyapp gives karass senses — it walks karass.dev daily and turns regressions into build tickets. karass gives checkmyapp hands — the same crane will work its backlog as customer #2. each builds the other.

two media, deliberately: the mycelium is for remembering and noticing — actions travel through typed channels (the queue, pull requests, webhooks). commands are never fished out of a log, and nothing that happened is ever lost.

## watch it grow

karass is invite-only while it raises itself. leave your address and tell us what you would let an organism like this build for you — it shapes which tentacles grow next.

$