Skip to content

Council vNext: challenge-derived seats and proposal-only findings - #52

Open
Kitahl wants to merge 1 commit into
upgrade/challenge-vnext-mindfrom
upgrade/challenge-vnext-council
Open

Council vNext: challenge-derived seats and proposal-only findings#52
Kitahl wants to merge 1 commit into
upgrade/challenge-vnext-mindfrom
upgrade/challenge-vnext-council

Conversation

@Kitahl

@Kitahl Kitahl commented Aug 27, 2026

Copy link
Copy Markdown
Owner

Scope

Implements WO-011 from EGR-FOIL-INT-001 as a stacked change on the completed Mind/shared-neutral-challenge branch.

  • extend Council seats with challenge kind, discriminator, capability, target obligation, concrete refuter, reviewer provenance, and explicit legacy/vNext compatibility
  • derive deterministic review seats from unresolved neutral challenge classes
  • reject duplicate challenge kinds or discriminators unless evidence partitions are genuinely distinct
  • add structured Council findings bound to candidate, scope, obligation set, target module, target obligation, and seat contract
  • convert supported findings into proposal-only neutral ChallengeRequest objects with origin=COUNCIL
  • preserve commit-reveal, cross-critique, overlap diagnostics, and matched DIRECT control

Authority boundaries

  • Council receipts may clear only REVIEW obligations
  • Council cannot clear a target domain obligation, resolve its own proposed challenge, apply a repair, or authorize a write
  • emitted Council challenges begin in PROPOSED state and remain subject to the shared target-module challenge gate
  • nominal seat count and separate messages never establish statistical independence
  • no non-FOIL module imports foil_*; no FOIL bridge is included
  • this implementation makes no behavioral-efficacy claim

Compatibility

  • existing four-field CouncilSeat construction remains valid
  • historical Council state and receipt behavior remain readable
  • legacy and vNext seats cannot be mixed within one Council run
  • existing Council commit/reveal and control tests remain applicable

Validation

All required checks pass on clean Council commit 132172944c07de77c11266c953996fc1e840b647:

  • Research software validation: passed
  • Security gates: passed, including full-history secret scan, dependency audits, deterministic hash-lock regeneration, and exact locked installation
  • Runtime portability: passed on Ubuntu, macOS, and Windows
  • CodeQL: passed
  • complete repository suite: 500 tests passed
  • focused Council vNext suite: 8 tests passed
  • vNext typed-runtime validator: 40/40 passed
  • public showcase validator: 33/33 passed
  • lint and compile checks: passed

The Council delta is one commit over af8dc2621099dd4993272cbc9e623190ef23ca9c, changes four files, and contains no temporary workflow or trigger files.

Focused Council coverage

tests/test_council_challenge_seats.py covers:

  • distinct challenge questions and duplicate kind/discriminator rejection
  • concrete skeptic refuters
  • deterministic derivation from open challenges
  • supported finding to neutral Council challenge conversion
  • target-domain authority denial
  • structured finding requirement for vNext clearance
  • mandatory same-artifact/same-budget DIRECT control
  • same-model seats never labeled independent by count

Base: upgrade/challenge-vnext-mind at af8dc2621099dd4993272cbc9e623190ef23ca9c.

@Kitahl
Kitahl changed the base branch from upgrade/challenge-vnext-mind to main August 27, 2026 06:36
@Kitahl
Kitahl force-pushed the upgrade/challenge-vnext-council branch from 07c4565 to 1321729 Compare August 27, 2026 06:39
@Kitahl
Kitahl changed the base branch from main to upgrade/challenge-vnext-mind August 27, 2026 06:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant