monkos.net · applied field

MonkOS in Reality.

One framework. Different scales.

MonkOS becomes visible when it enters real constraints: a body, a machine, a team, a decision that cannot remain abstract. These projects do not form one product. They express the same open framework through different material.

Observe→Detect→Interpret→Own→Act→Learn→Update

Active projects

One field. Different embodiments.

Each project keeps its own identity, scale, authorship, and source of truth. What connects them is a common discipline: signal through noise, early detection, explicit ownership, continuous feedback, local autonomy within wider coherence, and systems designed around human capacity.

Monkdroid · DC project mark

01 / Physical fieldDevelopment

Monkdroid

Repairable. Overrideable. Built for the field.

Monkdroid explores humanophilic, local-first, repairable robotics for assistance and field work. The purpose is not autonomy for its own sake. It is practical autonomy under human command: technology able to sense and act in the physical world while remaining understandable, bounded, interruptible, and repairable.

Nested development stream

Controllers

Controllers are Dragan Cvetanović’s coding and control-logic development within the broader Monkdroid project—the layer where perception, interpretation, decisions, and feedback begin to become controlled action.

Explore Monkdroid ↗Development notes ↗

02 / Organizational fieldImplementation in progress

M&H-OS

Integration over invention.

M&H-OS is an operating framework for complex engineering work. It connects structure, decisions, failure prevention, ownership, people development, and continuous improvement. Proven industrial mechanisms give the system operating strength; MonkOS and Humanophilic Technology define what the system must protect: attention, capacity, coherence, provenance, and meaningful human agency.

The framework is being introduced and developed within the Motor & Hydraulics engineering environment at Grundfos. In an organization of this scale, meaningful change moves incrementally. Despite the effort involved, the initial reception has been strong, and the work continues through real discussion, use, and integration. Its final reach is not claimed in advance.

A large ship turns slowly. The change of course matters more than speed.

M&H-OS project mark by Miki

Truthful status

Status is part of provenance.

We publish where the work actually stands. A development path is not disguised as a finished product. An implementation in progress is not inflated into organization-wide adoption.

Development

Real work. Open outcome.

The project is being designed, coded, tested, or assembled. Its direction and working material are real; a finished product is not implied.

Implementation in progress

Inside real conditions.

The framework has entered an operating environment and is moving through use, discussion, adaptation, and integration. Final outcomes are not claimed in advance.

Living record

Theory stays connected to evidence.

This page holds the stable map. Project domains hold their deeper architecture. Bikasha preserves the dated trail: field notes, decisions, iterations, observations, and named authorship from the people doing the work.

MonkdroidProject home ↗Monkdroid field logBikasha ↗MonkOS transmissionBikasha ↗

One framework · different scales