A sovereign entity is not a name on a Companies House register. It is an operational engine. Every entity has a purpose — whether that purpose is running a gateway, managing a revenue stream, operating a compliance function, or anchoring a kingdom. That purpose creates work. That work creates jobs. Protocol 078 formalises what the system already demands: every entity generates jobs because every entity does things.

The 42 entities of CircularOS collectively hold 2,332 sovereign jobs. Not because Jermaine assigned them manually — because the system architecture makes them inevitable. Protocol 078 ensures no entity escapes that inevitability. No entity can sit in the register with zero jobs. The minimum is 5. The expectation is more.

Source 1 — Revenue Streams: Every HOT or WARM revenue stream linked to an entity requires at least one person to manage it. That is a job. If a stream has no linked job, Protocol 078 flags it as a gap — the Entity Job Audit (MJ-ENT-001) catches it and recommends the job.

Source 2 — Protocol Execution: Protocols P001-P080 generate execution jobs. Every entity involved in protocol execution holds at least one PROTOCOL_OPS job. If the entity is listed in a protocol's entity field but has no execution job, that is a gap.

Source 3 — Operational Requirements: Every entity has administrative, compliance, and operational requirements. Director oversight, Companies House filings, covenant contribution tracking, entity health reporting. These are jobs. They may be micro or permanent — they are sovereign work.

Source 4 — Kingdom Alignment: Each entity belongs to a kingdom (Finance, Technology, Compliance, Marketing, etc.). The kingdom defines a natural job family. An entity in the Technology kingdom generates tech jobs. An entity in Finance generates finance jobs. Kingdom alignment is the most reliable predictor of what jobs an entity should hold.