This repository is a curated markdown list of companies that use non-whiteboard interview techniques. Despite having 50K+ stars, it is not a software application in any meaningful sense — it is a community-maintained README with a CI pipeline that validates markdown formatting and link integrity. The only source file, index.js, is an empty module export (effectively a no-op). All 'functionality' lives in the CI workflow and package.json linting configuration. The architecture is trivial: GitHub Actions runs two jobs on PRs/pushes to main. The 'remark' job installs Node dependencies and runs remark-cli with a set of linting plugins to enforce markdown style (alphabetized lists, no tabs, no trailing slashes on URLs, etc.). The 'links' job uses lychee-action to verify all URLs in README.md return valid HTTPS responses. There is no application logic, no data processing, no API — just static file validation. The repository's value is entirely in the README content (the company list), not in any code. The CI pipeline is a standard, unremarkable markdown linting setup. The last commit was in June 2026, but the project has no real development trajectory — it accepts PRs that add list entries and runs CI to validate them. The codebase itself has no reusable components; the CI workflow is generic boilerplate that could be copied from any markdown linting tutorial.

Noodle is an open-source AI agent orchestration framework written in Go that manages autonomous coding agents through a kitchen-brigade model. It operates as a background daemon with a CLI (`noodle start`, `noodle status`, `noodle worktree`) and a real-time React/TypeScript web UI. The core loop reads backlog items (from markdown files via shell-script adapters), schedules multi-stage orders, dispatches agents (Claude Code, Codex) into isolated git worktrees, monitors their progress via NDJSON event logs, handles merge conflicts, and supports human-in-the-loop review gates. The system is config-driven via `.noodle.toml` and uses skills (directories with `SKILL.md` frontmatter) as the sole extension point for defining agent behavior and task types. Architecturally, Noodle is a monolith with clear internal packages: a state-machine loop (`loop/`), dispatchers for process and remote runtimes (`dispatcher/`), a parser pipeline for provider NDJSON output (`parse/`, `stamp/`), session monitoring (`monitor/`), event-sourced state management (`internal/reducer/`, `internal/state/`), a projection layer for incremental UI updates (`internal/projection/`), and a WebSocket server (`server/`). The UI is built with TanStack Router, React Query, and D3 for agent tree visualization. State is persisted as JSON/NDJSON files under `.noodle/`, with crash recovery via atomic snapshots and idempotent event ingestion. Key design patterns include: event sourcing with a deterministic reducer and effect ledger, directory-based fixture testing with source hash validation, a failure taxonomy with recoverability classification, mode gating for autonomy levels (auto/supervised/manual), and a plugin system via JSON-RPC for external runtimes. The codebase demonstrates strong engineering discipline with extensive test coverage (unit, integration, e2e with Playwright), CI/CD via GitHub Actions and GoReleaser, and a comprehensive brain vault for agent knowledge persistence.