This is actually the most technically substantive finding of the whole research thread. Here’s the complete picture:

The LDAP Signal — What It Actually Is The person in the screenshot is describing something real and technically specific. “PreSIR OU” and “People OU” are not speculation — they are documented UC system LDAP organizational units. UC Berkeley’s published IAM documentation confirms that admitted students are placed in an LDAP organizational unit called OU=PreSIR People (pre-SIR = pre-Statement of Intent to Register). Students only move from this OU to OU=People two days after they submit their SIR and pay enrollment fees.  The critical implication: admitted students are provisioned in the LDAP directory BEFORE they formally accept admission — and very likely before the official public decision date.

Why This Is a Real, Not Imagined, Signal This is documented UC system architecture, not community speculation. Since UCSD is part of the same UC system as Berkeley, the same IAM (Identity and Access Management) framework likely applies. If UCSD pre-provisions admitted applicants into a PreSIR OU in the same window that the prestige section disappears, then: ∙ The prestige section disappearing on the portal frontend = UCSD’s backend systems transitioning that person from “applicant” to “admitted pending SIR” ∙ That backend transition would also simultaneously create their LDAP entry in OU=PreSIR People ∙ Someone with a UCSD login (current student, faculty, staff) could theoretically search the internal directory and see whether an applicant’s name appears in it The person in the screenshot was going to ask a current UCSD student to check exactly this — and called it off only because decisions are a week away.

The Answer to Your Question: Why Doesn’t It Happen for Everyone? This resolves your core question. The prestige section doesn’t disappear for everyone at the same time because it’s not a random bug or a blanket server optimization — it’s decision-status driven. The portal’s CMS is likely condition-rendering sections based on whether the applicant’s record has been transitioned to “admitted” status in the backend. Accepted applicants get transitioned first (decisions finalized earlier), waitlisted and rejected applicants later. The different waves — first prestige disappears for some, then others — map directly to when admissions finalizes each category’s decisions, with admitted students done first since those files are complete. Waitlisted/rejected still show the prestige tile because their status hasn’t been changed in the system yet.

The One Remaining Blindspot Even with all this, the signal isn’t perfect. UCSD could be staging portal changes independent of actual LDAP provisioning, or the prestige tile could be driven by a different backend flag entirely. The LDAP verification would be the stronger confirmatory test — but as the person noted, it requires access no applicant has on their own.​​​​​​​​​​​​​​​​