A map-first system for public-world awareness.

Manna-View is built around a simple operator question: pick a place, then understand what public signals, routes, cameras, weather, movement, and source conditions are visible around it.

The product direction is one coherent map surface with minimizable tools, popup-first inspection, source/confidence cues, and concise briefings that stay anchored to the data on the board.

See the project network Back to home

Designed To Answer

Three questions quickly and honestly

What is here?

Nearby cameras, events, weather, source layers, route context, local clusters, and map-native detail should be inspectable without leaving the place.

What is changing?

Movement, alerts, hotspots, world signals, and route-aware context should be visible as map objects instead of scattered dashboard fragments.

How reliable is it?

Source health, partial loads, credentials gaps, upstream rate limits, and fallback conditions should be visible instead of hidden behind confident UI.

Current Architecture Direction

One map runtime, one briefing path

The latest project direction is convergence. Manna-View should keep moving useful world and local behaviors into the shared map shell instead of reviving parallel surfaces.

MAP DATABASE

The preferred entry surface: fullscreen map first, minimizable drawers, focused controls, and popup/detail dock inspection.

Primary

WORLD scan on map

World counts, WatchWar reference state, partial-load issue summaries, and conflict/movement/reference/brief actions should live on the shared map.

Converging

Local clusters

Grouped local context can be focused, armed, inspected, and briefed directly from the map rather than hiding selection state.

Map-native

Legacy WORLD

The old dedicated world surface is fallback/reference infrastructure, not a peer primary path.

Demoted

Product Feel

The intended final surface

WatchWar Strength

Fast map-first urgency, live signal cadence, and a memorable briefing voice that feels like a transmission.

DeFlock Strength

Transparency-first rigor, structured surveillance metadata, open-map discipline, and readable source boundaries.

Manna Identity

A private-first operator tool: dark, clear, source-aware, minimizable, and useful without drowning the map in chrome.

Truth Rules

What Manna-View should never blur

Public Data Only

The system is for lawful public signals, explicit source integrations, and public-interest context.

Source Health Visible

Optional setup gaps, limited access, rate limits, and real upstream failures should not be conflated.

Neutral Startup

Startup should not default to a conflict-heavy posture before the user targets a place or theater.

Map Owns Context

Actions should preserve active map context instead of splitting behavior across hidden legacy paths.

Public Claim

What this page is and is not saying

Already True

The project is map-first and place-first
Lawful public signals and source boundaries are core rules
The UI direction is one unified map shell, not scattered dashboards

Not Claimed

No guarantee that every upstream public source is always live
No claim that this page is a public app launch
No promise that legacy surfaces are final product direction