Private / PM Only
Access Protected
GEMS / TATEKAN PM Portal
Last updated: 2026-03-01 JST
This page is the PM-facing one-page brief for the current state of TATEKAN, Toriteki, and dMemo.
1. System Overview
TATEKAN
- Role: GLOVIA replacement platform and accounting / data foundation
- Main datastore: Cloud SQL + BigQuery + legacy Oracle extraction inputs
- Current phase: restart preparation and procedure cleanup
- Next major task: rebuild Oracle extraction procedures and QA stack before active restart
Toriteki
- 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
dMemo
- 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
2. Current Position
godosangyo.com remains the current tenant operationtatekan.app is the long-term independent platform domaingems-project remains the implementation repositorytatekan-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
3. Restart Readiness
- 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
4. Read More
Deep documents are kept in the private GitHub repository so they remain canonical and reviewable.
5. Current Decision Priorities
- 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 active development only after procedure ownership and QA stack are ready
6. Repo / URL / Canonical Map
| 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 |