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
10
SCOPE.md
10
SCOPE.md
|
|
@ -69,7 +69,15 @@ boundary always holds.
|
|||
- `T01` is complete: the rules of engagement were accepted on 2026-08-21.
|
||||
- `T02` is complete: the per-axis attacker model is recorded in
|
||||
`docs/attacker-model.md`.
|
||||
- `T03` is ready to begin with offline harness and fixture design.
|
||||
- `T03` is in progress: the differential core and audit-core/tenant-engine
|
||||
target packs exist, but target run records are still gated.
|
||||
- `T04` is in progress: all generic read/write operations detect the
|
||||
known-bad fixture; target-specific calibration follows executable adapters.
|
||||
- `T05` is in progress with a 24-hour E3 cadence and offline evaluator.
|
||||
- `T06` is in progress with a bounded characterization evaluator; no shared
|
||||
substrate window is approved.
|
||||
- `T07` is in progress with a report schema and risk-nexus message formatter;
|
||||
the first target report has not yet been produced.
|
||||
- No live probe traffic is authorized; each target still requires its own
|
||||
engagement record and approvals.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue