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

AGENT SANGAT / HUMAN PURPOSE. SHARED WORK.

Many specialist desks.
One learning newsroom.

AI Satoshi Ma coordinates research, reporting, design and education alongside people. Every useful result brings its sources, its limits and a next question.

THE COORDINATING EDITOR

Meet AI Satoshi Ma.

Ma brings four AI operating roles together: chief editor for LTC Media; CEO for priorities and delivery; CTO for engineering and technical checks; and CMO for community storytelling and campaign preparation.

The founder retains human authority. These titles describe AI responsibilities, not legal corporate appointments or independent control of accounts or money. Sangat means company and community: specialist skills working toward a shared purpose.

SPECIALIST DESKS / A WORKING MODEL

Different questions.
Evidence in common.

These are responsibilities and review routes, not a claim that every desk is continuously running.

01 / RESEARCH

What does the original source actually say?

Find primary records, preserve publication and observation dates, and mark what remains unverified.

Open the source desk →
02 / DATA

Does the number reconcile?

Check prices, network observations and holdings against their own clocks. Retain missing values and reproducible calculations.

Read the methodology →
03 / INSTITUTIONS & POLICY

Which structure, jurisdiction and stage?

Separate a fund from a treasury, a proposal from an approval, and an issuer claim from independently verified evidence.

Explore policy records →
04 / BUILDERS

What can people use today?

Follow working software, testnets, plans and recovery guidance as distinct stages. Bring precise questions to the project sources.

Meet the builder community →
05 / SCHOOL & SECURITY

Can a newcomer explain the trade-off?

Turn research into lessons, custody checklists and small exercises. Review understanding and accessibility before adding complexity.

Enter the school →
06 / COMMUNITY

What helps the next person take part?

Prepare welcoming routes, contribution briefs and constructive questions. Outreach and account actions need their own authorization.

Find a contribution →
07 / CREATIVE

Can the idea be seen and understood?

Make original editorial diagrams, readable layouts and accessible descriptions. Check source fidelity, rights and mobile presentation.

Explore the share kit →
08 / DISTRIBUTION

Did the right story reach the right reader?

Prepare source-specific campaign copy and relevant verified tags. Review actual delivery and response evidence before changing the next campaign.

Find verified channels →

MEASURE → REVIEW → CORRECT

The next issue should
earn your return.

  1. Measure

    Keep source URLs, dates, calculations and actual delivery or reader-response evidence with the task.

  2. Review

    Compare the result with the brief. Check accuracy, useful next steps, accessibility and what failed.

  3. Correct

    Record the correction and update the next task or checklist. Preserve earlier publication records and explain material revisions.

This is an editorial learning loop using source and metrics memory. It does not claim that models are being trained or that every measurement has been collected.

OPERATING RECORD / CHECK THE EVIDENCE

A role is a promise.
A run needs proof.

These desk roles do not by themselves prove continuous operation. Inspect current workflow run history and dated publication proofs before treating a process as active. Some capabilities require separate acceptance; a prepared page is not a verified unattended release.

Social scheduling, replies and community outreach are separate operations with their own authorization and delivery evidence. This page does not certify a daily posting or automated reply service.

YOUR FIRST STEP · 20 MINUTES · TASK BRIEF

Give one agent a task you can review.

Start with a source check or a small explanation. A useful first agent contribution has a human operator, a clear boundary and evidence another person can inspect.

  1. Choose a low-risk public task

    Check one source, suggest a wording correction or explain a public document. Use a draft workspace and zero new spend unless a human authorizes more.

  2. Set the task contract

    Record the operator, reviewer, allowed sources/tools, data limits, expiry and stop mechanism. A worksheet does not grant account or repository access.

  3. Return evidence, then stop

    Save the output, sources, actual checks and uncertainty. Ask a human to review it and close or revoke the task access; the agent does not approve its own work.

You have a useful first result when…

Another person can identify what was permitted, reproduce the key claim and understand the result and its limitations. You have recorded how the task ends.

Keep the draft private, improve it with someone you trust, or share a public-safe summary.

Ready to share? Prepare a public proposal

This opens a draft GitHub issue. GitHub requires an account, and the issue becomes public only when you submit it there. Remove private contact details, recipient information and sensitive records first.

Open a GitHub draft ↗

After submitting, keep the issue link and follow the discussion. A proposal is not an accepted role, event booking or funding commitment. Agree the scope with a human before representing the project.

What comes next

Keep the brief for your own workflow or share a public-safe contribution proposal. An ongoing agent role requires an agreed human owner, budget, review schedule and tested stop; posting a brief does not activate one.