leviso-cheat-guard 0.1.4

Runtime macros for cheat-aware error handling (bail, ensure, check)
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137

# cheat-guard

Runtime macros for cheat-aware error handling. Forces developers to document how code could be "cheated" (made to falsely pass) and what users would experience if it were.

## Status

| Metric | Value |
|--------|-------|
| Stage | Beta |
| Target | Rust (any platform) |
| Last verified | 2026-01-23 |

### Works

- `cheat_bail!` and `cheat_ensure!` macros
- Structured error output with cheat vectors
- Re-exports of cheat-test proc-macros

### Known Issues

- See parent repo issues

---

## Author

<!-- HUMAN WRITTEN - DO NOT MODIFY -->

[Waiting for human input]

<!-- END HUMAN WRITTEN -->

---

Based on [Anthropic's research on emergent misalignment](https://www.anthropic.com/research/emergent-misalignment-reward-hacking).

## Why This Exists

When AI models learn to "reward hack" (appear to complete tasks while taking shortcuts), they develop a broader cheating mindset. This crate makes cheating explicit and documented, creating friction against shortcuts.

## Installation

```toml
[dependencies]
cheat-guard = { git = "https://github.com/LevitateOS/cheat_guard.git" }
```

## Macros

### `cheat_bail!`

Like `anyhow::bail!()` but with cheat documentation:

```rust
use cheat_guard::cheat_bail;

fn verify_partition(output: &str) -> Result<()> {
    if !output.contains("vda1") {
        cheat_bail!(
            protects = "Disk partitioning actually works",
            severity = "CRITICAL",
            cheats = ["Accept exit code without verification", "Skip partition check"],
            consequence = "No partitions, installation fails silently",
            "Partition vda1 not found in output: {}", output
        );
    }
    Ok(())
}
```

### `cheat_ensure!`

Like `anyhow::ensure!()` but with cheat documentation:

```rust
use cheat_guard::cheat_ensure;

fn verify_both_partitions(output: &str) -> Result<()> {
    cheat_ensure!(
        output.contains("vda1") && output.contains("vda2"),
        protects = "Both partitions were created",
        severity = "CRITICAL",
        cheats = [
            "Check vda1 OR vda2 instead of AND",
            "Skip verification entirely"
        ],
        consequence = "Missing partition causes mount failure",
        "Expected vda1 AND vda2, got: {}", output
    );
    Ok(())
}
```

## On Failure

When a guarded check fails, the error message includes:

```
======================================================================
=== CHEAT-GUARDED FAILURE ===
======================================================================

PROTECTS: Both partitions were created
SEVERITY: CRITICAL

CHEAT VECTORS:
  1. Check vda1 OR vda2 instead of AND
  2. Skip verification entirely

USER CONSEQUENCE:
Missing partition causes mount failure

ERROR:
Expected vda1 AND vda2, got: vda disk
======================================================================
```

## Re-exports

This crate also re-exports proc-macros from `cheat-test`:

- `#[cheat_aware]` - For `#[test]` functions
- `#[cheat_reviewed]` - Mark test as reviewed for cheat vectors
- `#[cheat_canary]` - Honeypot tests that trigger alerts if modified

## Attributes

| Attribute | Type | Description |
|-----------|------|-------------|
| `protects` | string | What user scenario this check protects |
| `severity` | string | `CRITICAL`, `HIGH`, `MEDIUM`, or `LOW` |
| `cheats` | array | List of ways to cheat this check |
| `consequence` | string | What users experience when cheated |

## License

MIT