[milestone Milestone 5 ] Multi-tenant isolation — introduce tenant-scoped trace segregation (by organiz...

[telleroutlook]

🤖 Auto-filed from milestone doc bullet.

Repo: WasmAgent/trace-pipeline
Milestone: Milestone 5 — Production Trace Pipeline at Scale
Bullet:

Multi-tenant isolation — introduce tenant-scoped trace segregation (by organization/team boundaries), per-tenant resource quotas, and audit-grade access logging for compliance consumers.

Relevant code context (from worktree)

new (does not exist yet): organization/team
contains 'multi': scripts/train_dpo.py
contains 'multi': scripts/train_sft.py
contains 'multi': evomerge/context_compile/compiler.py
contains 'isolation': evomerge/trust_score.py
contains 'isolation': evomerge/security/benchmark_linter.py
contains 'isolation': eval_trust/exploit_surface.py

Implementation note: Files marked "new (does not exist yet)" must be created from scratch. verify-first should return PROCEED (not NOT_YET) — there is no prerequisite blocking this work.

Acceptance criteria

• Command pip install -e . && python -m pytest passes
• The specific work described in the bullet above is implemented in the smallest number of files required.
• No unrelated files touched (git status --short output limited to the intended change).

Notes for the implementer

This issue was auto-created by SweepMilestoneBulletToIssue. The bullet text is verbatim
from the milestone doc. If ambiguous or too large for a single implement cycle,
verify-first should return NEEDS_SPLIT with sub-issue proposals or NEEDS_HUMAN with the blocker.

---

Filed automatically.

[telleroutlook]

Verify-first found this issue is already implemented at evomerge/multi_tenant.py:1. Closing without spawning implementation work.