Axismundi Activities

Axismundi Activities is the ledger: an append-only, URI-keyed record of things that happened -- somebody followed somebody, liked something, announced something, replied, withdrew one of those -- and the relationship state derived from reading it back. It is deliberately not the thing that talks to other servers. There is no HTTP inbox here, no outbox transport, no signatures, and no delivery queue. Those are somebody else's job, which is what lets this one be a plain, auditable record: an Activity is written once and never edited, and undoing something is a new Activity rather than a deletion. What it needs

• Axismundi Actors is required. Every Activity names an actor by URI, and that registry is the authority for those URIs.
• Axismundi Object Projections is required for the shared ActivityStreams vocabulary. Ledger admission reads registered Activity ancestry and property exclusions instead of maintaining a second type list. It also supplies Object representation and local post integration; Activities retains ownership of ledger storage and action effects.
• Axismundi Emoji and Axismundi Dialogs are optional. Emoji reactions and the anonymous remote-follow dialog use them where they are present.

What this version does

• A limited ActivityPub C2S outbox POST for Like and Undo(Like), authenticated using WordPress REST cookies with a nonce or Application Passwords. Other C2S verbs and bare Object creation are not implemented by this slice.
• An Actor liked collection, private by default. Account operators can publish its URI membership in Actor Profile settings. Publishing includes private-addressed Likes; it does not disclose member bodies or grant permission to fetch them.
• An immutable, URI-keyed Activity ledger with a read-only administrator log.
• Follow and Block relation state, for local actors and for cached remote ones, with the accepted inverse edge tracked separately from the outgoing one.
• Like, Dislike, emoji reactions, Announce, Reply and votes, each with its Undo, and each keyed by the URI of the thing it is about rather than by a local row id.
• FEP-044f QuoteRequest decisions, so a quote of somebody's post is something they agreed to rather than something that happened to them.
• Object lifecycle recording: one Create when a projectable post is first published, and a Delete from its stable identity when it goes.
• Feed blocks -- feed, loop, item template, tabs, filters, pagination, a density switch -- plus follow, interaction and reaction-bar blocks.
• A public-safe outbox query for representation plugins: the stored payload stays lossless while blind recipients and non-public Activities are kept out of anything public.

What this version does not do No HTTP inbox, no S2S delivery transport, no HTTP signatures, no delivery queue, and no scheduled tasks of any kind. It also does not own notifications or read state -- who gets told about an Activity, and whether they have seen it, belongs elsewhere. Uploading media stays deliberately silent: putting a file in the library is not an announcement. What is kept, and for how long The ledger is append-only. An Undo is recorded as its own Activity pointing at the one it withdraws; nothing is rewritten, because a record that can be edited afterwards is not evidence of anything. State like "does A follow B" is read back from that history rather than stored as a fact that could drift from it. An Activity therefore outlives the actor it names. When an Actor is tombstoned, it stops being something anybody can follow or react to, and the record that somebody once did stays where it is -- deleting an identity does not un-happen what it did.

1. Install and activate Axismundi Actors and Axismundi Object Projections.
2. Upload this plugin folder to /wp-content/plugins/, or install it through Plugins > Add New, then activate it.
3. Place the follow, interaction, reaction or feed blocks where you want them. There is nothing to configure first.
4. The ledger is readable, read-only, from the administrator log.

Activation creates this plugin's own database tables. Nothing is contacted on the internet during installation, and no scheduled task is added.

0.1.6

• Add object-based Sent membership and audience and reply filters independently of Outbox Activity history.
• Record Inbox receipt provenance for new deliveries without classifying historical receipts.
• Accept C2S submissions at protocol-named Outbox routes while keeping previous POST routes available.
• Sanitize named submitted fields and escape helper markup at output with local HTML allowlists.
• Preserve Interactivity context through block wrapper attributes instead of unescaped attribute output.

0.1.5

• Serve and observe a Person's featured collection, holding an unresolved member's position instead of publishing a partial replacement.
• Give a Community its moderators as an observed collection, without turning moderation into a grant over the Group's own account.
• Let a Community review what a remote Person submits to it, recording the decision as a further Activity rather than as an edit.
• Record a reply addressed to a Group here rather than in a product plugin, and give a Community's moderators one screen to work from.
• Carry an existing group across to the Community contract only when an administrator asks for it, never on activation.
• End a Follow by Block without letting the accepted inverse edge return.
• Sanitize the publication-selection nonce before verification, and name the escaping authority at every output boundary that defers to core. Earlier releases are recorded in changelog.txt.