Where to start: use it first, deploy it first, or connect data first

This system does not have only one valid entry point, because people do not arrive with the same first question.

Some people ask, “How do I start using this right now?” Others ask, “Can it run inside my own environment?” Others ask, “How do I connect my own data and workflows?”

So the right move is not to push everyone toward the same button. It is to help them choose the right first step.

If you want to use it first

Start with LinX, then go to Download.

This is the best path for most first-time visitors because the first thing you need to decide is whether the product actually holds onto your line of work.

Take this path if your main questions sound like:

• is this only another chat shell, or can it keep work moving
• can it bring chat, files, memory, and follow-up into one place
• am I willing to start on desktop first

If you care about deployment and boundaries first

Start with xpod.

This path is for people who care first about questions like:

• can this run on my own device or server
• do identity, storage, and permissions stay inside an environment I can shape
• can AI stay close to data I already control

If your first question is really about control, do not start with Download. Start with xpod.

If you care about data modeling and integration first

Start with drizzle-solid.

This is the right path for developers and integrators who need to:

• connect their own data sources and domain objects
• bring more states, workflows, and business objects into the system
• avoid pretending pods are just relational tables in another costume

If your first question is “how does this system keep expanding into more data and workflows,” start with drizzle-solid.

What most people should do

If you are unsure, start with LinX.

Most people need to decide whether the product is real before they need to decide how deep to go on runtime and extension.

Why all three paths need to exist

Because Weiming Intelligence is not building only an app, and not only a developer library.

It has:

• LinX as the product entry
• xpod as the runtime
• drizzle-solid as the developer data layer

The site needs one obvious main path, but it also needs real branching paths for deployment and extension. Otherwise people keep getting lost between understanding, using, deploying, and building.