Repository navigation
Conversation
Co-authored-by: Codex <codex@openai.com>
Co-authored-by: Codex <codex@openai.com>
Co-authored-by: Codex <codex@openai.com>
Co-authored-by: Codex <codex@openai.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
what changed
proto/sce/v1with theDataAccessservice (FetchRecordsstream,SubmitResult) and theRecordEnvelopeused at rest.RecordEnvelope(google.protobuf.Structpayload, AES-256-GCM) in a DynamoDB Binary instead of base64 JSON.records.json/result.jsonhandoff with a gRPC server on/data/sce.sock; the DC app pulls records and submits one result Struct, which sce-unit converts back to JSON for the vsock host./devwithurandomfor entropy; passSCE_RPC_SOCKET/ALGORITHM_IDinstead of file paths.gen-client-certidempotent so image rebuilds keep the cert the verifier trusts.why
Issue #21: the sce-unit to DC app contract was a file handoff. This makes it a real protobuf gRPC contract over the same unix socket and makes record access pull-based. Note that
google.protobuf.Structdoes not shrink numeric-heavy records: for the ehealth dataset it is about 18% larger on the wire than the old JSON envelope. The contract win is schema and transport, not size.Closes #21.
verification
go build ./...insecure/sce-unit,secure/samples/spend-analysis-go, andsecure/csav/registry-service.cargo buildandcargo fmt --checkinsecure/samples/audience-segments-rust.uv run python -c 'import main'in both Python samples;npx tsc --noEmitinseeding.DataAccessserver and ran all five sample clients; each streamed a record and submitted a result that marshaled back to the expected JSON.RecordEnvelope; sce-unitdecryptRecorddecrypted it and theStructround-tripped to the same JSON.secure-rads-pdm-service, rebuilt and shipped the CSAV registry image, reseeded 150000 ehealth records, uploaded the trial-eligibility EIF, and ran one sweep rep at size 10000. Resultexit:0,eligibleCount 282/2.82%, matching the sample's documented output. Raw sweep kept out of the commit.notes
make seed) and rebuilding the sample EIFs: the stored record format and the app contract both changed./devand binds/dev/urandom; without it gRPC's Abseil seed generator aborts on first RNG use.