EvoZeus Scanner Pack Authoring
Executable packs and scanner modules are components. They do not belong in the EvoZeus main repo; they start in EvoZeus-factor-lab and can become official only through release review.
When To Use
Use this skill for:
- executable Factor pack
- scanner module
- scanner pack
- resolver script
- file/session ingestion logic
- pack permission declaration
- dependency, sandbox, or supply-chain review
Route
EvoZeus Case / Candidate
-> maintainer route
-> EvoZeus-factor-lab submission
-> evidence + privacy + scanner permission gates
-> reviewed / rejected
-> optional promotion to EvoZeus-session-signal-skill
Required Packet
Every pack or scanner submission should include:
- source Case or Candidate link
- evidence packet
- purpose and trigger
- input files, env vars, commands, and network behavior
- output files, stdout, report fields, and local state changes
- dependencies, lockfile, license, checksum, or sandbox note
- failure modes and rollback path
- privacy note
Read Next
../evozeus-factor-authoring/SKILL.mdfor semantic Factor quality.../evozeus-redaction/SKILL.mdbefore public evidence.../../../docs/reference/scanner-pack-protocol.mdfor scanner pack contract.EvoZeus-factor-lab/templates/scanner-submission.mdwhen working inside the lab repo.
Boundaries
- Do not put executable scanner or pack code in the main repo.
- Do not treat lab review as official release.
- Do not let runtime consume lab moving branch.
- Do not skip security review for scanner code.