whoami

Set who you are in this root. It writes _eidos/me.md, which is personal and gitignored — one per person, never checked in.

Two minutes, and it changes every subsequent answer

This is the step people skip. It’s the difference between an agent explaining things you already know and one pitched at the person actually reading.

What it asks

First, which role — from whatever set your framework installed in _eidos/roles/. The software seed ships Framework Owner, Developer, Designer, Project Manager and Stakeholder; book and research ship their own casts.

Then it calibrates that role on three axes:

Axis	What it changes
Ownership	What you actually own here — and so which decisions come back to you.
Experience with the scope	How much orientation you get before the answer.
Technical capacity	Vocabulary and depth, independent of role.

Role sets the baseline; calibration tunes it per person. A senior developer new to this product and a junior developer who’s been on it two years need opposite things, and role alone can’t tell them apart.

A role is a baseline, not a cage

You can write a custom role directly in your me.md rather than picking one the framework ships.

Leaving it blank

Perfectly fine. The agent defaults to full, framework-owner-style facilitation, and offers to record who you are.

The one file in `_eidos/` that isn't committed

The seeded .gitignore handles it. It’s yours, not the team’s — which is what makes it safe to be honest in.

Related

• Roles & the Actor — what a role contract contains.