Skip to main content
Boundary First Labs
GLOBAL OBJECT NAVIGATIONSearch the Lab
Quick navigation61 objects · 26 declared relationships · 25 pages
↑↓ MoveEnter OpenEsc Close

NOW / ROADMAP — OCTOBER 2026

What is Boundary First Labs doing now?

Turning a very large body of existing work into a smaller set of public, testable, useful things that can survive contact with people outside the Lab.

This is a public view of the Lab's current priorities, what they depend on, and what would count as meaningful progress. It is not a promise calendar or a copy of every internal task.

THREE TIME SCALESRecent changes. Current priorities. Long-term history.
RECENT CHANGESWhat materially changed?
See all changes
Institution
The Lab's internal priority shifted from adding components to closing complete loops.Open affected surface

CURRENT PRIORITIES

Six priorities, each with a clear definition of progress.

Priority means the Lab is spending current attention here. It does not mean every task in that area is happening at the same time.
ACTIVEPRIORITY 01

Keep the public institution current and useful

The core website reconciliation is complete. The current job is to keep the public site synchronized with real Lab state and use it as an active interface for readers, collaborators, clients, funders, and reviewers.

Inspect priority
ACTIVEPRIORITY 02

Get real-world evidence from customers, users, partners, reviewers, and funders

Move the Lab's current service, product, software, and research-funding opportunities into contact with people outside the Lab.

Inspect priority
ACTIVEPRIORITY 03

Make sure the Lab's records actually cover the work they claim to cover

The Lab now has a complete directory of its durable record systems. The next question is whether those records actually contain all the research programs, experiments, publications, products, and other durable objects they are supposed to contain.

Inspect priority
ACTIVEPRIORITY 04

Run tests that can prove the Lab's strongest ideas wrong

Compare Boundary Theory, Distinction Space, Information Mechanics, and related methods against established mathematics, physics, computer science, and the native methods of each field.

Inspect priority
ACTIVEPRIORITY 05

Turn mature research into specific papers people can review

Convert the strongest research into specific manuscripts with clear claims, sources, related work, evidence limits, and a visible path for correction.

Inspect priority
NEXTPRIORITY 06

Make more of the Lab operable by someone other than its founder

Turn recurring Lab procedures into durable records and tools so another person can understand and operate bounded parts of the institution without depending on founder memory.

Inspect priority

NOW → NEXT → LATER

The order matters more than an artificial deadline.

Later work becomes credible only after earlier work produces the evidence, capability, or infrastructure it depends on.
01
Current cycle

NOW

Keep the public institution current while pushing the strongest work into outside contact and hard tests.
  • Keep Now, What Changed, services, products, and research descriptions synchronized with the Lab's current state.
  • Move services, products, collaboration, and funding opportunities into real outside contact.
  • Execute at least one end-to-end research or institutional loop using the machinery that now exists.
  • Continue the record-completeness audit, including the rule that every durable experiment belongs to a durable research program.
  • Run hard native-domain research tests and move the strongest manuscripts toward external review.
02
After the current closures

NEXT

Turn outside contact and internal machinery into evidence another person can inspect and continue.
  • Record paid work, product use, funding decisions, collaboration, review, and failed-fit events as distinct kinds of outside evidence.
  • Keep only the research machinery that survives comparison with established field methods and adversarial testing.
  • Release a small first cohort of manuscripts with clear review status and correction paths.
  • Test the Lab's architecture and record-keeping tools against real institutional changes rather than only controlled examples.
  • Test non-founder use of selected tools, methods, or operating procedures.
03
After repeated evidence

LATER

Promote repeatable capability into durable programs.
  • Scale only funding lanes that have repeatable external evidence.
  • Move from one-off review and product tests to durable programs where demand or research value is demonstrated.
  • Train non-founder operators, reviewers, collaborators, and maintainers around bounded machinery.
  • Expand institutional partnerships and larger public-interest funding routes where the evidence warrants them.
  • Transfer mature products, methods, or infrastructure when another steward can operate them better.

WHAT WOULD COUNT AS PROGRESS?

The roadmap closes on evidence, not activity.

Activity is not the objective. Progress means something changed in the outside world: a clearer public institution, independent use, a paid engagement, a reviewed publication, stronger evidence, or a process another person can operate.

01Legible institution

A new reader can explain what the Lab is, distinguish research from products and services, inspect the evidence boundary, and find a relevant path without reading the entire corpus.

02External transaction or use

At least one BFL-native service, product, software, funding, or collaboration lane produces evidence that originated outside the Lab.

03Complete and connected records

Durable research programs, experiments, packets, and other audited records can be listed from their sources, connected correctly, and contain no known orphan records in the audited scope.

04A research test that could change the conclusion

A major claim or method survives—or is narrowed by—a defined mathematical, computational, experimental, or field-native comparison whose negative results are preserved.

05A publication with a clear record

A released paper or research object has clear claims, sources, status, related work, review state, correction path, and a stable public identity.

06Independent operation

At least one non-founder can inspect or operate a bounded method, tool, or institutional workflow from durable state without ordinary execution depending on founder memory.

WHAT CAN CHANGE THE ROADMAP?

The plan is allowed to learn.

A roadmap that cannot respond to evidence becomes theater. These are the rules that can legitimately change sequence, scope, or priority.
EVIDENCE CAN MOVE WORK

A negative result, failed pilot, external criticism, or stronger neighboring method can demote, redirect, or close a line of work.

FUNDING CHANGES SPEED, NOT TRUTH

Runway can increase conversion capacity and parallelism. It does not promote a research claim or waive evidence gates.

DEPENDENCIES COME BEFORE CALENDAR

Some work cannot responsibly start until a prerequisite artifact, reviewer, partner, technical capability, or governance boundary exists.

CAPACITY IS FINITE

The Lab will not pretend every interesting workstream is an active priority. Lower-priority programs remain visible without being represented as current commitments.

TRANSFER IS A SUCCESS CONDITION

A line of work may move to another institution, collaborator, maintainer, or product owner when that creates stronger long-term stewardship.

THE ROADMAP IS DATED

This is a public planning projection of the current Lab state. It should be updated when the active queue materially changes rather than treated as a permanent promise.

CURRENT PUBLIC QUESTION

Can the Lab become useful to people who did not build it?

The next phase is less about adding new areas than about proving which existing areas are genuinely useful. Funding increases capacity. Collaboration and customers introduce outside reality. Evidence decides what deserves to grow, change, or stop.