skills.rest
edri2or
edri2orOFFICIAL
Explore all skills by this author →
GitHub

stage7-full-system-e2e

Run a 48-hour observation window to validate full-system E2E autonomy.

Updated Aug 27, 2026
Search Tags:#e2e#validation#evidence#autonomy#ci-cd#journey#stage7
One-click install
npx skills add https://github.com/edri2or/ripo-skills-main --skill stage7-full-system-e2e
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stage7-full-system-e2e
Source: https://github.com/edri2or/ripo-skills-main/tree/main/exported-skills/stage7-full-system-e2e
Command: npx skills add https://github.com/edri2or/ripo-skills-main --skill stage7-full-system-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stage 7 closeout provides a structured, evidence-driven end-to-end validation of autonomous systems by running a 48-hour window, collecting multi-stream proof, and gating completion on results.

Core Features & Use Cases

  • 48-hour autonomy observation window with zero active agent involvement
  • Dual autonomy proof (Level-1 rebuild, Level-2 hands-off) verification
  • Prerequisites checks, JOURNEY maintenance, and state-management guidance

Quick Start

Start the 48-hour window by creating a fresh claude/stage7-e2e-<slug> branch and initiating the observation workflow per the SKILL.md guidelines.

Frequently Asked Questions about stage7-full-system-e2e

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

FAQPage Schema
How do I validate full-system E2E autonomy for a deployed architecture?▼

You validate full-system E2E autonomy by running a 48-hour observation window with zero active agent involvement to confirm hands-off readiness. This process collects multi-stream proof and gates completion on the results.

What is the dual-proof requirement for Stage 7 readiness closeout?▼

The dual-proof requirement for Stage 7 readiness verifies autonomy through a Level-1 rebuild and a Level-2 hands-off test. Both proofs must be documented with JOURNEY entries and pass CI gating.

How do I start a 48-hour E2E autonomy observation window?▼

Start the 48-hour E2E autonomy observation window by creating a fresh claude/stage7-e2e branch and initiating the workflow per the SKILL.md guidelines. Ensure state.json prerequisites and metadata discipline are met first.

Do I need specific prerequisites before running an E2E autonomy validation window?▼

Yes, running an E2E autonomy validation window requires meeting state.json prerequisites and enforcing metadata discipline. These checks ensure the deployed architecture is ready for the observation and dual-proof collection.

What evidence streams are required to gate CI completion for Stage 7?▼

Gating CI completion for Stage 7 requires multiple evidence streams including documented JOURNEY entries, Level-1 rebuild proof, and Level-2 hands-off verification. All evidence must adhere to safety and governance rules.

Related Skills

Explore More Software Engineering Skills→
furqan90furqan90

local-prereq-check

Validate local development prerequisites and VPN reachability to corporate hosts.

Community
Intermediate
gaofeng21cngaofeng21cn
8

opl-completion-audit-writer

Audit OPL plan items against evidence to map completion statuses and flag blockers.

Community
Intermediate
intelli-verse-xintelli-verse-x
1

ivx-quality-gates

Automates quality gates for IntelliVerseX SDK projects in CI workflows.

Official
Advanced
simonheimlichersimonheimlicher
1

coding-autonomously

Automate end-to-end coding workflows from requirements to code and tests.

Community
Advanced