Open Zerverless adds a system-map workflow guide

Open Zerverless now includes a public workflow guide for producing a readable system map from AWS account discovery output. The guide focuses on the first questions a team asks when inheriting or reviewing a serverless workload: what is running, how resources connect, and where the event and data paths lead.

The workflow is built for inspection rather than control. It uses read-only discovery and keeps the resulting artifacts in your own working directory or repository, where they can be reviewed alongside the system documentation your team already owns.

The guide covers

• collecting a bounded inventory of supported serverless resources;
• grouping APIs, functions, queues, event buses, workflows, and data stores by workload;
• reviewing discovered relationships before publishing a map;
• saving Markdown or JSON output for architecture reviews and onboarding;
• identifying gaps that still need a human-maintained decision record.

Open Zerverless remains a standalone public project. It does not require a Zerverless product account and it does not request write access to generate a map. Read the source, adapt the workflow to your account, and contribute improvements through the public repository.