{
  "object": "list",
  "locale": "en",
  "count": 3,
  "data": [
    {
      "object": "venture",
      "slug": "metro-logix",
      "title": "MetroLogix",
      "category": "Logistics System",
      "status": "Concept Phase",
      "tagline": "First-attempt delivery, even when no one is home.",
      "description": "Connecting carrier authentication with condominium access to structurally reduce re-delivery in dense cities.",
      "longDescription": "MetroLogix's vision is to eliminate redelivery in urban logistics by ensuring that every package reaches the correct destination on the first attempt. By connecting carrier-issued driver authentication, encrypted package tokens, and building access policies, we transform last-mile delivery from a trial-and-error process into a precise, auditable system. MetroLogix does not need to store driver biometric data; it acts as the trust layer between carriers, buildings, and access-control systems.",
      "locale": "en",
      "availableLocales": [
        "en",
        "ja"
      ],
      "url": "https://www.meldotia.com/projects/metro-logix",
      "markdownUrl": "https://www.meldotia.com/projects/metro-logix.md",
      "content": "# Business Plan\n\n**MetroLogix**\nImplementing a Zero Re-delivery Society: Next-Generation Logistics Security & Orchestration\n\n---\n\n## 1. Executive Summary\n\nMetroLogix is a B2B/B2G solution designed to **structurally reduce the environmental, time, and human costs associated with re-delivery**. We provide a **\"Carrier Authentication Result × Building-Integrated Access Control × Encrypted QR Logistics Standard\"** system.\n\nOur project aims to achieve:\n*   **Drastic reduction in re-delivery rates** (Projected ▲30〜50%)\n*   **Quantitative improvement in delivery efficiency** (+15〜25% deliveries per driver)\n*   **Deterrence of unauthorized entry, misdelivery, and spoofing**\n*   **Direct contribution to CO₂ emission reduction** in urban areas\n\n---\n\n## 2. Problem Statement\n\n### 2.1 The Structural Issue of Re-delivery\n*   In Japan, **approximately 10〜15% of deliveries result in re-delivery**.\n*   Major causes include:\n    *   Inability to access auto-lock buildings\n    *   Misidentification of buildings or floors\n    *   Visiting when recipients are absent\n*   Consequences:\n    *   Increased labor burden on drivers\n    *   Increased CO₂ emissions and fuel costs\n    *   Chronically rising logistics costs\n\n### 2.2 Limitations of Current Solutions\n*   **Drop-off (Okihai)**: Issues with theft and liability attribution.\n*   **Delivery Lockers**: Installation costs and capacity constraints.\n*   **Scheduled Re-delivery**: Low utilization rates and reduced driver efficiency.\n\n**→ The core problem is the fragmentation of \"People,\" \"Buildings,\" and \"Logistics Data.\"**\n\n---\n\n## 3. Solution Overview\n\nMetroLogix resolves these issues through a **trinity structure**:\n\n### 3.1 Courier Identity Layer (Carrier-Issued Authentication)\n*   The carrier remains the identity provider.\n*   During delivery operations:\n    *   The carrier system or driver device verifies the worker.\n    *   MetroLogix receives only a signed authentication result, not biometric data.\n    *   Only authenticated personnel are granted delivery access rights.\n*   Prevents spoofing and unauthorized entry while avoiding an external biometric database.\n\n### 3.2 Logistics Data Layer (Encrypted QR Standard)\nIn addition to existing address/name slips, we add a **MetroLogix Standard QR Code**.\n\nThe QR Code contains:\n*   Encrypted **Building ID**\n*   Precise **Floor Number**\n*   Delivery **Permission Time Window**\n*   *Personal names and room numbers are **not directly included**.*\n\n→ Decrypted and verified only at the moment of scanning.\n\n### 3.3 Physical Access Layer (Building & Elevator Integration)\nWhen a driver scans the QR code:\n*   **If the building matches**:\n    *   Auto-lock unlocks temporarily.\n    *   Elevator allows selection of **only the delivery floor**.\n*   **If the building does not match**:\n    *   Access is completely denied.\n\n→ **Physically blocks misdeliveries, unauthorized entry, and wasted movement.**\n\n---\n\n## 4. Technical Architecture Overview\n\n### 4.1 Security Design (Critical)\n*   **Identity proof**:\n    *   Primary authentication stays with the carrier or local device.\n    *   MetroLogix receives only signed authentication results.\n    *   MetroLogix does not store driver face, fingerprint, or iris data.\n*   **QR Code**:\n    *   Token with expiration.\n    *   One-time use or time-limited.\n*   **Building Integration**:\n    *   API integration (BEMS / Smart Lock / Elevator Control).\n\n---\n\n## 5. Business Model\n\n### 5.1 Revenue Streams\n1.  **Building Setup Fees and Monthly SaaS**\n    *   Paid by building managers or developers.\n2.  **Public-Private Pilot Funding**\n    *   Tokyo/MLIT-aligned logistics improvement pilots and subsidy-backed deployments.\n3.  **Carrier API Fees**\n    *   Introduced after building coverage creates enough value for carriers.\n4.  **Certified Integration Revenue**\n    *   Smart lock, intercom, elevator, and access-control vendor partnerships.\n\n---\n\n## 6. Target Market\n\n### 6.1 Initial Targets\n*   Major Metropolitan Areas (Tokyo, Osaka)\n*   Large-scale Condominiums & Redevelopment Districts\n*   Major Logistics & E-commerce Operators\n\n### 6.2 Market Scale (Estimated)\n*   Japan's Delivery Market: ~2 Trillion JPY scale\n*   Urban Re-delivery Related Costs: Hundreds of Billions of JPY\n\n---\n\n## 7. Implementation Roadmap\n\n| Phase | Content |\n| :--- | :--- |\n| **Phase 1** | **Private PoC** (One carrier × one building manager × several properties) |\n| **Phase 2** | **Public-Private Pilot** connected to Tokyo/MLIT logistics policy |\n| **Phase 3** | **Joint Rollout** with major carriers, developers, authentication IT, and access-control vendors |\n| **Phase 4** | **Subsidies, Certification, and New-Building Standards** |\n\n---\n\n## 8. Competitive Advantage (Moat)\n\n*   **Simultaneous Physical × Digital Control** (Difficult to replicate)\n*   **Scalability as a Standard** (QR/API)\n*   Strong affinity with **ESG & Decarbonization** contexts\n*   Positioning that crosses Logistics, Real Estate, and Administration\n\n---\n\n## 9. Risks and Mitigation\n\n### 9.1 Privacy & Biometric Data Risks\n*   → MetroLogix does not store biometric data.\n*   → Identity proof stays with the carrier or device; only signed authentication results are exchanged.\n*   → Designed around data minimization and APPI-aligned access logs.\n\n### 9.2 Building Implementation Hurdles\n*   → API integration with existing smart locks.\n*   → Prioritize introduction in new construction and redevelopment projects.\n\n### 9.3 Driver Acceptance\n*   → Design incentives linked to reduced working hours and performance evaluation.\n\n---\n\n## 10. Vision\n\nMetroLogix is not just about delivery efficiency.\n\nIt is an infrastructure that **\"reclaims the time, energy, and humanity lost behind the scenes of the city,\"** evolving logistics into the next generation of social foundations."
    },
    {
      "object": "venture",
      "slug": "third-choice",
      "title": "ThirdChoice",
      "category": "Property Model",
      "status": "Concept Phase",
      "tagline": "Turn housing uncertainty into option value.",
      "description": "Revolutionizing home access with a flexible rent-to-own model that adapts to modern mobility and financial lifestyles.",
      "longDescription": "ThirdChoice challenges the premise that 'living equals consumption' by transforming it into an act of accumulating options. We are building a housing infrastructure that converts life's uncertainties not into constraints, but into option value—dismantling the binary choice between renting and owning.",
      "locale": "en",
      "availableLocales": [
        "en",
        "ja"
      ],
      "url": "https://www.meldotia.com/projects/third-choice",
      "markdownUrl": "https://www.meldotia.com/projects/third-choice.md",
      "content": null
    },
    {
      "object": "venture",
      "slug": "traffic-os",
      "title": "TrafficOS",
      "category": "Urban System",
      "status": "Concept Phase",
      "tagline": "Orchestrate the city as one organism.",
      "description": "A hierarchical distributed control system that redefines urban traffic as a single, controllable 'City OS' to minimize congestion and accidents.",
      "longDescription": "TrafficOS goes beyond autonomous driving for individual vehicles. It treats the entire city's traffic as a single control object. By integrating Micro (vehicle-to-vehicle), Meso (route optimization), and Macro (city-wide flow) layers, TrafficOS resolves the conflict between individual and collective rationality, aiming for a zero-congestion, zero-accident urban future.",
      "locale": "en",
      "availableLocales": [
        "en",
        "ja"
      ],
      "url": "https://www.meldotia.com/projects/traffic-os",
      "markdownUrl": "https://www.meldotia.com/projects/traffic-os.md",
      "content": null
    }
  ]
}