Resources
Learn to read the record.
Guides to build an Engineering Passport, share selected work, read a Builder Report, review an applicant, and prepare a Simulation.
- Build your Engineering PassportGuide
- Share selected workGuide
- How reports are madeMethodology
- Review an applicantGuide
- Prepare a SimulationGuide
Featured guide
How reports are made.
A Builder Report reads a project, checks each finding against its source, and states what it could not check.
The guide walks the same view you see here: pick a finding, read what was observed, open the source lines, then read the limitation that applies. A gap is shown as Not Assessed, never as a failure.
Findings cite their source
Every finding opens the lines it rests on.
Observation and inference apart
What was seen is labeled separately from what was inferred.
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.
Get started
Get started
Add a project, read the first findings, and choose what to share.
- Build your Engineering PassportGuideAdd a project, read each finding against your contribution statement, and see what the Passport shows.
- Share selected workGuideChoose projects, pin versions, preview the recipient view, set an expiry, and revoke access.
- Install the CLI or desktop appReferenceCollect a local folder from the terminal, or work in your own editor with the Windows desktop app (macOS when published).
Read the evidence
Read the evidence
What a finding establishes, where it stops, and how to review it.
- How reports are madeMethodologyHow findings are checked against source, how observations are labeled, and what a report could not check.
- Review an applicantGuideRead requirement by requirement, with the source open beside each claim, then record a decision.
- Compare agent setupsExamplePractice runs against held-out runs, and why “Not measured” is different from zero.
- Trust and securityReferenceWhat evidence establishes, and the boundaries shown beside every claim.
Docs and policies
Docs and policies
The full documentation, and the terms that apply to your work.
Technical
Technical
Prepare a Simulation, run the CLI, and fix common setup problems.
- Prepare a SimulationGuidePick representative work, disclose scope and AI policy, and define an acceptable result.
- CLI documentationReferenceCommands to initialize, inspect, review evidence, and upload a project.
- TroubleshootingSupportFix common setup problems and reach support with the details it needs.
Stuck on a record?
Bring the task name and the finding. Support can walk the same evidence path with you.