aoa-seed-route-inspect

Inspect Dionysus seed staging and planting constraints for candidate readiness.

2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/8Dionysus/8Dionysus --skill aoa-seed-route-inspect
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aoa-seed-route-inspect
Source: https://github.com/8Dionysus/8Dionysus/tree/main/.codex/plugins/aoa-shared-launchers/skills/aoa-seed-route-inspect
Command: npx skills add https://github.com/8Dionysus/8Dionysus --skill aoa-seed-route-inspect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves uncertainty about whether a reusable seed candidate is ready to be planted into Dionysus, by inspecting its staging state, wave context, and planting constraints before it becomes part of the owner-controlled system.

Core Features & Use Cases

  • Lifecycle posture inspection: Establishes the candidate’s current seed identity and where it sits in its live/staging lifecycle.
  • Wave and staging context review: Confirms relevant wave or staging notes (with the explicit boundary that staging notes are weaker than owner-repo truth).
  • Planting constraint verification: Reads planting rules to determine what is permissible and what decisions must still be made by the owner repo.
  • Provenance-aligned outcome contract: Produces a structured output distinguishing what belongs in Dionysus versus what must be decided by the owner repo (to preserve lineage evidence).

Quick Start

Ask the AI to run aoa-seed-route-inspect for the named Dionysus seed candidate and return the candidate identity, lifecycle posture, wave/staging context, planting constraints, and a decision boundary on what can enter Dionysus.

Frequently Asked Questions about aoa-seed-route-inspect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a seed candidate's staging state and planting constraints?▼

To verify a seed candidate's staging state and planting constraints, inspect its seed-route catalog, live wave context, and staging notes to determine readiness for movement into Dionysus, distinguishing what belongs in Dionysus from owner-repo decisions.

What is a seed lifecycle posture inspection in agent workflows?▼

A seed lifecycle posture inspection establishes a candidate's current seed identity and confirms where it sits in its live or staging lifecycle before it becomes part of the owner-controlled system.

How do I check planting rules and wave context for a reusable candidate?▼

Check planting rules and wave context by reading seed_next_live, seed_wave_context, and seed_planting_rules data to determine what is permissible and what decisions must still be made by the owner repo.

Can staging notes override owner-repo truth when inspecting seed provenance?▼

Staging notes cannot override owner-repo truth when inspecting seed provenance, because staging notes are explicitly weaker than owner-repo truth and serve only as supplementary context.

When do I need to inspect seed-route catalogs before moving a candidate into Dionysus?▼

You need to inspect seed-route catalogs before moving a candidate into Dionysus whenever a reusable candidate is being considered for movement, ensuring planting constraints and provenance-aligned outcomes are verified.

What is the decision boundary for what can enter Dionysus versus the owner repo?▼

The decision boundary separates what belongs in Dionysus from what must be decided by the owner repo, preserving lineage evidence through a provenance-aligned outcome contract based on planting constraints and wave context.