Council Motion Amendment History — DEFONEOS BFT Council

1. Amendment Ledger — Status Distribution

Acceptance rate 86.6%. No rejections — proposer withdraw path preferred (R5 re-proposes with red-line vector instead of forcing floor vote). All accepted amendments folded into motion text and re-issued SIGIL with supersession pointer.

2. Proposer Ring Distribution (R1-R5)

R1 owner-seat is a cosign-gate (mandatory for all 142 motions, never amended — by doctrine). R2 founders propose most (43.7%) and have highest acceptance rate. R5 observers can propose but cannot amend their own proposals during the same session.

3. Motion Class × Amendment Cross-Tab

UNANIMOUS and EMERGENCY classes are by-design unamendable on the floor (UNANIMOUS requires full body pre-coordination; EMERGENCY has 24h sunset). REDLINE motions have highest amend rate (57.9%) — vector addition is the dominant mechanism for sharpening scope.

4. Red-Line Amendment Audit Trail (3 red-line amendments)

All 3 red-line amendments passed with +29, +28, +31 margins (well above 27/33 quorum). Each was proposed by a different ring (R5, R4, R3), demonstrating cross-ring engagement. Each red-line vector is embedded into the sealable MCP corpus and verified by per-MCP red-line scan (see sbom-deep-dive).

5. Last 10 Motions — Amendment Footprint

10/10 last motions carried with owner cosign. 6/10 had at least one accepted amendment. UNANIMOUS motions (3 in window) never amended on the floor — pre-coordinated off-floor per doctrine.

6. Amendment Type Taxonomy (top 8)

7. Withdrawn / Superseded — Full List (9)

Withdrawals tend to be technical pivots (proposer chooses alternate path). Superseded motions are typically policy refinements with a sharper follow-up motion in the same session.

8. 5-Step Curl Verification Loop (runnable on buyer VM)

# Step 1: HEAD check freshness <24h SLA
curl -sI https://www.csoai.org/defoneos-council-motion-amendment-history.html | head -1

# Step 2: GET and verify SHA-256 in SIGIL matches body
curl -s https://www.csoai.org/defoneos-council-motion-amendment-history.html -o /tmp/amend.html
curl -s https://www.csoai.org/sigils/tick-125-sigil.json | jq -r '.pages["defoneos-council-motion-amendment-history"].sha256'
shasum -a 256 /tmp/amend.html | awk '{print $1}'

# Step 3: Cross-check totals — 142 motions, 67 amended, 58 accepted
grep -E "Total motions|Amended|ACCEPTED" /tmp/amend.html | head -5

# Step 4: Verify 3 red-line amendments present (A-RL-001..003)
grep -E "A-RL-00[123]" /tmp/amend.html

# Step 5: Verify owner cosign block
grep -E "R1 owner-seat|cosign" /tmp/amend.html | head -3
# Expected: all 142/142 motions carry owner cosign

Single-script buyer VM suite runs <60s on fresh VM. PASS expected: HEAD 200 + SHA-256 match + 3 red-line IDs present + 142/142 owner cosign. See buyer-evidence-acceptance-test-drilldown.

9. Cross-Reference Map

10. Red-Line Invariants (this page satisfies)

1. 142/142 owner cosign — every motion has R1 owner-seat signature.
2. 3 red-line amendments traceable — A-RL-001/002/003 with proposer ring, vote tally, effective date.
3. 0 rejections on the floor — withdrawal path preferred (doctrine), preserving proposer agency.
4. UNANIMOUS + EMERGENCY unamendable on floor — verified by class × amend cross-tab.
5. Owner veto never exercised — 0/142 motions required owner veto (cosign-gate sufficient).
6. Cross-ring engagement on red-line — A-RL-001 R5, A-RL-002 R4, A-RL-003 R3.
7. SIGIL supersession chain — accepted amends re-issue motion SIGIL with supersession pointer.