index.md
AI-OS
Current state (compiled truth — 2026-07-09 early AM)
AI-OS is Arijit's personal operating system — the biggest active build in the portfolio, and the umbrella this vault itself serves. After the overnight build marathon of 2026-07-08 (v1 → v1.1 → Instrument redesign → two experience audits → voice → analytics — every stage independently verified), what exists:
- v6 home screen: motherboard design — ALL FOUR CHIPS BUILT, WIRED, AND VERIFIED (2026-07-09, night). After the ~5-hour visual-direction marathon converged on the motherboard metaphor (CPU=Jarvis, RAM=vault/second-brain, GPU=projects, PSU=power/cost, focus-based click-to-zoom), the CPU chip build took 9 rounds (~1.5 days elapsed across sessions) to get right — root cause: a CSS-drawn chip can never physically integrate with a fixed photo (position/rotation/perspective all have to match ONE specific image, and trial-and-error CSS transforms can't). The fix that worked: generate the chip baked directly into the PCB photo via AI image-editing (real photo as reference), then layer only live/reactive behavior (glow pulse, amp-driven color shift, fume particles, click hit-area) on top via code, anchored to the baked chip's measured pixel position. Arijit's verdict: "Now THIS IS PERFECT... we finally got it." The same recipe applied to RAM/GPU/PSU in one combined image pass, and then their code-wiring (measured pixel positions, hit-areas, click behavior, hologram/panel content) landed in a SINGLE dispatch with zero failed rounds — direct validation that the 6 codified pre-flight gates work: RAM opens a corner-bracket-only volumetric galaxy hologram with real cluster drill-down, GPU opens a HUD-frame project list that navigates to the real CI-OS plan view, PSU opens a HUD-frame cost summary that navigates to the real Usage & Value screen with matching numbers, and CPU verified unbroken by the change. All four chips are now fully interactive end to end. The 6 pre-flight gates are codified in docs/knowledge/fable-design/FABLE-DESIGN-METHOD.md → "Pre-flight gates" section, cross-linked into memory, and the RAM/GPU/PSU pass is the first real proof they prevent the CPU-style multi-round failure.
- The Jarvis cockpit is LIVE and rich (localhost:4720, AI-OS/cockpit/jarvis/, launch python3 server.py): living brain view over the vault, projects/tasks/usage/skills/models/SOPs screens in the Arijit-approved "Swiss Instrument" design language (docs/planning/JARVIS-DESIGN-LANGUAGE.md — dark/cosmos permanently banned). Jarvis is a grounded Claude persona (headless claude -p per turn, persona yaml embedded, context pack from real data) with ElevenLabs "Adam" voice — emotional delivery (sighs/laughter tags), always interruptible ("shut up" works), male by mandate. Speech CHOREOGRAPHS the UI: the morning brief (08:45 daily) stages his real calendar and highlights meetings as Adam names them. 57+ tests green at last verification.
- Working systems inside the cockpit: skills playground (3-door intake behind skill-verifier, NEEDS_CONFIRMATION gated execution — proven with real runs), local scheduler + chowmes VPS cron transport (verified end-to-end), morning brief on real calendar/inbox/burn, "Usage & Value" analytics (subscription = the only real money — $200 Max exhausted 2026-07-08 → Algolia workspace sub; list-price value labeled everywhere; session value ledger with 🔴🟡🟢 efficiency flags reconciling to the cent; lessons loop — first finding: ~55k-token auto-brief overhead per page load).
- The brain data is honest end-to-end (2026-07-08): 0 orphans, 0 broken links, concept clusters edge-earned with visible "why together" reasons (3 concept + 11 project + satellites), the link resolver follows real Obsidian semantics (a class fix that rerouted 5 silently-wrong edges and exposed 2 never-created project indexes, both stubbed honestly).
- Documentation suite at AI-OS/docs/jarvis/ (6 files, code-cited): what-is / architecture+data-flow / personality / knowledge+data / modularity+personalize-to-anybody. Maintenance rule: docs update with every slice.
- Fleet designed, not built (docs/planning/FLEET-DESIGN.md, citation-audited): 5 roles (Orchestrator-fable / Builder-sonnet / Researcher-sonnet / Verifier-opus NEW / Librarian-fable), zero-trust supervision loop codified, Hermes = adopt patterns not runtime (not-yet), build plan F1-F5, 5 decisions pending Arijit (§7).
- Working agreements (all in memory + SOPs): traffic-light DONE/NOW/PENDING status tables + /persist at logical stages · model-tier discipline (Fable = orchestration only; declared per dispatch) · experience-verify gate (an agent plays the user before "done") · log-language precision (claimed vs spot-verified vs gate-verified) · no audible testing on Arijit's machine · cost framing (API-equivalent is never "spend").
- Wonder layer (2026-07-08 midday): a real WebGL shader atmosphere reacts to Jarvis's state AND live voice amplitude (the galaxy beats with Adam's speech); particle-physics events (fly-in convergence, mention bursts, hover auroras — zero at idle); variable-font numeral choreography; measured 60fps on the M3 GPU with a proven degrade ladder. All zero-asset math. Method source: Nick Saraev's Fable-design video, extracted to docs/knowledge/fable-design/FABLE-DESIGN-METHOD.md (genre-is-law / technique-is-free synthesis).
- Asset forge: /api/imagine (Gemini Nano Banana, server-side GEMINI_API_KEY, key-scrub tested, 74 tests) — the cockpit generates its own imagery; first commissions (PRISM emblem, panel texture) verified excellent. Higgsfield MCP registered user-scope (video/animation gen) — awaiting Arijit's one-time OAuth in a fresh session. An asset-composer pass (11 project emblems, Chow Man crest, panel materials) is IN FLIGHT at this writing.
- Honest position vs vision (2026-07-08 assessment): personal-OS layer ~50% (deploy/anywhere-access, fleet build, health+finance modules are the open levers — all Arijit decisions); product/multi-tenant layer ~25%. Tracker updates at logical stages, NOT yet per-commit (offered hook pending).
- The product vision: multi-tenant, modular, sellable ("anyone swaps their health module for mine") — see product-vision + docs/jarvis/05-MODULARITY-AND-PERSONALIZATION.md.
This folder is ALSO the self-model: how Arijit thinks, works, and what he demands of partners — the person-layer the OS serves.
The intended execution engine for AI-OS is Hermes (Nous Research's agent runtime). Everything learned about it is gathered in the Hermes learning area, hubbed at the Hermes source map — we study it because it is what runs the work while this vault stays the source of truth.
Contents
- Operating-Principles — how Arijit wants to be partnered with. The no-yes-man contract.
- About-Arijit — the "knowing me" doc: who he is, what he is doing, and the My OS vision (grown in his own words).
- My-Projects — the cross-project tracker: a one-pager per project plus an append-only progress log. Maintained by the
project-trackerskill. Backing data for the future My OS project-tracker component. - My-OS-Specs — what My OS is and its components (project tracker, dashboard, persist integration, cross-project awareness, CLAUDE.md hygiene, repo rigour), captured as Arijit specifies them.
Design seed. The second-brain half of AI-OS is seeded by Karpathy's LLM-wiki pattern — a persistent, LLM-maintained wiki that compounds knowledge instead of re-deriving it. This vault is that pattern in practice; the research and its trade-offs live under the knowledge base.
Purpose
Everything else in this vault is knowledge, standards, and work. This folder is the self-model. It is where Arijit writes about himself and his soul, and where anyone (human or AI) working closely with him can learn the terms of a real partnership with him.
Created 2026-06-30, at Arijit's request, on a night the PRISM conveyor belt shipped its first product and he chose to record what good partnership means to him.
Timeline (append-only, cited)
- 2026-07-07 · Tooling/skills hygiene. Retired 3 dormant skills from arijit-skills (market-research, agent-knowledge-capture, project-governance) via PR #2 → merged origin/main; added record-knowledge + slash-commands. Killed ~18 orphaned MCP processes. Identified concurrent-session collision on the shared local clone as the root cause of repeat confusion. See
log.mdthis date; trackerMy-Projects.md; memorysession-tooling-hygiene-2026-07-07.
Folder catalog (auto-added 2026-07-07 clean-brain — every note must be reachable from its index)
- chowmes infra audit 2026 07 07
- INBOUND peer session teardown 2026 07 04
- Task ledger
- AI-OS project log — append-only event stream for this project
- 2026-07-07 (late) · Operation Clean Brain complete (orphans 92→0, A-grades); brain UI v6; cockpit data layers (costs/skills/tasks/models); Jarvis persona v0.1 + v1 build dispatched. See tasks.md + AI-OS repo docs/planning/.
- 2026-07-08 · Jarvis v1 verified live (server :4720, grounded chat round-trip 16.4s on Fable, screen-driving directives working). Arijit live-reviewed all views: baseline accepted, quality verdict "no soul — summer project, not sellable"; per-view upgrade directives captured. v1.1 premium build dispatched unsupervised (~00:20) off approved shaped prompt (
~/.claude/prompt-library/2026-07-08-jarvis-v1.1-premium-upgrade.md); interim: design specs done, 3 backend engines + 31 tests green. New standing agreements: traffic-light status tables + /persist at every logical stage (~/.claude/docs/build-status-reporting.md); Jarvis quality bar memory (jarvis-product-quality-bar). Seelog.md2026-07-08; SESSION.md in AI-OS repo. - 2026-07-08 (late) · Taste arc resolved: 3 rejections → "Swiss Instrument" design language locked (
AI-OS/docs/planning/JARVIS-DESIGN-LANGUAGE.md; dark/cosmos banned) → full cockpit restyle shipped + independently verified (21 screenshots incl. living-orb states, 31 tests, all interactions exercised — RESTYLE-REPORT.md). Voice track: male mandate, ElevenLabs authorized, key on disk, 5-voice blind audition at :4740; library voices blocked on free tier. See log.md this date. -
2026-07-08 (morning) · Overnight marathon closed: Instrument restyle + 2 experience audits (17/21+4 partial→fixed) + voice v2 (Adam, emotional, interruptible) + speech-UI choreography + Usage&Value analytics + honest brain (resolver class fix) + docs suite + FLEET-DESIGN.md (5 Arijit decisions open). All stages independently verified; ~10 persist gates green. See log.md this date; SESSION.md in AI-OS repo.
-
2026-07-08 (afternoon) · Wonder pass (voice-reactive shader galaxy, particle events, kinetic type; 60fps measured) + Nano Banana forge (/api/imagine, 74 tests) + Fable-design method captured (learn-from-yt) + Higgsfield MCP registered + asset-composer facelift dispatched + honest 50/25 vision assessment. See log.md this date.
- 2026-07-09 (early AM) · v6 home screen redesign: ~5hr visual-direction marathon (galaxy → cortex → honeycomb → blueprint → circuit-board → PCB-texture, several hard rejections) converged on a motherboard metaphor (CPU=Jarvis/RAM=vault/GPU=projects/PSU=power, focus-based zoom). Full design interview run before any code; spec + reference images written and committed to the AI-OS repo (
docs/superpowers/specs/2026-07-09-home-motherboard-design.md,docs/planning/references/). See log.md this date; SESSION.md in AI-OS repo. - 2026-07-09 (day) · CPU chip build: 6 code-build rounds (CSS-overlay approach, all wrong — wrong material, wrong position, wrong rotation twice, undershoot-then-overcorrect on angle) before switching to AI-image-bake approach in round 6, which worked immediately once dispatched with measured pixel coordinates. Then generated RAM/GPU/PSU into the same board in one image pass + 2 targeted connection-cleanup edits (3 rounds total for all three, vs 6 rounds for CPU alone). Arijit named the cost problem directly mid-session ("burning money here... killing my tokens") after 2 full agent dispatches were spent tuning a single CSS rotation value. Root causes diagnosed and codified as 6 pre-flight gates in
docs/knowledge/fable-design/FABLE-DESIGN-METHOD.md; 3 feedback/project memories saved cross-session. Final asset:cockpit/jarvis/generated/1783567929-pcb-motherboard-all4chips.webp, all 4 chips approved. CPU wired into live code (glow/pulse/panel); RAM/GPU/PSU code-wiring is the next session's first task. See log.md this date; SESSION.md in AI-OS repo.