GEMS / TATEKAN PM Portal

Quick Map

• 1. System Overview
• 2. TATEKANOS Structure
• 3. Current Position
• 4. Restart Readiness
• 5. Read More
• 6. Current Decision Priorities
• 7. Issue Label Policy
• 8. Repo / URL / Canonical Map

1. System Overview

The PM portal now mirrors the system-by-system entry structure. The top page stays focused on the map, while each app has its own page for role and boundary context.

2. TATEKANOS Structure

• TATEKANOS: the parent concept for architecture, operations, future offerings, and AI-native operating workflows.
• TATEKAN Core: the direct replacement body for GLOVIA Sales and downstream accounting-related logic.
• Toriteki: the operational order, approval, compliance, and payment-side workflow module.
• dMemo: the daily reporting and analysis module that keeps standalone operability.
• TATEKAN Mitsumori: the quotation-focused additional app positioned as the Fredy successor.
• TATEKAN Control: the control plane that governs tenant composition, source-of-truth policy, numbering policy, and drift/conflict visibility.
• TATEKANMonitor: the operations monitor for app health, security signals, runtime drift, and incident response support across TATEKANOS apps.
• Voxia: the AI voice response PoC for phone answering, transfer, voicemail, and WebRTC/Opus research.

3. Current Position

• godosangyo.com remains the current tenant operation.
• tatekan.app remains the long-term independent platform domain.
• pm.tatekan.app is the PM portal custom domain served from Cloudflare Pages.
• gems-project remains the implementation repository.
• tatekan-ops is the PM portal and handover knowledge repository.
• Naming rule: TATEKANOS is the parent concept, while the direct GLOVIA Sales replacement body is TATEKAN Core.

4. Restart Readiness

• Oracle procedure baselines have been separated into parent runbooks.
• Weekly, backfill, and Windows delivery responsibilities are separated.
• .work remains non-canonical workbench space, not source of truth.
• Live DB-touching work still requires script QA, execution checklist, verification review, and QA-of-QA.
• No live DB connection test was performed as part of this portal update.

5. Read More

• Tkysys Migration Plan
• TATEKAN Core overview
• Toriteki overview
• dMemo overview
• TATEKAN Mitsumori overview
• TATEKAN Control overview
• TATEKANMonitor overview
• TATEKANBridge overview
• Voxia overview
• TATEKAN Industry OS Vision
• TATEKAN Mitsumori PM brief
• AI Chat Reference Architecture
• AI Agent Best Practices Integration
• architecture/domain_entity_service_mapping.md
• operations/tkysys_migration_plan.md
• operations/tatekan_mitsumori_brief.md
• operations/tatekan_control_brief.md
• operations/tatekan_industry_os_vision_brief.md
• operations/tatekan_restart_preparation_memo.md

6. Current Decision Priorities

1. Keep tatekan-ops as the canonical PM portal source.
2. Keep the private PM portal current with system overview and decision-support documents.
3. Use TATEKAN Control as the tenant-composition and governance layer for future multi-app tenants.
4. Resume TATEKAN Core only after procedure ownership and QA stack are ready.
5. Continue separating Mitsumori, Toriteki, and TATEKAN Core responsibilities clearly.

7. Issue Label Policy

• product:tatekan-platform: platform-wide themes, shared governance, and shared operating model.
• product:tatekan-core: direct GLOVIA Sales replacement body and core ERP work.
• product:toriteki: Toriteki-specific features and operations.
• product:dmemo: dMemo-specific features and operations.
• product:other: supporting work that does not fit the above.

8. Repo / URL / Canonical Map