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

Author: despiegk

README.md

@@ -1,50 +1,75 @@
-# 0-OS ![Tests](https://github.com/threefoldtech/zosbase/workflows/Tests%20and%20Coverage/badge.svg) [![Go Report Card](https://goreportcard.com/badge/github.com/threefoldtech/zos)](https://goreportcard.com/report/github.com/threefoldtech/zos)
+# Zero-OS Base ![Tests](https://github.com/threefoldtech/zosbase/workflows/Tests%20and%20Coverage/badge.svg) [![Go Report Card](https://goreportcard.com/badge/github.com/threefoldtech/zos)](https://goreportcard.com/report/github.com/threefoldtech/zos)
 
-0-OS is an autonomous operating system design to expose raw compute, storage and network capacity.
+Zero-OS Base contains shared foundational packages and core libraries common to all Zero-OS variants. It abstracts hardware interfaces, networking primitives, and storage operations used across the Zero-OS family.
 
-This repository host the V2 of 0-OS which is a complete rewrite from scratch. If you want to know about the history and decision that motivated the creation of the V2, you can read [this article](docs/internals/history/readme.md)
+## What this is
 
-0-OS is mainly used to run node on the Threefold Grid.
-Head to https://threefold.io and https://wiki.threefold.io to learn more about Threefold and the grid.
+This repository provides the shared building blocks that underpin Zero-OS, Zero-OS v4, and Zero-OS Light. Rather than duplicating low-level logic across each OS variant, zosbase centralizes hardware abstraction, common protocols, and reusable libraries. This ensures consistency, reduces maintenance burden, and makes it easier to evolve the operating system family as a whole.
+
+## What this repository contains
+
+- **Hardware abstraction layer** — CPU, memory, and device interfaces
+- **Networking primitives** — common network setup, wireguard, and routing utilities
+- **Storage operations** — volume, cache, and filesystem abstractions
+- **Shared protocols and data types** — reservation formats, capacity structures, and wire formats
+- **Documentation and specifications** — design docs, FAQs, and internal architecture documentation
+- **Common test utilities and development helpers**
+
+## Role in the stack
+
+Zosbase sits at the bottom of the Zero-OS software stack. It is imported and used by:
+
+- **zos** — the main Zero-OS V2 node operating system
+- **zos4** — the next-generation Zero-OS V4
+- **zoslight** — the lightweight variant for edge and constrained devices
+
+Any improvement or fix in zosbase propagates to all dependent OS variants, making it the central point of reuse for the Zero-OS ecosystem.
+
+## 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. This repository supplies the shared libraries and abstractions that make all Zero-OS variants possible.
+
+## 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.
 
 ## Documentation
 
-Start exploring the code base by first checking the [documentation](/docs) and [specification documents](/specs).
+Start exploring the codebase by first checking the [documentation](/docs) and [specification documents](/specs).
 
-An [FAQ](./docs/faq/readme.md) is also available for all the common questions.
+An [FAQ](./docs/faq/readme.md) is also available for common questions.
 
 ## Setting up your development environment
 
-If you want to contribute read the [contribution guideline](CONTRIBUTING.md) and the documentation to setup your [development environment](qemu/README.md)
+If you want to contribute, read the [contribution guideline](CONTRIBUTING.md) and the documentation to set up your [development environment](qemu/README.md).
 
 ## Grid Networks
 
-0-OS is deployed on 3 different "flavor" of network:
+Zero-OS is deployed on several network environments:
 
-- **production network**: Released of stable version. Used to run the real grid with real money. Cannot be reset ever. Only stable and battle tested feature reach this level. You can find the [dashboard here](https://dashboard.grid.tf/)
-- **test network**: Mostly stable features that need to be tested at scale, allow preview and test of new features. Always the latest and greatest. This network can be reset sometimes, but should be relatively stable. You can find the [dashboard here](https://dashboard.test.grid.tf/)
-- **QA network**: Mostly unstable features that need to be tested internally, allow preview and test of new features. Can be behind development. This network can be reset sometimes, but should be relatively stable. You can find the [dashboard here](https://dashboard.qa.grid.tf/)
-- **dev network**: ephemeral network only setup to develop and test new features. Can be created and reset at anytime. You can find the [dashboard here](https://dashboard.dev.grid.tf/)
+- **production network**: Released stable versions. Used to run the real grid. Cannot be reset. Only stable and battle-tested features reach this level. [Dashboard](https://dashboard.grid.tf/)
+- **test network**: Mostly stable features that need to be tested at scale. Can be reset occasionally. [Dashboard](https://dashboard.test.grid.tf/)
+- **QA network**: Internal testing of new features. Can be behind development. [Dashboard](https://dashboard.qa.grid.tf/)
+- **dev network**: Ephemeral network for developing and testing new features. Can be created and reset at any time. [Dashboard](https://dashboard.dev.grid.tf/)
 
-Learn more about the different network by reading the [upgrade documentation](/docs/internals/identity/upgrade.md#philosophy)
+Learn more about the different networks by reading the [upgrade documentation](/docs/internals/identity/upgrade.md#philosophy).
 
 ### Provisioning of workloads
 
-ZOS does not expose an interface, instead of wait for reservation to happen on a trusted
-source, and once this reservation is available, the node will actually apply it to reality. You can start reading about [provisioning](./docs/provision) in this document.
-
-## Owners
-
-[@maxux](https://github.com/maxux) [@muhamadazmy](https://github.com/muhamadazmy) [@delandtj](https://github.com/delandtj) [@leesmet](https://github.com/leesmet)
+Zero-OS does not expose an interface. Instead, it waits for reservations to happen on a trusted source, and once a reservation is available, the node applies it to reality. You can start reading about [provisioning](./docs/provision) in this document.
 
 ## Community
 
-If you have some questions or just want to hang out, you can find us on:
+If you have questions or want to connect, you can find the community on:
 
-- telegram: https://t.me/zero_os_tech
+- Telegram: <https://t.me/zero_os_tech>
 - Matrix: #zero-os:matrix.org
 
 ## 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.