Resource cleanup diagrams
Start with how the application begins, then follow data between its folders. Open an operation to see its decisions, calls, failures and cleanup. Its explanation supplies the exact contract and linked dependencies.
This view includes 2 application source files. Package and interface boundaries show checked contracts; their runtime implementations are not expanded. The views describe the checked program, not desired requirements or a recorded execution.
Where execution begins
Startup
It creates Resource and stores the result in owned resource (Resource). It prints "using resource". source
Data flow
Mermaid source
flowchart TD
n0["Startup"]
n1["resource"]
n0 -->|"Resource → Resource"| n1
Follow the data
Each row opens the complete operations and call sites behind one pair of logical units. A grouped arrow records calls between those units; connected arrows need not belong to the same execution path.
| From | To | Operations | Read |
|---|---|---|---|
| Startup | resource | 1 | Inputs, results and call sites |
Data crossing these boundaries (1 contracts)
Startup → resource
1 operation, 1 site
No caller-supplied inputs. Result: Resource.
| Caller or entry | Evidence |
|---|---|
| Startup | Call site · Caller explanation |
Open a module
| Module | Read |
|---|---|
| main.aug | Flow and sequences · Explanation |
| resource.aug | Flow and sequences · Explanation |
These are static call boundaries, not a request trace. Interface implementations and foreign internals stop at their checked contracts. Dotted arrows defer a callback or browser action. Imports alone do not imply a call.