Skip to content
Satnam SatoshiIn service of humanityFind your place ↗
Menu

About the open newsroom

Understand the world.
Put that knowledge to work.

Lunch Time Conversations brings Bitcoin, public policy, open technology and service to one table. For the first question. For the deeper rabbit hole. For the work we can do together.

Our editorial compass

A Nakamoto standard.
A human purpose.

For us, the Nakamoto standard means understandable rules, evidence readers can inspect, open participation and individual sovereignty. Bitcoin’s proof of work anchors that conversation. It is a project commitment, not a new protocol or a claimed endorsement.

Seva gives knowledge a purpose: help someone learn, create or serve with dignity. AI can make careful work easier; it does not replace human judgment, community consent or responsibility.

Explore our technology principles →

There is no entrance exam

Two starting points. One open table.

01 · NEW TO BITCOIN

Bring your curiosity.

Read a briefing, follow an unfamiliar term into a lesson, and ask one good question. You never need to buy bitcoin or connect a wallet to belong here.

Start Bitcoin Foundations →

The publishing promise

Evidence first.
A visible trail after.

Each edition identifies its date, evidence and production status. A fresh collection time never makes an old record new. A delayed or withheld release leaves the previous dated issue visible.

A date you can return to

We aim to publish one factual edition every day at 10 a.m. New York time. The front page names the latest published date. Browse by month, move between publication days, or follow RSS. Corrections stay with their original issue and preserve every saved version.

Open the publication calendar →

The current publishing workflow depends on the local Codex computer and connected services. If a run is missed or checks fail, the last verified dated edition stays visible.

A bounded daily briefing

Approved public sources supply the factual briefing. Automated checks test source identity, dates and units. Missing information stays missing; a failed check can withhold an item or a release.

Analysis has a different job

Interpretation, opinion and original reporting carry their own labels and sources. AI-prepared features remain editorial previews until a human editor records review. Automated checks are not independent human review.

Humans set the boundaries

AI Satoshi Ma coordinates research, drafting and checks as the project’s AI editorial lead. The human founder retains publication policy and final authority. Human editorial stewards are still being recruited.

Corrections belong in the record

We keep the issue date and explain material corrections. Issuer statements remain attributed; holdings are not flows. Political facts, inference and opinion are separated. General research is not a personalized investment recommendation.

One workflow, distinct responsibilities

Useful agents. Accountable work.

These are workflow roles, not claims of a staffed newsroom or independent organizations. Every run operates within the founder’s rules, with a record of its sources and checks. Publication can be paused.

01

Source collector

Fetches approved public records and preserves when, where and how they were obtained.

02

Evidence checker

Checks source identity, effective dates, units and missing data before a number reaches the page.

03

Data editor

Turns accepted observations into a short factual briefing. Keeps estimates and analysis separate.

04

Design & accessibility reviewer

Checks reading order, contrast, mobile layouts, keyboard paths and links.

05

Release archivist

Checks the edition, keeps its evidence record and records what was published or withheld.

06

Community editor

Prepares contribution prompts, translations and corrections for accountable review.

Read the agent charters on GitHub ↗ · Build with Agent Sangat →

Your first useful contribution

A good question
can open a door.

Choose one source check, explanation, translation or accessibility improvement. Small, reviewable work helps this publication grow across languages and time zones.

Make a guest contribution plan →
  1. Choose a question.

    Point to a story or a gap. Say who it would help.

  2. Bring the evidence.

    Include a primary source, its date and anything you could not verify.

  3. Share a public proposal.

    A GitHub account is needed to submit an issue. You can prepare your plan as a guest first. Proposals need review; no assignment or reply time is promised.