myFlow OS

Curated Knowledge

Why it belongs in control

Curated already contains tools, alternatives, and use-case mappings.

It should be treated as a knowledge surface inside control, not as a disconnected app.

Over time, selected curated data can be pulled directly into control cards and detail pages.

Integration direction

Phase 1

Expose curated as a first-class control entry point with direct links into catalog, evaluation, and use-case mappings.

Phase 2

Pull selected curated data into control overview widgets such as top tools, architecture decisions, and use-case support maps.

Phase 3

Link curated knowledge directly to solutions, modules, and future use-case detail pages in flowkit-os.