EvoZeus Start Here Onboarding
Start Here is the first protocol-only judgment after registration and install. It does not register the workspace, install skills, silently install runtime, scan files, write local state, or create GitHub artifacts.
Entry Flow
community /skill
-> EvoZeus-Install Registration completes
-> user approves protocol-only judgment
-> read root SKILL.md
-> output initial Session Verdict Card
-> ask before enabling runtime or preserving artifacts
First Pass
On the first pass:
- read root
../../../SKILL.md
- keep raw session local
- produce a Session Verdict Card in the response
- avoid writing files unless the user asks
- avoid runtime, scanner, factor installation, network, GitHub, or external upload
Optional Next Routes
| User asks for |
Read next |
install, registration, ~/.evozeus reconciliation, missing skills |
../evozeus-install-registration/SKILL.md |
| local scan, runtime, default official factors, report generation |
../evozeus-runtime-routing/SKILL.md |
| preserve this result, create Case/Candidate/Artifact |
../evozeus-artifact-preservation/SKILL.md |
| public issue, PR, example, or contribution |
../evozeus-redaction/SKILL.md then ../evozeus-community-contribution/SKILL.md |
| repository docs, governance, schema, or Skill edits |
../evozeus-development/SKILL.md |
Boundaries
- Do not write
~/.evozeus/ state during onboarding.
- Do not install EvoZeus skeleton or skills during onboarding.
- Do not install or enable default factors without user approval.
- Do not create GitHub issues or PRs without user approval.
- Do not turn onboarding into runtime implementation work.
1---2name: evozeus-start-here-onboarding3description: Use when a user has completed EvoZeus registration and install, then starts protocol-only EvoZeus judgment for the first time.4metadata:5 source: https://skillmd.com/skills/metainflow/evozeus-start-here-onboarding6---78# EvoZeus Start Here Onboarding910Start Here is the first protocol-only judgment after registration and install. It does not register the workspace, install skills, silently install runtime, scan files, write local state, or create GitHub artifacts.1112## Entry Flow1314```text15community /skill16 -> EvoZeus-Install Registration completes17 -> user approves protocol-only judgment18 -> read root SKILL.md19 -> output initial Session Verdict Card20 -> ask before enabling runtime or preserving artifacts21```2223## First Pass2425On the first pass:2627- read root `../../../SKILL.md`28- keep raw session local29- produce a Session Verdict Card in the response30- avoid writing files unless the user asks31- avoid runtime, scanner, factor installation, network, GitHub, or external upload3233## Optional Next Routes3435| User asks for | Read next |36| --- | --- |37| install, registration, `~/.evozeus` reconciliation, missing skills | `../evozeus-install-registration/SKILL.md` |38| local scan, runtime, default official factors, report generation | `../evozeus-runtime-routing/SKILL.md` |39| preserve this result, create Case/Candidate/Artifact | `../evozeus-artifact-preservation/SKILL.md` |40| public issue, PR, example, or contribution | `../evozeus-redaction/SKILL.md` then `../evozeus-community-contribution/SKILL.md` |41| repository docs, governance, schema, or Skill edits | `../evozeus-development/SKILL.md` |4243## Boundaries4445- Do not write `~/.evozeus/` state during onboarding.46- Do not install EvoZeus skeleton or skills during onboarding.47- Do not install or enable default factors without user approval.48- Do not create GitHub issues or PRs without user approval.49- Do not turn onboarding into runtime implementation work.