Japonics / SELF-DEVELOPMENT

SENSEI

A private self-development operating system connecting daily planning, habits, goals, learning, retrospection, mentoring, travel, and relationships.

System design Security AI/ML
SENSEI preview
Client: Japonics Year: 2026

A private self-development operating system

Where the project started

Sensei connects goals, habits, learning, and retrospection through cross-module signals (habit → goal, learning → goal, retrospection → next plan), with privacy as the default mode and a non-punitive approach to broken streaks.

Starting point

Users stitch self-development together from Notion, habit trackers, task managers, journals, and learning apps.

Direction taken

Sensei connects productivity, goals, learning, and retrospection through cross-module signals. The key architecture decision is separating behavioral facts from interpretation and insights, with privacy as the default mode.

Business / Product

Problems and solutions

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

Problem

Users stitch self-development together from Notion, habit trackers, task managers, journals, and learning apps.

Solution

Design an integrated, non-judgmental system where daily data turns into reflection and better next decisions.

Outcome Domain map for a personal development system
Problem

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

Solution

Sensei connects productivity, goals, learning, and retrospection through cross-module signals. The key architecture decision is separating behavioral facts from interpretation and insights, with privacy as the default mode.

Outcome Cross-module signals: habit -> goal -> retrospection
Problem

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

Solution

Cross-module signals: habit -> goal -> retrospection. Learning and book reviews connected to goals.

Outcome Strong positioning against Notion and habit trackers

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

Behavioral data and the private journal are private by default, and the non-punitive habit model is also a data-security decision: the system never profiles a user around 'failures'.

Open competency
Scope
  • Privacy as the default contract for behavioral and journal data
  • No sharing of retrospection or journal entries beyond the account owner
  • Non-punitive data model: gaps are a signal, not a risk flag
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
  • Domain logic engines
  • PostgreSQL
Tech Lead
  • Domain modeling
  • AI-assisted domain model
DevOps Engineer
  • OpenTelemetry
  • Cloud Logging
Security Engineer
  • Privacy architecture
  • Non-punitive data model
  • Owner-only data sharing
AI/ML Engineer
  • AI feedback loops
.NET / ASP.NET Core Angular web client PostgreSQL AI-assisted domain model Cloud Logging Non-punitive data model AI feedback loops Event log Mobile-first UX Angular .NET / ASP.NET Core Angular web client PostgreSQL AI-assisted domain model Cloud Logging Non-punitive data model AI feedback loops Event log Mobile-first UX Angular .NET / ASP.NET Core Angular web client PostgreSQL AI-assisted domain model Cloud Logging Non-punitive data model AI feedback loops Event log Mobile-first UX Angular
.NET MAUI mobile client Domain logic engines Domain modeling OpenTelemetry Privacy architecture Owner-only data sharing .NET 8 AI summaries .NET MAUI Owner-only journal sharing .NET MAUI mobile client Domain logic engines Domain modeling OpenTelemetry Privacy architecture Owner-only data sharing .NET 8 AI summaries .NET MAUI Owner-only journal sharing .NET MAUI mobile client Domain logic engines Domain modeling OpenTelemetry Privacy architecture Owner-only data sharing .NET 8 AI summaries .NET MAUI Owner-only journal sharing