Hotido: from a public notice to a reviewed opportunity

A procurement result worth accepting

Proposed pilot: turn permitted public procurement notices into a reviewed shortlist. The buyer gets provenance, dates, matching explanations and an explicit review queue. This is a proposed implementation pattern, not a claim that every source or competitor connector is already deployed.

A six-step workflow

1. Select allowed source and scope.2. Fetch and retain source URL/observed time.3. Normalise issuer, deadline, currency and identifier.4. Deduplicate by source/id and version.5. Check relevance and show unknown fields.6. A reviewer approves the shortlist before an authorised alert is sent. External posting or procurement submission is not automatic.

What each alternative can contribute

OpenClaw or Hermes can inform channel/memory UX; n8n can prototype a visible integration; LangGraph can inform state/recovery; SDK evals can inform labelled relevance tests; CrewAI can inform role contracts; Codex can help build the connector. These are proposed roles, not validated compatibility promises. TVIJO supplies the scoped integration and acceptance work.

Acceptance before scale

Use a synthetic fixture with10notices, two duplicates and two missing deadlines. Expect8unique records, retain both unknown deadlines and reproduce the same identifiers after a retry. Label relevance before testing. Record accepted/rejected results and cost; this example defines a test, not a measured result.

Continue in the domain wiki

• HOTIDO: agent-stack
• HOTIDO: open-tenders
• HOTIDO: tenderorch
• HOTIDO: supplier-osint
• HOTIDO: procurement-spider