Reduce misleading SLEEP blocks by correlating work that crosses BEAM process boundaries, especially GenServer.call/3, while preserving the existing per-process stack profiler.
This language is a new statically typed, functional, macro-capable language with Elixir-like syntax and a native backend strategy built around lowering through a Zig-oriented compiler pipeline.
It is:
You have persistent associative memory via Cog. Checking it before work and recording to it after work is how you avoid repeating mistakes, surface known gotchas, and build institutional knowledge. This is not optional overhead — it is how you operate effectively.
Truth hierarchy: Current code > User statements > Cog knowledge
Every task follows four steps. This is your operating procedure, not a guideline.
You are building a knowledge asset for the team—capturing insights that save time for new developers ramping up AND experienced developers debugging at 2am.
Your goal is NOT to document every file. It's to capture the understanding that takes significant time to acquire and would otherwise be lost.
Capture two types of knowledge equally:
| HTML element (tag / state) | SwiftUI closest equivalent(s) | Default action(s) | Trigger | Event name(s) to bind on the element |
|---|
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | |
| <title>DOM Benchmark Results</title> | |
| <script src="https://cdn.jsdelivr.net/npm/[email protected]/dist/chart.umd.min.js"></script> | |
| <style> | |
| * { |
