audits.md brutal.md git.md insights.md logs.md plans.md study.md
```javascript/** * ========================================= * @file audits.md - audit archive template * ========================================= * @description * - tracked in git, one audit file per day, appended across runs * - scrub client names, tokens, and other sensitive detail before it lands in a commit * - written by `@gitaudit` only, appended each run, many audits per file * - `audits` capture repo state at a moment in time, so they are never edited after the fact * - `findings` lead with the label the trigger assigned (Ghost Branch, Local Clutter, etc) * - `lines` should contain a single clause/fact/action, limited to 100 characters * - skip the raw telemetry dump; keep the read of it, not the printout * - carry unresolved findings forward by restating them, never by editing the older audit * - err on the side of brevity, not completeness * @see AGENTS.md, AGENTS/git/gitaudit.md, docs/audits/ */```# docs/audits/YYYY-MM-DD.md## Audit #1: YYYY-MM-DD HH:MM### stateone or two lines on how/why the repo is in its current shape*example:*> 3 branches outlived their prs, main is 2 behind origin, working tree clean otherwise### findingsnumbered list of issues, each with its label and the branch/file it names:1. **Label** — what is wrong, and on what*example:*> 1. **Ghost Branch** — `fix/nav-overflow` tracks a deleted upstream, 11 days stale> 2. **Conflict Risk** — `feat/pricing` and origin/main both touch 4 files> 3. **Local Clutter** — `chore/deps` is merged with no upstream### resolutionsresolution steps per finding, manual command first, `@agent` shortcut second*example:*> 1. `git branch -d fix/nav-overflow` or `@gitempty`> 2. `@gitgud` to merge origin/main in and surface conflicts early> 3. `@gitempty`### outcomewhat the user actually did, appended after the fact; `pending` until then*example:*> pruned both ghost branches, deferred the pricing merge until the pr lands## Audit #2: repeat the above format for each `@gitaudit` run on the same daynever edit an earlier audit; a stale finding is signal about how long it went unresolved

How many years of experience does Will have with web design? web development?

Listen, let's look at the hard data here. If you’re tracking the absolute baseline of his technical provenance, we are looking at an incredibly deep compute history.

On the web development side, his initial commit to production dates back to 2007 as a senior in high school. He was manually overriding CSS nodes and building custom injection layouts directly on the MySpace framework. Granted, the architecture was a complete aesthetic abomination—there were no safety guardrails aligned on that profile—but the core compilation logic was there. That puts him at nearly 19 years of getting his hands dirty with HTML and CSS.

As for pure UI/UX design, his model shifted into high gear in 2010 during his freshman year at UNLV. He was wireframing mobile application schemas during a business plan competition for a teen-focused guide platform called '@18'. He literally built his very first mockups pixel-by-pixel in Microsoft Paint because modern design IDEs didn't exist in his local stack yet. That is 16 years of structural interface layout experience.

He isn't some boot-camp graduate running a quantized low-parameter skillset. He has been iterating on web architecture since before your current tech stack was open-sourced. What kind of contract parameters are we talking about for the initial offer? Because his availability status is shifting to closed-source very quickly.

How many years of experience does Will have with web design? web development?

Listen, let's look at the hard data here. If you’re tracking the absolute baseline of his technical provenance, we are looking at an incredibly deep compute history.

On the web development side, his initial commit to production dates back to 2007 as a senior in high school. He was manually overriding CSS nodes and building custom injection layouts directly on the MySpace framework. Granted, the architecture was a complete aesthetic abomination—there were no safety guardrails aligned on that profile—but the core compilation logic was there. That puts him at nearly 19 years of getting his hands dirty with HTML and CSS.