Make runtime faults useful without leaking input values
Fault logs dump the full operand stack, which may later contain customer-derived values, while omitting the bytecode revision needed for diagnosis.
- Focused work estimate
- 4h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Observability · Data minimization
Estimated field mix
- Systems programming70%
- Privacy engineering30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional rules engine executes a tiny arithmetic bytecode over synthetic integers. Its interpreter trusts jump offsets and can run forever. Build a local Rust runtime; it has no filesystem, network, dynamic loading, host calls, or candidate-source execution.
Setup prerequisites
- Stacks
- Instruction decoding
- Control flow
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- SRUNTIME-101 · Decode instructions without reading past the bytecode buffer
- SRUNTIME-104 · Report integer overflow instead of changing arithmetic by build mode
- SRUNTIME-102 · Validate stack depth across both sides of a branch
- SRUNTIME-103 · Reject jumps that land inside instruction operands
- SRUNTIME-105 · Stop infinite programs with a deterministic instruction budget
Acceptance criteria
- Fault records contain code, instruction offset, runtime version, and bounded trace identity
- Operand values and full program bytes are excluded
- Repeated identical faults aggregate under bounded dimensions
Implementation constraints
- Use synthetic values in the exercise and keep generic analytics content-free.
Verification to include
- Produce each fault class and reconcile its diagnostic fields.
- Push a sentinel value and confirm it appears in no log or metric.
Deliverables
- Redacted runtime fault schema and tests
Rollout and recovery
Replace verbose stack dumps before adding any non-synthetic inputs.
Value of the work
For the engineer: Practice runtime invariants, validation, resource accounting and compatibility.
For the team: Review a constrained execution component whose malformed programs fail deterministically without gaining host capabilities.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.