Home, Projects, Manna-View, Deep Delvers, and Landscape are reachable now.
Manna Network
Public root domain
Private-first systems
Truthful status language
Private-first software with a public front door.
manna-core.dev is the public home for a growing network of locally owned software: map intelligence, internal operator tools, self-hosted systems, business software, and games that are still earning their final form.
The goal is not to make every internal build look launch-ready. The goal is to give the network a clean, trustworthy home that shows what is live today, what stays private on purpose, and what is still actively under construction.
Ownership, traceability, and human-reviewed systems matter more than generic SaaS polish.
One domain now gives the broader manna ecosystem a professional, coherent public identity.
- Focused public project pages with clear scope
- Public-facing business surfaces when they make sense
- Network-wide framing for how the ecosystem fits together
- Fake launch copy for tools that are still private
- Overclaiming maturity before a surface is actually ready
- Random disconnected pages with no shared identity
The root site now works as an umbrella layer: a polished entry point, a shared project hub, focused project profiles, and separate customer-facing routes where a project needs its own voice.
Live On The Domain
The current public surface area
These are the routes that are intentionally reachable today. Some are project pages, some are profile pages, and one is a standalone business surface.
Network front door
The umbrella homepage for the broader manna ecosystem, its principles, and its public shape.
manna-core.dev/
Shared build map
A cleaner directory for active builds, internal lanes, and public project briefs across the network.
manna-core.dev/projects/
Deep Delvers spotlight
A deeper public brief for the strongest current game concept in the workspace.
manna-core.dev/projects/deep-delvers/
Manna-View
The public summary page for the map-first intelligence system inside the network.
manna-core.dev/manna-view/
Manna-Landscape
A separate customer-facing route with its own service voice, still anchored to the shared domain.
manna-core.dev/landscape/
Featured Work
The strongest current projects in the network
This is a mixed ecosystem on purpose. Some projects are public-facing now, some are active internal systems, and some are detailed profiles for work still being built.
Manna-View
A place-first public intelligence system built around lawful public-world signals, route context, and source-visible map understanding.
Visit the Manna-View pageDeep Delvers
A stylized mining extraction game about dangerous descents, useful loot, and hauling a half-dead underground town back to life.
Read the Deep Delvers briefManna-Landscape
A public storefront for real landscaping work, with the deeper estimating and quoting logic kept private behind the scenes.
Open the landscape pageManna-Materialize
A structured workflow for turning site notes, photos, and job context into truthful field guidance for landscaping execution.
See it in the project hubManna-Watch
A local awareness tool that starts with home-network visibility and grows outward only when the truth boundary stays strong.
See it in the project hubManna-Books
A private ebook stack built around Calibre and Calibre-Web instead of handing the reading experience to closed ecosystems.
See it in the project hubGhost
The broader assistant layer of the ecosystem: more personal, more retrieval-oriented, and intentionally distinct from the builder-shell role of manna-core.
See it in the project hubOperating Rules
What the public site should communicate clearly
Each project should earn visibility by solving a real task, loop, or workflow before it starts sounding like generic product marketing.
The site should say whether a surface is live, internal, prototype-stage, or planning-stage instead of flattening everything into one launch voice.
Long-term control, private infrastructure, and system traceability are part of the product identity, not just hidden implementation details.
The domain should make very different projects feel connected without forcing them into one bland tone or pretending every route serves the same audience.