Soft launch: what we're shipping first

Soft launch, for Dharma Atlas, means the doors are open while the building is still being finished in public. We are not pretending the atlas is complete. We are shipping the parts that already help practitioners find communities, and we are leaving unfinished surfaces visible rather than decorating them into false polish.

If you have seen the welcome modal — the one that says we are still growing — that tone is the product strategy in miniature. Listings and features are evolving. Missing or outdated details are expected. Contribution is part of the design, not an afterthought.

What "soft launch" means in practice

A hard launch implies a finished promise: every tradition covered, every city dense, every manager tool complete, every integration live. We do not have that, and claiming it would waste trust we need later.

A soft launch implies a usable core:

• Explore places on a map and in a list
• Open place profiles with whatever enrichment exists
• Browse people / teachers as a second lens
• Read tradition context
• Submit missing entries
• Claim listings and begin stewardship
• Favorites for return visits
• Pilgrimage routes as a related geographic story
• Admin moderation behind the scenes so openness stays livable

Those surfaces are real enough to use. They are not evenly deep. Soft launch is the agreement that usefulness can precede completeness if we stay honest about the difference.

It also means we will sometimes ship quieter than a marketing calendar prefers. If a feature helps place managers keep schedules current, it may matter more than a splashy page that does not change anyone's week. Sequencing by practitioner value is how we avoid building a beautiful shell around a stale index.

What we are prioritizing first

Early priority goes to the loops that make a directory trustworthy.

Discovery that respects geography. Map, list, filters, search, and near-you behavior come first because the primary job is "find a place to practice." If discovery fails, nothing else matters.

Profiles that can grow. A place page should support photos, about text, offerings, teachers, events, links, and notices over time. Even when fields are empty, the structure should invite enrichment instead of looking like a dead end.

Contribution paths. Add and claim are not peripheral forms. They are how the atlas thickens. Soft launch without contribution is just a static export with nicer CSS.

Steward tools for places. Once someone is responsible for a listing, they need a manage path with draft discipline. Unreviewed public edits do not scale in spiritual data.

Moderation. Submissions, claims, and reports need human attention. Shipping the front of the directory without the back office is how open projects sour.

After those foundations, the next high-leverage work is already visible in our own gap list: stronger teacher self-serve after claim, cross-place events discovery, offerings filters that use data we already collect, and calendar import that meets managers where their schedules already live. Those are not random ideas. They close loops we started.

Incomplete on purpose (for now)

Soft launch includes deliberate incompleteness. Naming it reduces frustration.

Some regions are thin. We would rather show empty space than invent coverage.

Some teacher claim approvals do not yet unlock the same manage experience places have. Closing that loop is important; pretending it is already closed would be worse.

Some calendar import paths are partial. ICS and CSV can help today; other sources are still "coming soon" in the product for a reason.

Books and adjacent catalog experiments may appear before they are first-class everywhere. When that happens, treat them as beta shelves, not as finished recommendations infrastructure.

Global "what's happening this week" event browsing is an obvious retention feature we do not fully serve yet. Schedules can exist on profiles without a unified discovery surface. That gap is real.

Native reviews and deeper manager analytics are later trust and engagement layers. Soft launch focuses on accurate orientation first.

If you encounter a stub, take it as a boundary marker. It means we chose not to fake completion. The welcome modal's frankness is meant to set that expectation before the first map interaction.

The spirit of the welcome modal

The welcome message does three jobs.

First, it defines the product in one breath: an open directory of meditation centers, monasteries, and spiritual guides across traditions, built to help practitioners find communities near them.

Second, it admits beta status without theatrical apology. Evolving listings are normal. Out-of-date details will happen. The remedy is participation.

Third, it points people toward exploration rather than toward a feature tour. "Start exploring" is the right call to action for a directory. The value is in the territory, not in our interface chronology.

We want that spirit in the blog too. Soft launch communication should lower adrenaline. No countdown. No inflated metrics. No claim that Dharma Atlas replaces teachers, temples, or discernment. At best we shorten the distance between intention and a real-world door.

How to read the roadmap without getting lost

Roadmaps are easy to misread as promises. Ours are sequencing notes.

When we say something is first, we mean it unlocks trust or usefulness for the core directory job. Teacher manage after claim matters because claim without stewardship is a broken story. Events discovery matters because practice is timed, not only mapped. Offerings filters matter because people search by activity as much as by tradition name.

When we say something is later, we mean it depends on foundations or pulls us toward marketplace patterns we are not ready to center. Promoted listings, booking, multi-manager complexity, and installable app wrappers can wait until the index is healthier.

If you are deciding whether to invest time as a steward, the practical read is this: the place loop is real enough to claim and improve now; adjacent surfaces will keep expanding; your enrichment will not be thrown away when those surfaces mature.

What we want from early users

Early users help most when they are specific.

• Browse your city and notice absences
• Claim listings you actually represent
• Add missing places with solid public sources
• Report precise errors
• Tell us which incomplete surface blocks real use

Broad praise is kind. Specific friction is useful. If the explore filters miss the offering you need, say which offering. If a pilgrimage route is strong but local directory links are weak, say where the handoff fails. Soft launch is a conversation with evidence.

Also, please keep expectations aligned with about: curated public sources plus community submissions; accuracy as an aim; change as a given; no account required to explore. That page now carries the manifesto, mission, and roadmap. Soft launch should not need a novel of terms before someone can look at a map.

What we are not optimizing for yet

We are not optimizing for constant engagement. A directory can succeed if people use it deeply a few times a year.

We are not optimizing for identical coverage across all traditions on day one. Unevenness is a data and labor reality.

We are not optimizing for sounding finished. Polished emptiness is a worse failure mode than plain incompleteness.

We are not optimizing for every integration at once. Managers should get a few reliable update paths before a maze of half-connected imports.

These non-goals keep the soft launch coherent. They also explain why some requests will be heard and still not shipped next. Hearing is not the same as sequencing.

Closing

If you want the simplest next step, read the short about page, dismiss the welcome modal's honesty as a feature rather than a warning label, and then use the atlas as it stands: explore, notice gaps, and contribute where you have standing. Soft launch works when early practitioners treat the directory as a shared draft of public knowledge — already useful, still growing, and improved by careful hands rather than by louder announcements.