FA-10354 / Observability / Member archive

Structured telemetry field redaction: Redacted telemetry fields retain arbitrary insertion order · case 04

Redacted telemetry fields retain arbitrary insertion order.

Member previewVariant 4 · 3 implementations · 7 checks per implementation

Case contract

Remove forbidden keys, replace sensitive field values with REDACTED, truncate long public string values, preserve nonstring values, and return keys in lexical order. Forbidden removal dominates sensitive replacement.

Why this case matters

An offline model of structured telemetry field redaction, suitable for testing build and release tooling without external services.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
fixture 2	`[["b", "hel"], ["a", "xy"]]`	`[["a", "xy"], ["b", "hel"]]`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.