Repository navigation
Hive network console
Current automatic sensor collection is documented in Automatic energy. Historical per-job readings below retain their own scope and do not become live power.
The default Overview brings the global Hive, region planning, actual management hubs and execution groups, resource capacities, energy and devices into one workspace. Benchmarks, Routing and Recovery are advanced operations; changing a view never changes device permissions or workload eligibility.
Four regional zones are planned: Americas, Europe, Asia Pacific, and Middle East / Africa. Their map points are conceptual macroregion centres, not commissioned facilities or approved sites. The current pilot has one active management hub; regional federation is not deployed. Actual hub/group cards describe registered membership, not execution of one shared model. Nested membership totals must not be added together.
A device or hub without declared coordinates remains unlocated. Assign location records owner-declared coordinates with their source, precision and observation. A browser-location action requires an explicit user request and permission; no coordinates are inferred from IP address, language or time zone. Region labels do not establish legal residency or physical hosting.
- Open Hive operator console and sign in with the configured Authenticator.
- Choose Add a device to create a short-lived worker invitation.
- Install/open the appropriate companion and scan or paste that invitation. The package matrix separates public previews from private qualification kits; iOS installation depends on signing/provisioning, not an IPA downloaded in Safari.
- Check recent contact and operating policy. Use Benchmarks to qualify the supported compute profile before treating the node as usable measured capacity.
Pair Xbox / TV approves the code displayed by the console companion. It is separate from installing the application. Account → Open this management console on my phone transfers owner management access; it does not enroll the phone as a compute worker. Security/MFA settings and Sign out remain account utilities.
Cloud enrollment uses the public HTTPS identity. This does not establish that every workload data path has been physically verified across cellular networks, NATs or network changes. Existing LAN qualification kits retain their explicit transport prerequisites. Public signup, multiple-owner roles and arbitrary regional routing are not promised by this single-owner pilot.
- Registered devices may remain listed while offline. Recent contact is distinct from a fresh compute worker and from operating-policy permission.
- Installed RAM is hardware inventory, not a pooled model allocation. System available memory and process/app budget are different quantities.
- Qualified compute is profile-specific evidence. Current eligibility requires fresh worker/policy checks. Historical delivered CPU work belongs to its recorded common window and is not live throughput or LLM acceleration.
- Device search/contact filters affect presentation only. Expand Device details for declared location, operating hours, memory scope and checks. A missing operating-hours policy refers to scheduling, not the Windows operating system.
- Energy is always visible, including missing coverage. Live power requires fresh sensor samples; aggregate energy requires a common covered window. Battery charge, rated power and compute rate are not consumption measurements.
The backend accepts optional instrumented, full-job power evidence inside authenticated/fenced benchmark reports and integrates covered samples. It exposes per-job source/scope/window/uncertainty and enrolled-resource coverage. The separate automatic collector now publishes supported live sensor windows, with measured and estimated subtotals kept apart. Unreported failed-attempt energy and network/host overhead outside the meter window are not silently included. See energy evidence contract.
Validation distinguishes synthetic browser fixtures, authenticated live readback, model static critiques and physical device benchmarks. A UI review never qualifies a new backend or proves energy savings.
Choose a 9-hour, 1-week or 30-day session at sign-in, or change the existing session under Account. The deadline is absolute from authentication; polling does not renew it. Recorded FP32 qualifications are historical. Eligibility requires a current qualification, recent worker contact and an enabled operating window; expiry after 24 hours and per-node blockers remain visible.
Companion 0.2.29 (build 33) automatically presents new-release notes after a launch or weekly check. Android offers immediate verified downloads and app-active scheduling; Android still confirms installation. iOS offers reminders and unsigned-package instructions, not automatic installation. See the complete console guide.
Users → Invitations manages customer account access, independently from companion pairing. It supports bounded lifetime, immediate link revocation and SMTP outbox status. See account invitation setup and qualification.
NodeLift · © 2026 Fabrizio Degni · Mission and value · Source documentation · Engineering status remains scoped to its evidence.