Discovery products need a knowledge contract

Readiness depends on ownership, structure, freshness, access rules, duplication and whether important claims can be traced to a source. Gaps do not always block a bounded pilot, but they limit what the product may promise.

The same readiness decision names the authoritative source when versions conflict and the review path when no source can settle the answer.

The path begins with intent and source eligibility, then moves through retrieval, ranking, presentation, interpretation and action. Search can rank material; AI can assemble an answer.

In both cases, the reader needs claim-level support, permission and version boundaries, visible uncertainty and a correction route that updates indexes and dependent answers.

Search helps when a person can express what they need. Browse helps when they need to understand the available space. Recommendation helps when the product uses context and an objective to bring something forward.

A useful experience can combine these modes without presenting every route as one search box. It should preserve:

• what the system searched;
• how filters changed eligibility;
• why a result or recommendation appeared;
• which source and version the result represents;
• what the person can preview before committing;
• how feedback changes later discovery.

In the Eden AI case, Tcules brought template discovery, AI assistance and from-scratch workflow creation into one entry model while preserving their distinct modes. Preview and documentation access kept technical context near selection.

Summaries, answer generation and conversational retrieval can help someone move through a large corpus. They can also compress disagreement, omit relevant sources or present a partial answer with the tone of a complete one.

The article on generative AI product patterns distinguishes retrieval and synthesis from broader delegated action.

The product should expose source coverage, permission and version where they affect the decision. For high-consequence use, citation must connect the claim to the passage rather than only provide a list of documents. Correction and feedback should not rewrite the underlying source.

The W3C PROV-O recommendation (opens in a new tab) provides one formal vocabulary for representing provenance. Tcules uses standards according to the product context and does not imply that every content platform needs that implementation.