Personas and Developer Levels

The system uses persona names instead of assuming that one numeric skill level applies to every task. A maintainer can still be a first-time operator for a new host.

Persona	Primary question	Required system response
Evaluator	Is this product applicable, supported, and safe for my environment?	Honest product routes, support slices, prerequisites, sample boundary, and data-use summary
Operator	Can I install, verify, run, recover, update, and remove it?	One complete host-native journey with expected output and safe recovery
First-time contributor	Can I move from clone to a reviewable green change?	Small owner routes, focused checks, docs path, Preview path, and PR evidence guidance
Experienced contributor	Can I change a capability without reading unrelated internals?	Public module boundaries, typed command contracts, fixtures, and fast feedback
Adapter author	Can I add one host slice without overclaiming the others?	Federated host declarations, scaffold/conformance routes, native evidence, and promotion rules
Maintainer and releaser	Can I prove what is safe to merge, publish, and roll back?	Required gates, evidence freshness, release plan, protected apply, and post-publish verification
Support and security responder	Can I diagnose a problem without collecting secrets or raw sessions?	Bounded diagnostic plan, redaction, explicit persistence or upload, support lifecycle, and private disclosure