# CAVRA Customer Lifecycle Phase 8 Public Scorecard Monitoring Second-Cycle Activation Closeout

The customer lifecycle Phase 8 public scorecard monitoring second-cycle
activation closeout packet is the R7.41 release gate for proving that the
second public scorecard monitoring cycle has actually started. It closes out
activation only when the cycle is live, first signals are captured, monitors
ran, alert routes were checked, evidence is archived, and owners accepted the
activation state.

The packet consumes the R7.40 public scorecard monitoring second-cycle readiness
packet and validates cycle-start refs, initial-signal refs, monitor-run refs,
alert-route check refs, activation archive refs, owner activation
acknowledgement refs, CI gate coverage, and explicit second-cycle activation
controls.

It does not embed customer names, email addresses, recipient addresses, raw
monitor payloads, raw alert payloads, raw on-call rosters, raw escalation
records, raw signal payloads, raw monitor-run records, raw public status
records, customer health scores, private notes, pricing, contract values,
renewal amounts, raw contracts, legal terms, secrets, tokens, or commercial
terms.

## What It Verifies

- The R7.40 public scorecard monitoring second-cycle readiness packet is live,
  sanitized, ready, and blocker-free.
- Executive, communications, customer-success, security, product, web,
  compliance, audit, and operations owner refs are present.
- The second-cycle activation contract includes source readiness, cycle start,
  initial signal capture, monitor run, alert route check, evidence archive,
  owner activation acknowledgement, and redaction-status fields.
- Cycle-start refs prove the activation window, second-cycle start decision,
  operating calendar, and review cadence start are in place.
- Initial-signal refs prove scorecard health, link health, archive freshness,
  and redaction posture signals were captured through public-safe references.
- Monitor-run refs prove the scorecard, link, archive, and redaction monitors
  executed for the new cycle.
- Alert-route check refs prove alert smoke tests, escalation route
  acknowledgement, on-call acknowledgement, and the no-dead-route assertion.
- Activation archive refs prove the activation manifest, initial-signal
  archive, monitor-run archive, alert-route archive, and immutable activation
  archive exist.
- Owner activation acknowledgement refs prove operations, security,
  communications, and audit accepted the activation state.
- CI gate coverage exists for source second-cycle readiness, cycle start,
  initial signal capture, monitor run, alert route check, evidence archive,
  owner activation acknowledgement, and public-safe activation validation.

## Generate Examples

```bash
python3 scripts/validate_customer_lifecycle_phase8_public_scorecard_monitoring_second_cycle_activation_closeout.py \
  --export-dir examples/customer-lifecycle-phase8-public-scorecard-monitoring-second-cycle-activation-closeout \
  --repo-root .
```

## Validate Second-Cycle Activation Closeout

```bash
python3 scripts/validate_customer_lifecycle_phase8_public_scorecard_monitoring_second_cycle_activation_closeout.py \
  --packet examples/customer-lifecycle-phase8-public-scorecard-monitoring-second-cycle-activation-closeout/customer-lifecycle-phase8-public-scorecard-monitoring-second-cycle-activation-closeout.live.sanitized.example.json \
  --repo-root . \
  --require-live
```

Completion condition:

```json
{
  "ready_for_customer_lifecycle_phase8_public_scorecard_monitoring_second_cycle_activation_closeout": true,
  "blocker_count": 0,
  "warning_count": 0
}
```

The same gate is available through the CLI:

```bash
PYTHONPATH=src python3 -m cavra.cli release customer-lifecycle-phase8-public-scorecard-monitoring-second-cycle-activation-closeout \
  --packet examples/customer-lifecycle-phase8-public-scorecard-monitoring-second-cycle-activation-closeout/customer-lifecycle-phase8-public-scorecard-monitoring-second-cycle-activation-closeout.live.sanitized.example.json \
  --repo-root . \
  --require-live
```

## Public Repository Boundary

The public repository provides the second-cycle activation closeout contract,
examples, validator, CLI command, tests, docs, and CI workflow. Real signal
payloads, monitor-run records, alert route internals, on-call rosters,
customer identities, secrets, tokens, pricing, schedules, and commercial
context remain deployment-specific.