There is a company in this: a code review that reads every layer, for somebody to build

Say the business plainly: a review attached to a repository that keeps the layered graph current per commit and shows each change at every altitude, sold to anyone generating code faster than they can review it, and to teams whose threat model and component layer should be the same graph. What is defensible is the record and the loop, not the model; the scripts are Apache-2.0 and a founder needs a second language and a first customer, not permission.

Decided by. Nobody yet: a candidate for Dinis to read, comment on and decide (keep, rewrite, merge, cut, article first, later, not doing it).

Note. One of the business plans published for founders on sgit.ai; an example of the book's advice to start a company from a published plan. The business model settled by the layers: they are the customer's, so the loop runs where the code is, and a company that locked customers into its layers would be selling the one thing it has no right to own. Sell the customised deployment, the running of the loop and the versioned record; give away the grammar, the parser (a commodity) and the model (somebody else's). The offer in one line, from open-source.sgit.ai: 'You can take it. It will cost you that. Or you can pay me, and have it next week.' Who to sell it to: not developers, who have just been told they do not need review, but the people who buy, invest in and acquire software, as due diligence; every vendor that receives the agent has a reason to run it on itself first, which is how review gets back to the developers. 'What differs is the first customer, and the first customer decides whether a company exists.'

Where it comes from

Code review as a fractal semantic graph For somebody to build (newsroom)
If somebody built a company on code review The company; The grammar is fractal, the layers are yours (newsroom)
Send an agent, not a spreadsheet The twist on the last article (newsroom)

What it answers in the 2018 book

none named

Where it goes

Chapter Be a founder: the expert founders, part Start the company (drafting); topic Be a founder (or a one-person service).

Other ideas proposed for the same chapter: Be a founder: the expert can build first now, and the test is whether they miss it, The expert founders, in numbers: 45 is the mean age, experience doubles the odds, a third of US startups have one founder, The SaaS apocalypse will be decided by inertia, not by AI, because AI is available to both sides, Users were never happy: 91% frustrated, 80% of features rarely or never used, $21 million a year in idle licences, What SaaS refused to build to protect its moat is exactly what a customer's agent needs, A company sits in the two moves on the map: a guess becoming a product, and a product becoming a commodity.

Node idea:a-company-in-the-review in graph.json; see it in the graph. Source: admin/content/graph/ideas.json.