Creed is the one operator-specific layer. Where the charter, the executive, and the archive are shared and civic, creed is the overlay shaped around a single operator's repos, machine, and way of working. This page describes the idea of that layer, not its contents, because the contents are deliberately private. It is one of the four parts of Ordova.
Three of the four parts are the same for everyone. The fourth is shaped around one person's setup, and only that person's.
Creed holds the operator-specific layer: the skills, the machine discipline, and the configuration that fit one operator's particular repositories, store, and habits. It is not generic, and it does not pretend to be.
It lives under the operator's own namespace rather than the studio's, which keeps the ownership of it unambiguous.
Creed is personal professional capital, and it is kept private deliberately, not by neglect.
The methodology around it is documented in the open, and this page is part of that. What stays private is the operator's instance: the skills and discipline grown around one way of working. That is exactly the capital the charter sets out to keep on our own side.
So this page names the layer and its purpose, and says nothing of what is in it. The line between the shared idea and the private contents is the point, not an omission.
Creed does not replace the executive; it composes on top of it, and wins where the two name the same thing.
On a machine the two are installed together. The executive provides the generic core, and creed overlays the operator-specific layer on top of it. Where both define the same file, the overlay takes precedence, so the operator's version is the one that runs.
Shared machinery that happens to depend on an operator's setup stays in the executive behind a guard, so it simply does nothing when creed is absent rather than breaking.
A machine with no creed at all is fully supported, which is how we know the line was drawn honestly.
The charter, the executive, and the archive are designed to work on their own. Every step that depends on the overlay self-skips when the overlay is not there, so the shared system is whole without any operator layer attached.
That is the real test of the boundary: if the shared parts need the private one to function, the line was in the wrong place. They do not, so it is not.
The charter, executive, and archive pages are derived views of public sources, so each one carries a source anchor that flags it when its source moves. This page does not, and on purpose: creed is private, so there is no public source to anchor it to. It is a description of the idea of the operator layer, kept conceptual so the boundary it describes is never crossed by the page itself.