66. Portability Became a Runtime Requirement

The Starter Kit raised a deeper requirement.

It was not enough to export a few files.

The whole directory had to carry meaning.

A person should be able to move it to another tool, use another AI model, and still understand:

• where the community is,
• what has been decided,
• what is active,
• what is sensitive,
• what AI may do,
• what must be reviewed,
• what should happen next.

This became the portability test:

Open the directory in a clean tool with a different AI model.
Tell the model: "Read aifc/README.md and continue this workspace according to AIFC."
The model can identify where we are, what rules apply, what is active, what is pending, what must not be touched, and what the next safe action is.

That test changed the filesystem design.

Hidden chat memory was not enough.

Proprietary agent memory was not enough.

Tool settings were not enough.

The directory itself had to contain or describe the runtime:

manifest, state, source map, handoff, functions, validation, AI providers, external systems, skills, workflows, templates, community instances, cases, decisions, sessions, and cockpits.

This was not only convenience.

It was an anti-lock-in rule.

AIFC had already said that AI-first must not become AI-dependent.

The Starter Kit made that visible in the filesystem.