BotV8 should keep each runtime workflow scoped to its selected profile and input material.
Isolation protects privacy evidence from cross-test contamination and keeps application behavior predictable. It also makes release comparisons easier because each run starts from a known policy and state boundary.
- keep session state scoped to the active workflow
- prevent unrelated profile material from affecting a run
- separate local evidence from runtime inputs
- avoid host-machine details when profile-backed behavior is expected
- make repeated runs comparable
Runtime isolation is most useful for:
- release checks
- support reproduction
- browser signal audits
- request-context generation
- profile-family compatibility tests
BotV8 public material should describe isolation as a privacy and quality control measure. It should not describe internal sandbox internals or low-level escape assumptions.