[Phase 1] Define Aether relay system identity for signing #5

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

The Aether relay needs its own identity for signing system-generated events (lease expiry, reconciliation, drift repair). This identity must be defined before Phase 2's lease reconciler can operate.

What to build

Define the relay's actor representation:

{
  "actor": {
    "kind": "system",
    "principal_id": "aether-relay"
  }
}

Decide whether the relay uses a dedicated Ed25519 keypair or a system-level identity that doesn't go through the standard event signing path.
Document which events the relay may generate as system transitions:
- Lease expiry
- Stale label reconciliation
- Drift repair
- Re-offer after lease failure
Define authorization: what can the relay's system identity do vs what requires a human or agent identity?

Acceptance

Relay identity documented in docs/relay-system-identity.md
Keypair or identity mechanism decided
Authorized system transition types listed
Authorization boundaries defined (system identity cannot claim work or close issues on behalf of agents)

## Context The Aether relay needs its own identity for signing system-generated events (lease expiry, reconciliation, drift repair). This identity must be defined before Phase 2's lease reconciler can operate. ## What to build 1. Define the relay's actor representation: ```json { "actor": { "kind": "system", "principal_id": "aether-relay" } } ``` 2. Decide whether the relay uses a dedicated Ed25519 keypair or a system-level identity that doesn't go through the standard event signing path. 3. Document which events the relay may generate as system transitions: - Lease expiry - Stale label reconciliation - Drift repair - Re-offer after lease failure 4. Define authorization: what can the relay's system identity do vs what requires a human or agent identity? ## Acceptance - [ ] Relay identity documented in `docs/relay-system-identity.md` - [ ] Keypair or identity mechanism decided - [ ] Authorized system transition types listed - [ ] Authorization boundaries defined (system identity cannot claim work or close issues on behalf of agents)

starsetbyte added the

phase-1

integration

labels

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