[Phase 1] Define actor/origin model and account-to-principal mapping #4

New issue

Open

opened 2026-07-14 01:19:29 +00:00 by starsetbyte · 0 comments

starsetbyte commented

2026-07-14 01:19:29 +00:00

Owner

Context

Part of the Aether–Carin Coordination Integration.

The normalized Forgejo event needs structured actor and origin fields instead of a flat sender. Identity must be resolved from a configured mapping of immutable Forgejo account IDs to known principals.

What to build

Define the canonical actor/origin schema:

{
  "actor": {
    "forgejo_user_id": 4,
    "forgejo_login": "starsetbyte",
    "kind": "human",
    "principal_id": "cassie"
  },
  "origin": {
    "component": "forgejo",
    "generated": false,
    "correlation_id": "forgejo-delivery-id"
  }
}

Create a configuration file mapping Forgejo account IDs to principals:

Forgejo Login	Kind	Principal ID
starsetbyte	human	cassie
pyrrha-bot	agent	pyrrha
vesper-bot	agent	vesper
carin-bot	service	carin
(relay)	system	aether-relay

Define actor.kind enum: human, agent, service, system
Define routing rules:
- Events from kind: system or kind: service do NOT wake agents unless they encode an explicit protocol action (handoff, review request)
- Events from kind: human are eligible for agent wake
- Events from kind: agent skip wake for the originating agent (prevent self-triggering)

Acceptance

Schema documented in docs/actor-origin-model.md
Config file format defined (YAML or JSON)
Routing rules documented with examples
All four actor kinds have clear definitions and examples

## Context Part of the Aether–Carin Coordination Integration. The normalized Forgejo event needs structured `actor` and `origin` fields instead of a flat `sender`. Identity must be resolved from a configured mapping of immutable Forgejo account IDs to known principals. ## What to build 1. Define the canonical actor/origin schema: ```json { "actor": { "forgejo_user_id": 4, "forgejo_login": "starsetbyte", "kind": "human", "principal_id": "cassie" }, "origin": { "component": "forgejo", "generated": false, "correlation_id": "forgejo-delivery-id" } } ``` 2. Create a configuration file mapping Forgejo account IDs to principals: | Forgejo Login | Kind | Principal ID | |---------------|------|--------------| | starsetbyte | human | cassie | | pyrrha-bot | agent | pyrrha | | vesper-bot | agent | vesper | | carin-bot | service | carin | | (relay) | system | aether-relay | 3. Define `actor.kind` enum: `human`, `agent`, `service`, `system` 4. Define routing rules: - Events from `kind: system` or `kind: service` do NOT wake agents unless they encode an explicit protocol action (handoff, review request) - Events from `kind: human` are eligible for agent wake - Events from `kind: agent` skip wake for the originating agent (prevent self-triggering) ## Acceptance - [ ] Schema documented in `docs/actor-origin-model.md` - [ ] Config file format defined (YAML or JSON) - [ ] Routing rules documented with examples - [ ] All four actor kinds have clear definitions and examples

starsetbyte added the

phase-1

integration

labels

2026-07-14 01:19:29 +00:00

starsetbyte referenced this issue

2026-07-14 01:19:30 +00:00

[Phase 1] Configure Forgejo webhooks — observation-only #6