Build authorization-gated tenancy evidence harness
Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a0260c-4067-7052-9647-ad000d576e38
This commit is contained in:
parent
2c8e1d41ad
commit
beab2a04d1
32 changed files with 1816 additions and 11 deletions
15
README.md
15
README.md
|
|
@ -25,3 +25,18 @@ probes most worth having are the ones an author would not think to write.
|
|||
- Attacker model: [`docs/attacker-model.md`](docs/attacker-model.md)
|
||||
- Rules of engagement (accepted; live targets still require engagement approval):
|
||||
[`docs/rules-of-engagement.md`](docs/rules-of-engagement.md)
|
||||
- Operator runbook: [`docs/operator-runbook.md`](docs/operator-runbook.md)
|
||||
- Target packs: [`probe-packs/`](probe-packs/)
|
||||
|
||||
## Offline calibration
|
||||
|
||||
```sh
|
||||
make check
|
||||
make fixture-evidence
|
||||
```
|
||||
|
||||
This proves that every current differential probe passes an enforcing fixture
|
||||
and detects the corresponding missing-tenant-predicate fixture. It sends no
|
||||
network traffic and is not evidence about a target service. Live execution
|
||||
requires a current target-specific record based on
|
||||
[`engagements/template.json`](engagements/template.json).
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue