01
Public signal
One publication, multiple reading speeds.
News, Wire, briefings, market context, mining, macro, and policy give readers a fast scan or a deeper route through the same editorial world.
DesksWireBriefingsMarket context
Selected work
Flagship 02 / Active product build
Building a newsroom as a product.
Satoshi Gazette connects a public Bitcoin publication to the evidence, editorial state, retrieval, and distribution systems required to operate it with discipline.
satoshigazette.orgLive · Active build
ProductBitcoin-only newsroom
StatusLive · Active build
ScopeProduct · Editorial UX · Data · Operations
Evidence modelReviewed · Role-aware · Retrievable
The premise / Publication is the surface
Not a publication skin.
A newsroom operating system.
Editorial authority does not come from typography alone. The product has to preserve evidence, make state visible to operators, separate public reading from internal control, and keep human judgment in the consequential parts of the workflow.
System architecture / Three connected layers
The reader sees clarity.
The newsroom sees control.
Each layer has a different job. Together, they let the product move quickly without flattening editorial work into content automation.
02
Editorial spine
A newsroom needs state, not scattered documents.
Submissions, candidates, evidence review, editing, and publication move through an explicit lifecycle built for operator control.
IntakeCandidatesSource reviewPublish
03
Knowledge + distribution
Research should remain traceable after publishing.
Role-aware source links support citation-first retrieval, while distribution drafts and review queues extend the story without bypassing editorial judgment.
EvidenceAsk retrievalDraftsReview queue
Editorial lifecycle / Signal becomes record
Every handoff is a state change.
01Submission
Raw signal enters
02Candidate
Editorial value assessed
03Evidence
Sources reviewed and linked
04Publish
Story enters the newsroom
05Distribute
Platform drafts enter review
HUMAN REVIEW REMAINS IN THE LOOP
Live product / Current surfaces
A publication that behaves like one system.
These frames show the live product during its active newsroom build. They are working surfaces, not concept mockups.
01
Front page
One front page, multiple signal layers.
The masthead connects live market context, editorial desks, the Wire, briefings, and major stories without turning the product into a dashboard.
satoshigazette.orgFront page
02
The Wire
Fast reporting with structured source and time.
Wire entries are designed for high-signal updates: source identity and source time are part of the content model, not loose text added after publication.
satoshigazette.orgThe Wire
03
Macro desk
New desks inherit the same newsroom system.
The Macro desk demonstrates how the publication can expand its editorial coverage without creating a separate visual or operational product each time.
satoshigazette.orgMacro desk
Trust architecture / Product truths
Four decisions that keep the system honest.
Evidence has a role
Reviewed source documents can be connected as primary, supporting, background, or counterpoint evidence instead of becoming an undifferentiated link pile.
Publishing has a lifecycle
Submission, candidate, editorial review, publishing, and distribution are separate operating states with clear human decision points.
Retrieval has guardrails
Ask Satoshi is Bitcoin-only, citation-led, and designed to fall back when evidence is weak rather than improvise certainty.
Public and internal stay separate
The reading experience remains editorial while newsroom controls, source review, publishing, and distribution tooling stay behind the public surface.
MaydaLabs contribution
Brand, newsroom, and software shaped as one product.
The work connects editorial intent to the technical and operational systems that make it repeatable. AI accelerates research and production where useful; editorial responsibility stays human.
- Product
- Strategy, system architecture, release shaping
- Editorial UX
- Information hierarchy, desks, story and wire surfaces
- Engineering
- Application, data models, APIs, publishing workflows
- Knowledge
- Reviewed sources, citation roles, retrieval foundations
- Operations
- Intake, editorial control, publishing, distribution review
Open for new client work
Building an information-heavy product?