Evidence you can inspect. Access you can control.

Workspace isolation, scoped invitations, frozen submissions and inspectable evidence are implemented today. Limitations stay on this page so they are not discovered in procurement, but they do not lead the product.

The life of one evaluation

Seven stages, created in order. Each one carries the state of the record it produces, so you can see exactly where the trail stops being changeable.

Run lifecycleStage 05 of 07
  1. 01

    Invitation

    09:02Revocable until the candidate starts

    Scoped to one email address and pinned to one published version of the evaluation. It carries an expiry date.

  2. 02

    Session

    14:20Active

    Opening the invitation creates one session, and only one. A used invitation cannot open a second attempt.

  3. 03

    The attempt

    14:20—14:40Appending

    What the candidate opens, asks, writes and cites is appended to the session as timestamped events. Progress saves as they work.

  4. 04

    Submission

    14:40Frozen

    The answers are written as a snapshot. A database trigger rejects any later update or delete of that snapshot, including by us.

  5. 05

    Analysis

    14:41CurrentVersioned

    A versioned analysis pass turns the ordered work trail into observations, uncertainties and candidate-specific defense questions.

  6. 06

    Human review

    16:05Required in pilot

    A Fydell reviewer checks every publishable claim against supporting events, counterevidence and the applicable rubric.

  7. 07

    Brief and receipt

    16:22Separate views

    The employer receives a decision brief. Portable candidate evidence is assembled separately so employer-private judgment never enters a Work Receipt.

The order and the states are how the system behaves. The clock times belong to a synthetic Northline Components run and are illustrative.

Who can read what

There is no shared pool of candidates. A company sees the attempts it invited and nothing else, and that boundary is a policy on the table as well as a check in the code.

Read access by artifactRow-level security, checked again on the server
  • Invitation

    The candidate
    Their own link, partial read access
    The inviting company
    All of them, full read access
    Any other company
    None, no access
    Someone holding a shared link
    None, no access
  • Session and recorded events

    The candidate
    Their own, partial read access
    The inviting company
    Full, full read access
    Any other company
    None, no access
    Someone holding a shared link
    None, no access
  • Submitted answers

    The candidate
    Their own, partial read access
    The inviting company
    Full, full read access
    Any other company
    None, no access
    Someone holding a shared link
    None, no access
  • Evidence report

    The candidate
    Candidate view, partial read access
    The inviting company
    Full, full read access
    Any other company
    None, no access
    Someone holding a shared link
    None, no access
  • Work Receipt

    The candidate
    Full, full read access
    The inviting company
    Full, full read access
    Any other company
    None, no access
    Someone holding a shared link
    None, no access
  • Explained below: A link the candidate shares

    The candidate
    Creates and revokes, full read access
    The inviting company
    Full, full read access
    Any other company
    None, no access
    Someone holding a shared link
    Chosen fields only, partial read access

Selected artifact · A link the candidate shares

Assembled separately

The candidate view of a result is generated separately from the employer view. It does not include the answer key for the evaluation, the reviewer's notes, or the hiring decision.

Bounded by the candidate

A shared link carries only the fields the candidate selected, stops working at the date they set, and can be revoked afterwards.

Where a claim comes from

A claim in a report is not a summary of a score. It names the material it rests on and carries the lines the candidate was looking at, so you can disagree with one claim without discarding the report.

Alongside it, the session keeps an ordered record of what was opened, asked and changed. That record is what makes a limitation or a late revision legible instead of suspicious.

Source
The material the candidate was given.
Candidate action
What they did with it, recorded as it happened.
Claim
The conclusion, carrying the lines it rests on.
Limitation
Where the claim stops, kept attached to it.
Revision
What the candidate did once a fact changed.
Employer judgment
The decision Fydell does not make for you.
Claim lineage
14:22 — 17:05
  1. Source

    14:22
    quality_events.csvDisposition events, both periodsQ-303, Q-304
    Metric dictionaryHow yield is definedyield, line 4

    opened and read by the candidate

  2. Candidate action

    14:31

    Filtered quality events by period and found HOLD_RECLASS present only in the current period.

    establishes

  3. Claim

    14:44
    Selected claim2 citations

    Most of the reported drop is a reporting change, not a production change.

    quality_events.csvQ-303, Q-304

    event_id,period,line,disposition,units

    Q-301,prior,L1,SCRAP,30

    Q-303,current,L1,HOLD_RECLASS,42

    Q-304,current,L2,HOLD_RECLASS,58

    Metric dictionary · yield, line 4

    bounded by

  4. Limitation

    15:02

    The L2 Day loss is not explained by reclassification.

    Cause is not established. The data shows the loss but not why it happened.

    reopened when a fact changed

  5. Revision

    16:13
    New information16:08

    HOLD_RECLASS went live on day 9 of a 20-day period, not on day 1.

    Candidate response · revised

    Recalculated using only the days after the change, which lowered the reclassification share from most of the drop to about two thirds, and left the L2 Day loss intact.

    reviewed by

  6. Employer judgment

    17:05

    Reviewer confirms the correction holds.

    Human review happens before evidence is published to an employer during the pilot. The hire decision stays with the employer.

Northline Components is a synthetic scenario. The lineage is the one the product records; the clock times are illustrative.

Security and legal readiness

Fydell is early. The left column is built and you can ask us to demonstrate any line of it. The right column is not, and we would rather you learn that here than in a security review.

In place today

  • Row-level security policies on every table that holds candidate work, scoped to the organization that owns the session.
  • Server-side reads check organization membership before a session, report or receipt is returned.
  • A submission snapshot that the database itself refuses to let anyone edit after the fact.
  • An append-only audit record of workspace actions.
  • Versioned analysis outputs that preserve supporting events, counterevidence, confidence, model, prompt and rubric versions.
  • Human review before evidence is published to an employer during the pilot.
  • Managed Postgres with encryption at rest, in a single region.
  • Synthetic scenario data. Northstar and Acme are fictional and are not modelled on customers.

Not yet

  • No SOC 2 report. We have not been audited and we will not imply that we have.
  • No third-party penetration test to share yet.
  • No automatic retention window. Evaluation data stays until you ask us to remove it, and removal is done by hand.
  • No self-serve export. Ask and we will send it.
  • No single sign-on, SCIM, or custom data residency.

What Fydell does not claim

  • Fydell does not make, recommend, or rank a hire or reject decision.
  • Fydell does not detect external AI use, screen sharing, or remote desktop control, and does not claim to.
  • Fydell does not verify identity using biometrics.
  • Fydell is not a certified psychometric instrument and is not presented as one.
  • A platform failure during an attempt becomes a review state. It is never converted into a low score.

Questions about any of this?

Ask directly at admin@fydell.com. If something on this page is not accurate, we would rather correct it than defend it.