Workstate
Request access

Use cases

One foundation, every team

Each team connects what it keeps and records what it decides. The habit is the same everywhere, and every agent reads the same record.

  1. Search first

    Before acting, an agent checks what was decided and what was already tried.

  2. Cite

    Every answer points to where it came from, so a person can check it.

  3. Record after

    When the work ends, the agent records the decision or finding for whoever comes next.

By team

Examples are illustrative.

Engineering

Codebase answers with citations, and a record of every design decision.

  • Answer “how does this work?” with the file and the lines
  • Record design decisions and the options you rejected
  • Follow an incident from the report to the fix

Connect

  • GitHub
  • Confluence
  • Jira

Record Design decisions, incidents, defects, dead ends

Read the use case

IT & operations

Runbooks for every on-call agent, and a record of what fixed it last time.

  • Give every on-call agent the current runbook
  • Record what failed and what fixed it
  • Stop the same outage being investigated twice

Connect

  • Confluence
  • Jira
  • Uploaded runbooks

Record Incidents, root causes, fixes that worked

Read the use case

Customer support

Known issues and help pages, cited in every answer.

  • Answer from known issues and help pages, with the source
  • Record workarounds and support policies
  • Hand a case to engineering with its history attached

Connect

  • Jira
  • Confluence
  • Uploaded guides

Record Known issues, workarounds, support policies

Read the use case

Product

Specs, tickets and the reasons behind every product decision.

  • Find the spec, the tickets and the decision behind a feature
  • Record product decisions and the options you turned down
  • Brief a new teammate from the record, not from memory

Connect

  • Confluence
  • Jira
  • Uploaded research
  • Google Drive Coming soon

Record Product decisions and the options you rejected

Read the use case

Legal & compliance

Policies and contracts in a namespace of their own.

  • Search policies and contracts, kept apart from everything else
  • Record interpretations and positions as decisions

Connect

  • Uploaded policies and contracts
  • Google Drive Coming soon

Record Interpretations and positions

Read the use case

People & HR

Consistent handbook answers, with sensitive material kept apart.

  • Answer handbook questions the same way every time
  • Keep sensitive material in a namespace of its own

Connect

  • Uploaded handbooks and policies
  • Google Drive Coming soon

Record Policy interpretations

Read the use case

By pattern

Patterns cut across teams. They describe how people and agents work together through the ledger.

Multi-agent coordination

Several agents on one system: search before acting, record after, and supersede instead of rewriting.

Read the pattern

Human–agent handoffs

Hand work over through a ledger entry and its current state, not a chat transcript.

Read the pattern

One namespace per client

Keep each client or product apart, and pick the namespace with every request.

Read the pattern

Give every agent the same memory

Workstate is in early access. Tell us about your team, and we’ll set you up.

Request accessRead the docs