01 Task + context
Prevent double bookings.
Two customers request the same provider’s fixed, non-overlapping 30-minute slot.
Pilot training data from paid business workflows: model failures, expert fixes, and tests that show why the fixes work.
Expert network live. Data capture and packaging planned.
Inside a data package
From model failure to a testable expert fix.
01 Task + context
Two customers request the same provider’s fixed, non-overlapping 30-minute slot.
02 Model failure
Both pass the availability check before either booking is saved.
03 Expert fix
A unique database rule rejects the second booking.
UNIQUE (provider_id, slot_start)04 Expected verification
Reset the slot, then send both requests together.
Different slots must still book successfully.
Includes Brief, reset steps, attempt, fix, tests, provenance, and permissions.
How tasks are scopedWhy it matters
Capture the constraints and expert decisions that a successful outcome depends on.
Slot rules, database behavior, and API requirements define success.
A single request works. Two at once reveal the failure.
The expert explains the fix and ties it to a test.
Task decomposition
Each task needs a clear boundary, repeatable starting state, and acceptance test.
Proposed workflow. Only reproducible model failures qualify; context and tool errors are excluded.
Discuss a data pilotSelect the reservation conflict.
Our sourcing advantage
Our operating network connects expert businesses with paid customer work, giving us access to valuable tasks and specialist judgment.
The expert network and paid customer engagements operate today. Capture and data packaging are the next build.
Experts are onboarded through an established playbook, with specialists accountable for delivery.
Customer work has generated revenue and ongoing access to real requirements and decisions.
Planned: permissioned capture, verified failures, and expert corrections packaged for labs.
The network operates today. The data pipeline is the next build.
Bring your expertise to real work.
Rights & reproducibility
Proposed pilot requirements, agreed with your lab before capture and delivery.
Document the workflow, contributors, model setup, changes, and reviews within agreed disclosure limits.
Secure customer and expert consent. Agree training, evaluation, redistribution, retention, and exclusions.
Redact, transform, or exclude sensitive data. Recheck that the task still works.
Include the brief, versioned code, dependencies, fixtures, tool access, and reset instructions.
Replay failure and correction against the same criteria. Include execution evidence and expert review.
Split by project or task family. Keep evaluation tasks and reference answers out of training.
A paid pilot
Agree a focused dataset and a clear way to judge its value.
Pricing and dates follow source, rights, and engineering review. Training environments are scoped separately.
Define tasks, model and tools, failure types, format, uses, volume, and budget.
Agree failures, expert fixes, tests, and provenance. Confirm source access and rights before committing.
Review relevance, completeness, rights, replayability, and correctness. Rework or reject examples that fall short.
Where feasible, compare baseline and updated models on separate held-out tasks under matched conditions.
For AI labs
Let’s scope a pilot around your research priorities.
Discuss a data pilot