technology — the builder's stone

This is the document a technical founder walks into. Every other stone can be written by the owner alone; this one is usually the ghost town's most important empty room — and when it's absent, the advisor's #1 recommendation is almost always the hire who would write it. When it does exist, it does two jobs at once: it tells a human engineer how this company builds software, and it tells every agent session working in the company's repos the same thing, with the same authority. Stack choices stop being fashion, features stop being vibes, and "we'll clean it up later" gets a written definition of later. This skill writes the room's contents down — interviewing whoever holds the technical truth (founder, first engineer, or the owner admitting what they don't know), locking answers one at a time, and shipping the result as a Business OS module: canonical TECHNOLOGY.md, machine contract, core tables, MCP server, standalone site.

This is stone 8 of 8. Read ../PROTOCOL.md before composing — the module contract, workspace layout, and definition of done live there and are not repeated here.