WarDataLab now reads as a product system, not a pile of impressive screens
This page should explain how the product is framed, what kind of evidence discipline it uses, and who each route is for. It is no longer a generic capabilities brochure.
Three layers, three jobs
The release-shape work matters because each top-level route needs a clear job. This section explains that separation directly instead of hiding it inside nav labels.
Flagship live surface
Intelligence is the operating surface. It is where live tracking, layered monitoring, and the main product narrative now begin.
Open /intelligenceReviewed evidence layer
Incidents packages reviewed public-safe objects with explicit claim boundaries so the public evidence story stays disciplined.
Open /incidentsCore database and reference stack
Equipment remains a top-level database, while Research gathers comparison, country, conflict, and specialist reference routes around it.
Open /equipmentThe rules keeping the release coherent
Near release, product trust comes less from saying everything is powerful and more from showing route discipline. These principles are now part of the product shape.
One flagship surface, not several competing homepages.
Reviewed evidence should read differently from live intelligence and reference material.
Reference routes should support the core product instead of forking it.
Access pages should explain posture, then return users to the real product.
Release readiness is about user pathways, not ornament
Analysts and small teams
People who need a clear starting point in the flagship product, then deeper evidence or reference paths once a theatre matters.
Operators and repeat users
Users who need coherent movement between live monitoring, reviewed evidence, and structured access discussions without route confusion.
Institutions evaluating fit
Organizations that need the product shape to feel release-ready before pricing, access, or integration conversations make sense.
Understand the product here, then move into access and plan fit
About now frames the product posture. Pricing should translate that posture into plan depth, and Contact should turn it into a structured request path.