50. The Cockpit Became the First Human View

As the reference community grew, another problem appeared.

The folder structure was still useful.

Decisions had records.

Assets had records.

Prompts had records.

Skills had source files.

Workflows had Markdown.

But the human needed a quick answer:

Where are we now?

The source of truth was becoming richer.

That also meant it was becoming harder to scan.

This was the same problem that created the Human Cockpit Layer earlier in the journey, now appearing inside the reference community itself.

The first version did not need to be an application.

It could be a single Markdown file.

The first cockpit needed to show:

• how mature the project felt,
• what existed,
• what was in progress,
• what risks or gaps were visible,
• what backlog areas were emerging,
• and what the next smallest useful step should be.

So the first cockpit was created as:

reference-community/cockpit.md

It was intentionally primitive.

That was part of the design.

The cockpit should not become another long document.

It should remain a compact human view over the deeper source of truth.

This produced another practical rule:

The source of truth stores detail. The cockpit protects attention.

The cockpit is not the authority.

It is the view.

If it grows too long, detail should move back into source files, decisions, session logs, workflows or records.

The cockpit should preserve orientation.

---