feat: verify bit encoding consistency #23
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Slipstream/emc!23
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/verify-bit-encoding-consistency"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
quint.json,emc verify, and MCP verify process plans.emc checkreports drift if the new obligations are missing from generated artifacts.Rationale
Information completeness requires data-flow facts to preserve bit-level semantics at the point where data is presented or crosses an external boundary. The formal artifacts already required non-empty bit encodings and modeled data-flow coverage; this change makes the Lean4 and Quint artifacts mechanically compare those encodings for view and external payload targets.
Verification
cargo nextest run init_creates_deterministic_project_layout --no-tests=failcargo fmt --check && cargo nextest run -E 'binary(init_project) | binary(check_project) | binary(verify_project) | binary(mcp_verify)' --no-tests=fail && cargo build --quiet && git diff --checknix develop -c sh -lc 'cd <generated-smoke-project> && lake env lean model/lean/RepairDesk.lean && quint typecheck model/quint/RepairDesk.qnt && quint verify --invariant modelViewFieldBitEncodingsMatchDataFlows,modelExternalPayloadFieldBitEncodingsMatchDataFlows,modelMeaningfulDataFlowsAreCovered model/quint/RepairDesk.qnt'UTF-16 stringcaused Lean to fail atmodelViewFieldBitEncodingsMatchDataFlowsand Quint to report a counterexample formodelViewFieldBitEncodingsMatchDataFlows.The PR introduces new invariants to ensure bit encoding consistency between displayed view fields, external payload fields, and their corresponding data-flow rows. The changes are integrated into the verification process and tested for correctness. The modifications appear safe to merge.
Walkthrough
quint.json.LLM usage and cost
Estimated total USD: $0.096217 via https://api.openai.com and https://api.openai.com