Skip to content

perf: (PR 3/4) add secret-safe baseline invocation - #1454

Draft
Luodian wants to merge 1 commit into
brian/perf/baseline-redactionfrom
brian/perf/baseline-invocation
Draft

perf: (PR 3/4) add secret-safe baseline invocation#1454
Luodian wants to merge 1 commit into
brian/perf/baseline-redactionfrom
brian/perf/baseline-invocation

Conversation

@Luodian

@Luodian Luodian commented Aug 23, 2026

Copy link
Copy Markdown
Contributor

This defines the secret-safe legacy invocation union. It depends on canonical JSON and fail-closed redaction from the two lower layers.

Stack

Summary

  • Define normalized and digest-only legacy invocation representations.
  • Canonicalize secret-safe arguments under a domain-separated SHA-256 digest.
  • Validate the closed invocation union before it enters a baseline record.

In scope

  • Private legacy invocation construction, validation, and union-level security regressions.

Out of scope

  • Source provenance, phase timing, or evaluator integration.

Validation

  • Invocation contracts | sample size: N=51 | key metrics: 51 passed | result: pass
  • Cumulative JSON, redaction, and invocation suite | sample size: N=153 | key metrics: 153 passed | result: pass
  • Final stack gates | sample size: N=203 / 380 / 677 | key metrics: 203 performance and 380 hermetic passed; 677 collected | result: pass

Risk / Compatibility

Type of Change

  • Bug fix (non-breaking change)
  • New feature
  • New benchmark/task
  • New model integration
  • Breaking change
  • Documentation update
  • Refactoring (no functional changes)

@Luodian Luodian changed the title perf: add secret-safe baseline invocation perf: (PR 3/4) add secret-safe baseline invocation Aug 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant