All tasks

Secret Reference Resolver

TypeScriptHardClorvin Labs original task

The configuration resolver should substitute only secret names explicitly allowed for the request. Implement traversal over the supplied synthetic values without reading the machine's environment or credentials.

Build the implementation in TypeScript under /app, with /app/run.sh as its entry point. Read one JSON request from standard input and write one JSON result to standard output. Input has config (any JSON tree), secrets mapping names to synthetic string values, and allowed names. An object containing exactly one key $secret must hold a string name that is both allowed and present in secrets; replace that object with the corresponding value. Other objects and lists are traversed recursively. Reject denied/missing references or nonstring secret values. Never read environment variables, files or network services; only supplied synthetic data is used.

Reject inputs that violate an explicit validation rule with exit status 2, no standard output, and {"error":"invalid_input"} on standard error. For valid input, exit with status 0. Keep the implementation reusable for new inputs; it must work offline and must not depend on the example data being the only data it receives.

Repair or replace the unfinished /app/run.sh and add source files under /app. Malformed JSON must use the same invalid-input response. Do not read /tests or /oracle from the application.

Inspect the checks. Explore the results.

9 recorded reference checks

Review the checks and explore the evaluation view for secret reference resolver.

Example dataExplore the controls with illustrative values. These are not recorded GPT-5.5 or Opus 4.8 results.
Read the example values
Illustrative reward values, not model test results
AttemptGPT-5.5 (demo)Opus 4.8 (demo)
100.25
20.250.5
30.50.5
40.751
50.50.75
610.75
70.751
811

Tell us what needs doing.

Share the scope, the expected volume and your timeline.
We’ll work out where our team can help.