What OwnCharter does not do
The current limits of OwnCharter, stated plainly: no customers, no fleet-wide Control Information Center yet, and separate trust worlds for pack signing and fleet certificates.
Why this page exists
A technical director sent to assess a claim should not have to discover its limits by accident. This page states the current boundary and the construction that is real today.
OwnCharter is pre-alpha, heading for early alpha. The Gate, signed capability packs verified against a pinned root, no self-grant, and the hash-chained permanent record are the current product truths.
There are no customers
OwnCharter has no customers. I run my own governed agent operation on it while I build it, with my own business on the line.
That is not a substitute for customer evidence. It is the operating condition under which the current claims are made: the construction runs, and the broader product is still being built in the open.
The fleet view is not built
The fleet-wide Control Information Center is not built yet. It is being built in the open.
The Gate under every agent it will show is running today. Its authorization produces the record that makes a future fleet view worth trusting. You cannot measure what you did not authorize.
Two trust worlds, not yet one
Pack signing and the fleet certificate authority are separate trust worlds today. They are not presented as one integrated trust system.
What is true now is narrower and enforceable: signed capability packs verify against a pinned root at the Gate. Anything unsigned or unverified is denied before execution.
What I intend to deliver
I intend to deliver the fleet-scale Control Information Center, bringing order lifecycle, fleet health, and the records behind agents into one view. It is roadmap, not current product.
I will keep the boundary on this page current as the product changes. The newsletter carries the build record in between.