hnyOS / operates
Controlled work keeps its memory.
Events, outputs, tasks, bounded tools, contained runs, focused context, and checked changes.
In developmentRelease 01Bangalore
The future
leaves evidence.
Signals from two systems becoming one machine. Named milestones stay here; raw updates join them when the public feed is available.
00 / Active programs
One company. Two systems.
Operating + observingKiroshi / observes
Visual claims keep their evidence.
Current proof: a narrow synthetic signal experiment returning satisfied, violated, or unknown.
Research proof01 / Recorded signals
The proof is the work.
Loading live records
Kiroshi / synthetic proof
It learned the pulse. Not the world.
Recorded
24 of 24 held-out synthetic verdicts were correct. The target region was supplied; real-camera perception is not built yet.
hnyOS / change recordChanges can keep their reason.
Current
A checked text change now preserves what changed, how it changed, and why.
hnyOS / contextThe right project details arrive with the task.
Saved
A focused read-only project view can be prepared without changing the source of truth.
hnyOS / run boundaryWork runs in a contained space.
Saved
Network access is off, time is bounded, output is capped, and only a tiny command set can run.
hnyOS / controlRisk now gets an explicit decision.
Saved
Each action is allowed, denied, or held for a person. Interactive resume is still ahead.
hnyOS / foundationActions, outputs, tools, and ordered work gained a durable home.
Origin
The local record and the first execution boundaries are in place.
Records are secondary. The machine is the story.
Return to the chamber â