# hraness
> Tools for agents and humans. Hraness is Ben Guo's software studio in Puerto Rico. Most of its tools for AI agents and for people are open source.
When to use this site:
- Use hraness.com to learn what Hraness is, what it is building, and what its founder Ben Guo is writing now.
- Use /kb/evaluation for the frozen 2 August 2026 KB retrieval pilot metrics.
- Use /prompting for what predicts whether Ben Guo starts a Codex, Claude Code, or Devin session on a frontier model, read twice from his local stores, and the ALGAL router kept in step with the picks.
- Use /direct for Direct gives browser agents repeatable app states that open by URL, with your real interface running on fixture data.
- Use /sponge for public notes on Sponge, including an illustrated summary of how it works.
- Use /stripe for a sourced history of Stripe. It is company history, not Stripe API documentation.
- Use /eds for the EDS Research Index, a sourced index of Ehlers-Danlos syndromes research for patients and clinicians. It is not medical advice.
- Use /roam-research for a sourced history of roam research and its founder conor white-sullivan, from the hype and the backlash to the unfinished idea of networked thought.
- Use /obsidian for a sourced history of obsidian, its people, the discourse around it, and the file-over-app idea it is built on.
- Use /gumroad for a sourced history of gumroad and sahil lavingia's umbrella company, the discourse around them, and the small-company idea behind them.
- Use /every for a sourced history of every, the media house and app suite, the discourse around it, and the bundle idea behind it.
- Use /ink-and-switch for a sourced history of ink & switch, the independent lab behind automerge and the local-first software movement, and the tools-for-thought scene it seeded.
- Use /tldraw for a sourced history of tldraw, steve ruiz's infinite-canvas company: the sdk business, the make-real demos, and the canvas-as-infrastructure thesis.
- Use /antithesis for a sourced history of antithesis, the deterministic simulation-testing company from the foundationdb lineage, and its autonomous-testing idea.
- Use /midjourney for a sourced history of midjourney, david holz's self-funded independent research lab, its community, and its models.
- Use /zed for a sourced history of zed industries, the editor company founded by atom and tree-sitter veterans, from gpui to its idea of a fast collaborative editor.
- Use /core-automation for a sourced history of core automation, inc., the san francisco ai lab founded by former openai vp of research jerry tworek, not the industrial-automation firms.
- Use /morph for a sourced history of morph, the apply-model company behind fast apply, from its lingtual pivot years to its subagent suite.
- Use /moving-castles for a sourced history of moving castles, the berlin studio, its worlds, and the zero release.
- Use /typesafe for a sourced dossier on typesafe ai, the system-one lab behind jev: its founders, its launch, and the calibration question it leaves open.
- Use /cognition for a sourced history of cognition, scott wu's company behind the devin software-engineering agent, and its acquisition of windsurf.
- Use /deepseek for a sourced history of deepseek, the open-weights ai lab, its founder liang wenfeng, and high-flyer, the hedge fund behind it.
- Use /andon-labs for a sourced history of andon labs, the ai-safety evaluation shop, covering project vend and its model-behavior experiments.
- Use /convergent-research for a sourced history of convergent research, the nonprofit that incubates focused research organizations, and its cofounders adam marblestone and anastasia gamick.
- Use the writing, projects, and reading collection pages to browse essays, software, and reading notes. Do not treat this site as a public HTTP API, OAuth provider, GraphQL endpoint, MCP server, or store.
- Use /portfolio.json when you need the portfolio as data: project identity, shared foundations, typed relationships, and marketing copy. It is a generated static document, not a query API.
Public HTML pages also serve Markdown for `Accept: text/markdown`. Sibling `.md` URLs are the same representation. A few writing posts exist only as HTML, and their entries below link the HTML page. `/llms.txt` covers this origin.

## Pages
- [hraness](https://hraness.com/index.md): Hraness index: the organization statement, projects, Ben Guo's about section, reading, writing, social, reference, and gear.
- [kb evaluation](https://hraness.com/kb/evaluation.md): In a 2 August 2026 pilot with 18 frozen questions over 155 notes, exact and hybrid KB retrieval tied on held-out Recall@10 (0.833333).
- [direct](https://hraness.com/direct.md): Direct gives browser agents repeatable app states that open by URL, with your real interface running on fixture data.
- [introducing direct](https://hraness.com/direct/introducing): Open any state of your web app from a link. Direct gives each screen a named scenario with sample data, runs your real interface against it, and tells tests and coding agents when the page has settled.
- [consulting rate calculator](https://hraness.com/consulting.md): Estimate a consulting engagement from project hours, duration, human labor, and hourly costs for inference, infrastructure, and AI subscriptions.
- [puerto rico pulse](https://hraness.com/pr.md): Live emergency updates for Puerto Rico, including power outages, water service, weather, and earthquakes, gathered from official and community sources.
- [Stripe history](https://hraness.com/stripe/llms.txt): Timeline, category, valuation, payment-volume, appearance, and public-data guidance.
- [EDS Research Index](https://hraness.com/eds/llms.txt): Ehlers-Danlos research records with linked sources, labeled by kind of evidence, EDS type, and diagnostic criteria.
- [fiction](https://hraness.com/fiction.md): An original speculative chronicle.
- [bookshelf](https://hraness.com/bookshelf.md): Books Ben is reading, with notes.
- [movie shelf](https://hraness.com/movie-shelf.md): Movies Ben has watched, with notes.
- [writing](https://hraness.com/writing.md): ben guo on building a software factory with coding agents, music, and puerto rico, plus reviews of the mac apps and desk gear he uses. pieces hraness drafted with ai are marked.
- [discoveries](https://hraness.com/discoveries.md): Research from the Hraness lab, with mathematical results, computational evidence, and links to the papers and code behind each claim.
- [projects](https://hraness.com/projects.md): independent products, research, and open-source software from hraness, grouped by pack.
- [social](https://hraness.com/social.md): social profiles and audience stats for hraness.
- [reference](https://hraness.com/reference.md): lessons on agents, rust, and web delivery drawn from hraness projects, plus a study of model choice and sourced histories of software companies and labs.
- [roam research](https://hraness.com/roam-research.md): a sourced history of roam research and its founder conor white-sullivan, from the hype and the backlash to the unfinished idea of networked thought.
- [obsidian](https://hraness.com/obsidian.md): a sourced history of obsidian, its people, the discourse around it, and the file-over-app idea it is built on.
- [gumroad](https://hraness.com/gumroad.md): a sourced history of gumroad and sahil lavingia's umbrella company, the discourse around them, and the small-company idea behind them.
- [every](https://hraness.com/every.md): a sourced history of every, the media house and app suite, the discourse around it, and the bundle idea behind it.
- [ink & switch](https://hraness.com/ink-and-switch.md): a sourced history of ink & switch, the independent lab behind automerge and the local-first software movement, and the tools-for-thought scene it seeded.
- [tldraw](https://hraness.com/tldraw.md): a sourced history of tldraw, steve ruiz's infinite-canvas company: the sdk business, the make-real demos, and the canvas-as-infrastructure thesis.
- [antithesis](https://hraness.com/antithesis.md): a sourced history of antithesis, the deterministic simulation-testing company from the foundationdb lineage, and its autonomous-testing idea.
- [midjourney](https://hraness.com/midjourney.md): a sourced history of midjourney, david holz's self-funded independent research lab, its community, and its models.
- [zed](https://hraness.com/zed.md): a sourced history of zed industries, the editor company founded by atom and tree-sitter veterans, from gpui to its idea of a fast collaborative editor.
- [core automation](https://hraness.com/core-automation.md): a sourced history of core automation, inc., the san francisco ai lab founded by former openai vp of research jerry tworek, not the industrial-automation firms.
- [morph](https://hraness.com/morph.md): a sourced history of morph, the apply-model company behind fast apply, from its lingtual pivot years to its subagent suite.
- [moving castles](https://hraness.com/moving-castles.md): a sourced history of moving castles, the berlin studio, its worlds, and the zero release.
- [typesafe](https://hraness.com/typesafe.md): a sourced dossier on typesafe ai, the system-one lab behind jev: its founders, its launch, and the calibration question it leaves open.
- [cognition](https://hraness.com/cognition.md): a sourced history of cognition, scott wu's company behind the devin software-engineering agent, and its acquisition of windsurf.
- [deepseek](https://hraness.com/deepseek.md): a sourced history of deepseek, the open-weights ai lab, its founder liang wenfeng, and high-flyer, the hedge fund behind it.
- [andon labs](https://hraness.com/andon-labs.md): a sourced history of andon labs, the ai-safety evaluation shop, covering project vend and its model-behavior experiments.
- [convergent research](https://hraness.com/convergent-research.md): a sourced history of convergent research, the nonprofit that incubates focused research organizations, and its cofounders adam marblestone and anastasia gamick.
- [reading](https://hraness.com/reading.md): Notes on articles, books, talks, and posts Ben Guo has saved, each linked to its source. Permalinks live at `/reading/{slug}`.
- [sponge](https://hraness.com/sponge.md): Index of public Sponge notes and working documents.
- [Sponge summary](https://hraness.com/sponge/summary.md): Research reports are fast to produce with AI, but still costly to trust, reuse, and update. Sponge lets agents autonomously absorb their claims, evidence, and context into structured knowledge while people steer, review, and control release.

## Discoveries
- [A sharp limit on what reflection can change](https://hraness.com/discoveries/the-limit-of-reflection.md): Adding and subtracting the same points can produce different answers. A proof pins down the largest reflected ratio on four sites: seven quarters.
- [More differences from fewer sums](https://hraness.com/discoveries/more-differences-from-fewer-sums.md): Two explicit constructions show how subtraction can create more distinct outcomes than addition, with exact integer checks and carefully stated comparisons to earlier work.
- [When specialization wins in a mathematical team](https://hraness.com/discoveries/when-specialization-wins.md): In one task-allocation model, every optimal team gives each agent a single job. A companion result finds exactly when an exponential average preserves order.
- [When adding the same ingredient reverses an order](https://hraness.com/discoveries/when-mixtures-reverse-an-order.md): Two simple mixtures of exponential lifetimes exchange their hazard-rate ordering. Exact arithmetic identifies the crossing and explains why a two-component argument fails.
- [Placing points with no five on a sphere](https://hraness.com/discoveries/points-without-a-common-sphere.md): Small integer grids give a clear test of mathematical search: finding a configuration is one task; proving that no larger one exists is another.
- [Grouping components that last](https://hraness.com/discoveries/grouping-components-that-last.md): When a group works only if every member survives, a mathematical model says to group similar components together. The proof holds at every fixed survivor count.
- [What a Ramsey search can rule out](https://hraness.com/discoveries/narrowing-a-ramsey-search.md): A search for a 40-vertex graph produced checkable exclusions of several possible shapes. The main Ramsey question remains open in this work.

## Writing
- [my girlfriend thinks i have ai psychosis](https://hraness.com/writing/my-girlfriend-thinks-i-have-ai-psychosis.md): My current projects, from hotrodding harnesses to enabling agent civilizations.
- [fluidvoice vs wispr flow: local dictation won me over](https://hraness.com/writing/fluidvoice-vs-wispr-flow.md): FluidVoice matches Wispr Flow for me while keeping models local and the core open. Here is where the Mac app wins and the hosted service stays easier.
- [how i use duet display to reach two macs from an ipad](https://hraness.com/writing/duet-display-remote-access-ipad.md): I use Duet Display to reach two coding laptops from an iPad and keyboard. It occupies a useful middle ground between Sidecar and a dedicated remote desktop.
- [kitetasks gives google tasks the mac app it needs](https://hraness.com/writing/google-tasks-mac-kitetasks.md): Google Tasks already has the calendar, web, mobile, and widget behavior I need. KiteTasks adds the missing native Mac client without replacing the system.
- [periscope vs tailscale for a home vpn](https://hraness.com/writing/periscope-vs-tailscale.md): Periscope routes traffic through my home connection; Tailscale builds a broader private network. Here is how both differ from remote desktop.
- [why granola is still my ai meeting notes app](https://hraness.com/writing/granola-ai-meeting-notes.md): Granola's calendar and menu-bar loop keeps it sticky for me, despite my preference for local transcription. It starts deliberately, not as a hidden recorder.
- [beeper finally gave me one inbox for every messenger](https://hraness.com/writing/beeper-unified-inbox.md): Beeper unifies the messaging networks I miss, then adds a CLI and MCP for bounded agent workflows. That combination changed my inbox and my tools.
- [atlas for mac is my local visual bookmark library](https://hraness.com/writing/atlas-for-mac-review.md): Atlas is a fast local visual library with grid, canvas, and infinite views. It lets me collect inspiration without turning the collection into a social feed.
- [why i still use arc on desktop, but chrome on iphone](https://hraness.com/writing/arc-browser-review.md): Arc organizes my desktop browsing better than Chrome, but Arc Search's incomplete return sync keeps Chrome on my phone. Safari remains tempting on iOS.
- [amphetamine vs caffeinate for keeping a mac awake](https://hraness.com/writing/amphetamine-vs-caffeinate.md): Amphetamine makes keep-awake state visible in the menu bar; macOS caffeinate is better for scripts. I use the app for long-running coding-agent laptops.
- [why i use an apple magic trackpad instead of a mouse](https://hraness.com/writing/apple-magic-trackpad-review.md): A Magic Trackpad feels more familiar than a mouse after years on laptops. Gestures and continuity win; precision and wrist comfort remain personal.
- [lofree flow lite fits how i type now](https://hraness.com/writing/lofree-flow-lite-review.md): The Lofree Flow Lite's quiet, padded feel suits a workflow with much more dictation and less all-day typing. My old split keyboard solved another problem.
- [caldigit element 5 is the desk hub i wanted](https://hraness.com/writing/caldigit-element-5-review.md): The Element 5 gives my desk four Thunderbolt 5 ports, five fast USB ports, and 90W host charging in a compact aluminum hub. Its restraint is the point.
- [i use an owc envoy ultra for time machine](https://hraness.com/writing/owc-envoy-ultra-time-machine.md): My Envoy Ultra is a fast, rugged Thunderbolt 5 SSD, but Time Machine automation is why it matters. Local versioned backup is useful because it is boring.
- [teenage engineering ob–4 is my desk speaker](https://hraness.com/writing/teenage-engineering-ob-4-review.md): The OB–4 is compact enough to move and powerful enough for my desk. Bluetooth, line input, FM, and its tape controls make it more than a generic speaker.
- [why i still use the original arturia keystep 37](https://hraness.com/writing/arturia-keystep-37-review.md): The original KeyStep 37 gives me the keybed, sequencer, MIDI, and CV workflow I want. The mk2 is a stronger new buy, not an automatic upgrade.
- [akg k371 is my compact monitoring headphone](https://hraness.com/writing/akg-k371-review.md): The AKG K371 is affordable, closed-back, foldable, light enough for long sessions, and compact enough to travel. It is my private monitoring middle ground.
- [my girlfriend asked me why i have 15 codex subscriptions](https://hraness.com/writing/my-girlfriend-asked-me-why-i-have): I have 15 Codex Pro 20x subscriptions.
- [hotcodex seed prompt](https://hraness.com/writing/hotcodex-seed-prompt): on hotcodex as a minimal bun cli for multiple codex accounts, cloud-synced sessions, and account switching.
- [building a software factory](https://hraness.com/writing/building-a-software-factory): I’ve been building a software factory with 15 Codex subscriptions, working across a dozen software projects over the last month.
- [3 lessons for founders from my time at zo computer](https://hraness.com/writing/3-lessons-for-founders-from-my-time): what I learned building at the frontier.
- [harnessing puerto rico](https://hraness.com/writing/harnessing-puerto-rico): on agent harnesses, puerto rico, the Way of Hra, and making music again.
- [computronium](https://hraness.com/writing/computronium): on vibe computing, abstraction, and virtual living matter.
- [coding as music](https://hraness.com/writing/coding-as-music): on ai enabled coding, making music, and discovering what was already there.
- [a home for the mind](https://hraness.com/writing/a-home-for-the-mind): on architecture, malleable software, and a shell worth living in.
- [life and llms](https://hraness.com/writing/life-and-llms): on synchronicity, improvisation, and the magic of making things up well.
- [the future of software](https://hraness.com/writing/the-future-of-software): on legalese, pattern languages, transparency, and machine-generated code.
- [what is an agent harness?](https://hraness.com/writing/what-is-an-agent-harness): The program around the model: context, tools, loop, session, and translation. Why benchmarks name it, and how ALGAL makes it a value you can replay and grow.
- [relationships](https://hraness.com/writing/the-relationships-pack): The Relationships pack brings together contact management, message assistance, source-cited dossiers, and shareable life timelines.
- [knowledge](https://hraness.com/writing/the-knowledge-pack): The Knowledge pack covers cited research, memory with sources, trading-system design, and a daily news page that explains its rankings.
- [media](https://hraness.com/writing/the-media-pack): icon.place, SlopCamera, and Soundfish keep icons, video, and music as sources an agent can revise, and two of them run seeded or evolving work on ALGAL.
- [tools for token maximalists](https://hraness.com/writing/tools-for-token-maximalists): Tools for Token Maximalists brings together agent routing, compaction, testing, capability checks, collaboration, and software-factory reporting.
- [the thread through hraness](https://hraness.com/writing/the-thread-through-hraness): Every hraness project is a piece of one computer: a place you own, where work leaves evidence, permission is explicit, and useful methods accumulate.
- [the manager loop](https://hraness.com/writing/the-manager-loop): One agent holds the plan, another holds the work, and a progress surface sits between them. Where it came from, what it fixes, and how it fails.
- [ra-ness](https://hraness.com/writing/ra-ness): To be like Ra, to harness Ra-ness, make Creation a daily practice.

## Reference
- [when Ben Guo picks a frontier model](https://hraness.com/prompting.md): What predicts whether Ben Guo starts a Codex, Claude Code, or Devin session on a frontier model, read twice from his local stores, and the ALGAL router kept in step with the picks.
- [agent infrastructure](https://hraness.com/reference/agent-infrastructure.md): durable sessions, orchestration, and review for coding agents.
- [local-first software](https://hraness.com/reference/local-first-software.md): owning state on the device, syncing on the owner's terms.
- [knowledge systems](https://hraness.com/reference/knowledge-systems.md): markdown vaults, retrieval, and evidence beside the code.
- [web delivery](https://hraness.com/reference/web-delivery.md): metadata, sitemaps, social images, and proof of which commit production serves.
- [design systems](https://hraness.com/reference/design-systems.md): primitives, tokens, and brand catalogs shared across products.
- [browser media](https://hraness.com/reference/browser-media.md): audio, midi, and generative media in the browser.
- [accounts and commerce](https://hraness.com/reference/accounts-and-commerce.md): shared identity, billing, and marketplace payouts across products.
- [the factory](https://hraness.com/reference/the-factory.md): one engineer, many products: monorepo operations and agent workflow.
- [rust systems](https://hraness.com/reference/rust-systems.md): one cargo workspace, many small crates: ports, deterministic cores, and effectful shells.
- [programming languages](https://hraness.com/reference/programming-languages.md): small languages built to be run, measured, and replayed.
- [peer-to-peer systems](https://hraness.com/reference/peer-to-peer-systems.md): identity, discovery, transport, and consensus without a server in the middle.
- [computer science](https://hraness.com/reference/computer-science.md): simulation, evaluation, and complexity treated as engineering inputs.
- [correctness](https://hraness.com/reference/correctness.md): the methods that make agent-written software hold up: proofs, properties, replay, and receipts.
- [reference: one writer per session: leases and fencing for durable agent sessions](https://hraness.com/reference/agent-infrastructure/session-custody.md): One fenced writer per machine keeps a coding-agent session consistent through sleep, crashes, and closed laptops. How custody transfer, leases, and process generations work in practice.
- [reference: idempotent command records: the audit log an agent runtime owes you](https://hraness.com/reference/agent-infrastructure/record-before-dispatch.md): Every mutation is recorded before dispatch, bound to an idempotency key, and reconciled without speculative replay. The command-record design behind durable agent sessions.
- [reference: isolated provider accounts: why agent capacity means n subscriptions, not one api key](https://hraness.com/reference/agent-infrastructure/isolated-provider-accounts.md): Running coding agents at capacity means multiple provider accounts with explicit, evidence-bound handoffs. How account isolation and movement actually work.
- [reference: deterministic verification loops an agent can trust](https://hraness.com/reference/agent-infrastructure/deterministic-verification-loops.md): Agents verify interfaces against repeatable states and fixtures, not shared staging. The port-and-world pattern behind deterministic frontend verification.
- [reference: steer, queue, or redirect: three semantics for live agent control](https://hraness.com/reference/agent-infrastructure/live-agent-control.md): Steering a running coding agent has at least three distinct semantics: queue a message, steer the current turn, or redirect the task. What each one commits to and when to use it.
- [reference: state models where invalid states cannot exist](https://hraness.com/reference/local-first-software/invalid-state-design.md): Local-first apps survive on the strength of their state model. Modeling invalid states out of existence and parsing every foreign value from unknown, with examples from shipping products.
- [reference: content addressing for browser apps: dedupe, verify, sync](https://hraness.com/reference/local-first-software/content-addressed-documents.md): Content-addressed documents give local-first apps stable identity, free deduplication, and verifiable sync. How the pattern works in IndexedDB and on the wire.
- [reference: storage quotas and encrypted sync: budgeting bytes on someone else's machine](https://hraness.com/reference/local-first-software/encrypted-sync-quotas.md): Browser storage is a budget, not a disk. Quota discipline, encrypted sync with hard limits, and clean recovery: the operational side of local-first that tutorials skip.
- [reference: local-first doesn't need crdts: a state model for single-user apps](https://hraness.com/reference/local-first-software/local-first-without-crdts.md): Most single-user apps don't need CRDTs. An ordered log and content addressing cover single-writer sync, with an honest look at when local-first is the wrong call entirely.
- [reference: markdown and git are the database; everything else is a derived index](https://hraness.com/reference/knowledge-systems/markdown-authority.md): A knowledge base for coding agents works best when Markdown and Git stay authoritative and every index (graph, FTS, embeddings) is a rebuildable projection.
- [reference: hybrid retrieval: exact, text, and semantic search together](https://hraness.com/reference/knowledge-systems/hybrid-retrieval.md): Combining exact match, full-text search, and embeddings over a Markdown vault, with rank fusion kept inspectable as separate evidence, not a silent boost.
- [reference: source capture with provenance: a manifest for everything the agent read](https://hraness.com/reference/knowledge-systems/source-capture-provenance.md): Capturing a source into a knowledge base means keeping the raw bytes, the normalized note, and a manifest that records where every claim came from.
- [reference: typed relationships vs. wikilinks: what a knowledge graph buys an agent](https://hraness.com/reference/knowledge-systems/typed-relationships.md): Typed relationships between notes give agents provenance and bounded graph context that plain wikilinks can't. Where the line sits between authored edges and derived ones.
- [reference: the app router metadata checklist, and where it silently breaks](https://hraness.com/reference/web-delivery/typed-metadata-contract.md): Next.js App Router metadata fails silently in a handful of known places: metadataBase, title templates, absolute og:image URLs. A checklist built from shipping sites.
- [reference: crawler policy, sitemaps, and feeds that stay truthful](https://hraness.com/reference/web-delivery/crawler-policy-sitemaps-feeds.md): Robots, sitemaps, and Atom feeds all describe the same public surface. Keeping them generated from one registry so none of them can lie.
- [reference: accept: text/markdown in production](https://hraness.com/reference/web-delivery/content-negotiation-markdown.md): Serving a Markdown representation of public pages through Accept negotiation and sibling .md URLs: Vary headers, q-values, and why it isn't cloaking.
- [reference: og images as build artifacts: deterministic social cards, zero runtime](https://hraness.com/reference/web-delivery/deterministic-social-images.md): Social images generated deterministically at build time from the same registry as the page: no remote assets, no screenshot service, no drift.
- [reference: deploy proofs: verifying the published artifact is the reviewed source](https://hraness.com/reference/web-delivery/delivery-proofs.md): A deployed page should be provably the commit that passed review. Delivery proofs, exact-SHA production checks, and fail-closed release plumbing.
- [reference: token cascades across a product family: one brand, many surfaces](https://hraness.com/reference/design-systems/cascade-order.md): A design system for a family of products is a cascade: tokens, then reset, then primitives, then product rules. How the layering holds across a dozen sites.
- [reference: accessible primitives without re-implementing focus or keyboard](https://hraness.com/reference/design-systems/accessible-primitives.md): Accessible primitives are a custody decision: let React Aria own focus, keyboard, and screen-reader behavior, and keep product code on top.
- [reference: an icon pipeline agents can read: manifest, provenance, immutable releases](https://hraness.com/reference/design-systems/icon-pipeline.md): Icons generated from a brand catalog with a checked manifest and immutable releases: an icon pipeline legible to agents and reproducible by anyone.
- [reference: a /design gallery as the executable spec](https://hraness.com/reference/design-systems/gallery-as-contract.md): Every product mounts the same /design gallery built from real components, so the spec is executable and drift shows up as a failing check, not a stale doc.
- [reference: web audio graphs that stay deterministic](https://hraness.com/reference/browser-media/deterministic-web-audio.md): Deterministic Web Audio means separating the audio clock from the frame clock and treating the graph as data. Patterns from a browser MIDI editor and a sound machine.
- [reference: content-addressed media in the tab: identity without titles](https://hraness.com/reference/browser-media/content-addressed-compositions.md): A composition whose URL is its hash can't be renamed out from under you. Content addressing for browser media: encoding, dedupe, and sharing without a server.
- [reference: canvas as a control surface an agent can operate](https://hraness.com/reference/browser-media/canvas-sequencing.md): Canvas sequencing UIs that hold frame budget and stay operable by software, not just eyes: state outside the DOM, hit-testing by construction, scripted verification.
- [reference: local inference in the tab: what fits, what's cached, what it costs](https://hraness.com/reference/browser-media/local-inference-in-the-tab.md): Running models in the browser means living inside storage quota and memory limits. What fits in a tab, how to cache it, and when local inference is the right call.
- [reference: one identity, many products: shared identity, per-app entitlement](https://hraness.com/reference/accounts-and-commerce/one-identity-authority.md): One account authority signs users into many products while each product keeps its own sessions, data, and entitlements. The seam that makes a suite possible.
- [reference: idempotent checkout and signed webhooks, fail-closed](https://hraness.com/reference/accounts-and-commerce/idempotent-checkout-webhooks.md): Checkout state comes from signed webhooks processed idempotently, never from the success redirect. The fail-closed pattern for payments across products.
- [reference: a credits ledger agents can spend against: double-entry for compute](https://hraness.com/reference/accounts-and-commerce/double-entry-credits.md): Prepaid credits for agent-driven spend need double-entry discipline in a single transaction: holds, captures, and idempotent retries that never double-charge.
- [reference: marketplace payout boundaries: what the platform owns and what it never touches](https://hraness.com/reference/accounts-and-commerce/marketplace-payouts.md): A marketplace for paid conversations has to decide exactly which money it holds and which it merely routes. Payout boundaries, Connect, and the asker-askee split.
- [reference: cataloged dependencies: one registry for a one-person monorepo](https://hraness.com/reference/the-factory/monorepo-catalog.md): Bun catalogs, one lockfile, and pinned immutable releases give a one-person monorepo dependency discipline that scales across dozens of products.
- [reference: merge queues for agent-written commits: affected checks and serialized integration](https://hraness.com/reference/the-factory/affected-checks-merge-queue.md): When agents write most commits, the merge queue enforces policy instead of reviewing code: affected checks, resource lanes, and serialized integration for one human.
- [reference: agent skills as tested, released procedures](https://hraness.com/reference/the-factory/skills-as-procedures.md): A skill that lasts is a procedure with tests and an immutable release. How portable skills turned repeated work into durable machinery.
- [reference: reviewing agent work: gates, evidence, and the final read](https://hraness.com/reference/the-factory/reviewing-agent-work.md): One reviewer can only check what the gates don't already prove. Structuring agent work so evidence is machine-checked and the human reads only what needs judgment.
- [reference: how we split a p2p system into small crates (and the rules that survived)](https://hraness.com/reference/rust-systems/workspace-of-small-crates.md): How a peer-to-peer Rust workspace was split into small crates: what earns a crate boundary, the dependency rules that survived, and where the split went too far.
- [reference: when to make something a crate instead of a module](https://hraness.com/reference/rust-systems/crate-vs-module.md): Crate boundaries are a dependency and test-boundary decision, not a file-organization one. The working rules used across the Hraness Rust workspaces.
- [reference: deterministic cores, effectful shells](https://hraness.com/reference/rust-systems/deterministic-core-effectful-shell.md): The pattern behind the engine and the network alike: a deterministic core that owns the rules, and effectful shells that own IO, so tests replay the world.
- [reference: closed error sets and parsing from unknown](https://hraness.com/reference/rust-systems/closed-error-sets.md): Closed error enums, parsing every foreign value from unknown, and rejecting noncanonical input at the boundary: the error discipline shared across the crates.
- [reference: a desktop app around a headless rust core](https://hraness.com/reference/rust-systems/headless-core-desktop.md): How Valhalla's retired menu bar stayed a thin shell over a headless Rust core, and why vhalla tui and vhalla status --json could replace it without moving any logic.
- [reference: a policy language that decides what simulated organisms do](https://hraness.com/reference/programming-languages/bounded-policy-language.md): Designing a bounded policy language for simulated organisms: bounded integers, local sensing, no recursion, and why a policy VM is not a general-purpose language.
- [reference: designing a vm cost model: instruction pricing for a bounded language](https://hraness.com/reference/programming-languages/vm-cost-model.md): Every interpreter step, sense, and action carries a versioned cost, and experiments cap total fuel. How to price a small VM so untrusted programs stay bounded.
- [reference: deterministic semantics: seeded order, atomic commits, replay](https://hraness.com/reference/programming-languages/deterministic-semantics.md): A language whose execution must replay bit-for-bit needs seeded activation order, atomic commits, and no hidden clocks. The semantics that make replay possible.
- [reference: file formats and protocols as small languages](https://hraness.com/reference/programming-languages/protocols-as-languages.md): Composition encodings, frontmatter schemas, and wire formats are small languages too; designing them with the same care as syntax pays off in validation and identity.
- [reference: versioning a language without breaking saved artifacts](https://hraness.com/reference/programming-languages/versioning-a-language.md): When saved artifacts outlive the interpreter, the language needs explicit versions and migrations. Keeping every old program runnable, or honestly retired.
- [reference: identity without a central authority](https://hraness.com/reference/peer-to-peer-systems/identity-without-authority.md): In a peer-to-peer network the keypair is the identity: no signup, no recovery email. How cryptographic identity, display names, and verification work without a server.
- [reference: peer discovery in layers: mdns, bootstrap, dht, and when each fails](https://hraness.com/reference/peer-to-peer-systems/peer-discovery.md): Peer discovery stacks local broadcast, known bootstrap nodes, and distributed lookup. Each layer fails differently. A layered design from a working p2p system.
- [reference: a wire protocol that survives version upgrades](https://hraness.com/reference/peer-to-peer-systems/wire-protocol-design.md): A wire protocol between peers that upgrade at different times needs explicit framing, versioned messages, and a policy for unknown fields. Design notes from a live system.
- [reference: consensus for a group chat: why raft assumes things your peers can't promise](https://hraness.com/reference/peer-to-peer-systems/room-scale-consensus.md): Consensus at room scale means a handful of peers that sleep, lose connectivity, and rejoin. Why datacenter algorithms don't fit and what the smaller problem actually needs.
- [reference: journaling for p2p apps: wal ideas outside the database](https://hraness.com/reference/peer-to-peer-systems/journals-and-ledgers.md): An append-only journal gives a peer an auditable record of everything it did and saw: the same discipline databases call a WAL, applied to a p2p client.
- [reference: what minimal systems can show](https://hraness.com/reference/computer-science/minimal-systems.md): Minimal-systems research asks what simple executable parts do together. What a small simulation can demonstrate, what it can't, and how to keep claims within that limit.
- [reference: deterministic simulation without foundationdb's budget](https://hraness.com/reference/computer-science/deterministic-simulation.md): Deterministic simulation is a discipline, not a framework: seeded ordering, atomic steps, and a checker that proves conservation. Building it into a small engine.
- [reference: feasibility checking and witness runs](https://hraness.com/reference/computer-science/feasibility-witness-runs.md): Before a simulation challenge can measure anything, the engine has to prove it's solvable: a checked witness run under the same rules and resource limits.
- [reference: your benchmark is an experiment: measuring behavior without overclaiming](https://hraness.com/reference/computer-science/measuring-emergent-behavior.md): Treating every benchmark as an experiment: matched controls, component-removal tests, and explicit limits on what a measured behavior actually demonstrates.
- [reference: p-vs-np-adjacent experiments: what they can and can't tell you](https://hraness.com/reference/computer-science/complexity-experiments.md): Small programs and explicit solvers can produce real evidence about complexity: average-case, bounded-size, and clearly not a proof. Doing it without crankery.
- [reference: unreasonably robust programming: a working definition](https://hraness.com/reference/correctness/unreasonably-robust-programming.md): How Hraness writes robust software with agents: types that rule out wrong values, parsing at every edge, caps on every input, and failing closed.
- [reference: lean: proving the books balance before the tests run](https://hraness.com/reference/correctness/lean-proving-the-books-balance.md): Where a Lean proof fits in a shipping product: laws over transcripts and quorum arithmetic that CI checks like a test, and what it leaves to tests.
- [reference: tla+: checking every interleaving a test can't reach](https://hraness.com/reference/correctness/tla-checking-every-interleaving.md): TLA+ checks every ordering of events that a test might miss. How vhalla and Gobstopper use specs, and why a checked spec proves the model, not the code.
- [reference: hegel: stateful tests that find the three-step bug](https://hraness.com/reference/correctness/hegel-finding-the-three-step-bug.md): Hegel generates crash-and-restore sequences no reviewer would write, then shrinks each failure to the shortest sequence that reproduces it.
- [reference: property tests everywhere: parsers, projections, and round trips](https://hraness.com/reference/correctness/property-tests-everywhere.md): Property tests across the portfolio: round-trip laws for parsers, ordering laws for projections, and a saved corpus so a found failure is rerun forever.
- [reference: kani: checking every possible number a function can see](https://hraness.com/reference/correctness/kani-every-possible-number.md): Kani checks every input to a Rust function up to a declared limit. Where the proofs sit in the Rust crates and why the limit is part of the claim.
- [reference: claims ledgers: writing down what you did not prove](https://hraness.com/reference/correctness/claims-ledgers.md): A claims ledger lists what each feature verified, how, and what it did not. The pattern in Gobstopper's assurance ledger and GhostGet's claims register.
- [reference: planted bugs: how to test the tests](https://hraness.com/reference/correctness/planted-bugs.md): Mutation testing plants a deliberate bug and checks that the test suite fails. Where the mutants live and what a surviving mutant tells you.
- [reference: invalid states: types, result, and parsing from unknown](https://hraness.com/reference/correctness/invalid-states.md): How the portfolio handles outside data: values arrive as unknown, are validated where they enter, and fail into result types instead of exceptions.
- [reference: two implementations, one spec: parity as a test oracle](https://hraness.com/reference/correctness/two-implementations-one-spec.md): Run the same examples through two independent runtimes and each checks the other. The parity suites behind ALGAL and Oh, and what divergences they catch.
- [reference: replay without clocks: deterministic reruns as evidence](https://hraness.com/reference/correctness/replay-without-clocks.md): A run that replays bit for bit can be debugged and audited later. How ALGAL verify, xcb task replay, and Clankdar archives record the inputs of each run.
- [reference: direct: every screen by url, deterministically](https://hraness.com/reference/correctness/direct-every-screen-by-url.md): Direct renders each screen from a declared JSON world at a stable URL, so a browser check gives the same answer until the code or the data changes.
- [reference: stylex: one typed design system across every site](https://hraness.com/reference/correctness/stylex-one-typed-design-system.md): Why the portfolio styles sites with typed StyleX instead of class strings: one palette, props the compiler checks, and a CSS contract a test can assert.
- [reference: releases that prove their origin](https://hraness.com/reference/correctness/releases-that-prove-their-origin.md): How Hraness releases carry signed evidence of the commit, workflow, and run that built them, and why each later stage checks it again.
- [reference: rust where it earns its place: memory-critical cores](https://hraness.com/reference/correctness/rust-where-it-earns-its-place.md): Where Hraness uses Rust and where it doesn't: cores that must never crash, a documented ban on unsafe, and TypeScript everywhere a GC is fine.

## Roam research
- [roam research: history](https://hraness.com/roam-research/history.md): the company, sourced and dated — founding, funding, product, community, and the quiet years.
- [roam research: conaw](https://hraness.com/roam-research/conaw.md): conor white-sullivan's early posting and writing, where he argued for the idea in public before roam was a company.
- [roam research: coverage](https://hraness.com/roam-research/coverage.md): what the discourse made of roam — the articles that traveled, the backlash, and the decline narrative.
- [roam research: the idea](https://hraness.com/roam-research/the-idea.md): the unfinished business — memex to zettelkasten to roam, why it stalled, and what agents change.
- [roam research: sources](https://hraness.com/roam-research/sources.md): the catalog — every source behind every claim, dated and typed.
- [roam research: method](https://hraness.com/roam-research/method.md): how this was researched — parallel agent lanes, the evidence model, and how to correct it.

## Obsidian
- [obsidian: history](https://hraness.com/obsidian/history.md): the company, sourced and dated — dynalist, the 2020 beta, and building in public without vc.
- [obsidian: people](https://hraness.com/obsidian/people.md): shida li, erica xu, and steph ango — who they are, what they wrote, and what they believe.
- [obsidian: side quests](https://hraness.com/obsidian/side-quests.md): the pursuits around the company — minimal, flexoki, inkodye and lumi, dynalist, minecraft plugins, and the ecosystem's own projects.
- [obsidian: coverage](https://hraness.com/obsidian/coverage.md): what the discourse made of obsidian — the darling phase, the canonization, and the critiques.
- [obsidian: the idea](https://hraness.com/obsidian/the-idea.md): file over app — the lineage obsidian inherited, what it proved, and what agents do to it.
- [obsidian: sources](https://hraness.com/obsidian/sources.md): every source cited in the obsidian history, with its date and type.
- [obsidian: method](https://hraness.com/obsidian/method.md): how ai agents researched the obsidian history, the evidence rules they followed, and what they could not verify.

## Gumroad
- [gumroad: history](https://hraness.com/gumroad/history.md): the company, sourced and dated — the weekend hack, the unicorn chase, the failure essay, and the company that came back smaller.
- [gumroad: people](https://hraness.com/gumroad/people.md): sahil lavingia and the people around gumroad — who they are, what they wrote, and what they believe.
- [gumroad: side quests](https://hraness.com/gumroad/side-quests.md): the pursuits around the company — painting, the book, doge, and the antiwork umbrella that actually exists.
- [gumroad: coverage](https://hraness.com/gumroad/coverage.md): what the discourse made of gumroad — the prodigy press, the failure essay wave, and the fee backlash.
- [gumroad: the idea](https://hraness.com/gumroad/the-idea.md): the minimalist company — the lineage gumroad inherited, what it proved, and what agents do to it.
- [gumroad: sources](https://hraness.com/gumroad/sources.md): every source cited in the gumroad history, with its date and type.
- [gumroad: method](https://hraness.com/gumroad/method.md): how ai agents researched the gumroad history, the evidence rules they followed, and what they could not verify.

## Every
- [every: history](https://hraness.com/every/history.md): the company, sourced and dated — the bundle launch, the columnist years, and the ai pivot into software.
- [every: people](https://hraness.com/every/people.md): dan shipper and the people around every — who they are, what they wrote, and what they believe.
- [every: side quests](https://hraness.com/every/side-quests.md): the pursuits around the company — firefly, the early startups, the podcasts, the courses, and the columnists' own projects.
- [every: coverage](https://hraness.com/every/coverage.md): what the discourse made of every — the bundle-wave press, the pivot coverage, and the app-suite verdicts.
- [every: the idea](https://hraness.com/every/the-idea.md): the media house that ships software — the lineage every inherited, what it proved, and what agents do to it.
- [every: sources](https://hraness.com/every/sources.md): every source cited in the every history, with its date and type.
- [every: method](https://hraness.com/every/method.md): how ai agents researched the every history, the evidence rules they followed, and what they could not verify.

## Ink & switch
- [ink & switch: history](https://hraness.com/ink-and-switch/history.md): the lab, sourced and dated — the reconvening, the manifesto years, the prototypes, the track era, and the tenth year.
- [ink & switch: people](https://hraness.com/ink-and-switch/people.md): the founders, the director, the bench, the residents, and the collaborators — who they are and what they wrote.
- [ink & switch: side quests](https://hraness.com/ink-and-switch/side-quests.md): the projects around the lab — automerge, the tracks, the prototypes, muse, the residencies, and the conference circuit.
- [ink & switch: coverage](https://hraness.com/ink-and-switch/coverage.md): what the discourse made of the lab — the hacker news threads, the community press, and the outside analysts.
- [ink & switch: the idea](https://hraness.com/ink-and-switch/the-idea.md): the independent research lab as a model — the lineage it inherited, what a decade proved, and what stays open.
- [ink & switch: sources](https://hraness.com/ink-and-switch/sources.md): every source cited in the ink & switch history, with its date and type.
- [ink & switch: method](https://hraness.com/ink-and-switch/method.md): how ai agents researched the ink & switch history, the evidence rules they followed, and what they could not verify.

## Tldraw
- [tldraw: history](https://hraness.com/tldraw/history.md): the company, sourced and dated — the drawing-app experiments, the sponsorware launch, the viral fortnight, and the license-key era.
- [tldraw: people](https://hraness.com/tldraw/people.md): steve ruiz and the people around tldraw — who they are, what they wrote, and what they believe.
- [tldraw: side quests](https://hraness.com/tldraw/side-quests.md): the pursuits around the company — ruiz's pre-tldraw libraries, the demos and experiments, and the community projects the canvas attracted.
- [tldraw: coverage](https://hraness.com/tldraw/coverage.md): what the discourse made of tldraw — the launch threads, the demo virality, the license fights, and the sentiment eras.
- [tldraw: the idea](https://hraness.com/tldraw/the-idea.md): canvas-as-infrastructure — the lineage tldraw inherited, what it proved, and what agents do to it.
- [tldraw: sources](https://hraness.com/tldraw/sources.md): every source cited in the tldraw history, with its date and type.
- [tldraw: method](https://hraness.com/tldraw/method.md): how ai agents researched the tldraw history, the evidence rules they followed, and what they could not verify.

## Antithesis
- [antithesis: history](https://hraness.com/antithesis/history.md): the company, sourced and dated — foundationdb's simulation-first build, six years of stealth, the launch, and the jane street series a.
- [antithesis: people](https://hraness.com/antithesis/people.md): will wilson, dave scherer, and the foundationdb diaspora — who they are, what they wrote, and what they believe.
- [antithesis: side quests](https://hraness.com/antithesis/side-quests.md): the pursuits around the company — foundationdb itself, the nes r&d program, bugbash, and the open-source satellites.
- [antithesis: coverage](https://hraness.com/antithesis/coverage.md): what the discourse made of antithesis — the launch thread, the engineering-blog canon, the pricing complaints, and the agent-era reframing.
- [antithesis: the idea](https://hraness.com/antithesis/the-idea.md): deterministic simulation as a product — the lineage antithesis inherited, what it proved, and what agents do to it.
- [antithesis: sources](https://hraness.com/antithesis/sources.md): every source cited in the antithesis history, with its date and type.
- [antithesis: method](https://hraness.com/antithesis/method.md): how ai agents researched the antithesis history, the evidence rules they followed, and what they could not verify.

## Midjourney
- [midjourney: history](https://hraness.com/midjourney/history.md): the company, sourced and dated — twelve years of leap motion prehistory, the discord opening, v1 through v8.2, the lawsuits, and the scanner.
- [midjourney: people](https://hraness.com/midjourney/people.md): david holz and the people around midjourney — the leap motion cofounder, the staff and advisors, and the community that writes the record.
- [midjourney: side quests](https://hraness.com/midjourney/side-quests.md): the pursuits around the lab — leap motion, a print magazine, niji, patchwork, midjourney tv, the hardware program, and the union square scanner.
- [midjourney: coverage](https://hraness.com/midjourney/coverage.md): what the discourse made of midjourney — the wonder, the backlash, the realism panic, the lawsuits, and the slop saturation.
- [midjourney: the idea](https://hraness.com/midjourney/the-idea.md): the independent-lab bet — the lineage midjourney inherited, what it proved about taste and distribution, and what the world-model ambition requires.
- [midjourney: sources](https://hraness.com/midjourney/sources.md): every source cited in the midjourney history, with its date and type.
- [midjourney: method](https://hraness.com/midjourney/method.md): how ai agents researched the midjourney history, the evidence rules they followed, and what they could not verify.

## Zed
- [zed: history](https://hraness.com/zed/history.md): the company, sourced and dated — atom's rise and sunset, the xray rehearsal, the empty-repo restart, and the agent-era turn toward delta.
- [zed: people](https://hraness.com/zed/people.md): sobo, brunsfeld, scandurra, and the bench — who they are, what they wrote, and what the company's essays keep arguing.
- [zed: side quests](https://hraness.com/zed/side-quests.md): the projects around the editor — tree-sitter, xray and memo, gpui, zeta, acp, the community programs, and the fork that took the name away.
- [zed: coverage](https://hraness.com/zed/coverage.md): what the discourse made of zed — 'vaporware, but in rust,' the open-source conversion, the platform march, the ai backlash, and the delta question.
- [zed: the idea](https://hraness.com/zed/the-idea.md): the fast-editor-as-collaboration-layer idea — the lineage from engelbart through atom, what zed proved, what stalled, and what delta is for.
- [zed: sources](https://hraness.com/zed/sources.md): every source cited in the zed history, with its date and type.
- [zed: method](https://hraness.com/zed/method.md): how ai agents researched the zed history, the evidence rules they followed, and what they could not verify.

## Core automation
- [core automation: history](https://hraness.com/core-automation/history.md): the company, sourced and dated — the openai years, the january exit, the april launch, the round that kept changing, and the lab in public.
- [core automation: people](https://hraness.com/core-automation/people.md): tworek and the team he nerdsniped — who they are, what they wrote and said, and which identities stay flagged.
- [core automation: side quests](https://hraness.com/core-automation/side-quests.md): the pursuits around the company — the founders' earlier work, the competition and the internship, and the neo-lab ecosystem.
- [core automation: coverage](https://hraness.com/core-automation/coverage.md): what the discourse made of core automation — the departure press, the talent-shock launch, the funding ledger, and the thin controversy file.
- [core automation: the idea](https://hraness.com/core-automation/the-idea.md): the automated lab as the product — the lineage core automation inherited, what it has and hasn't shown, and what agents do to the argument.
- [core automation: sources](https://hraness.com/core-automation/sources.md): every source cited in the core automation history, with its date and type.
- [core automation: method](https://hraness.com/core-automation/method.md): how ai agents researched the core automation history, the evidence rules they followed, and what they could not verify.

## Morph
- [morph: history](https://hraness.com/morph/history.md): the company, sourced and dated — lingtual to innkeeper to autoinfra to morph, the hn launch, and the suite broadening.
- [morph: people](https://hraness.com/morph/people.md): tejas bhakta, the reported co-founder who isn't on the yc page, and the three-person team — who they are, what they wrote, and what they claim.
- [morph: side quests](https://hraness.com/morph/side-quests.md): the pursuits around fast apply — the prior pivots, the plugins and integrations, the other models, and the community packages.
- [morph: coverage](https://hraness.com/morph/coverage.md): what the discourse made of morph — the launch thread, the shelf-life debate, the integration ledger, and the competitor coverage.
- [morph: the idea](https://hraness.com/morph/the-idea.md): the fast-edit-model idea — the lineage morph inherited, what it demonstrated, and whether the frontier compresses the layer.
- [morph: sources](https://hraness.com/morph/sources.md): every source cited in the morph history, with its date and type.
- [morph: method](https://hraness.com/morph/method.md): how ai agents researched the morph history, the evidence rules they followed, and what they could not verify.

## Moving castles
- [moving castles: history](https://hraness.com/moving-castles/history.md): the studio, sourced and dated — the trust years, the london residency, the onchain games, the survival year, and the daemons pivot.
- [moving castles: people](https://hraness.com/moving-castles/people.md): the co-founders, the contributors, and the pseudonymous middle — who they are and what they wrote.
- [moving castles: side quests](https://hraness.com/moving-castles/side-quests.md): the pursuits around the studio — trust and foam, the gvn908 art practice, the games, and the ecosystem that built alongside.
- [moving castles: coverage](https://hraness.com/moving-castles/coverage.md): what the discourse made of moving castles — the manifesto's reception, the wired moment, the launch slate, the 'aw is dead' fight, and the pivot's first day.
- [moving castles: the idea](https://hraness.com/moving-castles/the-idea.md): who owns the subjectivity of a shared digital system — the lineage the studio inherited, what it proved, and what the pivot bets on.
- [moving castles: sources](https://hraness.com/moving-castles/sources.md): every source cited in the moving castles history, with its date and type.
- [moving castles: method](https://hraness.com/moving-castles/method.md): how ai agents researched the moving castles history, the evidence rules they followed, and what they could not verify.

## Typesafe
- [typesafe: history](https://hraness.com/typesafe/history.md): the company, sourced and dated — the founding, two years of stealth, the argument in public, and the september launch.
- [typesafe: people](https://hraness.com/typesafe/people.md): the founders, the bench, and the backers — who they are, what they wrote, and what they claim.
- [typesafe: side quests](https://hraness.com/typesafe/side-quests.md): the pursuits around the company — prior ventures, the oss perimeter, the discord, and the clones.
- [typesafe: coverage](https://hraness.com/typesafe/coverage.md): what the discourse made of jev — the launch wave, the claims audits, the independent evals, and the hn verdict.
- [typesafe: the idea](https://hraness.com/typesafe/the-idea.md): the system-one bet — the lineage jev inherits, what the launch demonstrated, and the calibration question everything hangs on.
- [typesafe: sources](https://hraness.com/typesafe/sources.md): every source cited in the typesafe ai history, with its date and type.
- [typesafe: method](https://hraness.com/typesafe/method.md): how ai agents researched the typesafe ai history, the evidence rules they followed, and what they could not verify.

## Cognition
- [cognition: history](https://hraness.com/cognition/history.md): the company, sourced and dated — the ioi apartment, the devin launch and debunk, the windsurf weekend, and the $48b arc.
- [cognition: people](https://hraness.com/cognition/people.md): scott wu, steven hao, walden yan, and the people around cognition — who they are, what they wrote, and what they claim.
- [cognition: side quests](https://hraness.com/cognition/side-quests.md): the pursuits around the product — lunchclub, the upwork demo, openhands, deepwiki, the swe model family, and the diaspora.
- [cognition: coverage](https://hraness.com/cognition/coverage.md): what the discourse made of cognition — the launch press, the debunk cycle, the windsurf saga, and the funding arc.
- [cognition: the idea](https://hraness.com/cognition/the-idea.md): the ai-software-engineer bet — what cognition inherited, what it proved, what stayed unfinished, and who inherits it next.
- [cognition: sources](https://hraness.com/cognition/sources.md): every source cited in the cognition history, with its date and type.
- [cognition: method](https://hraness.com/cognition/method.md): how two ai agents researched the cognition history, the evidence rules they followed, and what they could not verify.

## Deepseek
- [deepseek: history](https://hraness.com/deepseek/history.md): the company, sourced and dated — from the dorm-room trading bots to fire-flyer ii, the r1 shock, and the first raise.
- [deepseek: people](https://hraness.com/deepseek/people.md): liang wenfeng and the people around both companies — the zju classmates, the fund's partners, the research bench, and the diaspora.
- [deepseek: side quests](https://hraness.com/deepseek/side-quests.md): the pursuits around the flagship — the philanthropy, the compute-donation program, the edge model lines, open source week, and the raise.
- [deepseek: coverage](https://hraness.com/deepseek/coverage.md): what the discourse made of deepseek — the sputnik week, the crash, the bans, the censorship and chip sourcing debates, and the incumbent turn.
- [deepseek: the idea](https://hraness.com/deepseek/the-idea.md): the whale-funds-the-lab model — the lineage deepseek inherited, what it proved, and what it left unresolved.
- [deepseek: sources](https://hraness.com/deepseek/sources.md): every source cited in the deepseek history, with its date and type.
- [deepseek: method](https://hraness.com/deepseek/method.md): how ai agents researched the deepseek history, the evidence rules they followed, and what they could not verify.

## Andon labs
- [andon labs: history](https://hraness.com/andon-labs/history.md): the company, sourced and dated — vectorview, yc w24, the andon rename, the vending-bench arc, and the year the agents got businesses.
- [andon labs: people](https://hraness.com/andon-labs/people.md): lukas petersson, axel backlund, emil fröberg, and the named agents — who they are, what they wrote, and what they believe.
- [andon labs: side quests](https://hraness.com/andon-labs/side-quests.md): the pursuits around the evals — vectorview, the unpublished danger-cap corpus, bengt, the radio stations, and the platform at the end.
- [andon labs: coverage](https://hraness.com/andon-labs/coverage.md): what the discourse made of andon — the delighted-discovery wave, the launch-day benchmark, the ai-boss unease, and the backlash.
- [andon labs: the idea](https://hraness.com/andon-labs/the-idea.md): the safe autonomous organization — the lineage andon inherited, what it proved, and what it ships next.
- [andon labs: sources](https://hraness.com/andon-labs/sources.md): every source cited in the andon labs history, with its date and type.
- [andon labs: method](https://hraness.com/andon-labs/method.md): how ai agents researched the andon labs history, the evidence rules they followed, and what they could not verify.

## Convergent research
- [convergent research: history](https://hraness.com/convergent-research/history.md): the incubator, sourced and dated — the thesis chapter, the day one memo, the 2021 unveiling, the first cohort, and the federal turn.
- [convergent research: people](https://hraness.com/convergent-research/people.md): marblestone, gamick, rodriques, kalil, the board, the mission-control staff, and the fro founders — who they are and what they wrote.
- [convergent research: side quests](https://hraness.com/convergent-research/side-quests.md): the fro roster and the orbit around it — the subsidiaries, the incubator's own programs, the founders' other work, and the line beyond convergent.
- [convergent research: coverage](https://hraness.com/convergent-research/coverage.md): what the discourse made of convergent — the launch press, the policy uptake, the funding headlines, the cohort's outputs, and the scene's critiques.
- [convergent research: the idea](https://hraness.com/convergent-research/the-idea.md): the fro as institutional technology — the lineage it inherited, what the model proved, what stayed unfinished, and who carries it next.
- [convergent research: sources](https://hraness.com/convergent-research/sources.md): every source cited in the convergent research history, with its date and type.
- [convergent research: method](https://hraness.com/convergent-research/method.md): how ai agents researched the convergent research history, the evidence rules they followed, and what they could not verify.

## Optional
- [sitemap](https://hraness.com/sitemap.xml): Indexable HTML URLs.
- [writing atom](https://hraness.com/writing/atom.xml): First-party writing feed.
- [discoveries atom](https://hraness.com/discoveries/atom.xml): Research from the Hraness lab.
- [reading atom](https://hraness.com/reading/atom.xml): Reading notes, newest first.
- [portfolio.json](https://hraness.com/portfolio.json): Machine-readable portfolio: active projects, product packs, shared foundations, typed relationships, and canonical product copy, generated from the Hraness registries.
- Reading notes live at `/reading/{slug}` and have Markdown representations. Start from `/reading`.