# Project Status and Tomoki Action Summary

Status: CEO-facing current-location summary.

Date: 2026-07-04

Save target: Google Drive in future. Current MCC v1.1 stores this as a local docs artifact because Google Drive real OAuth is not connected yet.

## Executive Summary

MCC is now the source of truth for M&T OS governance.

The current portfolio should be treated as:

- MCC: command center and source of truth.
- M&T OS: company-level operating architecture.
- AI Integration: MCC core module candidate, not a separate project.
- Inventory, Field Log, FX, Keiri/Accounting: independent Products managed by MCC.
- AI automated side business: Business Operations Module candidate inside MCC.

Tomoki should not become the operator for each project. Tomoki's work should stay limited to approval, direction, account authorization, and real-world priority choices.

## Current Location and Tomoki Actions

| Area | Current Location | Current Status | Tomoki Should Do Next | Codex / Mia Should Do Next |
| --- | --- | --- | --- | --- |
| Inventory Management Table | Independent Product managed by MCC | Latest usable product root exists as GAS/Sheets inventory system. Older duplicate exists and should not be used as the primary source. | Decide whether this is a near-term business Product and choose the first target/customer scenario. Approve future Google/LINE authentication only when ready. | Keep independent, compare old/new copies before deprecating old, register readiness in MCC Project Module. |
| MCC | Source of truth / command center | MCC v1.1 local architecture foundation is active. Module Registry, Worker Registry, Identity Layer, Storage Provider Registry, AI Provider Registry, Codex Usage fallback, and Portfolio docs exist. | Confirm local operation, provide GitHub repository URL when ready, approve Preview Deploy separately. Do not approve Production yet unless intentionally ready. | Add visible Project/Product Registry UI, keep modules separated, avoid Version4 until approved. |
| AI Automated Side Business | Business Operations Module candidate | Mia Company / AI side-business operations exist as docs and beta-operation workflow. It should feed MCC, not become a second command center. | Choose the next service offer to prioritize and approve only Apply / Delivery / Strategic decisions. Avoid doing operational task work manually. | Convert sales/delivery workflow into MCC Business Operations Module and link to Project/Product Registry. |
| Field Log | Independent Product managed by MCC | LINE + GAS + Google Sheets field-log MVP exists. Earlier PR copy appears superseded. Real LINE/Google auth is still approval-gated. | Decide pilot usage: which site, which form/log flow, and whether to authorize LINE/Google test connection. | Keep product independent, extract reusable LINE/GAS service patterns, register status and blockers in MCC. |
| M&T OS | Company-level architecture | Constitution v2 and Portfolio Architecture docs exist. M&T OS is now organized as company > MCC > modules > products > services > repositories. Version4 is not started. | Approve or adjust the portfolio direction. Decide when Project Registry should become visible in MCC. Do not approve Version4 until scope is explicit. | Maintain governance docs, enforce Project/Product/Module categories, prevent date-folder drift. |
| AI Integration | MCC core module candidate | AI Integration has been inventoried and redesigned as AI Router + Worker Registry + AI Provider Registry + fallback + review flow. Real paid AI execution is not connected. | Approve mock-only AI Router design if this should move next. Do not approve paid provider routing until cost/security gates are visible. | Add provider/worker metadata, then add pure local `routeMccIntent` routing before any real AI API execution. |
| FX Log / FX Automatic | Independent Product / research product | FX Automatic is active research/log infrastructure. YouTube FX research is supporting context. Automatic trading/order execution is explicitly out of scope. | Decide report cadence and what decisions the FX log should support. Confirm sources and whether Drive storage should be primary. | Keep FX independent, connect reports to MCC Result Inbox later, preserve no-auto-trade safety boundary. |

## What Tomoki Should Not Do

- Do not manually manage every project folder.
- Do not approve Production Deploy casually.
- Do not approve Version4 without a written scope.
- Do not enter secrets/tokens into code or docs.
- Do not let AI Integration become a separate command center.
- Do not merge product code into MCC just because it is useful.

## Recommended CEO Priority Order

1. Confirm MCC local operation and GitHub repository URL.
2. Approve Project/Product Registry becoming visible inside MCC.
3. Choose the first revenue/product priority: Inventory, Field Log, Keiri AI, FX, or AI side-business.
4. Approve mock-only AI Router design.
5. Approve one external connection at a time, starting with Google Drive/Sheets only when needed.

## Current Approval Gates

| Gate | Current State |
| --- | --- |
| Production Deploy | Not approved |
| Version4 | Not started |
| GitHub push | Waiting for repository URL / approval |
| Google Drive real OAuth | Not connected |
| LINE real connection | Product-specific approval required |
| OpenAI / paid AI API | Not connected; approval required |
| Cloudflare Preview | Prepared in docs; execution approval required |

## Mia Summary

Right now, Tomoki's job is not to organize files or operate tools.

Tomoki's job is:

1. Confirm direction.
2. Choose business priority.
3. Approve safe connection steps.
4. Judge final outputs.

Mia and Codex should handle the rearrangement, implementation, documentation, tests, and status reporting.