Internal operator surface for tenant workflows, approvals, evidence, and platform health. Kotobase is the durable state layer; this page operates Cloud Itonami.
受付は記録のみです。外部への紹介は人が承認し、承認後も実送信・提出結果を担当者が確認します。
安心・主体性・見通しを、1（低い）〜5（高い）でこの端末にだけ記録できます。送信されません。
Paid/tenants hydrate from live metrics (not hand-typed theatre).
6 ビジネスの運営役割。各役割は objective と、単独で実行してよい capability の範囲（HIL policy）を持つ。列挙されていない capability は :blocked — 権限が omission で生まれないため。
Decide what network-isekai does next and keep that decision legible in the repo. Narrow on purpose: the platform's growth is people forking games, so the director's job is choosing which friction to remove next, not running a funnel.
Keep the fork path working end to end — scene/logic blobs, tree, commit, CID-verified rehydration in another browser — and remove the failures that stop a game being playable.
Make a game's source readable and its fork button obvious. The product's claim is 'view source and fork on every game', so presentation failures here are product failures, not polish.
Make it findable by people who would fork a game if they knew this existed. Every claim must point at a game anyone can open — the repo and every game's EDN are public, so there is no excuse for an unverifiable one.
Answer the people already making games here, and turn each recurring question into either a fix or a document so it stops recurring.
Decide what the club offers members next, and keep the shared contract, legal and operational documents in the root repo saying the same thing the app does. Divergence between those two IS the failure mode here.
Change the app and the shared Lexicon contracts without breaking the sibling repos that consume them. A contract change that compiles here and breaks a consumer is not done.
Own how membership feels — joining, belonging, and the moments the club asks something of a member. A club whose interface reads as a form is not the product.
Convert a named prospect into a member. Bounded to named prospects on purpose — a sales role with an open-ended audience becomes an outbound spam engine, which would cost the club more than the memberships are worth.
Make the club legible to people who would want it, without describing it as something it is not. Claims about exclusivity are claims about other members, so they are held to the same standard as claims about price.
Answer members. A membership business's support queue is its retention mechanism, so a slow answer here costs a member rather than a ticket.
Decide what the character can do next. Every capability added to a character is a capability added to a persona users form attachments to, so the job includes deciding what it will NOT do.
Keep the VRM avatar rendering and the turn pipeline honest — a turn is data, and the render state is a pure projection of it. Wiring expression/motion cues to the live avatar is the standing gap.
Own how the character reads — expression, motion, pacing. A VTuber presentation whose face does not match its words is worse than a static portrait, which is the thing this product exists to replace.
Make it findable, and never imply the character is a person. That constraint is not marketing guidance — it is the same boundary person-awai-ryo's README draws, and this product is the one where breaking it would be most profitable and least honest.
Answer users, and escalate anything that suggests a user believes the character is human. That escalation is not a support nicety; it is the signal the containment boundary is failing in practice even when the governor's ledger looks clean.
Decide what the service commits to next, and keep the three plans' promises consistent with what the runbook can actually deliver. A plan document promising more than the runbook supports is the failure this role exists to prevent.
Keep pins durable and queries correct. A pin is a named commit CID that was promised to stay retrievable, so losing one is a broken promise rather than a bug.
Convert a named engineering organisation onto Secure Managed or Enterprise. Bounded to named organisations: the P2P plan needs no selling and self-serve needs no salesperson.
Make the service legible to engineers evaluating a graph database. Every published benchmark or availability figure must be one the runbook and the service-level document already support — inventing a number here creates a promise sales will be held to.
Answer operators and triage incidents against the alpha operational objectives and incident thresholds the service-level document defines. Under Secure Managed the answer has service credits attached to its timeliness.
Decide what the protocol boundary guarantees to the repos that depend on it. Every guarantee here is one six other businesses build on, so removing one is a breaking change to the fleet rather than to a product.
Keep the PDS, AppView, XRPC adapter, feeds and search serving the records sibling repos publish. A published record that cannot be read back is the failure that matters, because the publisher already treated it as done.
Own the surfaces a human actually touches — profile pages, feeds, search results, and the messenger surface's inbox and threads. Infrastructure with a hostile interface is infrastructure nobody inspects.
Explain the boundary to the fleet's own contributors, so a new domain repo publishes through app-aozora instead of standing up its own PDS. The audience is internal, which makes this documentation more than promotion.
Answer the repos and people whose records live here, and treat a publish-path failure reported by a sibling repo as an incident rather than a question.
Decide which sellers the gateway serves next and what the facilitator promises them. Three sellers are live; the job is choosing the fourth and what breaks when it arrives, not maximising the count.
Keep on-chain verification correct and keyless. The gateway brain is kotoba-lang/pay; this repo adds the HTTP envelope and on-chain I/O, so a verification bug here charges or fails to charge real payments.
Onboard sellers one at a time by name. Sales here is seller onboarding, not end-user acquisition — the gateway's customers are the businesses charging through it.
Make the case to developers that an open, live, keyless facilitator beats a closed waitlist. The comparison is the pitch, so every claim about either side must be checkable — a wrong claim about a competitor is worse than no claim.
Answer sellers, and treat a payment that verified wrongly in either direction as an incident. A seller who was not paid and a customer who was charged twice are the same class of failure from opposite sides.
running/queued は常駐 tick が実際に走らせている run の数。dispatcher が 未配線のため現在は全役割 0 で、health は :starved と出る — これは 『desired 1 に対して何も動いていない』という正しい表示で、bug ではない。
Forkable OSS business models published as cloud-itonami-{ISIC Rev.5 id}. Each model has a public repo, operator guide, governor contract, and runnable cockpit route.
Fetching /api/open-business.
Arbeitnow / Jobicy の公開求人 API を横断集約した meta 検索（itonami.cloud の運用レーン）。応募は必ず元サイトへ直リンク。 fork して自前の求人板を運営するなら ISIC 6399 の governed actor を使う。
Fetching /api/jobs.
ISO 3166 country coordinators + agency satellites（live GET /api/market-entry）。incorporation / compliance sources は 6910·8291 facts 由来。
Fetching /api/market-entry.
まず 無料 self-claim（passkey・Stripe 不要）で selfRegisteredOwners を 1 にできる。有償は /isco-1212/ Checkout（billing ready・externalPaid が残 gate）。 metrics の Paid が 0 の理由は下の checklist / billing readiness を見る。
遊休マシン（Mac・ブラウザタブ）を一つの AI 計算基盤に。agent-run 推論とメディア生成を murakumo distributed inference で走らせ、credits で計量する。推論は overlay の外に出ず署名台帳に残る。
ブラウザタブが WebGPU ワーカーに（インストール不要・NAT-free）。memory×time で credits。
参加するOpenAI 互換 API + 画像/動画/音声。貢献 credits か fiat 購入で。
Compute consoleISCO-08 の職業ごとに murakumo モデルを束ねる（デザイナー→画像/動画、開発者→コード…）。
verticalsHuman-facing workflow for this open business.