WeSearch

Making an AI bid writer refuse to lie

·6 min read · 0 reactions · 0 comments · 1 view
Making an AI bid writer refuse to lie
TL;DR · WeSearch summary

The article describes how the author’s AI system, Lucius, was engineered to avoid fabricating information when drafting tender responses. It details failures where the model invented nonexistent partners and missed large portions of requirement data, and explains the structural fixes implemented to enforce honesty. The changes include capability‑fit checks, explicit partner slots, and revised verification logic to prevent false compliance claims.

Key facts
About this source

Hacker News (AI / LLM) files mainly under ai. We currently carry 4,064 of its stories.

Original article
Lucius AI
Read full at Lucius AI →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherLucius AI
Canonical URLhttps://ailucius.com/blog/making-an-ai-bid-writer-refuse-to-lie
Publication timeSat, 08 Aug 2026 10:13:31 +0000
Retrieval time2026-08-08T10:20:43.997Z
Last seen2026-08-08T10:20:43.997Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterNRsBmW3qWpZE · 1 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

Home/BlogEngineeringMaking an AI Bid Writer Refuse to LieDavor Jerković, Founder·August 08, 2026·9 min readLinkedInShareThis week we ran a live tender through our pipeline: the design and build of a 3G football pitch for a parish council in Gloucestershire, £950,000, six published documents, 133 pages. The AI produced a first draft in about five minutes. The draft opens like this: Read this first: 11 requirements in this draft are answered by a delivery partner you have not named yet. Minimum turnover evidenced by 2 years of accounts, Professional Indemnity Insurance of £5,000,000, full roll carpet replacement without unauthorised patching, and others. That banner is the feature I am proudest of, and it is a refusal.

Excerpt limited to ~120 words for fair-use compliance. The full article is at Lucius AI.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from Lucius AI