Gareth Andrew gingerhendrix

Inferal Workspace Architecture: How We Work at Inferal

(Blog version available at https://inferal.com/blog/workspace-architecture/)

Update: Inferal Workspace is going open source!

Your org's brain that AI can use

This is not our core product. This document describes our internal operating environment - how we run the company. We share it to show the environment you'd join and demonstrate our philosophy in action. For what we're building, see What We're Building below.

Reimplement the current branch on a new branch with a clean, narrative-quality git commit history suitable for reviewer comprehension.

Steps

Validate the source branch
- Ensure the current branch has no merge conflicts, uncommitted changes, or other issues.
- Confirm it is up to date with main.
Analyze the diff

Study all changes between the current branch and main.

To make sure that the files you edit and create look good, you MUST ALWAYS use a command like the following one to export a rendered image, view it, understand how it looks and what needs improvement, and iterate - making updates to the excalidraw file, exporting, and reviewing again - until the results are pixel perfect.

npx excalidraw-brute-export-cli \
  --input slides.excalidraw \
  --output slides.png \
  --format png \
  --scale 2 \
  --embed-scene true

ALWAYS export and review. NEVER declare the work on an Excalidraw drawing or presentation done until you've reviewed its rendered visual representation to verify and adjust as needed.

You MUST NOT try and generate a Rails app from scratch on your own by generating each file. For a NEW app you MUST use rails new first to generate all of the boilerplate files necessary.
Create an app in the current directory with rails new .
Use Tailwind CSS for styling. Use --css tailwind as an option on the rails new call to do this automatically.
Use Ruby 3.2+ and Rails 8.0+ practices.
Use the default Minitest approach for testing, do not use RSpec.
Default to using SQLite in development. rails new will do this automatically but take care if you write any custom SQL that it is SQLite compatible.
An app can be built with a devcontainer such as rails new myapp --devcontainer but only do this if requested directly.
Rails apps have a lot of directories to consider, such as app, config, db, etc.
Adhere to MVC conventions: singular model names (e.g., Product) map to plural tables (products); controllers are plural.
Guard against incapable browsers accessing controllers with `allo

	"""
	Quick and dirty replication of
	"Winning Gold at IMO 2025 with a Model-Agnostic Verification-and-Refinement Pipeline" (https://arxiv.org/abs/2507.15855)
	using LangGraph.

	Export GOOGLE_API_KEY to run.
	Change the model, question and constants directly in the code (no CLI).
	"""

	import asyncio

	import React, { isValidElement } from "react";
	// @ts-ignore
	import * as ReactServer from "react-server-dom-webpack/server.edge";
	// @ts-ignore
	import * as ReactClient from "react-server-dom-webpack/client.browser";

	import { DurableObject } from "cloudflare:workers";

	type FirstParameterOr<T, Fallback> = T extends (
	arg: infer U,

	// Update globs depending on your framework
	---
	name: tailwind_v4
	description: Guide for using Tailwind CSS v4 instead of v3.x
	globs: ["*/.{js,ts,jsx,tsx,mdx,css}"]
	tags:
	- tailwind
	- css
	---