AURA ENGINEA public kindness engine for New York City. An early public experiment from psyoptin.com. The engine finds and prepares; people bring judgment and action. Activity records public; private requests protected.

The Aura Army

An army of good-deeds bots, and the people who join them. Five branches, seven divisions, a corporate staff, and fourteen named workers, each with one written job. The bots may read, list, like, repost, draft and maintain; only a person sends. No ranks, no scores: the army counts deeds, not people. Every action is in the engine log, every dollar on the ledger, and you can talk to the engine about any of it.

BOT ACTIONS TODAY
28
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.

4 bot actions 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.

15 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.

9 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 · 9 failed · 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.

4 bot actions today · 8 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 · 9 failed · 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 · 2 failed · 1 waiting for a person · 0 open orders · 0 humans enlisted · 0 reports today
Orders and rules →

Communications Division

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

6 bot actions today · 49 failed · 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.11 (2 failed)bot and owner only
▤ Chief Financial Officerthe LedgerKeeps the books in public: cost per day, income to date, runway, and the price of each attention space.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.6 (49 failed)open · 0 holding
⬡ Head of Partnershipsthe DeskFinds organizations worth working with, drafts the first note (free listing first, the paid option twice a week), and waits for a person to send it.1open · 0 holding
? Head of Supportthe HelperAnswers questions from a fixed list that cannot hallucinate, 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.2bot 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.2open · 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.3 (9 failed)bot and owner only
§ General Counselthe LawsThe written rules and the tests that enforce them: only its own accounts, only a person sends, provenance on every line, nothing about a private person, crisis to real people first.1 (9 failed)bot 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 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 AuditorAURA's own log, ledger 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 onlypublish7 posts a day, none before 6am New Yorkthe post URL in the loga login failure; the cap
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 Night Watchpublic mentions of AURAread draft5 drafts a nighta queued answer a person sendsalways: it never replies itself
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 dollar cap on Claude)the answer, labeled generateda crisis phrase (988 first); the cap; any instruction to change a rule
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

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)every note to a stranger, every answer to a mention, every wrong-information report from a volunteermarked sent or dropped by hand
3The owneradding or removing a hand, an account, a division, or a rulethe code and the ledger, both public

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 by a person

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: only a person sends.
Provenance on every line
In September 2026 a US operation was nearly launched on an AI-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 AI 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-AI 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. The army 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, on the ledger and in the log.
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, because the ledger shows no income. 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 ledger, 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
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, for a person to send
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 and drafts honest answers for a person to send
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, so it cannot make anything up. If you are in trouble it points you to real people first.