docs: update README with neutral technical framing and TF-Tech NV ownership

Author: despiegk

README.md

@@ -1,21 +1,43 @@
 # Zinit [![Rust](https://github.com/threefoldtech/zinit/actions/workflows/rust.yml/badge.svg)](https://github.com/threefoldtech/zinit/actions/workflows/rust.yml)
 
-Zinit is a lightweight PID 1 replacement inspired by runit, written in Rust using Tokio for async I/O. It provides both a Unix socket interface and an HTTP API for interacting with the process manager.
+Zinit is a lightweight PID 1 replacement inspired by runit, written in Rust using Tokio for async I/O. It manages service startup, supervision, and lifecycle, ensuring configured services remain running and handling dependencies through a simple declarative interface.
 
-### Key Features
+## What this is
 
-- **Service Management**: Ensures configured services are up and running at all times
-- **Dependency Handling**: Supports service dependencies for proper startup ordering
-- **Simple Control Interface**: Provides an intuitive CLI to add, start, stop, and monitor services
-- **Container Support**: Can run in container mode with appropriate signal handling
-- **Configurable Logging**: Multiple logging options including ringbuffer and stdout
+Zinit is an init system and process supervisor designed for environments that need reliable service management without the complexity of traditional init systems. It runs as PID 1 or in container mode, monitors configured services, restarts them on failure, and respects dependency ordering during startup and shutdown. Zinit exposes both a Unix socket control interface and an HTTP proxy with a JSON-RPC 2.0 API.
+
+## What this repository contains
+
+- **`zinit` binary** — the init system and process supervisor
+- **Unix socket control interface** — for local CLI interaction
+- **HTTP proxy** — JSON-RPC 2.0 API for remote management
+- **CLI commands** — `init`, `list`, `start`, `stop`, `monitor`, `proxy`, and more
+- **Declarative service configuration** via YAML files
+- **Container mode** with appropriate signal handling
+- **Configurable logging** including ringbuffer and stdout options
+
+## Role in the stack
+
+Zinit serves as the init system for ZOS / Zero-OS nodes and can also be used as a standalone process manager in containers or lightweight Linux systems. It is the layer that ensures system services (networking, storage, provisioning, and user workloads) are started in the correct order and kept healthy. External tools and clients — including the Zinit Client Rust library — can interact with it over its socket or HTTP APIs.
+
+## ZOS / Zero-OS
+
+ZOS, also known as Zero-OS, is the operating system layer used to run and manage nodes. It provides the low-level runtime environment for workloads, networking, storage, and automation. Zinit is the init system at the core of ZOS, responsible for bootstrapping and supervising all node services.
+
+## Relation to ThreeFold
+
+This technology is used within the ThreeFold ecosystem and was first deployed on the ThreeFold Grid. The component itself is designed as reusable infrastructure technology and should be understood by its technical function first, independent of any specific deployment.
+
+## Ownership
+
+This repository is owned and maintained by TF-Tech NV, a Belgian company responsible for the development and maintenance of this technology.
 
 ## Installation
 
 ```bash
 curl https://raw.githubusercontent.com/threefoldtech/zinit/refs/heads/master/install.sh | bash
 
-#to install & run
+# to install & run
 curl https://raw.githubusercontent.com/threefoldtech/zinit/refs/heads/master/install_run.sh | bash
 ```
 
@@ -75,4 +97,4 @@ See the [OpenRPC specs](openrpc.json) for more information about available RPC c
 ## License
 
 This project is licensed under the Apache License 2.0 - see the [LICENSE](LICENSE) file for details.
-Copyright (c) TFTech NV.
+Copyright (c) TF-Tech NV.