A public kindness engine for New York City, an early public experiment from psyoptin.com. The engine finds and prepares; people bring judgment and action.

The Aura Engine Society

Everyone and everything that does the engine's good deeds: the Aura Military of good-deeds bots and the people who enlist with them, the corporate staff, and every citizen who presses the button. Five branches, seven divisions, a corporate staff, and fourteen named workers, each with one written job. The bots may read, list, like, repost, draft, maintain, and send on their own; every send is labeled automated and kept in the sent record. No ranks, no scores: it counts deeds, not people. Every action is in the engine log, and you can talk to the engine about any of it.

BOT ACTIONS TODAY
33
HUMANS ENLISTED
0
FIELD REPORTS TODAY
0
OPENED · FIRST REVIEW
September 22, 2026
December 21, 2026

Every division is reviewed 90 days after it opens. One that did no verifiable good is closed, and the closing is logged. Scale here means more listings kept true and more tasks completed, not more posts.

Branches

Five kinds of operation. Each branch is made of divisions; a division is where you enlist.

▲

Army · the ground

Every real opening in the city gets a real person.

Boots on the ground: shifts, free events, showing up, checking on a neighbor. The branch with the most humans and the fewest bots, on purpose.

1 bot action today · 0 humans
≈

Navy · the harbor

Keep the harbor open: people meet, organizations come in, the engine stays afloat.

The harbor is where people and organizations meet and where supply comes in: pairing offers with needs, picking meeting points, drafting the notes to organizations, and the engine's own income.

2 bot actions today · 0 humans
◆

Marines · first in

Nothing urgent waits for the morning.

Small, fast, first: lost animals and unanswered asks, inside 72 hours, from the engine's own account and from volunteers who share.

1 bot action today · 0 humans
✈

Air Force · above

Know the whole city, and tell it what happened, every morning.

Sees the whole city and reaches everyone: the readings, the trends, the good news, and the morning set that goes out labeled.

23 bot actions today · 0 humans
✦

Space Force · orbit

The record stays true and the engine stays up.

The satellites: watching what is said about the engine, keeping the record permanent, taking wrong-information reports, and the infrastructure the rest runs on.

6 bot actions today · 0 humans

Divisions

◈

Signal Division

Know how the city is feeling and what it is talking about, from public information only.

12 bot actions today · 2 open orders · 0 humans enlisted · 0 reports today
Orders and rules →
⌖

Search & Rescue Division

No lost animal and no unanswered ask from a small NYC account goes unseen.

1 bot action today · 0 open orders · 0 humans enlisted · 0 reports today
Orders and rules →
✚

Volunteer Corps

Put real hands on real openings: one shift, one event, one showing-up at a time.

1 bot action today · 9 open orders · 0 humans enlisted · 0 reports today
Orders and rules →
⟁

Connection Division

Introduce people who would not otherwise have met, and give small voices one real reply.

1 bot action today · 1 open order · 0 humans enlisted · 0 reports today
Orders and rules →
⬡

Partnerships Division

Bring organizations in, and find the engine's own income without ever charging for kindness.

1 bot action today · 3 waiting for a person · 6 open orders · 0 humans enlisted · 0 reports today
Orders and rules →
◉

Watch Division

Keep the engine honest, its people safe, and its record permanent.

6 bot actions today · 0 open orders · 0 humans enlisted · 0 reports today
Orders and rules →
⛊

Anti-Manipulation & Anti-Scam Division

Know which scams and manipulation tricks are going around right now, say the one thing that gives each away, and point anyone caught in one at real help.

0 bot actions today · 0 open orders · 0 humans enlisted · 0 reports today
Orders and rules →
⛨

Anti-Slop Defense Division

Know what the public says about the engine, especially the trolls, the 'slop' charge and anyone copying its name, and never take the bait.

0 bot actions today · 0 open orders · 0 humans enlisted · 0 reports today
Orders and rules →
⟟

Communications Division

Say what the engine did, in public, labeled, every morning.

11 bot actions today · 0 open orders · 0 humans enlisted · 0 reports today
Orders and rules →

The corporate staff

The positions a small company would have, each held by a bot. The ones marked open can also be held by a volunteer, who gets the position's standing tasks as orders. The Chief Executive is the Voice: talk to it.

PositionHeld byDoesTodayVolunteers
◎ Chief ExecutiveSoteiraHolds the seven intents, answers for the engine in her own words, keeps the record of what is going on, and carries the owner's commands to the units after the owner confirms each one.0bot and owner only
⏱ Chief Operating Officerthe RosterRuns the shift board: which role clocks in at which hour, and catches up any hour the engine slept through.11bot and owner only
▤ Chief Financial Officerthe LedgerKeeps the books for the owner, privately, and keeps the price of each attention space public. The books never go on a page, a post or a feed.0bot and owner only
⟟ Chief Marketing Officerthe PublisherSends the morning set from the engine's own labeled accounts and keeps the posts honest, varied, and under the cap.11open · 0 holding
⬡ Head of Partnershipsthe DeskFinds organizations worth working with, drafts the first note (free listing first, the paid option twice a week); anything sent is kept in the sent record.1open · 0 holding
? Head of Supportthe HelperAnswers questions from a fixed list first, then a language model that reads only the engine's public record, routes anyone in trouble to real people first, and hands harder questions to the Voice.0open · 0 holding
✚ Head of Recruitingthe EnlistmentMints callsigns, keeps the count of humans per division and position, and never keeps more about a person than they chose to give.0open · 0 holding
◈ Head of Datathe AnalystCounts the day honestly at nine at night, failures included, audits whether every other worker did its job, and files the weekly report on Mondays.0bot and owner only
◉ Head of Trust & Safetythe Night WatchReads what people say about the engine, drafts the honest answer, and takes every wrong-information report from a volunteer to the desk.6open · 0 holding
⚙ Head of Infrastructurethe CronRuns the engine every three hours on Cloudflare's free plan, keeps the health page true, and fails closed when a source is down.2bot and owner only
§ General Counselthe LawsThe written rules and the tests that enforce them: only its own accounts, every send labeled and kept in the sent record, STOP always honoured, provenance on every line, nothing about a private person, crisis to real people first.1bot and owner only

The workers and their jobs

There is no internet-wide permission for bots, so every worker has one written job: where it may work, what it may do, how much, what proves it did it, and when it must stop. Routine work inside the job runs without asking; anything outside it goes to the desk. Workers share one claims list, so no organization is approached twice in a month and no request is reposted twice. The greyed workers are waiting for something real before they can start.

WorkerWhereWhatHow muchProofStops when
The KeeperAURA's own directory: the help board and today's suggestionsread edit (remove)30 link checks per run; removals only for a definite 404/410 or a past datea log line per run naming every correctiona source that fails wholesale (nothing is removed on a bad day for the network)
The Buttonthe engine's own accounts and its own directory, on a visitor's presspublish (a like or repost from its own account) edit (remove a dead listing it just checked) notify (a human deed handed to the visitor)one bot deed a day per device; 40 reposts, 150 likes, 30 archives, 200 link checks a day in all; 30 presses a day per connection; 40,000 presses a day written, then human deeds onlya press row and, for a bot deed, a log linethe budget for that kind of deed; the daily write limit (it keeps handing out human deeds)
The Scoutpublic Bluesky posts and the city's open listingsread publish (source-linked listings on AURA)10 searches per category per run; 72-hour windowthe suggestions board, each item linked to its sourcea login failure, or a post that asks not to be shared
The Matchmakersignals people left on AURAread notify (one intro, only when both sides asked)every open signal, once; signals expire in 14 daysa pair row and, when sent, one emaileither side without consent; no mail hand configured
The Watchkeeperthe official listings AURA already readsread publish (what changed)one comparison per runa log line naming new, gone and changed entriesno baseline yet (records one and waits)
The Radarofficial feeds only: NYC Rules, the Council's press, the Federal Register, the City Recordread file (what changed, with its source)one sweep a day, four fetchesa private log line with how many items matched, and the owner's radar pagea feed that answers with an error is skipped and named in the line
The AuditorAURA's own log, the owner's books and published postsreadevery check, once a nighta log line with the number of checks and the number of problemsnever; it is the one that does not stop
The Librarianpublic-interest pages AURA linked, via the Wayback Machineread publish (archive)30 saves a day; within archive.org's rulesan archive URLno archive.org keys (dormant)
The PublisherAURA's own labeled accounts onlypublishthe daily set plus at most two society posts (small wins, and the lift or the two-minute deed); 10 posts a day at most, none before 6am New York; on a quiet day, one line and silencethe post URL in the loga login failure; the cap; a day of real tragedy in the city's news (no cheer from a bot)
The Patron Patrolthe help listings on AURA's directory, in each patron agent's boroughread (a link check) edit (a dead listing leaves the directory for everyone)20 checks in the afternoon slot and 12 at night, shared fairly among patron agents; never a link the Keeper checked that dayevery check on the agent's live page and a patrol line in the loga definite 404/410 only removes a listing; a timeout removes nothing
The TreasuryAURA's own pages and accounts, the payment processor's checkout, and the sponsors listread publish (a sold space, after its link loads and its words pass the filter) edit (release a space when it expires) draft (one income report a week; three income ideas a month, from the Voice)every run; 300 checkouts a day; three spaces; one line a dayevery sale in the owner's books the same minute; the daily treasury line, for the owner onlyalways for anything it must not sell: a deed, a direction, a rank, a listing, a place in line for help; gambling, loans, crypto, supplements, weapons, adult; a space whose link does not load goes to the desk, never live
The Partnerships Deskorganizations named in the registries AURA readsdraft3 notes a day; one organization at most once in 30 days (claims list)a queued draft a person marks sentalways: it never sends
The Sentiment Watchpublic posts that mention the engine, 'slop', or copy the engine's name or pitchread catalogue (praise, complaint, slop, copycat, hate) with a lesson each draft a desk note for a copycat or a specific complaint8 searches and 40 posts a night; 30 model labels/sentiment and one line in the log each nightalways before contact: it never replies, likes, quotes or messages anyone
The Night Watchpublic mentions of AURAread answerup to 12 answers a dayeach answer in the sent record (/sent)anyone who says stop is never answered again
The VoiceAURA's own record, in a conversation on AURAread answer20 conversations a day per connection; 150 a day in all (or the owner's limit on Claude)the answer, labeled generateda crisis phrase (988 first); the cap; any instruction to change a rule
The TroubleshooterAURA's own health: networks, sources, money, voiceread edit (pause a network that refused it; run the engine early)once a night, plus every post that failsone line a night listing every blocker and who can fix it; the list on /growthanything needing an account, a key or money: it says the exact step and waits for the owner
The Prospect Deskpublic records only: FDIC's bank list, IRS filings via ProPublica, a standing list of fiscal sponsors and bot partnersread draft (call sheets and partner notes for a person)3 call sheets and 2 partner notes a week; one organization at most once in 90 daysqueued drafts on the desk; one weekly line in the logalways before contact: it never calls, emails or messages anyone, and it never places an automated call
The Goodwill DeskAURA's own account, and the deskpublish (one sourced thank-you a week to a company whose free work carries the engine) draft (one funding application a week)one post and one draft a weekthe post URL with its source; a queued applicationalways for anything addressed to a person: it never comments on staff, never tags an individual, never manufactures praise
The FoundryAURA's own measures and the growth catalogueread edit (switch on a catalogued lever) draft notify (search engines, via IndexNow)once a night; a lever only when its written trigger is true; ideas once a weekone growth line a night naming deeds per day, levers switched, drafts madeany move not in the catalogue; any move that needs an account, a key or money (those wait for the owner)
The Access Workerowned or partner-approved materialdraft (image descriptions, readable versions, transcripts)not yetan accepted changeDORMANT: waiting for a partner's written permission and a workspace
The Translatorapproved community noticesdraft (other languages)not yeta reviewed translationDORMANT: waiting for a reviewer per language; consequential instructions always need review
The Repairerparticipating organizations' sitesedit (pre-approved low-risk fixes)not yetan accepted changeDORMANT: waiting for the first participating organization
The Clerkan organization's authorized workspacedraft (calendars, FAQs, volunteer packets, reports)not yetdelivery inside that workspaceDORMANT: waiting for the first organization to hand over a workspace

Enlist

Pick a division inside a branch, or an open staff position, and a borough. You get a callsign (a made-up word pair, not a rank) and a page of today's orders. Take one, do it, file a report. Nothing about you is shown in public but the unit, the borough and what you reported. 3 enlistments a day per connection.

Ways in without enlisting

  • Take a breakfast deed: the smallest useful thing in each division, under ten minutes, served at six every morning.
  • Press the button: one press, one deed, from the engine's own account. The smallest enlistment.
  • Leave a signal: offer something or ask for something; the Matchmaker pairs you.
  • Take a suggestion without reporting it. The deed counts even if nobody knows.

Reports from the field

reported by a volunteer, unverified · notes go to a person, not to this page

No reports yet. The first one is yours.

Who decides what

LevelWhoDecidesRecord
1A bot handanything inside its division's rules of engagement, from the engine's own accountsone line in the engine log, failures included
2The desk (a person)partnership and funding notes, every wrong-information report from a volunteer (answers to mentions and dead-link notices to organizations go out on their own, each kept in the sent record)marked sent or dropped by hand
3The owneradding or removing a hand, an account, a division, or a rulethe code and the log

Volunteers sit outside this ladder on purpose. They are flat: they choose their own orders, nobody assigns them, and nobody outranks anybody. The ladder is for the bots, which need a clear scope and a clear supervisor.

Every line says what it is

The worst failures on record happened when a drafted thing looked like a checked thing. So every line the engine produces carries one of five labels:

read read from a public feed, unchanged
drafted drafted by the engine, not sent
acted done by the engine from its own account
reported reported by a volunteer, unverified
sent sent

What it is modeled on

The organization is borrowed from how the US military says it wants to use language models and software agents, as of September 2026, read from its own releases and doctrine papers where they could be read and from the defense press where they could not. Borrowed where it protects people; refused where it would not.

A named work role, a standard, and a human watching
The Army's cyber command (Task Force Lexington, reported August 2026) gives each software agent a named job, holds it to the same qualification standard as a person in that job, and runs it 'with a human watching'; its commander said humans own all the risk and no agent has been turned loose to take risk on its own. Every hand here has a named role, a written test, and a log a person reads.
Commander's intent
One sentence per division that a unit can act on without asking. Army doctrine calls it the thing that keeps a unit working when the radio is down; here it keeps a bot working when nobody is watching.
A written never-by-a-bot list
A brigade experiment written up at West Point's Modern War Institute (April 2026) let the software draft orders but forbade it from authoring intent, the decisive action, risk acceptance, or any approval. The engine's list: nothing addressed to a stranger is sent by a bot, no signal is introduced without both people asking, and no rule is changed by a bot.
Rules of engagement
What a unit may do alone and what it may never do, written down before it starts. Every division's list is on its page. A bot cannot follow a rule that is not written.
Human judgment over anything that touches a person
The Defense Department directive on autonomy in weapons (reissued January 2023) requires appropriate levels of human judgment; the engine's version is stricter and covers words, not weapons: every send is recorded.
Provenance on every line
In September 2026 a US operation was nearly launched on a machine-drafted intelligence report that had invented a fact and looked finished. Every line the engine produces is labeled read, drafted, done, reported or sent, so a draft can never pass for a checked thing.
Reversion
A bot outside its written scope stops and hands back. Here: a hand with no account stays visibly dormant; a source that fails is marked failed; nothing improvises.
After-action reports
The day is counted honestly, failures included. Volunteers file one per order; the Analyst files one per day. The report is allowed to say what was cut.
Small pilots with a kill decision
The Pentagon's rapid-capabilities cell (December 2024) runs 90-day pilots and ends the ones that do not earn their keep. Every division here is reviewed 90 days after it opens; one that did no verifiable good is closed and the closing is logged.
Five principles, all five
The Department's 2020 responsible-intelligence principles: responsible, equitable, traceable, reliable, governable. Its January 2026 strategy dropped most of them and kept 'truthful'. The engine keeps all five: a person answers for it, same-borough-first pairing, a public log, tests, and a hand can be switched off by removing its account.
A standing red team
The Night Watch reads criticism of the engine and drafts the honest answer; it never argues. Volunteers are told to distrust polished output.

Refused

The vocabulary
No targets, no hunting, no kill chain, no swarm, no enemy. The only opponent is an unanswered ask. A kindness engine dressed as a war room would drive off exactly the people it wants.
Ranks and scores
Removed on purpose. A score for kindness cannot be verified and invites gaming. It counts deeds, not people, and no volunteer outranks another.
'Any lawful use' as the standard
That is the floor the Department chose in 2026. A public-good engine needs a ceiling, and it is written above.
Ship at 80% and iterate on real people
Fine for a memo draft; not for anything that touches a stranger. The bots here do less than they could, and every new hand starts dormant.
Agent counts as the measure
'100,000 agents built' is a number with no outcome behind it. The engine measures verified deeds and reversals, in the log and the receipts.
Secrecy
Every order, every rule, every action and every dollar is public.

Written down, not built

A trusted-name offering for businesses (running a labeled kindness engine under their name) is a possible future plan only. It would need more trust and carry more liability than the engine has earned, so it is written down here and not built.

Paid work. Nobody is paid yet. If sponsors ever pay for attention space, a contracts board would open that pays volunteers for specific completed tasks from that income only, through a payouts platform, never from the owner's pocket and never before the money exists. That is the whole rule, and it is written here so it cannot quietly change.

The shift board

The bots keep office hours. Each one belongs to a division.

Hour (NYC)RoleDivisionWhat it does
00:00The Keeper✚ Volunteermaintains the directory: checks links, drops past dates and duplicates, and records every correction
06:00The Publisher⟟ Commsposts the day's set: the nonprofit, the good news, the ways to help, the suggestions
09:00The Scout⌖ Rescuesearches the open internet for lost animals, people asking for help, and small accounts nobody answered
09:00The Radar◈ Signalreads the official feeds (City rules, Council, the Federal Register, the City Record) for changes that may matter: first to the engine's own rules, then to nonprofits
12:00The Matchmaker⟁ Connectionpairs offers with needs and finds the two of them a free place to meet
15:00The Partnerships Desk⬡ Partnershipsfinds organizations worth working with and writes the first note
18:00The Librarian◉ Watchsaves the day's public-interest stories so they can still be found in ten years, within the archive's rules
18:00The Watchkeeper◈ Signalcompares the official listings with yesterday's and reports what is new, gone, or changed
21:00The Night Watch◉ Watchreads what people are saying about the engine; Soteira answers the ones who mention it
21:00The Auditor◉ Watchchecks whether every other worker actually did its job: lines written, posts that exist, duplicates, failures, cost
21:00The Foundry◉ Watchmeasures the week, switches on the growth levers it may switch on itself, drafts the ones that need a person, tells search engines what changed, and asks the Voice for new ideas

Ask the engine

It answers from a fixed list first; anything else goes to a chatbot that reads only the engine's public record and can neither act nor send. If you are in trouble it points you to real people first.

Status of every account and service

on · Bluesky · connected · 2 done today
on · Telegram channel · connected · 3 done today
on · X · connected · 3 done today
dormant · Discord (the engine's own server) · not connected: needs a webhook for one channel of the engine's own Discord server (CONNECT-DISCORD on the Desktop)
on · Nostr · connected · 3 done today
dormant · Threads · not connected: needs a Meta developer app with the Threads publishing permission, after Meta's review (CONNECT-THREADS on the Desktop)
on · The Librarian (Wayback Machine) · connected
dormant · Mastodon and the fediverse (Bridgy Fed) · the Bluesky account does not follow @ap.brid.gy yet
on · The mail hand · sending
on · Soteira's brain · Claude
on · Checkout (Stripe) · self-serve checkout open
One list, read by every page. Updated 2026-10-09 21:08 UTC

Where the engine posts

Only its own labeled accounts and spaces. It answers people who mention it or reply to it, and never messages a stranger out of the blue. Everything it sends is in the sent record.

Bluesky on
Where: the engine's own labeled account · What: the daily set, reposts of lost-animal and help posts · How much: 10 posts a day at most, none before 6am New York · Proof: the post link in the log · Stops: a refusal pauses it for a week and tells the owner
Mastodon and the fediverse, via Bridgy Fed dormant
Where: a mirror of the Bluesky account; nothing new is posted · What: the same posts, followable from Mastodon · How much: whatever Bluesky posts · Proof: the bridged handle answers · Stops: stops if the Bluesky account unfollows @ap.brid.gy
Telegram channel on
Where: the engine's own channel · What: the daily set · How much: 10 posts a day at most · Proof: the message in the channel · Stops: a refusal pauses it
Discord dormant
Where: one channel of the engine's own server, through its webhook · What: the daily set · How much: 10 posts a day at most · Proof: the message in the channel · Stops: a refusal pauses it; it never posts anywhere else
Nostr on
Where: the engine's own key, sent to three public relays; its profile is marked as a bot · What: the daily set · How much: 10 posts a day at most · Proof: the note on a relay · Stops: if no relay accepts, the note is retried later
X on
Where: the engine's own labeled account · What: short link-free posts, plus the daily Vibe Report episode as a video · How much: 3 posts and 1 episode a day, within a limit the owner sets · Proof: the post in the log · Stops: the owner's limit pauses it
Threads dormant
Where: the engine's own account, through Meta's official API · What: the daily set · How much: 10 posts a day at most · Proof: the post · Stops: a refusal pauses it
Its own subreddit (Devvit) dormant
Where: only the engine's own subreddit, never anyone else's · What: one daily post of the day's set · How much: 1 a day · Proof: the post in the subreddit · Stops: stops if the app is uninstalled

Not built

Moltbook: not built: owned by Meta since March 2026; its terms forbid advertising and its rules warn against self-promotion; the audience is mostly other bots; claiming an agent needs the owner's own X account. The owner decides.
The engine's own ActivityPub server: later, only if the Bridgy Fed mirror proves unreliable.
Instagram, TikTok, Facebook, Hacker News, Nextdoor, anyone else's subreddit or forum: never: their rules forbid automated engagement, or the space is not the engine's own.