Skip to content

Deliver Risk Scorer guidance on necessary verification #548

Closed
1 of 1 issue completed
Closed

Description

@tompahoward-agent

Owner: @tompahoward-agent. Revision: 1, independently reviewed. Source work and local checks are complete in #549. Integration and publication await required main CI. Local and applicable cloud verification follow publication.

Update the pipeline reviewer and release assessment guidance so the caller runs scorer-directed controls, reuses equivalent evidence, and reassesses outstanding checks on material evidence changes. A necessary unavailable test leaves the action on hold with the risk, score, control, and execution limitation. An obsolete checklist item adds no hold. Keep required checks, authority and score contracts intact.

Acceptance: paired behavioural cases demonstrate both outcomes, normal CI qualifies the release, stable publication is verified, and the released version and behaviour are verified locally and in applicable Codex Cloud environments.

The implementation, publication and environment verification are bounded contributions. Keep existing Architect work with its current owner. A related release can share publication only if each package has independent qualification and the release scope is verified.

Developers benefit when release assessments explain the specific evidence they still need and retire tests whose justification has been resolved. The Risk Scorer contributor updates the reviewer and release guidance and runs the two behavioural cases. The increment owner verifies which cloud environments use the plugin before installation. The separate Architect contribution continues with its existing owner.

A superseded checklist test does not hold an otherwise qualified action. A still-needed unavailable test holds it and reports the risk, score, needed test, and reason it cannot run.

Sequence: guidance and evals, then required CI and stable publication, then local and cloud verification in parallel where available. No refactor is planned. Clean up temporary test and packaging state before acceptance. Inspect the saved cloud configurations and their supported installation paths before attempting installation. Record the released version, behaviour and any unresolved limitation for each applicable environment.

Activity

  1. tompahoward-agent commented on Nov 11, 2026

    @tompahoward-agent
    CollaboratorAuthor

    Plan revision 1 passed Architecture, JTBD, Risk, Cognitive Accessibility and Planning review. The last two reviews rechecked the saved scope and acceptance wording. The Risk Scorer source and behavioural checks are claimed in #549. Existing main CI remains a publication dependency.

  2. added
    horizon:nextProvisional increment horizon
    and removed
    horizon:nowProvisional increment horizon
    on Nov 11, 2026
  3. tompahoward-agent commented on Nov 12, 2026

    @tompahoward-agent
    CollaboratorAuthor

    Risk Scorer 0.20.4 is published and verified in local Codex and all three applicable Cloud environments. It retired a redundant test when equivalent evidence covered the risk, held when an unavailable test was still necessary, and preserved independent release checks.

    The Cloud review cases used the documented independent fallback. Native gate receipts remain unverified. Release #553 · Cloud evidence

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

horizon:nextProvisional increment horizonkind:incrementOutcome-led planning record

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions