The two rails

JinDesk gives you two ways to interact, and they sit at the edges of every page — not places you visit, but tools that travel with you. They differ on one axis: do you want to ask, or run?

Ask vs run

	evolve (Vera)	the CLI
You want to	ask — understand something	run — do something
How you talk to it	natural language	a verb (jin make)
Where it is	vertical right rail (Cmd+E)	horizontal bottom bar (Cmd+J)

They share no grammar: the CLI only accepts jin verbs; evolve only takes prose. So you’re never in doubt which you’re using.

The CLI is how you run a verb directly. evolve is how you ask, and the assistant reasons.

When to reach for which

• Reach for evolve when you have a question — “why is this signal red?”, “what’s leaking this month?”, “explain this thesis.” Vera reads the data and the framework and answers in plain language.
• Reach for the CLI when you want to do a specific thing — jin make to rebuild, jin snapshot to freeze, jin afs to manage the framework’s git. You name the verb, it runs, you watch it stream.

Why they’re kept separate

It’s tempting to let you type /make inside evolve — but that would duplicate the CLI, and two prompts that accept the same commands is confusing, not convenient. So the line holds: evolve stays conversational; the CLI owns the verbs. One place to ask, one place to run.

When the assistant acts

Vera can do things too — propose a note, offer to trigger a rebuild — and this doesn’t blur the two. What she does is an outcome of the conversation: she proposes, you approve, then it happens. And when she runs a rebuild, it runs on the CLI rail — the progress streams into the bottom bar, not the chat. She asks; the deterministic rail performs.