--- artifact_type: ccpe-skill name: Model Lifecycle Scope Guard skill_id: model-lifecycle-scope-guard author: CCPE System version: 0.1.0 created: 2026-06-19 updated: 2026-06-19 status: draft skill_type: evaluation target_platform: Codex / platform-neutral Markdown related_models: - qpi-front-routing-boundary related_agents: - ccra-local-reviewer related_runtimes: - ccra-local-review based_on: CCPE System --- # Model Lifecycle Scope Guard ## 1. Purpose Provide a reusable judgment method for detecting lifecycle overclaims, round-scope drift, and authority confusion in cognitive model governance work. This Skill defines review rules. Deterministic scanning for status fields belongs in `skills-vault` as `lifecycle-status-guard-scan`. ## 2. Skill Type ```text evaluation ``` ## 3. Trigger Conditions Use when review material claims or implies: ```text stable accepted approved owner-reviewed ccra-approved round closed ready for Web final review model upgraded selector validated regression sufficient ``` ## 4. Input Contract ```yaml claim_text: claim_location: round_goal: project_lifecycle_rules: engineering_evidence: content_evidence: selector_evidence: regression_evidence: owner_decision_reference: web_ccra_reference: local_ccra_reference: ``` ## 5. Output Contract ```yaml claim_type: allowed_authority: actual_authority_present: evidence_sufficient: true | false overclaim_risk: none | low | medium | high | blocking recommended_classification: blocker | major | minor | calibration | defer recommended_action: ``` ## 6. Core Rules ### 6.1 Engineering Evidence Is Not Lifecycle Authority Passing tests, schema validation, selector demos, or regression gates can support a claim, but cannot alone promote model lifecycle status. ### 6.2 Local CCRA Is Not Owner Approval Local CCRA may recommend readiness, identify blockers, and advise local tuning. Owner approval is still required before findings become accepted work or lifecycle status changes. ### 6.3 Local CCRA Is Not Web CCRA Final Review Local CCRA may prepare the project for Web CCRA final review. It must not label itself as Web CCRA approval. ### 6.4 Round Scope Controls Work Do not force future calibration, third-model design, LLM selector design, platform behavior, or product-system architecture into a round whose goal is narrower. ### 6.5 QPI Boundary QPI remains a front-routing / misframing-diagnostic model. Do not convert it into an intervention model or generic psychological advice system during review. ### 6.6 The Mindscape Governance Boundary The Mindscape of Bro Tsong is the engineered model-governance system for the user's cognitive model library. CCPE model-card and model-index assets may inform structure, but should not be treated as the future canonical governance store for this product's model library. ## 7. Procedure ```text 1. Extract the claim. 2. Identify whether the claim concerns engineering, content, selector behavior, regression, lifecycle, Owner approval, or Web CCRA approval. 3. Identify the authority required for that claim. 4. Check whether the required authority is present and cited. 5. Check whether the evidence type matches the claim type. 6. Identify whether the claim belongs to the current round. 7. Classify overclaim risk. 8. Recommend repair, deferral, calibration, or Owner/Web escalation. ``` ## 8. Branch Logic ```text If a lifecycle claim lacks Owner or required CCRA authority: classify as high or blocking overclaim. If engineering evidence is used to support an engineering claim only: no overclaim unless wording implies content/lifecycle acceptance. If a future policy issue appears in the current round: classify as calibration or defer. If Local CCRA readiness is phrased as Web final approval: classify as blocker. ``` ## 9. Stop Conditions Stop when the claim's authority, evidence sufficiency, overclaim risk, and recommended action are recorded. ## 10. Failure Handling If required authority cannot be found, treat the claim as unproven. Do not infer Owner or Web CCRA approval from silence. ## 11. Validation Checklist ```text Claim located? Claim type identified? Required authority identified? Actual authority cited? Engineering vs product judgment separated? Local CCRA vs Owner vs Web CCRA separated? Round scope considered? Recommended action provided? ``` ## 12. Related Automation Planned deterministic scanner: ```text requirements/skills-vault/2026-06-19-lifecycle-status-guard-scan.md ``` ## 13. Version Notes ```text v0.1.0: - Initial lifecycle and scope guard method for Local CCRA review. ```