NvjmiOS

active

AI-native personal Life OS

v0.1 — Foundation

Updated 2026-05-13

Active Modules

of 10 total

Open Tasks

—

link tasks module

Key Decisions

logged decisions

Build / Friction

6 build log entries

Modules

Finance

Accounts, transactions, receipts

active

Learnings

Books, courses, notes

planned

Tasks

Task management & focus

active

Projects

Living project dossiers

active

Wellness

Sleep, supplements, weight

active

Boop

Companion / presence layer

idea

Core API

Fastify backend on Render

active

KIB Scope

Scoped views for key domains

active

Design System

Tokens, components, icons

wip

Portfolio / Publishing

Case studies, public presence

planned

Key Decisions

/projects/nvjmios is locked as the NvjmiOS self-tracker route

Architecture2026-05-13

NvjmiOS Projects should act as living project dossiers, not flat project rows

Design2026-05-13

Decision cards should be pickable and become agent-readable rules

Agent2026-05-13

Fuel paid by dad via Setel/Najeli Family Wallet tracked as External Benefit / Third-party Paid Expense

Finance2026-05-01

KIB tasks are scoped views of the same source-of-truth task records, not duplicate tasks

Architecture2026-05-01

Build Log should include failures, time wasters, roadblocks, and lessons learned

Design2026-05-13

Frontend-first project cockpit before backend persistence — getting a useful self-tracking page live quickly was more valuable than delaying for perfect schema design

Architecture2026-05-13

Build Log

2026-05-13

NvjmiOS Project Cockpit went live at /projects/nvjmios. Created the first self-tracking project page for NvjmiOS — now the home base for modules, decisions, build logs, failures, references, agent rules, design system notes, architecture notes, and portfolio direction. Built with ChatGPT (planning), Claude Code (implementation), GitHub PR (review/merge), Vercel (deploy). Lesson: frontend-first was the right move — avoided backend overbuild and got a useful cockpit live quickly. Next: design backend persistence for project dossiers, decisions, build logs, friction logs, and agent rules.

2026-05-13

/projects/nvjmios chosen as NvjmiOS command center. Added concept for key decisions, failures, references, design system, and app icons.

2026-05-13

/projects section created — project dossier detail pages now supported.

2026-05-12

Tasks page live. Needs stronger project linkage for NvjmiOS context.

2026-05-10

Finance: receipts and accounts became real first — foundation module solid.

2026-04-28

NvjmiOS v0.1 foundation started. Shell, layout, core modules defined.

Failure / Friction Log

Type	Issue	Impact	Note
failure	Scattered decisions across many chats	high	Key decisions lost when closing ChatGPT/Claude sessions
failure	Ideas not linked to modules or projects	high	Loose ideas in inbox with no project/module anchor
blocker	Backend schema may not support full project dossiers	med	Need to design project metadata schema
time-waster	Rebuilding context from scratch each chat session	high	No persistent memory meant re-explaining NvjmiOS constantly
blocker	Tasks too granular without project linkage	med	Tasks alone don't capture the narrative/evolution of NvjmiOS
failure	Finance can get messy without meta-structure	med	Categories and tags needed before transaction volume grows

References

Software 3.0

LLMs as a new programming layer above Software 1.0 and 2.0

Claude Code workflow

Agentic coding with persistent context and memory

CLAUDE.md / agent memory pattern

Persistent agent instructions — agent reads before acting

Karpathy-style LLM interface ideas

LLM-generated HTML and adaptive interfaces

NvjmiOS as Software 1.0 source of truth + Software 3.0 agent layer

The core thesis of the system

LLM-generated HTML / interface options

Future direction for adaptive UI generation

Agent Instructions

CLAUDE.md preview — When working on NvjmiOS:

01Treat /projects/nvjmios as the source of truth for the NvjmiOS project.

02Preserve decisions, failures, and build logs.

03Prefer low-friction, ADHD-friendly workflows.

04Do not overbuild dashboards before the source-of-truth structure is clear.

05When adding new NvjmiOS ideas, link them to a module, decision, task, or build log.

06Capture first, clarify later, structure gently.

07Avoid enterprise software cosplay.

Design System

Accent

Type scale

H1BodyMeta

wipFull design system coming

Architecture

Frontend

Next.js · Vercel

Backend

Fastify · Render

Database

PostgreSQL

AI Layer

Claude · Anthropic SDK

Agent Rules

CLAUDE.md · persistent memory

Portfolio Notes

NvjmiOS is a real living system — build it before packaging it.

Case study angle: AI-native Life OS built by one person, end-to-end, with Claude as co-pilot.

Interesting narrative: the struggle to capture scattered ideas is the first problem NvjmiOS solves for itself.

Future: publish modular write-ups per module (Finance, Wellness, etc.) as each reaches v1.

Design language: clean, personal, anti-enterprise — show that productivity tools can feel like personal software.