The Blueprint Lab
CONTRIBUTE

Contribute

The Blueprint Lab is an open design environment for structural reform. The work here is drafting and refining — not signing, not endorsing, not voting. If you have expertise to bring to a specific reform pathway, this is where you bring it.

How to contribute

Read and critique

File an issue on any reform card or artifact. Spot a flaw, a missing pathway, a stale citation, a doctrinal misread. The Lab's repository issue queue is open. Lowest barrier, highest-volume contribution path.

Anyone who can read closely and document a problem with citation.

Draft and propose

Fork the repository. Propose alternative language — for an amendment in the Forge, a statute the Engine analyzes, an executive order, an interstate compact. Submit your version as a pull request. Editorial review responds with reasoning.

Anyone with drafting expertise — constitutional, statutory, regulatory.

Verify and source

Cite-check existing claims. Find primary sources for items flagged as verification-pending. The Tier 1 scoreboard data, the bill records, manuscript-aligned citations — all welcome verification work. Verification commits are credited and merged on the fast track.

Researchers, librarians, legal-research veterans, journalists.

Bring domain expertise

The Lab is built for the contribution we cannot get without you: civil-rights litigation veterans, Hill staffers and legislative counsel, federal workers in regulatory practice, civic technologists who have watched this kind of project fail before, constitutional scholars, state-level reform organizers. Each domain has work the Lab cannot do without it.

Domain professionals.

How contributions are reviewed

All contributions enter a public pull-request queue visible to any reader. The editorial review process is tiered by the kind of change proposed.

  1. Fast track

    Examples
    Typo fixes. Citation corrections. Doctrinal updates with primary-source backing (e.g., adding a recently decided case to a doctrinal note). Stale-link repairs.
    Reviewer
    Editor.
    Timeline
    Days. Most fast-track items merge within one week.
  2. Standard review

    Examples
    Structural changes to amendment language. New bill analysis. Reform card content changes. Methodology updates. Forge artifact revisions.
    Reviewer
    Editor with domain consultation as needed.
    Timeline
    Weeks. Substantive changes may go through a public comment period before merge. Each merge ships with editorial reasoning attached to the commit.
  3. Panel review

    Examples
    Tier reclassifications. Addition of new reform cards (a new domain-level reform). Editorial-policy changes. Code of conduct amendments.
    Reviewer
    Editor plus two invited domain experts (rotated by reform domain — constitutional, legislative, judicial, executive, technology policy, technology practice).
    Timeline
    Up to thirty days. Decision is published with reasoning and panel composition. The audit trail becomes part of the Lab's tier-classifications and editorial record.

The full review queue is public. Anyone considering contribution can see what is currently in review, what was recently merged, and on what reasoning.

Tier-classification disputes

The Lab classifies every reform, bill, and Forge artifact under one of three tiers — Tier 1 (begin tomorrow), Tier 2 (federal statute, testable now), Tier 3 (requires Article V). The classification is consequential: it shapes how readers understand whether reform is reachable in the current cycle or requires constitutional repair.

Tier classifications are published with reasoning and citation, and they are open to dispute.

Filing a dispute

Anyone can file a tier-classification dispute on any reform, bill, or Forge artifact. A valid filing includes:

  1. The artifact in dispute (slug or URL).
  2. The currently published tier and the proposed alternative tier.
  3. Reasoning grounded in manuscript citation and current doctrine.
  4. Primary sources supporting the proposed reclassification.

Filings are submitted as issues on the Lab's repository under the tier-dispute label.

Review

Disputes are reviewed by a panel composed of the editor plus two invited domain experts, rotated by the reform's domain — constitutional, legislative, judicial, executive, technology policy, technology practice. The panel rules within thirty days of filing.

Decision

The decision is published with the panel's reasoning and a citation map. If the dispute succeeds, the artifact's tier classification updates and the change is recorded in the Lab's tier-classifications audit trail with the dispute reference. If the dispute is denied, the reasoning is published alongside the existing classification so future readers see both the original argument and the dispute that was considered.

Appeal

A single appeal is permitted, requiring substantively new reasoning or new primary sources not available at the time of the original dispute. The same panel reviews appeals. After one appeal, the classification is final until and unless the underlying doctrine changes.

Resolved disputes

As disputes accumulate, a small set of resolved disputes will be surfaced as exemplars on the methodology page — to show that the process is real and to teach by example what arguments succeed and what arguments do not.

Contributor protections

The Lab depends on contributors whose contribution carries professional cost. A federal worker who critiques regulatory architecture, a Hill staffer who proposes a redrafted statute, an agency veteran who flags an enforcement gap — these are the contributions the Lab cannot do without, and they are also the contributions that put their authors at professional risk.

The Lab's contributor protections are explicit.

Pseudonymity

The Lab does not require legal name for contribution. Contributors may use a chosen handle. The handle is what appears on commits, in editorial responses, and in any public attribution.

No identity disclosure

The Lab does not voluntarily link a pseudonymous contributor to a legal identity under any circumstance. We do not maintain a separate registry tying handles to identities. In the unlikely event of valid legal compulsion to disclose, the Lab will, where permitted by law, notify the affected contributor before any disclosure to allow their counsel to respond.

Attribution at the contributor's discretion

A contributor can choose to be credited by handle, partially credited (for example, role only — "federal employee"), or not credited at all per contribution. The default for pseudonymous contributors is handle attribution; the contributor can override per-commit.

Mutual standard

These protections come with a corresponding obligation. Pseudonymous contribution is for protection of professional position, not for unaccountable bad-faith conduct. Pseudonymous contributors are held to the same code of conduct as named contributors, and pseudonymous bad-faith actors are blocked under the same standard. The pseudonymity is to enable the contribution, not to insulate the contributor from the editorial standard.

What the Lab is not

The Lab is built around a specific purpose. The clarity of that purpose depends on being explicit about what the Lab is not.

Not a petition tool. The Lab does not aggregate support for any reform. There is no "sign here" affordance. Read the case, bring work, not endorsement.

Not a political campaign vehicle. No fundraising. No candidate endorsement. No electoral organizing through the Lab.

Not legal advice. The Lab is a design environment, not a counsel-client surface. Drafts, arguments, and analyses published here are not legal advice and cannot substitute for professional legal counsel.

Not a consensus engine. The Lab does not aggregate or average opinions. The Lab publishes what its editorial process accepts, with reasoning. Readers can see the editorial process and contest it; readers cannot vote it.

Not a substitute for political organizing. Every reform pathway the Lab models — Tier 1 ballot initiatives, Tier 2 federal legislation, Tier 3 constitutional amendments — requires organizing the Lab cannot do. Technology is the amplifier, not the movement.

Not the deciding authority on what is constitutional. The Lab models, drafts, and stress-tests proposals. The Constitution is interpreted by the courts; reforms become law through Article I or Article V; the Lab is the design surface, not the decider.

Code of conduct

Argue from primary sources. Disagreements are welcome — they are the work. Disagreements without citation are not.

Doctrine, not partisan labels. Critique a bill, a doctrine, a draft amendment. Do not critique by partisan affiliation. The Lab is structurally non-partisan and editorially holds that line.

Bad faith is blocked. Spam, harassment, vexatious filing, attempts to weaponize the dispute process, and conduct designed to waste editorial resources are grounds for permanent block. Blocks are issued with public reason. The contributor protections do not extend to bad-faith conduct.

The Blueprint Lab is in MVP preview. Not all modules are live. See /modules for status.