← back to index

Contributor Pathway

The standing truth

Any human can become a contributor to EVE Glyph Design.

The combination required is already publicly available:

• A publicly accessible large language model. Free or paid tier. Any vendor. The reference model does not require a specific LLM and does not gatekeep on which one a contributor uses.
• Appropriate GitHub access. A GitHub account, which is free; read access to the public repositories, which is open; and contribution access through the standard pull-request and intake flow this organization operates.

That is the entire prerequisite stack. No certification. No tuition. No invitation. No platform commitment beyond the two free public substrates a contributor is already entitled to.

Why this is structural, not aspirational

This is not an aspirational statement about lowering barriers in the future. It is a description of the conditions that already hold today.

• The lattice methodology is committed in the open. A contributor reads it directly with the LLM of their choice.
• The education repository teaches the protocol, the game design, the observed operator patterns, and the roadmap in the open.
• The marketplace repository documents the free icon submission channel and the approval gate.
• The assessment service documents how an external architecture is routed for review.
• The reviewer mirror is one-way; the contribution path is the standard PR path, not a side channel.

A contributor using a publicly accessible LLM to read these surfaces, form a contribution, and submit it through the standard pathway is doing exactly what the reference model expects.

What "appropriate GitHub access" means

Appropriate is a deliberate word. It points at what the standard GitHub flow already provides:

• Read access to public repositories — already granted to anyone with a GitHub account.
• Fork rights on public repositories — already granted; this is the foundation of the "sell a fork" exit vector under Pattern 6.
• Pull-request submission — the standard contribution surface.
• Issue submission — the standard intake for questions, observations, and proposed changes.

A contributor does not need write access to the organization's repositories to contribute. Write access is reserved for the lead operator and named authors, consistent with the human-in-the-loop posture. A contributor without write access is not blocked from contributing; they are protected by the same gate that protects the reference model.

How LLM-assisted contribution fits the methodology

A contributor using a publicly accessible LLM to read, interpret, and draft against the methodology is exercising the integration the methodology is designed for. The methodology is explicit that the AI substrate is the substrate humans are integrating with. A contributor who uses an LLM to engage with the reference model is demonstrating the integration, not bypassing it.

What the methodology asks of LLM-assisted contributors is what it asks of any contributor:

• A clear footprint trace on the contribution (what was authored, what was assisted, against which methodology dimensions).
• Cognitive-fitness posture on the contributor's side (the operator is awake, not driven by the model).
• No lock-in — the contribution is portable across LLMs and across forks.
• Reference-model conformance at approval time, which is the same gate that applies to icon submissions and architecture assessments.

The LLM is a tool the contributor brings. The reference model is the standard the contribution is held against. The two are compatible by design.

What this enables

Three things follow directly from the standing truth:

1. The contributor pool is the entire population of humans with internet access. The reference model is not bounded by employer, institution, geography, or credential.
2. The protocol's diffusion is bottom-up by default. Operators read, draft with public LLMs, submit, and either merge or fork. Paid platform integrations (roadmap Phase 6) are diffusion accelerators, not access gates.
3. The exit vectors are real. A contributor who disagrees with the lead operator's direction can fork. The fork is a first-class outcome of the pathway, not a failure of it. Pattern 6 Vector 3 already names "sell a fork" as a legitimate exit.

What this does not enable

The pathway does not grant:

• Write access to the organization's repositories.
• Authority over the reference model's standards.
• Bypass of the WhatsApp routing layer for architecture submissions.
• Bypass of the approval gate for icon submissions.
• Authority over patent governance, which sits with the patent holder.

A contributor is welcome. A contributor is not the lead operator. Both statements are true at the same time, and the pathway is designed to hold them together without collapse.

Structural consequence: hyperscaler commoditization

Because the pathway requires only a publicly accessible LLM and appropriate GitHub access, the choice of LLM vendor — and the hyperscaler hosting it — is substitutable substrate, not a gatekeeper of contribution. This is the structural condition Methodology 17 names: early-iteration hyperscaler commoditization. It is the protocol's standing refusal of the institutional-runaway sequence (useful start → asymmetric authority accrual → only-path consolidation → resistance to exit) the operator has observed in SAP and named as "the Fauci sequence."

The pathway being open is not only a welfare statement. It is the operational mechanism by which the protocol prevents itself, and the substrate around it, from becoming the next runaway institution. See eve-glyph-lattice/methodology/17-early-iteration-hyperscaler-commoditization.md.

Pour le bien-être du peuple

Individual IP ownership inside the collective welfare invariant requires a pathway that any individual can actually walk. A pathway that requires private LLM contracts, paid education, or institutional sponsorship would convert the welfare invariant into a credentialing scheme. The reference model refuses that conversion.

The combination of publicly accessible LLMs and standard GitHub access is the pathway. It is sufficient. It is open. It holds today.

© 2026 Dany Theriault. EVE “digital stem cell” glyph and glyph-based design principles — all rights reserved. Stewardship of rights of use and assignment for large public and institutional usage rests with the Pacific Utilities Design Council. Published as a time-stamped record of authorship and intent.
pour le bien-être du peuple