A portable profile

The original and the rubbing

The name Takuhon (拓本) comes from a 2000-year-old craft: pressing paper against a stone inscription to lift a portable rubbing of the original. The stone stays put; the paper carries its imprint anywhere.

Takuhon applies that idea to identity:

• The original is immutable — your career, skills, and story at a given moment, like a stone inscription.
• The reproduction is portable — takuhon.json is the rubbing: the canonical you, copied into a form you can carry into APIs, JSON-LD, and profile pages.
• The reproduction flows freely — a JSON-LD-aware profile is read by humans, AI agents, and search engines alike.
• The reproduction outlasts the platform — when a platform shuts down, your takuhon.json survives.

One canonical file

Everything Takuhon serves is derived from a single canonical document, takuhon.json, that lives on infrastructure you control. There is no database to administer and no CMS to keep alive — the file is the source of truth.

From that one file, Takuhon produces:

• a mobile-first profile page,
• a JSON API (including locale-resolved responses),
• JSON-LD for AI agents and search engines, and
• a full export you can hand to anyone.

Multilingual by design

Human-readable fields are language maps, so the same profile can speak more than one language:

{ "displayName": { "en": "Sam Lee", "ja": "リー・サム" } }

Takuhon resolves the right value per request and emits correct hreflang and lang metadata. See The takuhon.json file.

A platform-independent core

The data model and logic live in @takuhon/core; where your profile runs is a separate choice handled by adapters. Moving from one host to another is a matter of copying one file — the rubbing travels.