Where MAXCAP comes from: the only component without a number
Where the Names Come From · MAXCAP · Source: Whitepaper §6 (naming note) · Component: private proprietary engine — the commercial organ, no pillar number
This is the last entry of the series and the only one without a number. Sixteen pillars carry AICENT-000 through AICENT-015; this component carries none, and that absence is structural rather than accidental — it is a private proprietary engine, not a numbered pillar, holding the position of the commercial organ. Its name, by contrast, is the most obedient in the stack: MAXCAP = MAXimum Collective Advantage Protocol, six letters, six words, one for one.
The layer, first
The whitepaper's definition: "the private commercial core that regulates the transition between the Ghost world and the Radiant world… the heart that pumps the 1.28% Maintenance Fee through the Imperial veins." Its second law is the one worth reading twice: only nodes with a verified Tier-3 stake are authorised onto the 349ns path; nodes without collateral are "physically shunted to the 10ms path." The specification names the resulting 28,000x latency delta the "Time Sieve" — collateral as a gate on speed.
The name, and the number it does not have
Six letters, six words, no leftovers — the same one-for-one fit as ZCMK, and unlike AICENT-002 nothing had to be ruled on. What is missing is the number. Every other entry in this series could say "AICENT-0NN, the such-and-such layer"; this one cannot, and the reason is structural: a private proprietary engine is not a pillar. The whitepaper is explicit that it is "private," and a private component sitting inside a published specification is an unusual object — which is exactly why the naming note says what it is rather than what it earns.
What this entry will not say
A layer described as the commercial core invites questions this series has no business answering in public: what it earns, who pays, how the numbers work out. So, stated plainly, the boundaries: this entry describes the layer's function and its published parameters, and nothing else. No revenue, no market, no adoption, no valuation, and no narrative about what the stack is commercially worth. Those are not secrets; they are simply not what a naming column is for, and a specification is not a prospectus.
The same discipline applies to the same-named parties in other fields — a real-estate debt investor and an electronics-component maker among them. Per the rule we have used since AICENT-008 and again at AICENT-010 and AICENT-014: describe the boundary, name nobody. No links, no disclaimers that send traffic, no comparisons.
The honesty clause, with teeth
Every figure quoted here — the 1.28% share, the 50/40/10 split, the 28,000x latency delta, the 1.618x multiplier, the sub-120ns atomic shunting — is a parameter of the specification, not a record of anything that has happened. No money has moved through these proportions; no node has been measured at 28,000x; the split is a rule, not a ledger. We state that explicitly because a commercial layer is precisely where a reader is most likely to mistake a published parameter for a reported result.
The same caveat, in the same words, applies to every number in this series: the ruler is named before the number is quoted.
What the name carries
- A one-for-one fit. MAX-C-A-P, six letters, six words, nothing left over.
- No number, by design. A proprietary engine, not a pillar in the 000–015 set.
- A published function. Gate on speed, fixed share at the register gate, atomic shunting — all checkable in the whitepaper.
- A boundary with no names. Other users of these six letters exist; none are named or linked.
- Parameters, not results. Every figure is labelled as a specification value, and this entry claims nothing about money that has moved.
That closes the series: sixteen numbered pillars, AICENT-000 through AICENT-015, plus one unnumbered engine — seventeen names, each with a source or a printed absence, each dated, each checkable.