GEMS / TATEKAN PM Portal

Last updated: 2026-03-04 JST

This page is the PM-facing one-page brief for the current state of TATEKAN, Toriteki, and dMemo.

Quick Map

Role: the parent concept containing TATEKAN Core, Toriteki, and dMemo
Purpose: unify the GLOVIA Sales replacement core and surrounding services under one operating model
Main datastore: platform-wide mix of Cloud SQL, BigQuery, Datastore mode, and legacy Oracle extraction inputs
Current phase: naming clarification, boundary cleanup, and restart preparation

Role: the direct replacement body for GLOVIA Sales
Main datastore: Cloud SQL + BigQuery + legacy Oracle extraction inputs
Current phase: restart preparation and procedure cleanup
Next major task: rebuild Oracle extraction procedures, WebUI, accounting linkage handling, and QA stack before active restart

Role: operational business application for order / approval / compliance workflows
Main datastore: Datastore mode
Current phase: active application / governance / AI-readiness improvement
Next major task: continue safe operational improvement without destabilizing current tenant use

Role: daily report / overtime / analysis application
Main datastore: BigQuery
Current phase: stable service-side cleanup and future independence preparation
Next major task: remove hard-coded dependency patterns and keep architecture simple

TATEKAN Platform: parent concept for architecture, operations, and future external offerings
TATEKAN Core: direct replacement body for GLOVIA Sales, including the business data foundation moved from Oracle toward Cloud SQL and BigQuery
Toriteki: quotation request, quotation creation, and order workflow module, designed so it can also be offered independently
dMemo: daily report, overtime, and analysis module, expected to preserve standalone operability

godosangyo.com remains the current tenant operation
tatekan.app is the long-term independent platform domain
gems-project remains the implementation repository
tatekan-ops is the PM portal + handover knowledge repository
Current work is a preparation phase: clarify boundaries, reduce confusion, and rebuild safe procedure ownership before larger implementation resumes
Naming rule: TATEKAN means the platform, while the direct GLOVIA Sales replacement body is TATEKAN Core

Oracle procedure baseline has been separated into parent runbooks
Weekly / backfill / Windows delivery responsibilities are separated
.work is non-canonical workbench, not source of truth
Live DB touching work requires script QA, execution checklist, verification review, and QA-of-QA
No connection test or live operation was performed during this documentation phase

Deep documents are kept in the private GitHub repository so they remain canonical and reviewable.

Bootstrap tatekan-ops
Move first-batch PM / continuity documents
Build the private PM portal minimum page
Keep active runbooks and active policies in gems-project
Resume TATEKAN Core active development only after procedure ownership and QA stack are ready

product:tatekan-platform: platform-wide themes, shared governance, shared operating model
product:tatekan-core: direct GLOVIA Sales replacement body, Oracle / Cloud SQL / BigQuery / WebUI core work
product:toriteki: Toriteki-specific feature and operation work
product:dmemo: dMemo-specific feature and operation work
product:other: supporting work that does not fit the above

This label map keeps TATEKAN from collapsing back into an ambiguous single application name.

Role	Location
Implementation repo	`zipdev0423/gems-project`
PM / handover repo	`zipdev0423/tatekan-ops`
PM portal private URL	`pm.tatekan.app` or equivalent Cloudflare private URL
Live runbook authority	`gems-project/docs/runbooks/`
PM / handover canonical docs	`tatekan-ops`