Repository navigation
Keep AI confidentiality disclosure only in the opening note - #53
Merged
Merged
Conversation
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.
Keep the opening AI Research and Engineering Confidentiality & Disclosure Note verbatim and remove nine repeated notices: NDA language in all four Experience summaries, the four detail-page Confidentiality & Scope Disclosure sections, and the proprietary-telemetry disclosure clause in project 1's synthetic benchmark section. Preserve the June 2026 AUM qualifier from project 4's removed note by moving it into that project's summary.
The existing optional disclosure component handles the removal without any component, CSS, font, asset, or route changes. Update the canonical importer, exact-content contracts, manifests, and maintenance guidance so regenerated pages retain the single-note structure. Key Contributions, architectural context, all formulas, scientific benchmark qualifications, and the other fourteen Experience entries remain unchanged.
Validation: production build, lint, typecheck, 111 artifact tests, protected-source checks, visible-copy verification, npm audit (0 vulnerabilities), and git diff --check pass. The opening note is byte-for-byte unchanged. All nine built CSS/font files match the pre-change hashes; all four detail pages contain no repeated disclosure, and each directory/compatibility route contains exactly one opening disclosure. Formula source and order are unchanged across all four projects.