EvoZeus-Runtime Routing
Runtime routing preserves local-first behavior and user approval gates. EvoZeus main repo is Protocol-only; runtime implementation belongs in evozeus-runtime. This skill is the routing and trust-policy handoff from the main repo context to the runtime component.
Runtime Principles
- Zero-install by default for root
SKILL.md and /skill.
- Local-first: raw sessions and runtime state stay under
~/.evozeus/.
- Markdown/JSON first before dashboards or charts.
- Opt-in packs for scanner, factor code, MCP, LLM, browser, or visualization behavior.
- Manifest before download: show dependencies, permissions, inputs, outputs, and fallback.
- User approval before upload, GitHub issue, PR, or external sync.
User Journey Role
Runtime is optional component assembly after registration, skeleton install, and skills install:
Web /skill
-> EvoZeus-Install Registration
-> EvoZeus skeleton + skills installed
-> user approves runtime
-> read evozeus-runtime/SKILL.md
-> runtime reads EvoZeus registry pointer
-> runtime verifies default official factors
-> runtime runs local judgment
Do not silently install, scan, network, or create local state. Show what will be read, written, installed, and verified before enabling runtime.
Handoff
When runtime is approved:
- Read the component repo root skill at
evozeus-runtime/SKILL.md.
- State the requested capability: scanner execution, factor execution, local registry, report generation, TUI, browser companion, or runtime development.
- State files to read, files to write, commands to run, dependencies, network behavior, rollback path, and privacy impact.
- Stop if the runtime repo lacks the required manifest, checksum, attestation, lockfile schema, or implementation.
Default Official Factors
When the user asks to use default factors, this skill routes consumption only. Registry publication or default set changes belong to ../evozeus-registry-release/SKILL.md.
- Read the main
EvoZeus registry pointer.
- Resolve only official release manifests.
- Verify checksum, SBOM / attestation, compatibility, and review state.
- Enable only the selected factors.
- Keep raw session data local.
If the registry pointer, manifest, checksum, or attestation is missing, stop and report the blocker instead of inventing an install path.
Runtime Scope
Runtime PRs should state which surface changes:
| Surface |
Examples |
| Local registry |
session IDs, artifact index, cache |
| Report generation |
Markdown/JSON evidence report |
| Doctor implementation |
environment check implementation after diagnosis identifies a runtime change |
| TUI |
local review flow |
| Browser companion |
optional local UI inspection |
| User home state |
~/.evozeus/ structure and cleanup |
Implementation PRs for these surfaces go to evozeus-runtime. Main repo changes should be limited to protocol, schemas, trust policy, registry pointer, or routing docs.
Required Checks
Runtime work should include:
- reproduction or real behavior proof
- command used after the patch
- before/after output or generated artifact
- privacy impact
- fallback when optional dependencies are unavailable
For main repo protocol or routing changes, use the appropriate ../../../.github/PULL_REQUEST_TEMPLATE/* template and run python3 scripts/check_pr_ready.py --base <base-ref>. For runtime implementation, open the PR in evozeus-runtime and use that repo's checks.
Boundaries
- Do not use this skill for
/skill registration or skeleton/skills installation; use ../evozeus-install-registration/SKILL.md.
- Do not use this skill for report content writing; use
../evozeus-reporting/SKILL.md unless local file generation or runtime execution is needed.
- Do not use this skill for first-pass diagnosis; use
../evozeus-doctor-debugging/SKILL.md.
- Do not bypass the main registry pointer or consume lab
reviewed assets as default user-installable releases.
1---2name: evozeus-runtime-routing3description: Use when routing approved EvoZeus runtime behavior, local registry, CLI, TUI, browser companion, workspace state, scanner execution, factor execution, or report execution from the main repo context to evozeus-runtime.4metadata:5 source: https://skillmd.com/skills/metainflow/evozeus-runtime-routing6---78# EvoZeus-Runtime Routing910Runtime routing preserves local-first behavior and user approval gates. `EvoZeus` main repo is Protocol-only; runtime implementation belongs in `evozeus-runtime`. This skill is the routing and trust-policy handoff from the main repo context to the runtime component.1112## Runtime Principles1314- Zero-install by default for root `SKILL.md` and `/skill`.15- Local-first: raw sessions and runtime state stay under `~/.evozeus/`.16- Markdown/JSON first before dashboards or charts.17- Opt-in packs for scanner, factor code, MCP, LLM, browser, or visualization behavior.18- Manifest before download: show dependencies, permissions, inputs, outputs, and fallback.19- User approval before upload, GitHub issue, PR, or external sync.2021## User Journey Role2223Runtime is optional component assembly after registration, skeleton install, and skills install:2425```text26Web /skill27 -> EvoZeus-Install Registration28 -> EvoZeus skeleton + skills installed29 -> user approves runtime30 -> read evozeus-runtime/SKILL.md31 -> runtime reads EvoZeus registry pointer32 -> runtime verifies default official factors33 -> runtime runs local judgment34```3536Do not silently install, scan, network, or create local state. Show what will be read, written, installed, and verified before enabling runtime.3738## Handoff3940When runtime is approved:41421. Read the component repo root skill at `evozeus-runtime/SKILL.md`.432. State the requested capability: scanner execution, factor execution, local registry, report generation, TUI, browser companion, or runtime development.443. State files to read, files to write, commands to run, dependencies, network behavior, rollback path, and privacy impact.454. Stop if the runtime repo lacks the required manifest, checksum, attestation, lockfile schema, or implementation.4647## Default Official Factors4849When the user asks to use default factors, this skill routes consumption only. Registry publication or default set changes belong to `../evozeus-registry-release/SKILL.md`.50511. Read the main `EvoZeus` registry pointer.522. Resolve only official release manifests.533. Verify checksum, SBOM / attestation, compatibility, and review state.544. Enable only the selected factors.555. Keep raw session data local.5657If the registry pointer, manifest, checksum, or attestation is missing, stop and report the blocker instead of inventing an install path.5859## Runtime Scope6061Runtime PRs should state which surface changes:6263| Surface | Examples |64| --- | --- |65| Local registry | session IDs, artifact index, cache |66| Report generation | Markdown/JSON evidence report |67| Doctor implementation | environment check implementation after diagnosis identifies a runtime change |68| TUI | local review flow |69| Browser companion | optional local UI inspection |70| User home state | `~/.evozeus/` structure and cleanup |7172Implementation PRs for these surfaces go to `evozeus-runtime`. Main repo changes should be limited to protocol, schemas, trust policy, registry pointer, or routing docs.7374## Required Checks7576Runtime work should include:7778- reproduction or real behavior proof79- command used after the patch80- before/after output or generated artifact81- privacy impact82- fallback when optional dependencies are unavailable8384For main repo protocol or routing changes, use the appropriate `../../../.github/PULL_REQUEST_TEMPLATE/*` template and run `python3 scripts/check_pr_ready.py --base <base-ref>`. For runtime implementation, open the PR in `evozeus-runtime` and use that repo's checks.8586## Boundaries8788- Do not use this skill for `/skill` registration or skeleton/skills installation; use `../evozeus-install-registration/SKILL.md`.89- Do not use this skill for report content writing; use `../evozeus-reporting/SKILL.md` unless local file generation or runtime execution is needed.90- Do not use this skill for first-pass diagnosis; use `../evozeus-doctor-debugging/SKILL.md`.91- Do not bypass the main registry pointer or consume lab `reviewed` assets as default user-installable releases.