Circuit-Forge/circuitforge-core
3
0
Fork 0
Code Issues 6 Pull requests Projects Releases 5 Packages Wiki Activity Actions 4

feat: add circuitforge_core.activitypub module (MIT) — ActivityPub actor management and Lemmy/PieFed integration #51

New issue
Open
opened 2026-04-20 08:18:08 -07:00 by pyr0ball · 0 comments
pyr0ball commented 2026-04-20 08:18:08 -07:00
Owner
Copy link

Building Rook (mutual aid exchange tool) requires publishing offers/requests to Lemmy communities via ActivityPub. Kiwi and Snipe have parallel needs (community feed posts, trust score broadcasts). Extract to cf-core so all three products consume the same plumbing.

Scope

  • Actor identity management per CF instance
  • ActivityPub object construction (Create, Note, custom Offer/Request types)
  • Lemmy API post creation + signed HTTP delivery
  • Inbox handling stub (for federation responses)

License

MIT — discovery/federation layer, not an AI feature.

Consumers

  • Rook: publish exchange offers/requests
  • Kiwi: publish community feed posts to Fediverse food communities
  • Snipe: broadcast trust verdicts to relevant Fediverse communities

This module is the prerequisite for all three downstream tickets.

Building Rook (mutual aid exchange tool) requires publishing offers/requests to Lemmy communities via ActivityPub. Kiwi and Snipe have parallel needs (community feed posts, trust score broadcasts). Extract to cf-core so all three products consume the same plumbing. ## Scope - Actor identity management per CF instance - ActivityPub object construction (Create, Note, custom Offer/Request types) - Lemmy API post creation + signed HTTP delivery - Inbox handling stub (for federation responses) ## License MIT — discovery/federation layer, not an AI feature. ## Consumers - Rook: publish exchange offers/requests - Kiwi: publish community feed posts to Fediverse food communities - Snipe: broadcast trust verdicts to relevant Fediverse communities This module is the prerequisite for all three downstream tickets.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
feature/api-exports
feature/license-validation
feature/affiliates-module
feature/docker-ci
feature/manage-py
feature/agent-watchdog
feature/hardware-docuvision
feature/orch-llm-server
feature/orch-auto-lifecycle
feature/orch-dashboard
feature/shared-task-scheduler
feature/cforch-core-orchestration
v0.11.0
v0.10.0
v0.9.0
v0.5.0
v0.4.0
v0.3.0
v0.2.0
Labels
Clear labels   
architecture

   
backlog

   
enhancement

   
module:documents

   
module:hardware

   
module:manage

   
module:pipeline

   
module:voice

cf_voice module

  
priority:backlog

   
priority:high

   
priority:medium
No labels
architecture
backlog
enhancement
module:documents
module:hardware
module:manage
module:pipeline
module:voice
priority:backlog
priority:high
priority:medium
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Circuit-Forge/circuitforge-core#51
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?