Profiles, not press releases
Researchers are covered as working people with constraints, methods, tradeoffs, and unfinished claims.
Open Research Institute
Occasional web edition / Issue 000
Corrections invited
A newspaper for work that is still becoming legible
The Open
Research Register
An occasional publication from the Open Research Institute covering researchers, builders, methods, open questions, and the material conditions behind the work.
Project announcement
Not a hype sheet. A public record.
The Register profiles people doing research in the open: what they are building, what evidence exists, what remains uncertain, and what kind of help would actually matter.
What is the work? Plain-language mechanisms, artifacts, links, and context.
Why now? The moment, pressure, or bottleneck that makes the work urgent.
What is uncertain? Open questions, weak claims, and failure modes named directly.
What would help? Specific asks. Not the usual mist of "support research."
What this is
A newspaper-shaped archive.
Short enough to read. Structured enough to verify. Durable enough to matter later.
Mechanism before adjectives
If a claim cannot survive being explained plainly, it does not get promoted by typography.
Needs, not vibes
Each profile ends with specific asks: collaborators, reviewers, compute, funding runway, datasets, users, or documentation help.
Corrections are part of the artifact
The archive gets more valuable when misses are logged with the same dignity as hits. Terrible for ego. Useful for truth.
Coming soon / Profile 001
defenderofbasic
The first Register profile will cover defenderofbasic: the project, the mechanism, the visible evidence, the real bottleneck, and the open questions that still have teeth.
Editorial rules
How we avoid becoming a brochure.
Disclose the stake. If ORI, Leo, funding, collaboration, friendship, or token exposure shapes why a subject is covered, the piece says so plainly.
Name the unknowns. Unknown does not mean unimportant. It means the reader is allowed to see the edge of the map.
Show the artifact. Repositories, papers, posts, demos, diagrams, transcripts, screenshots, or public records beat adjectives every time.
Respect the subject. Pre-publication fact review is for factual correction and boundary checks, not for sanding every useful edge off the piece.
Publish the miss. Corrections remain attached to the artifact. Accuracy without a correction trail is just confidence with nicer shoes.
Next
The first issue is in reporting.
Expect a concise profile on defenderofbasic, followed by a reusable format for future ORI profiles. The paper will ask the same four questions every time: what is the work, why does it matter, what is uncertain, and what would help?