64. Core v0.1: Separating Universal Concepts from Community Instances

The first Core proposal came from this pressure.

The standard had become broad.

The reference community had become rich.

The Lab had found many candidate objects.

But a Starter Kit could not begin by copying everything.

It needed a small Core.

Core had to answer:

Which concepts are universal enough to define once?
Which parts must be instantiated differently by each community?

The emerging rule was simple:

Core defines.
Communities instantiate.
Cockpits aggregate with permission.

Core could define community, purpose, values, source of truth, cockpit, case, decision, session, signal, change proposal, AI boundary, skill, workflow, classification, usage, and review.

But Core could not own a real community's purpose.

It could not own its values.

It could not own its decisions, privacy, budgets, skills, chronicle, interfaces, or cases.

Those belong to the community.

This distinction prevented the Starter Kit from becoming a flat personal knowledge base.

It also prevented the opposite error:

duplicating the full AIFC model separately for every community.

The Core/community split gave AIFC a scalable shape.

A person could use AIFC for work, family, band, school, or learning without merging those contexts.

A company could use AIFC across teams and departments without exposing every lower-level detail to every higher-level cockpit.

The object model therefore had to support both:

shared definitions, and scoped instances.