Core Workflows

Use the evidence layer properly

Documents, uploads, data, and reports should strengthen the system foundation instead of living in isolated silos.

What this helps with: Explain how evidence should support the rest of the product.

What belongs in evidence

Evidence is any source material that helps the platform understand the project more accurately.

Briefs, decks, transcripts, interview notes, and supporting documents.

Structured research reports generated by the system.

Uploaded datasets and analysis blocks where relevant.

Evidence should improve system grounding everywhere it is relevant.

Discovery uploads should remain available later as evidence.

Research methods should consume approved context through the system.

Evidence should not leak sideways in uncontrolled ways between methods.

Better evidence usually leads to better outputs, but the system still needs structure.

Upload meaningful source material, not noise.

Use the discovery session to tell the system what matters about the evidence.

Prefer specific source material over generic background content.