Software Session

A Software Session is a bounded interval of interactive or autonomous software operation with a defined start and end, its own working context, and lifecycle protocols that establish and wind down that context.

• AKA: Agent Session, Work Session.
• Context:
  • It can be the unit within which context is loaded, work is performed, and durable artifacts are handed off — particularly for collaborative software agents.
  • It can be governed by session protocols: an Initialization Protocol at open, checkpointing during, and a termination protocol at close.
  • It can persist state across its boundary via handoff artifacts, distinguishing it from a stateless request/response exchange.
  • It can be measured (duration, outcomes, cost) as an operational unit.
• Example(s):
  • An agent session opens with an initialization protocol that loads identity and pending work, and closes by writing a handoff file for the next session.
  • A login session on a multi-user system; an interactive REPL session with persistent workspace state.
• Counter-Example(s):
  • A single stateless API request — no established working context, no lifecycle.
  • A continuously-running daemon — no bounded start/end tied to a unit of work.
• See: Session_Protocol, Initialization Protocol, Process, Workflow, Learning Document, State.

---

References

• Published from the AGET framework; machine-readable concept: w3id.org/aget/vocab#Software_Session