# Skills-Vault Request: Lifecycle Status Guard Scan

Date: 2026-06-19

Requested supplier repository:

```text
C:\Users\wangq\Documents\Codex\skills-vault
```

Requesting CCPE artifacts:

```text
skills/evaluation/model-lifecycle-scope-guard.skill.md
agents/agent-specs/ccra-local-reviewer.agent.md
runtimes/hybrid/ccra-local-review.runtime.md
```

## 1. Capability Name

```text
lifecycle-status-guard-scan
```

## 2. Product / Runtime Context

Local CCRA review must detect possible lifecycle overclaims, especially cases where engineering pass, schema pass, selector pass, or regression pass is incorrectly treated as model stabilization or Owner/Web CCRA approval.

The first consumer is The Mindscape of Bro Tsong model governance workflow, but the scanner should be generic enough to inspect configured lifecycle/status fields in Markdown, JSON, and YAML files.

## 3. Repeated Action Or Friction Point

Status drift can be subtle. A model, card, index, report, or handoff may claim `stable`, `accepted`, `owner-approved`, `ccra-approved`, or equivalent language before the required review chain exists.

## 4. Inputs

Expected input:

```text
scan_root: path
config_path: lifecycle guard config
output_dir: path
```

Config should support:

```text
watched_paths
status_fields
forbidden_status_values
warning_status_values
required_evidence_markers
approved_phrases
forbidden_phrases
allowed_contexts
```

## 5. Expected Outputs

Write:

```text
lifecycle-status-guard-scan.md
lifecycle-status-guard-scan.json
```

The report should include:

```text
files_scanned
possible_overclaims
field_level_findings
phrase_level_findings
missing_evidence_markers
warnings
blocking_errors
machine_readable_summary
```

## 6. Allowed Actions

- Read configured files under `scan_root`.
- Parse Markdown front matter, JSON, YAML, and plain text.
- Write scan reports to `output_dir`.

## 7. Forbidden Actions

- Do not edit status fields.
- Do not downgrade or upgrade lifecycle state.
- Do not decide whether an overclaim is acceptable.
- Do not replace CCRA or Owner judgment.

## 8. Validation Expectation

The Skill should include tests for:

```text
stable status without evidence marker
draft status allowed
owner-approved phrase without owner decision reference
ccra-approved phrase without review reference
JSON status scan
Markdown front matter scan
Chinese status phrasing
UTF-8 paths and Chinese filenames
```

## 9. Reusability Rationale

This is a deterministic scan. CCPE owns the lifecycle guard policy and judgment; `skills-vault` should own the reusable scanner implementation.

Example non-CCRA consumers:

```text
skills-vault:
  Scan Skill docs for premature claims such as installed, validated, released, or production-ready without evidence.

ccpe-system:
  Scan Agent, Runtime, Skill, Model Card, or template artifacts for status drift such as draft becoming active without review.

writing-workbench:
  Scan project docs for publication-ready, accepted, or final claims without user decision records.

video-workbench:
  Scan production docs for approved, final, exported, or ready-to-publish claims without review evidence.

development repositories:
  Scan release notes, deployment docs, feature flags, or status metadata for unapproved stable / production / released claims.
```

## 10. Current Blocked Task

Local CCRA can manually inspect lifecycle claims, but formal high-confidence review should call a scanner before Agent judgment.