Structure

Layers are inferred from where files sit in the tree, not from reading the code. A project that names its directories unconventionally will read oddly here — open the file browser to check anything the diagram implies.

Languages

Share of indexed source by file size. Binary and vendored files are excluded.

Dependencies

Declared in the repository’s manifests at the indexed commit. A declared package is not proof it is used, and runtime dependencies are listed first.

Feature verification

• Agreement update when freelancer selectedVerified

  When a freelancer is selected and both parties reach an agreement, the object gets updated

  Claimed on readmehigh confidence

  • frontend/move/agreement/sources/agreement.move:36 — claim() entry function updates the freelancer field on the shared Agreement object
  • frontend/hooks/useClaimTransaction.ts:16 — Frontend hook calls the agreement::claim move function with the object id and recipient address
• AI talks back to recruiter with voice outputVerified

  The AI then talks back to the recruiter, showing the top candidates

  Claimed on readmehigh confidence

  • backend/output.js:51 — Uses Deepgram speak.request TTS to synthesize a spoken summary of matched candidates, saved as output.wav and played in the UI
  • frontend/components/Jobs.tsx:50 — Frontend fetches and plays http://localhost:8000/output.wav
• AI-powered candidate matching via database searchVerified

  This data is then analyzed and parsed through our vast database of Freelancers for the best matching candidates

  Claimed on readmehigh confidence

  • backend/index.py:19 — Runs a SingleStore full-text MATCH AGAINST query over the Freelancer table using extracted skill keywords
  • backend/output.js:12 — Express endpoint /exec/:list writes keywords, invokes python index.py, and returns freelancers.json to the frontend
• Escrowed funds released upon task completion via smart contractVerified

  escrowed funds are released upon task completion, all through Smart Contracts developed in Move

  Claimed on readmehigh confidence

  • frontend/move/agreement/sources/agreement.move:58 — settle() entry function transfers the escrowed Balance<SUI> to the freelancer on success or back to the recruiter on failure
  • frontend/hooks/useSettleTransaction.ts:19 — Frontend hook invokes agreement::settle with the success flag and object id
• Express.js backend routingVerified

  We also used Flask and Express.js to manage backend and routing efficiently

  Claimed on readmehigh confidence

  • backend/output.js:9 — An Express app is instantiated with routes /exec/:list and /audio, and listens on port 8000
• Next.js frontendVerified

  We built starting with the Frontend using Next.JS

  Claimed on readmehigh confidence

  • frontend/next.config.mjs — Next.js config file present
  • frontend/app/page.tsx — App Router page structure present under frontend/app
• SingleStore database with Full-Text SearchVerified

  Using SingleStore's real-time data analysis and Full-Text Search, we find the best candidates

  Claimed on readmehigh confidence

  • backend/index.py:2 — Connects via singlestoredb SDK and issues a MATCH(TABLE ...) AGAINST full-text query
• Smart contract / agreement object on SUI blockchain via MoveVerified

  For secure transactions, we utilized SUI blockchain, creating an agreement object once the recruiter posts a job... via Smart Contracts developed in Move

  Claimed on readmehigh confidence

  • frontend/move/agreement/sources/agreement.move:11 — Defines an Agreement struct with freelancer, recruiter, balance, status fields
  • frontend/move/agreement/sources/agreement.move:41 — create() entry function converts a Coin<SUI> to a Balance and shares an Agreement object on-chain
• Voice input capture in browserVerified

  Clients talk to our AI, explaining the type of candidate they need

  Claimed on readmehigh confidence

  • frontend/components/Speech.tsx:53 — Uses browser webkitSpeechRecognition to capture and transcribe recruiter speech
• Deepgram voice AI integrationCode-supported

  We integrated Deepgram to generate human-like voice and process recruiter inputs

  Claimed on readmemedium confidence

  • backend/output.js:2 — Deepgram SDK is used for text-to-speech generation; no evidence Deepgram is used for recruiter speech-to-text input, which instead relies on browser webkitSpeechRecognition (frontend/components/Speech.tsx)
• End-to-end wiring of recruiter/freelancer addresses in agreement creationCode-supported

  Once the recruiter picks the right candidate, they can create a smart contract that's securely stored and managed on the blockchain

  Claimed on Devpostmedium confidence

  • frontend/hooks/useCreateAgreementTransaction.ts:16 — Recruiter/freelancer addresses are hardcoded placeholders with a code comment 'how do i get recruiter address and amount from the frontend?', indicating candidate selection is not actually wired to contract creation
• Fetch.ai uAgents scaffoldingCode-supported

  handled by Fetch.ai's agents

  Claimed on Devposthigh confidence

  • backend/evi-env/agents/sui.py:4 — uagents.Agent instances are defined (sui, hume, singlestore, singlestoreHumeSync, frontBackSync) but each only logs a startup greeting
  • backend/evi-env/agents/frontBackSync.py:44 — No ctx.send/on_message handlers found anywhere in the agents directory, so no actual inter-agent messaging/coordination is implemented despite Agent objects existing
• Keyword highlighting from speechCode-supported

  As they speak, the AI highlights important keywords

  Claimed on readmemedium confidence

  • frontend/components/Speech.tsx:54 — Transcript words are bolded via a hardcoded client-side keyword list match, not an AI/NLP model as implied by the claim
• Terraform deployment for scalabilityCode-supported

  we deployed the entire application on Terraform for seamless scalability

  Claimed on readmemedium confidence

  • config.tf:7 — Terraform config exists defining an S3 bucket, versioning, and a CloudFront distribution for static hosting, but contains placeholder values (e.g. generic OAI id) suggesting it was not a fully deployed/verified pipeline
• DAO-based conflict resolutionClaimed only

  Next, we plan to implement DAOs for conflict resolution

  Claimed on readmehigh confidence
• Fetch.ai agents handling voice/keyword/database/communication in tandemClaimed only

  These agents work in tandem: one agent interacts with Flask to analyze keywords, another queries SingleStore, a third handles communication with Deepgram

  Claimed on readmehigh confidence
• Flask backend for keyword analysisClaimed only

  We also used Flask and Express.js to manage backend and routing efficiently

  Claimed on readmehigh confidence
• SUI mainnet launchClaimed only

  We also aim to launch on the SUI mainnet

  Claimed on readmehigh confidence

An AI agent derived these features from the project’s Devpost page and readme, then searched the code for each one. Verified features are backed by cited code; claimed-only features had no supporting code, which is not by itself proof a feature is missing.