Contributing to the Architecture

The L/0 architecture is community-built. Here's how you can propose changes, provide feedback, and help shape the frameworks that will define our post-labor future.

Ways to Contribute

Whether you have a major framework proposal or just want to fix a typo, there's a place for your contribution.

Join Discussion

Participate in community discussions about proposed changes, share your perspective, and help refine ideas.

Skool Community

Propose Changes

Have an idea for improving a framework, adding a concept, or changing a principle? Submit a proposal.

See Process

Improve Documentation

Help make our frameworks clearer, fix errors, add examples, or translate content for global audiences.

GitHub

Research & Evidence

Share research, data, or real-world examples that support or challenge our frameworks.

Research Hub

The ADR Process

Significant architectural changes follow our Architecture Decision Record (ADR) process to ensure transparency and community input.

1

Propose

Start a discussion in Skool or open a GitHub issue describing your idea.

  • Describe the problem or opportunity
  • Explain your proposed solution
  • Note any alternatives you considered
  • Tag relevant community members for feedback
2

Discuss

Community members provide feedback, ask questions, and suggest refinements (2 weeks minimum).

  • Respond to questions and concerns
  • Incorporate feedback into your proposal
  • Build consensus where possible
  • Document dissenting views
3

Draft ADR

If there's sufficient support, create a formal Architecture Decision Record.

  • Use the ADR template (see below)
  • Include context, decision, and consequences
  • Reference the discussion thread
  • Status: "Proposed"
4

Review

Architecture stewards review the ADR for alignment with principles and overall coherence.

  • Check alignment with mission and principles
  • Ensure no conflicts with existing decisions
  • Verify community consensus
  • May request revisions
5

Adopt

If approved, the ADR is merged and the change is implemented.

  • Status changes to "Adopted"
  • Published on the governance site
  • Relevant documentation updated
  • Announced to community

ADR Template

Use this template when creating a formal Architecture Decision Record.

ADR-XXX: [Title]

# ADR-XXX: [Decision Title] ## Status Proposed | Adopted | Deprecated | Superseded by ADR-YYY ## Date YYYY-MM-DD ## Context What is the issue we're addressing? What forces are at play? ## Decision What is the change we're proposing or have decided? ## Alternatives Considered What other options were evaluated? Why were they rejected? ## Consequences What are the results of this decision? Both positive and negative. ## References Links to discussion threads, related ADRs, external resources.

Contribution Guidelines

Please keep these principles in mind when contributing.

Be Respectful

Engage constructively, assume good faith, and respect diverse perspectives. We're building something that affects everyone.

Ground in Evidence

Support proposals with research, data, or real-world examples where possible. Link to sources.

Align with Principles

Proposals should align with our established architecture principles. If you disagree with a principle, propose changing it first.

Think Globally

Consider how proposals apply across different cultures, economies, and political systems. Avoid assumptions based on one country.

Build on What Exists

Check existing ADRs and discussions before proposing. Your idea might already be in progress or previously considered.

Ready to Contribute?

The architecture of our post-labor future is being written now. Your voice matters.

Join the Community View Active Proposals