Trust
How Fydell handles evidence.
How Simulations freeze a record, who can read Engineering Passports and Builder Reports, and where decisions stay with your team.
- InvitationScoped
- SessionSingle use
- The attemptAppended
- SubmissionFrozen
- AnalysisVersioned
- Team reviewYour team
- Brief and receiptSeparate views
Lifecycle
The life of one Simulation.
Seven stages from Simulation invitation to Hiring Workspace review. Each one shows where the record stops being changeable.
Invitation
Scoped to one email and one published Simulation version, with an expiry.
ScopedSession
One Simulation session per invitation. A used link cannot open a second attempt.
Single useThe attempt
Simulation work is appended as timestamped events until submission.
AppendedSubmission
Answers freeze in a snapshot the application cannot edit afterward.
FrozenAnalysis
A versioned pass turns the trail into a Builder Report with observations and defense questions.
VersionedTeam review
Your hiring team reads Builder Reports in the Hiring Workspace. Fydell staff do not gate release.
Your teamBrief and receipt
The Hiring Workspace brief and the candidate’s Work Receipt or Engineering Passport share are separate views.
Separate views
Access
Who can read what.
There is no shared pool of candidates. A company sees only the Simulations and Engineering Passports it invited, inside its Hiring Workspace.
Row-level security on every table, checked again on the server. Engineering Passport and Work Receipt links carry only the fields the candidate selected and can be revoked.
- CandidateOwn Simulations, Passport, and shares
- Inviting companyHiring Workspace for invited work
- Other companiesNo access
- Work ReceiptSimulation result; candidate-owned
Lineage
Where a claim comes from.
A Builder Report finding names the material it rests on and the lines the candidate was looking at, so you can disagree with one claim without discarding the Builder Report.
The limitation sits in the same view as the claim. When nothing supports a claim, the Builder Report says so.
How Builder Reports are made
Webhook delivery service
- Cited2Cited · backed by a selected file
- Partial1Partial · evidence is incomplete
- Not Assessed1Not assessed · not claimed either way
CitedCited2
PartialPartial1
Not AssessedNot Assessed1
HBR-201
Partner posts stop after five failed attempts.
CitedObserved
The retry cap is five attempts, and the loop exits on the first successful response.
Inferred
A partner outage cannot hold a worker open indefinitely.
Source
retry.ts lines 18-27
Limit
Backoff timing is not exercised in the selected files.
Every finding names the file it rests on or says what was not checked. fydell does not score the project.
On the candidate's computer
Desktop for Simulations. Browser for everything else.
Timed engineering Simulations run in Fydell Desktop. Passports, hiring review, agent comparisons, and reports stay in the browser.
Task-scoped capture
Recording runs only inside a Simulation or task the candidate opened, after showing what is recorded.
Downloads from GitHub
Installers come from public releases and are not code-signed yet; updates verify against Fydell's key after you agree.
Local tests are not a sandbox
Tests on the candidate's machine run with their permissions; Fydell reruns checks in its own sandbox.
- Passport
- Builder Report
- Hiring Workspace
Project from this source
Webhook delivery service
Partner event delivery with retries and a duplicate-event gate.
Files in the snapshot
retry.tsdispatcher.tskeep-draft.test.ts
What you can do
Check the record yourself.
Trust here is something you can inspect, not something you are asked to assume.
- Available
Trace any Builder Report finding to its source
Open the material and lines a finding rests on, and read its limitation beside it.
- Available
Preview and revoke what you share
Engineers choose the fields in an Engineering Passport or Work Receipt link, preview them, and revoke at any time.
- Available
Export or delete your data
Self-serve export and account deletion are in Settings.
- Backlog
Review a SOC 2 report
No SOC 2 report or third-party penetration test exists to share yet.
Readiness
Security and legal readiness.
The first column is built and you can ask us to demonstrate any line of it. Service providers are listed on the privacy page.
In place today
Available- Row-level security on tables that hold candidate work.
- Server-side membership checks before any Simulation session or Builder Report is returned.
- A submission snapshot the database refuses to edit after the fact.
- Engineers choose, preview and revoke Engineering Passport and Work Receipt shares.
- Self-serve data export and account deletion from Settings.
Not yet
Backlog- No SOC 2 report or third-party penetration test to share.
- No automatic retention window; workspace deletion is confirmed by hand.
- No single sign-on, SCIM or custom data residency.
- Desktop installers are not code-signed yet.
Boundaries
What Fydell does not claim.
The decision stays with your team.
Not claimed
- Fydell does not make, recommend or rank a hire or reject decision.
- Fydell does not detect external AI use or verify identity with biometrics.
- Fydell is not a certified psychometric instrument.
- A platform failure during an attempt becomes a review state, not a low score.
Questions about any of this?
If something on this page is not accurate, we would rather correct it than defend it.