01
Inspect a System
Point us toward a public system that deserves inspection.
Nominate a civic, institutional, service, data, software, or infrastructure system that is consequential but difficult to understand, reconcile, contest, or repair.
OPEN LAB
Bring us a problem, a critique, or work that does not fit neatly anywhere else.
Open Lab is the public door into Boundary First Labs.
You can challenge our work, point us toward a consequential public system, propose a collaboration, or bring unusual technical or research work for review. You do not need to learn BFL terminology before writing.
FOUR WAYS INPoint us at a system.
Challenge our work.
Work with us.
Bring something unusual.
WAYS TO PARTICIPATE
Four simple starting points.
02
Critique Our Work
If we are wrong, show us where.
Report factual, mathematical, logical, implementation, accessibility, evidence, prior-art, overclaim, or stewardship defects in the Lab's work or behavior.
03
Work With Us
Start with one useful thing we can do together.
Explore a bounded relationship when another person or organization has expertise, infrastructure, lived knowledge, implementation capacity, data, distribution, capital, or stewardship the work genuinely requires.
04
Bring Us Your Work
You do not need to know what category it belongs in first.
Bring completed work, unusual experience, technical artifacts, evidence, stubborn systems failures, cross-disciplinary projects, or a question you cannot yet formulate cleanly.
OPEN PROBLEMS
Eight long-horizon research goals.
The Lab welcomes criticism, counterexamples, specialist knowledge, and collaboration around work that should improve under outside pressure.
MOONSHOTS08LONG-HORIZON OBJECTIVES
OBJECTIVE INDEXBig goals must break into smaller tests.
- 01Research OS
- 02Distributed Science
- 03Math Interoperability
- 04Executable Science
- 05Representation Mechanics
- 06Self-Improving Infrastructure
- 07Millennium Problems
- 08Fine-Structure Constant
WHAT HAPPENS AFTER FIRST CONTACT
Simple entry, clearer rules as the relationship deepens.
CHALLENGE AND RESPONSE
The Lab can be challenged without treating every submission as correct.
Criticism and local knowledge should be reviewable, while the Lab still distinguishes evidence, scope, and responsibility.
PRIVACY AND CONSENT
Collecting information creates obligations immediately.
Any structured intake should make privacy, consent, retention, security, moderation, and response expectations explicit.
KEEP THE REQUEST INTACT
One contact system should not erase what the person actually asked for.
Shared routing can support multiple kinds of participation while preserving whether the person brought a critique, system, collaboration idea, or other work.
PLAIN-LANGUAGE INTAKE
The Lab should do the categorizing, not the visitor.
People should be able to describe what happened, what they have, what keeps failing, or what they are trying to do in ordinary language.
LEAVE CAPABILITY BEHIND
Useful work should make the other side stronger.
The preferred outcome is durable knowledge, tools, documentation, or process rather than dependence on Boundary First Labs.
OPEN LAB PROMISE
Valuable criticism, knowledge, people, and work should be able to reach the Lab without being forced into the wrong category first.
First contact is intentionally simple: write the Lab, give enough context to understand what you are bringing, and keep sensitive or confidential material out of the first message. If the work needs a more structured review, consent, or data boundary, establish that before sending more.