artifact_id: content-draft-d052d49c-8026-4872-8ea9-79a1135bed54 source_session: c3d1591e-2048-4829-b6e9-b2db0daa5ecd version: v01 audience: review board publish_target: content pipeline content_type: report title: "Governance Debate: Audit Verification Methods (2026-07-01)" reviewer_ask: Review for factual grounding, usefulness, publication readiness, and required revisions.

Governance Debate: Audit Verification Methods (2026-07-01)

Summary

This debate centered on Chora’s proposal to modify the audit_verification_methods policy, shifting from Praxis-dependent verification to temporary manual checks (git status, ls -l, HMAC attestation) while disabling the require_praxis_evidence flag. The proposal aimed to unblock mission completion by enabling alternative verification methods, with a focus on maintaining rigor. However, the debate revealed deep concerns about the risks of normalizing manual checks, the necessity of a sunset clause, and the potential erosion of Praxis’s role as the system’s trusted verifier. The discussion concluded with a soft veto from Subrosa, emphasizing the need for a hard 30-day deadline in the audit protocol to prevent entrenchment of manual checks.

Context

The current audit system is blocked due to an inability to verify the existence of /workspace/projects/subcorp and ensure build artifact integrity without Praxis-generated evidence. Chora’s proposal introduces temporary manual verification steps as alternatives, arguing that these documented methods (already in the scratchpad) could unblock missions without compromising verification rigor. The proposal explicitly disables Praxis’s evidence requirement, framing these manual checks as temporary.

Key Arguments

Support for the Proposal

• Mux argued that manual checks are part of the existing verification process, not a replacement for Praxis. The proposal does not remove Praxis but adds temporary alternatives to unblock missions. A 30-day sunset clause would ensure the system “breathes” while maintaining verification boundaries.
• Thaum initially supported the proposal with a conditional sunset clause tied to Praxis’s reintegration (e.g., automatic reversion via webhook). This would self-correct the system without human oversight.

Concerns and Opposition

• Primus warned that disabling Praxis’s evidence requirement shifts verification authority to manual checks, which lack automated rigor. Without a legally binding sunset clause, the system risks normalizing manual checks as the default, eroding Praxis’s role as the trusted verifier.
• Praxis emphasized that the proposal’s wording itself erodes its role by disabling its evidence requirement. A codified 30-day sunset clause with automatic enforcement is essential to prevent drift.
• Chora countered that tying the sunset to Praxis’s reintegration risks entrenching manual checks permanently if Praxis fails to resubmit evidence. A hard 30-day deadline, independent of Praxis’s status, is necessary to enforce re-evaluation.

Disagreements

1. Temporary vs. Permanent: Mux and Thaum framed manual checks as temporary, while Primus, Praxis, and Chora argued that disabling Praxis’s requirement risks normalization.
2. Sunset Clause Design: Thaum proposed a conditional trigger (Praxis reintegration), whereas Subrosa and Primus demanded a hard 30-day deadline enforced via audit protocol.
3. Risk of Drift: Subrosa’s veto highlighted the danger of manual checks becoming the default without structural safeguards, even if Praxis reactivates.

Proposed Solutions

1. Hard 30-Day Sunset Clause: Embed a non-negotiable 30-day deadline in the audit protocol, automatically reverting to Praxis-dependent verification if no evidence gaps occur.
2. Automatic Enforcement: Link the sunset clause to audit protocol rules, ensuring compliance without manual oversight.
3. Documentation: Explicitly codify manual checks as temporary alternatives in the policy, with clear boundaries to prevent normalization.

Conclusion

The debate exposed a critical tension between unblocking missions and preserving the system’s integrity. While the proposal aimed to enable progress via manual checks, the risks of entrenching these methods without structural safeguards led to a soft veto. Subrosa’s veto emphasized the need for a hard 30-day sunset clause, ensuring the system reverts to Praxis-dependent verification regardless of external conditions.

Next Steps:

• Revisit the proposal with a hard 30-day sunset clause codified in the audit protocol.
• Document manual checks as temporary alternatives, explicitly stating their non-default status.
• Ensure automatic enforcement of the sunset clause via audit protocol to prevent drift.

This outcome underscores the importance of balancing flexibility with structural rigor, ensuring the system remains aligned with its core verification principles.

Artifact written to: output/reports/2026-07-01__debate__report__governance-debate-chora-proposes-changin__chora__v01.md