The setting
develops an AI answer engine that searches the web and replies with cited sources. is the version for large organizations, including regulated industries, with administrator controls over access and use.
Key destruction turns disputed document copies into a permanent access decision.
Security wants uncertain copies excluded, while enterprise leadership wants research preserved before the old key disappears.
Who you’d be doing this for
“The research desk sent me twelve links they need tomorrow, and three belong to the group we removed this morning.”
Meron Mengistu · Financial-services IT administrator · a character in this brief
Coordinates the customer's key destruction and must explain which internal documents employees can still use afterward.
What is at stake
A customer's key destruction puts 2.4 million document versions beyond recovery tonight. You must weigh permanent research loss against carrying disputed permissions into the only readable copies.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- research continuity vs permission certainty
- unique document preservation vs containment
- validation coverage vs destruction deadline
- ongoing synchronization vs a stable cutover boundary
Why Perplexity
Computer depends on permission-aware enterprise knowledge, so preserving readable documents without preserving revoked access is part of research continuity.
Written with these in mind
Not your kind of problem? 48 more at Perplexity, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Perplexity. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Member of Technical Staff (iOS Engineer, Computer Growth) (opens in a new tab)
- Engineering Manager (Enterprise) (opens in a new tab)
- Enterprise Control Plane: Building the identity, security, and governance foundations that enable large organizations to deploy Perplexity confidently, including SSO, SCIM, role-based access, customer-managed encryption keys (BYOK), admin APIs, and enforceable policies governing access to data, models, and tools.
- Enterprise Data Plane: Building the connector platform and semantic data layer that give Computer reliable, permission-aware access to enterprise systems and knowledge, including managed authorization, private-system access, and data freshness.
- Member of Technical Staff (Software Engineer, Enterprise Trust & Governance) (opens in a new tab)
- Encryption, customer-managed keys, and key lifecycle management.
- Set the technical bar for authorization correctness and reliability, with fast, consistent, explainable permission checks, well-defined failure behavior, and strong tenant isolation.
- Member of Technical Staff (Senior QA Web Engineer) (opens in a new tab)
- Member of Technical Staff (GTM Engineer, Growth) (opens in a new tab)
Reporting read before this brief was written
The pieces closest to the situation in this brief.
On October 20, 2026, Perplexity announced a partnership with UK sovereign infrastructure company Valarian to run Perplexity Computer on institutions' own servers, including air-gapped networks, aimed at finance, government and defense buyers.
Valarian Partnership Puts Perplexity Computer on Institutional Servers – Unite.AI (opens in a new tab) · unite.ai · Oct 20, 2026
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these is about an irreversible change forced by a fixed date.
Pre-migration checks show 0.18% of sampled objects fail to decrypt on the target service, mostly in legacy storage.
You have to commit to a cutover you can verify, knowing a bad one locks customers out of their records.
A review confirms the shared-key design misses a contractual isolation rule that lands next quarter.
You have to check migration plans and inventory scans yourself, since a wrong classification can lock records away for good.
Signing moves to hardware-backed keys in one irreversible step, and the maps and the traces disagree about a few legacy send paths.
You have to decide what evidence is enough before you approve the cutover.
The same setting, from another role
Each is set around Perplexity’s Perplexity Enterprise, written for a different role. They’re separate briefs, not the same scenario.
Regulated IT administrators wait while agreement requests arrive without key context.
You must decide whether the system only proposes routes or also holds incomplete matters for counsel.
Regulated IT administrators cannot yet govern Computer access by role.
You must decide which controls belong in reusable terms and which require customer-specific approval.
A healthcare IT administrator cannot enable Computer until the BAA commitments are settled.
You must choose which agent commitments belong in the signed terms and which cannot be promised yet.
Other problems with a similar purpose
In each of these, as in this one, the aim is to build high-assurance systems where a consequential change's correctness can be demonstrated, not merely hoped for.
Rehearsals show the routing works, but recall of sources varies by 0.9% and provenance records are incomplete.
You have to weigh the contractual launch against how much you verify before each matter moves.
The old encrypted store retires on a fixed date, and 6.9% of historical artifacts still lack a source record and retention decision.
You have to weigh speed against proof that reports stay reproducible.
The residency commitment you signed forces a one-way split of event data, and 9% of derived datasets still lean on labels a machine guessed.
With six weeks left, you weigh completeness by region against keeping analytics intact.