Skip to content

Play the role. Build the startup.

Six steps. One selected Flow.

A Project is the startup or product you are actively building: the lasting context for its Roles, started FlowKits and process history. FahDeProcess does not invent or evaluate it for you.

Project contextIllustrative
Project
AI research workspace
Category
AI
Mission
Turn customer research into product decisions.
Suggested FlowKit
Software Product Launch

Category helps surface relevant published FlowKits, including Software Product Launch and Enhance User Experience for SaaS. The founder still chooses what to start.

Roles come from a managed list. Select the roles this Project may use; each FlowRun pins the one Role that fits its Flow.

IllustrativeAvailable Roles1 Role selected

Choose the managed Roles this Project may call. A FlowRun pins the Role that fits its selected Flow.

FlowKits are published content catalogues. A Project can use them without owning them; starting one creates its runs, and you explicitly select the single Flow the agent may enter.

IllustrativePublished FlowKit / Software Product LaunchOne Flow selected
Agent command shape@FahDeProcess #…

Selected Flow: Validate positioning

After the selected Flow is called, the agent fetches one canonical current Node, its pinned Role and the requirement that tells it what useful output looks like.

Current NodeIllustrative · Ready

Confirm the audience you are willing to ignore

Output requirement
Submit a specific, defensible audience decision.
Frontier
One current executable Node
State
Fetched at the current revision

The conversation stays in your agent chat. The agent asks and suggests wording in its own way, then submits the normalized outcome once the required decision is clear.

CHANNELAgent chat
FOUNDER INPUTYour decision, in your own words
SUBMISSIONNormalized understanding

Provider disclaimer: agent wording, reasoning and local actions belong to the provider. FahDeProcess receives only the accepted submission and process state.

A structured result or normalized decision becomes accepted evidence. The Flow advances atomically, with the record and its provenance attached to the canonical state.

Illustrative accepted evidence

Kind
Founder decision
Node
Confirm the audience you are willing to ignore
State after
Ready for structured result
Provenance
Authenticated submission

The system keeps accepted process records. It does not store your folders, files, provider transcript, hidden reasoning or local execution.