oliama
Home The Model Sketchbook Studio Notebook Access Visit

742-4 Shinmachi, Osaka 530-0015
Open daily 06:00–20:00
[email protected]

The model · モデル

One engine,
two hands.

oliama is a single creative model maintained in Osaka. It is not a platform and not a marketplace — it is one instrument with two well-practised motions: writing code and drawing lines. Below is exactly what each hand does, and how a request moves through the room.

Hand one · 書く

Kaku, the code hand

Give Kaku a plain sentence — "a queue that retries gently", "this file, but readable" — and it returns code with the shape of a considered answer: named honestly, commented where the comment earns its place, and accompanied by the tests it would want reviewed alongside.

  • DRAFT  New functions, services and scripts from short briefs in twelve languages.
  • REPAIR  Refactoring that respects the original author's intent before improving it.
  • EXPLAIN  Every draft arrives with a short note on the choices made, so review is fast.
kaku · example draft
# brief: "a queue that retries gently"

class GentleQueue:
    def __init__(self, patience=3):
        self.patience = patience
        self.pending = []

    def offer(self, task):
        """Try now; wait kindly if refused."""
        for attempt in range(self.patience):
            if task.attempt():
                return True
            task.rest(attempt)
        self.pending.append(task)
        return False

Draft 1187 · reviewed and accepted, June 2026

Study 0462 · torii, two-colour vector

Hand two · 描く

Egaku, the drawing hand

Egaku draws in vectors, not pixels, so every study stays editable. It was raised on ink practice — enso circles before breakfast — and it shows: the work is spare, the spacing deliberate, and the model would rather leave a corner empty than fill it badly.

  • STUDY  Ink-style line art, delivered as clean layered vector files.
  • FIGURE  Diagrams, maps and architectural figures with measured geometry.
  • SCREEN  Interface compositions from rough briefs, ready for Kaku to build.

How a request moves

Four motions, no theatre

01

Brief

You write a plain sentence about what you need. No forms with forty fields — a sentence, a deadline, a constraint or two.

02

Draft

The engine produces a first pass. Kaku drafts code; Egaku drafts lines. A studio member reads everything before you do.

03

Correct

You mark what is wrong in plain words. Corrections teach the engine your taste, and the second pass is usually the keeper.

04

Keep

You receive the final files with full rights. The studio keeps only the lesson, never your work.

Questions

Asked often, answered plainly

Something more specific? Write to [email protected] during studio hours.

No. Access means a seat on the Osaka node with a daily allowance of requests, plus a human who reads your drafts. There is no app store, no plugin marketplace, no tier of add-ons.

You do, entirely. Code drafts, vector studies, diagrams — full rights transfer on delivery. The studio retains only anonymised lessons about the engine's habits.

Twelve, currently: Python, JavaScript, TypeScript, Go, Rust, Ruby, Java, Kotlin, Swift, C, C++ and SQL. We add a language only when the engine passes a month of internal review in it.

Yes — send three to five examples of your existing visual work and Egaku will study them for a day before drafting. It matches restraint better than flamboyance; we will tell you honestly if your style sits outside its hand.

The node serves a fixed number of seats. Small batches keep response times honest and let us say no — politely — to work the engine would do badly.

See what the hands produce.

Open the Sketchbook Request Access