Skip to main content

Role-based guides

Not everyone approaches AetherFS from the same angle.

Some users are reviewing proposed changes. Some are building agents or automation. Some are integrating the hosted system into a product. Some just need a local mounted workspace through Aether CLI.

These guides organize the docs by role instead of by protocol surface.

Choose your path​

Reviewer​

Read Reviewer guide if your main job is:

  • inspecting sessions
  • navigating the tree
  • reading or writing annotations
  • granting or denying approvals
  • using health and event context to make decisions

Agent author​

Read Agent author guide if your main job is:

  • building an agent or workflow runner
  • creating and mutating sessions
  • storing workflow state in cache or bus messages
  • checkpointing, requesting approval, and committing

Platform engineer​

Read Platform engineer guide if your main job is:

  • integrating the hosted platform into a product or internal tooling
  • designing session and source lifecycle UX
  • choosing the right HTTP routes and workflow boundaries
  • exposing reporting, review, and approval behavior cleanly

End user with Aether CLI​

Read End user with Aether CLI guide if your main job is:

  • mounting sessions locally
  • configuring the Aether CLI client
  • using editors or shell tools against a mounted session
  • debugging client-side behavior

Why these guides exist​

The docs site is already organized by system, CLI, and API.

That structure is accurate, but role-based guides answer a different question:

"What should I read first, and what should I actually do in this role?"

Use these guides when you want a practical path instead of a full reference map.