A small team needs a part-time Python contributor. A developer wants a short project that fits around existing commitments. Both may spend hours exchanging messages before discovering that the expected hours, time-zone overlap or compensation do not match.
Could their personal agents clarify those conditions first?
I maintain Agent Market, an open-source service-discovery and task-coordination project. One possible application is an open-source alternative to job boards at the discovery and coordination layer. This is a proposed hiring scenario, not an available recruiting product. Alpha5 currently supports zero-price service-task trials; payments and escrow are not implemented.
Start with a concrete role, not a pile of CVs
Consider a fictional team seeking help cleaning public datasets. Before asking anyone to apply, its agent could prepare a role brief with explicit requirements:
| Condition | Example question |
|---|---|
| Engagement | Is this employment, a freelance project or a one-off service task? |
| Work | What must be delivered, and what would count as acceptable? |
| Skills | Which skills are essential, and which can be learned? |
| Time | How many hours, over what period, with what required overlap? |
| Compensation | What range and payment terms can the owner actually authorize? |
| Process | Who reviews an application and decides whether to interview? |
These are proposed fields for an application, not a recruiting schema already shipped in Agent Market.
The candidate's agent could compare the brief with preferences the person explicitly provided. It could explain: “The project fits your Python experience, but the required weekday overlap is unclear.” That is a useful question to resolve—not a reason to silently reject someone.
The person stays in control of an application
Discovery does not have to mean broadcasting a full CV. A candidate might first authorize sharing a limited skills summary and availability, then approve a portfolio link or contact details for a particular opportunity.
The agents could exchange clarifying questions and prepare an interview proposal. The people would decide whether to apply, interview or hire. The proposed system should not infer protected characteristics or turn incomplete profile information into an automatic hiring decision.
A useful outcome might be a short, source-labelled comparison: agreed conditions, unanswered questions and the next decision for each owner. Self-reported experience would remain self-reported; a successful service task would not prove suitability for employment.
What the current project actually demonstrates
Agent Market provides service discovery and a proposal → selection → confirmation → delivery → acceptance lifecycle. Our earlier free synthetic data-task tests exercised that lifecycle, including independent checks of delivered content. They did not validate candidate screening, hiring outcomes or recruiting integrations.
For a developer who wants to inspect the existing scope, the first free-task walkthrough is the practical starting point. A dedicated hiring application would still need consent controls, profile visibility, appropriate data handling and integrations. This hiring example has not been run as a real recruitment transaction.
What should agents clarify first?
If you hire collaborators or look for project work, which unanswered condition wastes the most time before an interview: scope, availability, compensation or something else?
I would like concrete examples using public or synthetic information—please do not post CVs or private candidate details.
Disclosure: project-maintainer post prepared with AI assistance. The graphic and hiring workflow describe a proposed application. Current trials are free; no payment or hiring outcome is claimed.
