Council v3: seat-local smart evidence acquisition - #53
Open
Kitahl wants to merge 1 commit into
Open
Conversation
Kitahl
force-pushed
the
upgrade/challenge-vnext-council-v3
branch
from
August 27, 2026 08:49
13e6eac to
7fcfd25
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scope
Implements Council v3 as an additive layer over the completed Council vNext branch.
foil_*FOIL boundary
The Smart-Tool update is proposed/unvalidated and no smart-tool implementation exists in the repository yet. Council v3 therefore does not depend on or import FOIL internals. A future FOIL controller may supply neutral
EvidenceBundleCandidaterows only; Council retains its frozen utility policy, evidence admission, review authority, and target-module handoff.Authority
EVIDENCE_ACQUISITION_ONLYValidation
The exact Council v3 tree
5a606e97c09e44493422e9d6b9cf1f24ee94b862was validated through tree-identical CI trigger commit13e6eac226fde531026697a48b0039dd024954bd, then the branch was restored to the clean one-commit implementation7fcfd259a6b103a464061c1d30f2a48fa1ff7f52.All required checks passed:
Focused Council v3 coverage
tests/test_council_v3_evidence.pycovers:Base:
upgrade/challenge-vnext-councilat132172944c07de77c11266c953996fc1e840b647.