About Hardwindex

The proposed publication

Hardwindex is designed as a small editorial reference shelf rather than a product catalogue. Its first six manuals begin with observable constraints: workload, sustained power, short electrical peaks, physical clearance, air paths, memory working sets, write volume, retention, and recoverability. The articles organise specification categories and show their arithmetic. They do not rank products or tell a reader what to buy.

The visible publication language is English. The intended country context is the Netherlands, chiefly for transparency and privacy framing. No Dutch city is claimed because the responsible operator’s location has not been supplied. No office, test bench, laboratory, commercial company, editorial team, or trading history is represented.

Why this site says pre-launch

The domain name and visible brand were supplied. The identity behind them was not. Hardwindex therefore cannot truthfully state a legal operator, responsible editor, street address, KVK registration, VAT position, telephone number, credentials, funding source, affiliate arrangement, sponsorship policy, or vendor relationship. These are not decorative omissions. They determine legal notices, accountability, privacy roles, conflicts, and whether publication should occur at all.

The displayed author names are explicitly illustrative editorial roles. Their monograms demonstrate the proposed byline system; they are not claims that those people exist, wrote the articles, or possess technical experience. Before launch, accountable editors must fact-check and adopt the work under their real names, or the bylines must be replaced with another truthful accountability model after legal review.

Boundaries by design

Hardwindex does not publish product recommendations, rankings, scores, testimonials, affiliate links, named vendors, fabricated benchmarks, or laboratory claims. Public photographs are unresolved decorative media and carry no factual captions. Calculations use invented scenarios whose assumptions are shown. Actual parts vary across revisions, environments, firmware, and workloads.

Generic hardware guidance cannot approve an actual parts list or replace current component manuals. Electrical uncertainty, damaged hardware, connector ambiguity, and fire-safety questions require qualified help. This publication’s useful role is narrower: turn a fuzzy build idea into a set of questions that can be checked.

Readers can start with the constraint-first desktop framework, inspect the proposed evidence rules in editorial standards, and see every identity gap on the illustrative authors page. The contact preview does not transmit information.