Development capture and storage
Normal user mode leaves the development subsystems dormant. An API consumer cannot override the user's INI ceiling.
Permission layers
- INI mode: User, Observe, Harvest or Capture.
- Cache policy: Off, ReadOnly or ReadWrite.
- Allowed scope mask derived from those settings.
AllowApiActivation, which decides whether API demand may wake dormant work.- A consumer lease requesting an allowed subset for 1–1200 frames.
INI auto-start is separate. If API activation is disabled, both explicit capture leases and older high-cost capability demand remain unable to wake the work.
Scope meaning
| Scope | Work |
|---|---|
PassiveObservation | Passive reload/animation observation. |
ExactAnimationHarvest | Exact off-screen weapon clip sampling. |
WeaponMotionCompilation | Compile value-only motion paths. |
CompiledCacheRead | Read validated compiled records. |
CompiledCacheWrite | Persist compiled records. |
LiveMotionLearning | Learn strokes from native observations. |
The 128 MiB sample budget bounds raw in-process animation evidence. Persistent storage contains compiled value-only motion paths, not native graphs or the raw sample catalog. ReadOnly never creates directories/files, touches timestamps, prunes, or writes.
An authoring UI should show allowed, requested, active and denied scopes; lease
remaining; preharvest progress; sample bytes; clip/part/stage counts; persistent
records; and pending writes. PermissionDenied is a valid user policy result.
Ship capture disabled, renew a short lease while the authoring session is open, and clear it immediately on close/reset/shutdown.