Field notes/Editorial method

Show the work behind the words.

The field notes explain browser software: how it renders, how it fails, and how its interface communicates what happened. A useful article should leave you with something you can inspect or try.

Who publishes this site

Joel Ryan runs stackwith.me, an independent software workshop in India. The projects and articles belong to that workshop. The site does not have an invented editorial team, customer panel, or independent testing laboratory.

Questions and corrections can be sent to hello@stackwith.me. The public repository provides further context for the work.

What counts as evidence here

• Source walkthroughs describe a named implementation. Dated excerpts preserve the relevant file paths, original line numbers, and full-file hashes so a later revision is not silently substituted.
• Worked examples explain a technique separately from the production page. The camera-response comparison, pixel worksheet, and latency allocation are calculations, not device or service benchmarks.
• Measurements name what was measured and how. For example, the asset-size record uses actual file byte lengths and hashes; it does not infer compression ratios without matching raw files.
• Design exercises propose behavior that may not be implemented. AXON’s agent trace, approval model, and orchestration budget belong to this category.

A source excerpt proves what that source contains. It does not prove that the code was deployed, that a browser ran it successfully, or that it meets a performance target. Browser results need their own environment and source record.

How AI assistance is used

AI tools assist with drafting, code, and revision. The October 2026 editorial pass compared technical claims with the repository and primary documentation, replaced unsupported specifics, and added reproducible examples. AI assistance is disclosed because it is part of how these notes are made.

AI-generated explanations can be wrong even when they sound precise. These articles do not claim that a named person independently tested every example or that an anecdote happened without evidence. Readers should use the linked implementation and references to evaluate a claim, and report discrepancies.

Corrections and updates

Send the article URL, the passage you think is wrong, and a source or reproduction where possible. A useful correction identifies a wrong result, stale implementation detail, unclear boundary, or broken example. A different design preference is also welcome, but it should be distinguished from a factual error.

Material corrections are recorded with the article’s updated date and revision note. Original publication dates are retained. Dates are not changed merely to make an old article look recent.

This revision corrected several substantive errors:

• The camera guide now distinguishes the current exponential follow from a separate spring example.
• The asset guide uses the real sRGB command and measured file sizes.
• The networking guide corrects message fields, interpolation, traffic arithmetic, and trust claims.
• The testing guide no longer claims that the browser smoke suite runs automatically on every deployment.
• The interface study distinguishes removing pricing promotion from disabling a checkout route.

Commercial context

Articles are freely readable without an account. Advertising is disabled in this version. A publisher verification record remains in the site’s metadata and ads.txt. Any future advertising or sponsorship should be identified where it appears and described in the privacy policy.

AXON is a prototype interface, not an operational agent service. Optional account features and the separate supporter checkout should be evaluated according to their own descriptions; they do not turn a design target into a delivered software product.