docs: align Capture lifecycle and canonical quickstart - #10
Conversation
- Split the summary policy binding into acceptance_policy_sha256 (pinned private acceptance policy digest) and lifecycle_policy_sha256 so the two authorities cannot be collapsed into one field. - Replace the free-form condition inventory with a closed qualification contract: campaign contract/outcome digests, a task-condition inventory digest, and a zero excluded-trial count. - Domain-separate the target release and artifact inventory digests so a digest cannot be replayed across targets or claim scopes. - Accept millisecond UTC retention timestamps, matching the canonical form the private acceptance certificate records; refuse any other precision. - Apply minimum_trials_per_condition to observed trials, and keep the policy floor of three on required trials per condition. - Keep governed-repair model calls informational while refusing any healthy-path model call through the failure taxonomy. - Keep this PR mechanism-only: restore the profile README and keep Capture's public label Experimental (the Beta relabel stays in draft PR #10 until the final evidence lands). All Production memberships and admission lists remain empty. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* feat: gate Production lifecycle on acceptance evidence * feat: harden Production lifecycle admission * feat: bind acceptance policy and keep the lifecycle PR mechanism-only - Split the summary policy binding into acceptance_policy_sha256 (pinned private acceptance policy digest) and lifecycle_policy_sha256 so the two authorities cannot be collapsed into one field. - Replace the free-form condition inventory with a closed qualification contract: campaign contract/outcome digests, a task-condition inventory digest, and a zero excluded-trial count. - Domain-separate the target release and artifact inventory digests so a digest cannot be replayed across targets or claim scopes. - Accept millisecond UTC retention timestamps, matching the canonical form the private acceptance certificate records; refuse any other precision. - Apply minimum_trials_per_condition to observed trials, and keep the policy floor of three on required trials per condition. - Keep governed-repair model calls informational while refusing any healthy-path model call through the failure taxonomy. - Keep this PR mechanism-only: restore the profile README and keep Capture's public label Experimental (the Beta relabel stays in draft PR #10 until the final evidence lands). All Production memberships and admission lists remain empty. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
HOLD -- do not merge until the acceptance evidence exists. This is the visible maturity-label change for Capture, isolated so it can ship as one action under the one-visible-change-at-the-end rule. The stale-fact half of this branch (the canonical launcher quickstart) merged separately in #12 and is already on main. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
fb55714 to
4f9d62d
Compare
Split: the stale-fact half merged, the relabel is heldReviewed under the rule that no visible maturity label changes until the acceptance evidence exists (one visible change at the end). Merged as #12 (
One correction was made while merging: the description said the quickstart "lints". It does not. Held on this branch (
The current decision is that Capture goes straight from Experimental to Production once its evidence passes, so a Beta step is a holding step. Keep this branch only if that decision changes. Dropped, not carried onto the held branch:
|
What changed
openadapt-capturefrom Experimental to Beta in the canonical lifecycle registryWhy
The old registry and profile caused search systems to describe the complete Capture package as Experimental. The old quickstart also bypassed the supported launcher path. These statements did not match the released component role or the target product path.
The repository lifecycle label does not replace production readiness. The target product supports production-qualified workflows through exact evidence, verification, and deployment contracts. Capture's custom Chrome extension remains a separate prototype component.
Validation
python scripts/check_profile.pygit diff --checkorigin/main