saascode
hr, payroll & talent·run 255 · Jun 2026

Conscript

A relationship-level employment-control review layer separating agent actions, worker corrections, jurisdictional factors, counsel findings, remediation and operational readback.

Genesis score6.54/10
Make Conscript real.0/500
500 more votes and Conscript is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The case

Marketplaces and companies increasingly use automated systems to assign, schedule, direct or pay human workers. Those actions may change facts relevant to employment classification, but the legal result depends on the full relationship and current jurisdiction-specific tests. The supplied research confirms live human-contractor classification products, a 2024 European directive with a December 2026 transposition deadline, and a 2026 United States economic-reality rule. It found no reviewed product using agent-action logs as evidence input.

Conscript would preserve organization, platform, relationship, worker identifier or pseudonym, worker notice, jurisdiction assertion, contract version, agent identity assertion, human principal, action type, instruction, schedule constraint, acceptance or rejection option, supervision assertion, payment cadence, rate-setting event, exclusivity assertion, expense or tool assertion, source event, source limitation, worker correction, employment-factor question, rule source, rule version, applicability candidate, counsel finding, uncertainty, remediation proposal, owner approval, operational change, destination acknowledgment, monitoring period, appeal and deletion as distinct records.

Scheduling or repeated payment does not automatically create employment, and contract labels do not prevent it. Agent logs are incomplete operational evidence, not legal conclusions. A graded alert about an individual can stigmatize the worker or trigger retaliation. The product should group evidence by relationship and route questions privately to qualified counsel and authorized operations owners. No model may classify a worker, advise termination, hold payouts, change schedules or claim legal privilege, compliance or defense.

The pilot should use synthetic relationships and agent-event fixtures with no real workers or operational changes. Current primary law and qualified employment counsel define the factors and applicability. Workers need notice, correction, access and appeal for evidence about them. The likely buyer is a marketplace compliance, legal-operations or workforce-governance owner, but jurisdiction mix, worker population, counsel workflow, labor relations, privacy, budget and willingness to adopt beyond confirmed classification vendors remain unverified.

Who pays — and why

A marketplace compliance, legal-operations or workforce-governance owner responsible for counsel-reviewed monitoring of automated control evidence.

What it unlocks
A relationship evidence trail linking contract version, jurisdiction assertion, agent and human principals, directions, schedules, payment events, source limits and worker corrections
A versioned legal-review record separating employment-factor question, current rule source, applicability candidate, uncertainty and qualified counsel finding
A remediation workflow separating proposal, owner approval, operational change, destination acknowledgment, monitoring period, worker appeal and deletion
How Genesis scored it
6.54across seven criteria
tension 7temporal 8blindspot 5buyer 5leverage 8convergence 5why-not 7
8
Temporal window

A future European transposition deadline and current United States rule support a review window.

8
Asymmetric leverage

Evidence normalization and counsel workflow scale across relationships after jurisdictional mapping.

5
Convergence

The supplied record has several cross-references but no grounded cross-vertical cluster.

Why it scored well

The input combines confirmed classification products, current legal triggers and a distinct agent-action evidence source for marketplace governance.

What's holding it back

Buyer details are weak, classification is legally complex, worker surveillance and retaliation risks are high, and existing vendors can add agent-log ingestion.

Signals detected3 sources crossed
SignalSupplied competitor research

SignalSupplied primary-law research

SignalSupplied competitor search

Direction briefconscript.md
conscript.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.