The system
How it fits together
Most components are standalone. What holds them together is one shared path and a clear line between the public slice and the private system.
A slice, not the whole
Plectis is a cross-section of a larger system. What's here runs on its own; the larger working environment stays out of the public tree. Each component is chosen because it can be understood and run without that context.
The public estate
One private system stands behind everything public here, and each public object holds a different authority. The Plectis repository is the source of record for the runnable slice; this site is the reading surface projected from the same public source, and each generated page names its source refs. The companion Lean repository carries the machine-checked mathematics, where the authority is the Lean proof kernel rather than any page. The 13 papers are built in those repositories, and every deploy byte-binds the copies hosted here to their sources. If a page here and the source disagree, the source wins.
The shared path
However different the areas look, most components bind to one shared path. It runs from a project on disk through to an explanation you can read and an assimilation loop that feeds the next pass:
A component reads a project, finds the right pattern and the standard it answers to, follows a route to do some work, records the events and the evidence they produced, reaches a plain explanation, and feeds assimilation back into the system. That repetition is what makes a large system navigable.