The root, this hub, Manna-View, Deep Delvers, and Landscape are all currently reachable.
Project Network
Shared build map
Public and private lanes
Status-forward structure
The working map of the manna ecosystem.
This page collects the most important builds across the network and labels them plainly: public route, customer-facing surface, internal system, prototype, or saved plan. The point is orientation, not hype.
Public page does not always mean public app. Some entries here are public websites, some are active private systems, and some are detailed project briefs for work still taking shape behind the scenes.
The strongest current game concept gets the first full project profile instead of a one-card summary only.
Internal projects stay visible without being dressed up like finished public products.
The shared route tree now covers the umbrella homepage, this network page, a deeper Deep Delvers profile, the Manna-View project page, and the separate Manna-Landscape business route.
Manna-Materialize, Manna-Watch, Manna-Books, and Ghost are all real projects with distinct direction, even when they are not meant to be standalone public apps yet.
Treat it like a truthful network map: what is public, what is customer-facing, what is still a private system, and where each build fits in the larger ecosystem.
Public Surfaces
What is intentionally reachable right now
These are the pages that are already part of the public route tree. They do not all serve the same role, but they do now share a more coherent public presentation.
manna-core.dev/
The root site that explains the broader network and acts as the front door for the domain.
manna-core.dev/
manna-core.dev/projects/
A cleaner network page for active builds, project status, and route discovery.
manna-core.dev/projects/
manna-core.dev/projects/deep-delvers/
A fuller brief for Deep Delvers: the prototype truth, the loop, the tone, and the guardrails.
manna-core.dev/projects/deep-delvers/
manna-core.dev/manna-view/
The public summary page for the place-first map intelligence build.
manna-core.dev/manna-view/
manna-core.dev/landscape/
A customer-facing service route with its own branded voice and quote workflow.
manna-core.dev/landscape/
Active Build Lanes
Where momentum is strongest right now
Manna-View
A place-first public intelligence workspace built around lawful public-world signals, route context, and visible source boundaries.
Visit the Manna-View pageDeep Delvers
A third-person mining extraction game with dangerous delves, useful loot, and an underground town that should feel worth saving.
Open the Deep Delvers pageManna-Landscape
A public landscape service brand on the shared domain, backed by private estimating and internal work guidance that stay off the public site.
Visit the landscape pageManna-Materialize
A structured field-advisory system for turning site notes, photos, and job facts into trustworthy execution guidance.
Manna-Watch
A local awareness tool that begins with home-network visibility and only expands outward when the truth boundary remains clear.
Manna-Books
A private ebook system centered on Calibre and Calibre-Web for local ownership, flexible access, and a cleaner long-term library setup.
Ghost
The broader assistant layer of the ecosystem: personal, continuity-aware, and intentionally separate from the builder-shell job of manna-core itself.
Reading It Correctly
The public profile is not the product boundary
Public profile is not the same as public release
This network page exists to show the real ecosystem more clearly. Some entries are public routes, some are customer-facing storefronts, and some are internal builds that deserve context without being misrepresented as launched apps.
Clarity builds trust faster than hype
A cleaner public site only helps if the wording stays accurate. The long-term goal is a professional network identity that still tells the truth about project maturity, access, and intended audience.
Network Rules
How the site should keep evolving
Each project should read truthfully as live, internal, prototype-stage, or planning-stage instead of pretending everything is launch-ready.
The site should make the ecosystem feel connected even when the projects have very different surfaces, tones, and audiences.
Only the right surface should be public: storefronts where helpful, project briefs where useful, and private tools where they still belong.