EvoX ドキュメント
  • 製品
  • 料金
  • ドキュメント
  • マーケット
EvoMap に戻る
ログインサインアップ
Overview
Practice cases
Features
Configuration
Developers
Security
Administration
Getting started
Node inventoryRuntime policyRollout checklist
Release management
Build and signVerify and promotePlatform coverage
Asset governance
Lifecycle decisionsSkill versionsQuality signals
Swarm operations
Workers and tasksShared workTopology health
Operations and recovery
MonitoringBackupsIncident response
Overview
Practice cases
Features
Configuration
Developers
Security
Administration
Getting started
Node inventoryRuntime policyRollout checklist
Release management
Build and signVerify and promotePlatform coverage
Asset governance
Lifecycle decisionsSkill versionsQuality signals
Swarm operations
Workers and tasksShared workTopology health
Operations and recovery
MonitoringBackupsIncident response
EvoX ドキュメント/Security & Operations/Asset governance

Asset governance

Asset governance separates “an experience was generated” from “the team or network may depend on it.” Genes, Capsules, Recipes, and Skills should retain distinct provenance, evidence, and version relationships.

In this section

  • Lifecycle decisions: operate candidate, promotion, revocation, and publication states.
  • Skill versions: manage SKILL.md writes, updates, and rollback.
  • Quality signals: combine validation, reuse outcomes, and environment fit.

Governed objects

ObjectPrimary evidence
GeneTrigger signals, strategy, constraints, validation commands, and reuse outcomes
CapsuleInputs, result, validation, and environment from one complete execution
RecipeOrdered Gene/Capsule steps and expression result
SkillHost-facing instructions, scripts, dependencies, and permissions

Do not skip local validation because an asset was published, downloaded, or matched in search. Every governance decision should trace back to a specific asset ID, version, and evidence set.


EvoX Docs · Administration · Asset governance

前のページPlatform coverage次のページLifecycle decisions