Human Systems
The entire system depends on humans behaving in specific ways the engineering cannot enforce; this section treats the human substrate KCC operates on as part of the design.
The KCC specification is precise about engineering and less precise about the humans the engineering depends on.
The entire system depends on humans behaving in specific ways that the engineering cannot enforce.
Engineers must trust the platform enough to use it rather than route around it. Reviewers must engage substantively. Maintainers must care about their capabilities. None of this is engineering; all of it is required for the engineering to work. KCC is a sociotechnical system. Five social components are load-bearing — each can be designed for, though none can be unilaterally enforced.
12.5.1 Trust as Infrastructure
Without trust, bypass accelerates and the compounding mechanism fails. Trust is the predictable consequence of three observable properties: competence (the platform does what it says), transparency (costs visible, decisions auditable, failure modes acknowledged), and a non-punitive culture (bypass is platform feedback, workslop is a system signal, load over-utilization triggers backpressure not productivity demands).
Trust is infrastructure in the same sense that decision traces are infrastructure: invisible when working, catastrophic when absent, costly to repair once broken.
12.5.2 Ownership Psychology
Anonymous ownership produces unowned outcomes.
KCC insists on named individuals, not team aliases. When a capability is owned by platform-team@org, no specific human feels accountable — issues get bounced and the capability rots. A named owner can be asked and must respond, hand off, or deprecate. Ownership is a costly commitment the organization recognizes and budgets for.
12.5.3 Autonomy Evolution
The HITL → HOTL trust ladder applies to humans too: reviewers earn calibrated trust over time based on demonstrated behavior, not role labels. Behavior-based trust avoids discrimination, lets junior engineers outperform senior ones, and is recoverable — the Butler reads recent behavior more heavily than ancient behavior.
12.5.4 Resistance Patterns
When adoption produces resistance — bypass, workslop, rubber-stamping, silent contract violation — the resistance is a signal, not a failure of engineer character. Each pattern has a diagnostic question (what need is the bypass route serving? what incentive rewards workslop? why didn't the cell surface the need?) and a response that addresses the cause, not the symptom.
Resistance is information about the system.
12.5.5 Authority Without Bureaucracy
KCC creates explicit authority (kernel veto, capability direction, cell composition). The risk is bureaucratization. KCC mitigates it: authority is bounded, comes with obligations, is documented, and has term limits. Authority that does not carry corresponding obligation produces gatekeeping rather than stewardship. A healthy KCC organization treats authority positions as stewardship roles, not power positions.