GO / SYSTEMS STUDY / PROJECT MANUALS
Batchlark
A retained Go concurrency study; a practical replacement is under discussion.
A useful reading order
- Start with Using Batchlark for the practical workflow and current availability.
- Read the technical overview for setup and implementation details.
- Follow the specialist guides, architecture and operations references relevant to your task.
- Read dated release evidence to see exactly what was checked. Archive entries are historical references.
Current status: Retained study, not a differentiated production service. Batchlark is the portfolio name; Hermes remains the source repository/internal name. Delivery is simulated, state is in memory and no separate public production backend is established.
These are reviewed documentation snapshots from 16 October 2026, not live provider/account-status feeds. Each imported record links its source revision; reviewed public editions can be downloaded as Markdown. How this library is published .
Follow the implementation history
Read the build history for the recorded steps, successful commands, evidence and known corrections.
Using Batchlark
Run the Go demonstration and understand what its events represent.
Batchlark: the retained study and replacement decision
Why the old generic queue stopped expanding, what was preserved and how history can be cleaned safely.
Running the queue simulation
Go setup, API endpoints, bounded concurrency, shutdown and production boundaries.