feat: portfolio architecture v2 - #18
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.
Why
The portfolio has grown from a static personal site into a product with Recruiter Mode, Ajoop, Command Palette, bilingual content, case studies, games, request intake, automated QA and active flagship products. Current project truth had started drifting across HTML, the monolithic runtime and the old
flagship-copy.jspatch layer.Architecture V2
portfolio-data.jsas the source of truth for current flagship projects, recruiter profiles, build status, Labs and sanitized SINAMA evidence examplesportfolio-v2.jsfor Recruiter Mode V2, role deep links, evidence-backed Ajoop synchronization, unified V2 bilingual copy, Build Log, Labs, request receipts and SINAMA Evidence Explorerportfolio-v2.cssfor the new runtime surfacesflagship-copy.jslegacy-script.jsscript.jsinto a compatibility bootloader:PORTFOLIO_ARCHITECTURE.mdProduct / UX changes
?role=applied-ai?role=solution-engineering?role=software?role=gamenow.htmlliving Build Loglabs.htmlso technical experiments no longer dilute the professional project narrativeSINAMA Interactive Proof
Conversation → Tool Trace → Deterministic Findings → Release VerdictMerge Rush Proof
Request flow
no-corsbrowser submission cannot truthfully prove server-side receiptDrift prevention / QA
qa-portfolio-consistency.jsandnpm run qa:portfoliosingle-work.htmlto Lighthouse specifically to verify the global bootloader pathFinal Site Preflight — run #49
Head:
f21db0ac076ed5951ceaa26a07d4bba6ba249d62All workflow steps passed:
Lighthouse
Safety
This PR is isolated from
mainand has not been merged. Production remains unchanged until explicit merge approval.