Loading the page.
Documentation
Journal
Frontend
Backend
Admin
CI/CD
Loading the page.
Card · concepts · updated 18.07.2026
concept · running a company through specs
Spec-Driven Company (SDC) - a way to run a company where the single source of truth is specs in git, code and content execute them, CI verifies them, and AI agents roll out changes. The owner updates tables - everything else moves on its own.
SDD
Root
≤1 screen
Spec
CI test
Verification
agents
Implementers
docs/spec.md - owner updates the table | parses verification (CI test) - red until code catches up | verifies carrier module - the only place for values in code | imported by the whole project - agents roll out the change # truth chain: spec - verification - carrier - project▌
What it gives you
What it is not
The seven laws of SDC - how it works in practice:
Families · Adjacent approaches - and how SDC differs:
| Type | What it's for | Today |
|---|---|---|
| Spec-Driven Development | a feature spec guides code development | the root of SDC; a wave with GitHub Spec Kit (09.2025) |
| docs-as-code | docs live in git and ship through a pipeline | half a concept: no obligation for code to follow docs |
| design tokens | design values in one source | a narrow special case of the chain - visual values only |
| SSOT | a single source of truth for data | an umbrella principle; SDC adds checks and agents |
| SDC | the entire company as a set of specs with checks | this site has worked this way since July 2026 |
The idea took a decade to assemble - an agent fleet made it practical:
2010s
docs-as-code
Documentation moves into git and learns to live like code: reviews, versions, pipelines.
2017
design tokens
Design values become data: one table - every platform. A special case of a future vertical.
09.2025
GitHub Spec Kit
SDD becomes an industry term: the spec comes first, and code is generated from it.
2026
Spec-Driven Company
Agent fleets remove the main barrier - the cost of execution. The principle expands from code to the entire company; this site is a living example.
The path has been tested on this site - six verticals in one day:
Live case
Editing one palette table recolored 68 site files in one pass
Owner's verdict on five color conflicts - a 10-role spec table - a 666-replacement codemod - verification prevents displaced values from returning. July 18, 2026, this site.
Breakdown on this page · 2026-07-18
Scale on this site
Six specs with verification hold up the entire frontend: grid, palette, radii, type scale, viz palette, glossary
Each has a canonical table in docs + a single module in code + a CI test. Plus 1150+ tests in the shared suite.
vibecoding.tech (repo) · 2026-07-18
Against docs rot
Documentation does not become stale by design: a mismatch between docs and code means red CI
The classic pain of "docs lie" is solved not by discipline but by mechanics: every spec has a consumer test. A spec without a consumer is a candidate for archiving.
vibecoding.tech (repo) · 2026-07-18
What they say - and what practice shows:
Docs will become outdated anyway
Every spec has a consumer test: if it diverges from code - CI goes red. It has no way to lie.
This is bureaucracy for a solo founder
The spec for the entire site's grid is just 10 lines. Write it once, then only edit it by replacement.
You can't trust agents with prod
An agent can't stray from the spec: the check fails the build. Gates are stricter than human review.
It's easier to keep the truth in code
Code is read by programmers, a spec - by the owner in 30 seconds. Decisions are made by whoever sees the table.
The terms are adjacent, the work is different:
| Term | What it is | Example |
|---|---|---|
| ·SDC | a company built on specs: docs - code - agents, CI checks | editing the palette table recolors the site |
| ⊃SDD | spec-driven development - about code | GitHub Spec Kit generates a feature from a spec |
| ⊃⊃SSOT | a single source of truth - the shared principle | a product's price lives in one database |
| ⊃⊃⊃vibecoding | assigning tasks to agents in natural language | the SDC execution layer |
A company where the single source of truth is specs in text files (git), code and content execute them, and a machine performs verification: changing a spec without changing the code breaks CI. The owner changes tables, AI agents roll out the changes.
SDD is about code: a feature spec drives development. SDC applies the same principle to the whole company: specs for the site palette and grid, content queues, brand rules, and processes. The implementer is different too: not a developer with a copilot, but a fleet of agents.
A spec here is a one-screen table of values, not a 40-page technical brief. The canonical grid for the entire vibecoding.tech site is just 10 lines. Rule: if the owner does not need a line to make a decision - it belongs in code, not the spec.
Because every spec has a consumer test in CI: it parses the table from the document and checks it against the code. If they diverge - the build stays red until someone catches up. Documentation physically cannot lie.
Spec-code-verification mechanics work with people too (that is classic SDD plus discipline). But the scale of "editing a table recolors 68 files in one pass" comes specifically from an agent fleet: such a codemod is tedious and expensive for people.
Tooling-wise - almost nothing: git and CI are already available in any project. The real cost is an agent fleet (subscriptions around $100-200/mo for Claude Code or Codex) and one-time work to freeze the specs: six verticals on this site took one day.
The mechanics work in full: git, CI, and docs do not depend on borders. The only dependency is access to agents: Western ones (Claude Code, Codex) are paid for from Russia through intermediaries or foreign cards; the local alternative is GigaCode and open models through OpenRouter.
Start with one vertical: choose the set of values most scattered across the codebase (usually the palette), freeze it in a table in docs, create a single propagation module and a verification test. Then proceed in waves: grid, typography, processes.
Related concepts
Vibecodingthe SDC execution layer: agents that roll out specs
AI agentwho does the work: an autonomous model with tools
Coding agent ratingschoosing executors by measurable benchmarks
Entry · spec-driven-company · facts · 7 (source and date for each) · card edited 2026-07-18 · facts verified 2026-07-18
Where to go next
New cards, price and limit changes, ranking shifts - by email, no spam.