Description
An app with traffic.from_resource mints requests by StochasticRound of the queue’s served rate per tick, so its log lines and traces are a random draw around the rate rather than one per served event; the bound Lambda construct uses deterministic whole-event carries, so app logs and CloudWatch Invocations disagree in any window (found reviewing the private demo). Mint from_resource requests from the same whole-event carry the bound construct uses.
Acceptance Criteria
- #1 A from_resource app mints exactly the served events per window the bound construct counts
- #2 Apps without from_resource unchanged
Definition of Done
- #1 just check (fmt-check, lint, gen-check, env-check, docs-check, test, race, hygiene, ui-check, compose-check, helm-test, lab-check, signal-fidelity)
- #2 just gen (only if a blueprint field, construct/workload config struct, or a skill under plugins/synthkit/skills/ changed)
- #3 just dump — inventory diffed against signals/
Implementation Notes
loop58 residuals: carries align only from a common start (live may differ by one event per window until aligned); throttled functions count fewer invocations than minted requests by design; pause-resume asymmetry; span metrics still derive from served rate x interval.