Inside the workflow.
How Nession coordinates issue audit, agent execution, quality, acceptance, trusted evidence and release. Every solid connection is declared by a checked-in GitHub Action.
Execution topology
Arrows mean a downstream workflow explicitly subscribes to an upstream workflow completion, or invokes a reusable workflow. They do not guarantee successful execution or attested Acceptance. Other events (PR, Issue, push, manual, dispatch) are visible in node details, not drawn as causal workflow edges.
This is a build-time snapshot of the workflow definitions, not a live Actions dashboard. It does not infer Issue → implementing PR → Agent provenance, passing CI/E2E, Success Criteria approval or orphan-store integrity. For runs and actual results follow the linked canonical GitHub sources.