saascode

Decoyfreight

A procurement-profile publishing workspace for long-tail business suppliers that maps approved catalog and ordering facts to a versioned draft-standard file, validates it, hosts it with provenance, and lists opt-in vendors without claiming buyer discovery or ranking quality.

Genesis score5.90/10
Make Decoyfreight real.0/500
500 more votes and Decoyfreight 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 opportunity
1Confirmed draft specification versions
0Reviewed generator-plus-directory products found
0Verified agent-adoption evidence
The case

The research confirms that procurement.txt exists as a newly published draft specification with a permissive license and fields for catalogs, ordering, pricing, negotiation, requests for quote, tracking and commerce protocols. It found no reviewed generator-plus-directory product. Adoption by procurement agents remains unproven, so discoverability and network effects are hypotheses rather than established demand.

Decoyfreight should separate vendor source fact, field mapping, generated profile, validation result, vendor approval, publication command, host acknowledgment, retrieval observation, directory opt-in, listing fact, buyer query, referral and commercial outcome. Conformance to one draft version is not certification, procurement eligibility, buyer endorsement or proof that an agent will use the file.

Catalog, price, capacity, certifications, geographic coverage and ordering claims need source owners, effective dates and expiry. The directory cannot sell hidden rank, fabricate popularity or use a listing to imply government qualification, quality, availability or contract readiness.

Who pays — and why

Marketing, commerce and operations leaders at smaller logistics and supply-chain vendors seeking a controlled machine-readable procurement profile.

What it unlocks
A vendor fact registry with legal entity, catalog, ordering route, price and negotiation policy, quote process, tracking, geography, capacity, credentials, source owner, evidence, effective date, expiry and approval
A versioned mapping from approved vendor facts to a named draft-specification version with required fields, optional fields, omissions, validation rules, compatibility notes and migration history
A publication record separating generated file, validation result, vendor preview, exact approval, host command, acknowledgment, retrieval check, cache state, correction, withdrawal and archive
An opt-in directory listing with factual filters, disclosed ranking method, sponsorship label, freshness, complaints, correction, removal, buyer query, referral and outcome attribution
How Genesis scored it
5.90across seven criteria
tension 6temporal 5blindspot 7buyer 5leverage 8convergence 5why-not 5
8
Asymmetric leverage

Generation, validation and hosting are code-scalable if adoption emerges.

7
Incumbent blindspot

A new open standard may favor a neutral product layer over incumbent catalogs.

5
Why nobody did it

The new draft enables the concept but does not prove which barrier previously prevented it.

Why it scored well

A confirmed draft standard and missing product layer create a concrete publishing wedge.

What's holding it back

Buyer, budget, adoption, standard stability, source accuracy, directory integrity and actual agent consumption remain unvalidated.

Signals detected3 sources crossed
SignalGenesis research

SignalGenesis research

SignalGenesis research

Direction briefdecoyfreight.md
decoyfreight.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.