Engine

Nothing on these pages appears by decree. The enclave’s next state is proposed, weighed, and funded through the Evolution Loop (Enclave Doctrine §10; cadence in the SOP §13) — the engine that turns member work into roadmap.

The loop runs on structural developer-spaces: the Developer Spaces in the commons that the Tech Board has designated as structural. Designation is a resourcing act, not an editorial one — it marks a space’s projects as candidates for the roadmap and for funding, without touching the commons’ standing as an open sounding board. Each such space acts in two directions at once:

• Shape. It drafts the enclave’s next state — proposals, designs, roadmaps — on the member shelves of the Common Library. Mature drafts surface as projects before they become load-bearing.
• Assess. It evaluates the enclave as it now runs, through the standing visibility and guided tours of the audit.

A shaped project leaves the loop only through the Tech Board, which puts it on one of two tracks — or records why not:

• Funded → Contractor. Economic-Group-funded work, built under real identity in the Workplace.
• WiseNxt-available → Volunteer. Unfunded but approved work, surfaced through the Climb for work-discovery.

When funding is withheld, the reason is recorded. The Board sets funding and track — never identity, and never who governs: root, legal title, and the Charter stay where the Constitution puts them. The loop proposes; it does not ratify.