Submittals

How a better way travels upward and returns to everyone as the next edition.

Someone at one table finds a better way to do a shared thing. They write it down as a proposal, it travels up with their season's sheet, it is read together with everything else that arrived, and what is adopted comes back down to every Cell as the next edition of the common part. That circuit is the submittal, and it is how a body of thousands improves without anyone owning the improvement.

It is load-bearing because it is the alternative to the two failures that kill shared practice. The first is a centre that issues updates: everyone waits, nothing local ever reaches the whole, and the centre becomes a target. The second is silent local editing: every Cell quietly improves its own copy, all the copies drift, and one day two Cells discover they are no longer playing the same game. A submittal is the narrow path between — local invention, freely made, travelling by a route everyone can see (Nucleus, Proposal, The edition, Polycentric Implementation of Shared Solutions).

It is also what makes local adaptation honest. A Cell may of course do things its own way. What it may not do is change the common half in secret. Translate freely, adapt openly, name what you changed and why — and send the change up, because the odds are good that somebody else needs it too (On translating, Minimum standards of interoperability, Knowledge as commons).

Its rhythm is the turning. Submittals gather across the season, are read together rather than one at a time — because the pattern across several is usually worth more than any one — and the edition changes at a turning and not before, so that nobody is ever out of the game for holding last season's card (The Season Sheet, The Clock of the Game, Retrospective).

Also called: a submittal · proposing upward Stands on: Proposal · Nucleus · Current Best Understanding · Continuous Improvement Opens onto: The edition · The Season Sheet · Curation · Knowledge as commons · Minimum standards of interoperability · Polycentric Implementation of Shared Solutions · Process (and the Process List) · LIØNSBERG Mission Control In play: Home · beyond — written at the table, read at the turning Sources: Projects/the term pages/Nucleus.md (draft, unreviewed — the Seed changes by submittal upward) · Submittals.md (wiki root; three sentences, and those tied to one commercial platform) · LIØNSBERG Mission Control.md (unmarked — propose a change to what hangs on the wall, never edit it silently) · Process For Submittals, on the process list · lionsberg.wiki: Submittals Open: The canon's own page describes the practice entirely in terms of one commercial platform and a trained project manager, which is the opposite of the paper floor everything else here assumes. · Nothing states who reads the gathered submittals, or by what standard one is adopted into an edition.