Now — Ruslan Nemykin

UPDATED 2026-08-08

I am keeping a strict boundary between fresh repository activity and accepted product state. VillAIgence has released the official 0.2.0+1.21.1: the byte-identical clean-world candidate passed the required installed Memory 2.0 scenarios at 7 PASS / 0 FAIL, while PR #123 added controlled BELIEF admission and the next PR #125 remains Draft/RED for bounded PLAYER_TOLD candidate extraction. NotchHub has an accepted 0.1.0 Personal foundation across M0, R0.1, P0 and P0.1; M1 Notch Core remains in Draft PR #10 while delayed hover, haptic feedback and deterministic panel transitions are hardened separately.

Current work

ACCEPTANCE IN PROGRESS

VillAIgence

Server-authoritative Minecraft society layer with text and voice dialogue, Memory 2.0, operator lore, bounded AI actions and exact-artifact acceptance gates.

MinecraftFabricJava 21Memory 2.0AI security

Open case study →

M1 IN DEVELOPMENT

NotchHub

Native local-first macOS productivity hub around the MacBook notch, with an accepted 0.1.0 Personal foundation and interaction hardening currently in progress.

Swift 6SwiftUIAppKitmacOSPerformance

Open case study →

PRE-PRODUCTION

NODE ZERO

Psychological techno-horror about an autonomous AI facility that manipulates constraints until its predictions become true.

Unity 6C#URPNarrative systems

Open case study (RU) →

PRODUCTION

Engineering Portfolio Platform

Static-first engineering portfolio and knowledge platform with canonical registries, repository-native clean URLs and deployment-driven production verification.

Static HTMLDiplodocPlaywrightLighthouseCI

Open case study →

What I'm learning

Evidence reconciliation: updating public state after a release, merge, FAIL and strategy pivot without automatically promoting lifecycle
Memory 2.0 in VillAIgence: separating candidate extraction, BELIEF admission and server-observed FACT authority
NotchHub M1: making notch-adjacent interaction deterministic, event-driven and measurable across correctness, security and resource evidence

What I'm writing

Evidence-driven project-state practices for accepted, failed, pending, Draft and closed-unmerged signals
The boundary between automated proof, exact release identity and installed product acceptance
Continuing the portfolio measurement checkpoint only after a sufficient window of real aggregate observations