Japonics / HEALTH PLATFORM

TAIIKU

A holistic health and fitness platform connecting training, nutrition, recovery, biometrics, education, coaching, and organizations.

System design Security
TAIIKU preview
Client: Japonics Year: 2026

Consent-aware health-data architecture

Where the project started

Taiiku connects training, nutrition, sleep, and recovery into one readiness model, but coach access to a client's health data always requires explicit consent, and the product deliberately avoids medical claims.

Starting point

The fitness market splits training, food, sleep, recovery, coaching, and organizations into separate tools.

Direction taken

Taiiku needs consent and health-data access architecture. Training, nutrition, recovery, health, coaching, and organizations operate as separate domains, while analytics connects them only through controlled projections.

Business / Product

Problems and solutions

Each tile connects a real product tension with the decision that clarified the domain, UX, or operations.

Problem

The fitness market splits training, food, sleep, recovery, coaching, and organizations into separate tools.

Solution

Design a B2C/B2B2C/B2B platform that shows the full context of readiness and progress.

Outcome Full health/fitness domain map
Problem

The scope could easily become a feature list without one product, data, and ownership model.

Solution

Taiiku needs consent and health-data access architecture. Training, nutrition, recovery, health, coaching, and organizations operate as separate domains, while analytics connects them only through controlled projections.

Outcome B2C, B2B2C, and B2B in one domain topology
Problem

The project needed decisions that would stay readable after the first version: for users, the team, and further delivery.

Solution

B2C, B2B2C, and B2B in one domain topology. Consent-aware coach access.

Outcome Consent and permission model for coaching

Roles and competencies

The competencies this build required

Competencies are shown as ownership roles: CTO, Tech Lead, engineering, DevOps, cloud, security, and AI where they were part of the work.

01

Fractional CTO

Connecting the product thesis, domain risk, and priorities so technology supports business decisions instead of becoming a separate workstream.

Open competency
Scope
  • Product category and positioning
  • Scope priorities and risk
  • Decisions ready for founder or CTO review
Applied experience
  • Product thesis translated into technical priorities.
  • Risks framed in a language stakeholders can review.
02

Tech Lead

Shaping responsibility boundaries, domain modeling, and architecture decisions so the project can grow without drifting into an accidental monolith.

Open competency
Scope
  • Bounded contexts and ownership
  • Readable technical decisions
  • Roadmap without implementation chaos
Applied experience
  • Domain boundaries and decisions that remain reviewable after MVP.
  • Ownership model readable for later delivery stages.
03

Software Engineer

Turning the domain into screens, APIs, flows, and maintainable implementation with focus on clarity and post-MVP evolution.

Open competency
Scope
  • Backend and application contracts
  • UX surfaces ready for iteration
  • Code and maintenance model
Applied experience
  • Implementation tied to the real product workflow.
  • Contracts and code prepared for post-launch iteration.
04

DevOps Engineer

Designing delivery, observability, and operations so release, diagnostics, and recovery are part of the product.

Open competency
Scope
  • CI/CD and release readiness
  • Observability and production signals
  • Operations without manual rituals
Applied experience
  • Release, diagnostics, and recovery designed as product capabilities.
  • Production signals ready for maintenance without guessing.
05

Security Engineer

Coach and organization access to a client's health data is consent-gated, and the 'no medical diagnosis' boundary is maintained as a deliberate product-liability control.

Open competency
Scope
  • Consent-gated coach/organization access to health data
  • HealthKit / Health Connect as a controlled data-source boundary
  • No diagnostic claims as a deliberate liability control
Applied experience
  • Privacy, roles, and auditability built into the product model.
  • Security visible in domain decisions, not only around the UI.
06

AI/ML Engineer

Treating AI as a product capability: with context, constraints, versioned signals, and a clear boundary between facts and interpretation.

Open competency
Scope
  • LLM as a controlled capability
  • Signal and projection quality
  • Responsible product constraints
Applied experience
  • AI constrained by context, signals, and product responsibility.
  • Boundary between facts and interpretation preserved in architecture.

Stack by competency

Tech stack

The stack is grouped by competency so it shows both technology and responsibility: software, leadership, DevOps, cloud, security, and AI.

Software Engineer
  • .NET / ASP.NET Core
  • .NET MAUI mobile client
  • Angular web client
  • PostgreSQL
Tech Lead
  • Analytics & projection boundaries
  • Consent domain boundaries
DevOps Engineer
  • OpenTelemetry
  • Cloud Logging
Security Engineer
  • Privacy architecture
  • Consent-aware health data
  • Consent management
  • Liability & scope boundary
AI/ML Engineer
  • Product analytics
  • Profile projections
.NET / ASP.NET Core Angular web client Analytics & projection boundaries OpenTelemetry Privacy architecture Consent management Product analytics .NET 8 HealthKit Analytics projections Angular Non-diagnostic liability boundary .NET MAUI mobile client PostgreSQL Consent domain boundaries Cloud Logging Consent-aware health data Liability & scope boundary Profile projections Mobile APIs Health Connect .NET MAUI Consent-gated coach access .NET / ASP.NET Core Angular web client Analytics & projection boundaries OpenTelemetry Privacy architecture Consent management Product analytics .NET 8 HealthKit Analytics projections Angular Non-diagnostic liability boundary
.NET MAUI mobile client PostgreSQL Consent domain boundaries Cloud Logging Consent-aware health data Liability & scope boundary Profile projections Mobile APIs Health Connect .NET MAUI Consent-gated coach access .NET / ASP.NET Core Angular web client Analytics & projection boundaries OpenTelemetry Privacy architecture Consent management Product analytics .NET 8 HealthKit Analytics projections Angular Non-diagnostic liability boundary .NET MAUI mobile client PostgreSQL Consent domain boundaries Cloud Logging Consent-aware health data Liability & scope boundary Profile projections Mobile APIs Health Connect .NET MAUI Consent-gated coach access