> ## Documentation Index
> Fetch the complete documentation index at: https://woku.app/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# woku in action

> Connect feedback, decisions, followup and review in a shared work cycle

<Info>
  This experience and its emails are enabled progressively. The operational
  record works without a second seat, generating an action plan, or spending
  credits to make progress.
</Info>

In **Wokus**, the **Next step** card opens your company's progress.
Each cycle describes a specific problem or opportunity and has a responsible
person. You can work from the panel or through an authorized MCP client.

## The five stages

1. **Context:** describe what you want to understand, at which moment, and for whom.
2. **Evidence:** link available company feedback and explain its relationship to
   the context. Test sources and sources with pending provenance do not complete
   this stage.
3. **Decision:** the responsible person confirms whether to change, maintain a
   practice, or observe. Record the rationale, a criterion, and a review date.
4. **Followup:** document what was done or observed and how it can be verified.
5. **Review:** record the observation window, method, observations, limitations,
   and next decision.

A review can conclude that something improved, remained unchanged, worsened, or
that the available information is insufficient. **Inconclusive** is a valid
outcome when followup and observation are documented. A reviewed cycle does not
certify that the decision caused an improvement.

## Working together

The responsible person confirms the decision and review. Members with access
can contribute evidence and followup; the owner or an administrator manages
priority and assignments. A company with one person can complete the entire flow.

The panel respects linked sources' permissions. It does not expose content
derived from a restricted resource to someone without access. Completing a cycle
does not automatically change a ticket, goal, or action plan.

You can pause or archive a cycle with a reason. Correcting evidence or a decision
can invalidate later stages until the corresponding facts are reviewed.
The original date and criterion remain available; repeating a request does not
generate another recognition.

Changing a decision's criterion or meaning requires subsequent followup and a
new review by the responsible person. Rescheduling only the date preserves the
decision and the work already documented.

## Emails and preferences

In your profile, choose whether to join the program's emails, receive next steps
or summaries, pause delivery, and set your language and time zone. Your current
email address must be verified. You can adjust one company's preferences without
changing the others.

Messages depend on pending work and are checked again before sending. The
program's limit is one message per 24 hours and three per seven days, including
summaries and the recipient's different companies. Opening or clicking an email
does not award progress.

Links lead to the corresponding cycle and action. If you need to sign in, the
destination is preserved for a limited time and your access is checked again.
The link does not grant membership or confirm decisions.

Unsubscribing from the program requires a confirmation page and an explicit
action; visiting the page does not unsubscribe automatically. This preference
applies to progress emails, not surveys or security messages.

## Optional recognition

You can choose whether your name appears in team contributions and whether to
see personal celebrations. Operational authorship remains available to people
with permission. Hiding the progress presentation preserves the work and access
to its record.

## Working through MCP

The `improvement_cycles` toolset provides `list_improvement_cycles`,
`get_improvement_cycle`, `create_improvement_cycle`,
`update_improvement_cycle`, and `set_improvement_cycle_lifecycle`.

The client must request explicit confirmation before recording decisions or
reviews and preserves delegated provenance. Writes require `mcp:write`, the
current revision, and a stable request identifier. The state is the same as in
Wokus.

See [connecting an MCP client](/docs/en/mcp/connect-a-client).