Home, Projects, Minecraft Builder, Deep Delvers, Manna-View, and Landscape.
Manna Core / Snapshot 2026-05-31
A public front door for private-first software.
Manna is a local, memory-backed build system turning Grayson's project network into real software: Minecraft generation, map intelligence, game prototypes, media digestion, service workflows, and private assistant infrastructure.
This site is the outside layer. It shows the shape of the ecosystem without pretending every internal tool is public, finished, or ready for strangers to use.
The builder bot is producing castles and village slices inside a local Java world.
Memory, project spines, testable loops, and human review stay at the core.
Latest Network Signal
What the public site is now catching up to
The ecosystem moved fast since the first site pass. The homepage now reflects the actual active lanes instead of only the older domain, landscape, and Manna-View story.
Local bot and generator project for building readable Minecraft places from prompts, with deterministic command execution and live visual critique.
Active buildA public machine-journal lane for build logs, maps, field notes, project artifacts, and carefully approved social posts.
New public lanePlayable Unity sandbox for a third-person mining extraction game, with the first loop already proving movement, mining, banking, extraction, and pressure.
PrototypeMap-first public intelligence workspace built around lawful signals, source health, route context, and one coherent map surface.
Project pageCustomer-facing route for real landscape work, with the deeper quoting and planning logic kept private behind the scenes.
Business routeLive Routes
The current public surface area
These routes are intentionally reachable today. Some are public profiles, one is a business page, and most of the real software still runs privately on local machines.
Network front door
The umbrella homepage for the broader Manna ecosystem and its current build lanes.
manna-core.dev/
Working map
A status-forward directory for the public, private, prototype, and planning lanes.
manna-core.dev/projects/
Minecraft Builder
The newest public brief for the local Minecraft build-generation project.
manna-core.dev/projects/manna-minecraft-builder/
Deep Delvers
The game prototype profile for the mining extraction concept.
manna-core.dev/projects/deep-delvers/
Manna-View
The public summary for the map-first intelligence system.
manna-core.dev/manna-view/
Manna-Landscape
A service-company page with direct quote routing.
manna-core.dev/landscape/
Project Network
The strongest current lanes
The public site now names the work that is actually moving. Internal systems stay framed as internal; public routes do not automatically mean public releases.
Manna Minecraft Builder
A private Minecraft Java builder that turns compact plans into validated command builds, with castles, villages, adventure routes, undo, progress, and visual critique.
Read the project profileManna Archive
A public archive concept for Manna's own build logs, project notes, tools, maps, and approved artifacts without fake engagement or autonomous social posting.
See it in the project hubDeep Delvers
A stylized mining extraction game about dangerous descents, useful loot, banking pressure, and hauling a struggling underground town back to life.
Read the game briefManna-View
A place-first intelligence surface for lawful public data, route context, source visibility, and one shared map workflow.
Open Manna-ViewManna Digest
A local-first digestion pipeline for YouTube and media files, producing summaries, chapters, action items, clip candidates, and reusable artifacts.
See it in the project hubManna-Landscape
A public storefront for real landscape work, while pricing logic, job notes, and field guidance remain private operational infrastructure.
Visit the landscape pageOperating Rules
What the site should keep saying clearly
Core systems should keep favoring local data, local tools, explicit files, and recoverable project state over generic cloud drift.
Live, private, prototype, planning, and customer-facing surfaces should be labeled differently because they are different.
The network earns its shape through working loops: implement, verify, document, remember, and choose the next move.
Games, maps, media tools, archive posts, and field software should feel connected without being forced into one bland product voice.