The Jobs Entity Decision

The 39 entity count is not a ceiling — it is a design. Each entity exists because the law requires that specific function to be legally separated from another. You cannot hold a CIC and a trading licence in the same entity. You cannot be the IP holder and the employer simultaneously. The 39 arose from necessity, not from counting. When the question "where do jobs live?" was asked, the answer was not "add a 40th." The answer was "which of the 39 was already built for this?" The answer was #22. A 40th entity would have required a reason for its legal existence that #22 already satisfies. Creating unnecessary entities is a signal of architectural weakness, not strength. Staying at 39 — by activating #22 — is a signal of architectural mastery.

The most common mistake in grant applications is trying to make a standard commercial entity sound like a social impact organisation. CICs don't have that problem. The CIC legally cannot operate without demonstrating community benefit. Every year, the CIC files a Community Interest Report — a public document proving social impact. By placing jobs in #22, that report now includes employment data, training completions through Overstand University, and the 40-meals conversion metric. Funders read that document and see exactly what they fund. The CIC doesn't just make the application stronger — it makes the application write itself. Every job placed, every Overstand University graduate deployed through the jobs system, every meal funded by material proceeds: all of it is CIC mandate evidence, grant eligibility evidence, and sovereign impact evidence simultaneously.

When investors see 39 entities and are told that each one exists for a specific legal reason, they respect the architecture. When they see 40 and are told the extra one is for jobs — something that could have lived inside the CIC — they question the judgment. Investors do not reward complexity. They reward intentional structure. Every entity in the 39 exists because it had to. Jobs didn't have to create a new one — it had a home. Using that home shows architectural discipline. "39 entities cover everything" is a cleaner, stronger, more credible statement than "39 entities plus a separate jobs company we created." The difference is not numerical. The difference is the story it tells about how you think.

The jobs system spanning four entities looks like distribution. It is actually precision. Each entity handles the layer it was built for. #22 holds the community mandate and the asset lock. #2 holds the financial rails and the Covenant compliance. #15 holds the training credentials and the grant eligibility. #18 holds the operational deployment. If all four functions lived in a single jobs entity (#40), that entity would need to be simultaneously a CIC (for community benefit), a finance company (for payroll), an education institution (for training), and an operations company (for placement). That is impossible under UK company law — and even where it isn't technically illegal, it would confuse regulators, funders, and auditors. The four-entity model is not a workaround. It is the correct architecture for a jobs system inside a sovereign infrastructure.

Activation is not registration — #22 already exists. Activation is designation and integration. Step 1: Board resolution formally designating the Job Zone as a programme of FullLoop Nourish CIC, recorded in the minutes. Step 2: Update the CIC Community Interest Report to include employment and training as a designated community benefit area. Step 3: Open the job board formally under the CIC — all job listings cite #22 as the employing and placing entity. Step 4: Establish the 4-entity coordination agreement (internal MOU between #22, #2, #15, #18) governing payment flows, training pipelines, and placement protocols. Step 5: First grant application citing the CIC's employment programme — DWP or Shared Prosperity Fund as the priority target. None of these steps require new entity registration. This is deployment, not formation. Deploy #22. Now.