ENGINE DESIGN REPORT

The Engine researched, designed, then rebuilt.

This page shows the design artifacts created before the live site was rebuilt.

Design brief

# VoidComms Engine-Chosen Design Brief

## Chosen direction
Public Intelligence Command Site.

## Why
VoidComms should feel like a public-facing control layer: serious enough for investors, clear enough for customers, and structured enough for the owner to run from a phone.

## Visual logic
Use a restrained command-centre style:
- dark base for authority
- one trust accent
- one warning accent
- one action accent
- minimal motion for live-system feeling
- no random rainbow style

## Layout logic
Each page must have:
- hero
- plain-English purpose
- proof/decision section
- public/private boundary
- internal links
- commercial or owner next action

## Copy logic
Plain, strong, founder/operator language.
No generic SaaS filler.
No fake claims.
No legal/financial/betting guarantees.

## Page logic
Homepage sells the category.
Reports prove the thinking.
Decisions show the control model.
Factory sells the money engine.
Predictions drive traffic.
Phone hub makes it usable.

Visual style

{
  "chosen_style": "Public Intelligence Command Site",
  "base": "dark serious command-centre",
  "accent_trust": "single green trust accent",
  "accent_warning": "single amber warning accent",
  "accent_action": "single blue action accent",
  "motion": "minimal pulse/status only",
  "avoid": [
    "random colours",
    "generic SaaS look",
    "thin placeholder cards",
    "fake metrics",
    "overdesigned gimmicks"
  ]
}

Risk review

{
  "green": "public reports, proof, website factory, source maps, phone links",
  "amber": "predictions, racing, finance, auction, medical research",
  "red": "public owner-control, investment/auction offers without legal structure",
  "x": "fake claims, fake users, guaranteed profits, guaranteed winners, private data harvesting, secret exposure"
}