pdurlej/platform

Fork 0

feat(iskra): wire OpenClaw mail consumer — close Iskra value loop (read+reply) #235

New issue

Closed

opened 2026-05-12 07:58:23 +02:00 by pdurlej · 2 comments

pdurlej commented

2026-05-12 07:58:23 +02:00

Owner

Why this helps Iskra

Iskra's #1 promised value is: "reads my email + replies as me, with context." Per state/L3/OPEN_LOOPS.md (Apr 12 audit), mail infra is 60% done — gateway on RS2000 is healthy, but VPS 1000 OpenClaw isn't consuming. The user-facing reply action doesn't exist yet. Every day this stays open is a day where Iskra is technically alive but practically silent on her highest-value job.

This is operator-emotional priority. Not architectural.

Context (from `state/L3/OPEN_LOOPS.md` — `unresolved_active` cluster "Mail infra '60% done'")

Three concrete gaps surfaced in 3 independent threads (Apr 4, Apr 12, repeatedly):

OPENCLAW_MAIL_OPENCLAW_DISPATCH_URL and _TOKEN empty (commit 617b59fa, Apr 12) — RS2000 mail-infra-x4 gateway is healthy and dispatching, but VPS1000 OpenClaw side has no consumer URL/token configured.
dispatch_openclaw_intake not configured — action-plane partially inactive on the OpenClaw side; no handler picks up the dispatched messages.
No first-class reply action (commit a931c692) — even when intake works, there's no symmetric outbound path. Iskra can read, can't respond.
Telemetry gap: lastInboundAt / lastOutboundAt null on Signal/Matrix despite running=true. We can't see if anything is moving.

These have been open since early April. Three threads, never closed.

Acceptance criteria

Discovery (Codex first task): SSH to VPS1000, confirm current state of OPENCLAW_MAIL_OPENCLAW_DISPATCH_URL / _TOKEN in OpenClaw runtime env (~openclaw/.openclaw/runtime.env or extension config). Write findings to state/reports/2026-05-12-mail-infra-recon.md BEFORE writing code.
Configure dispatch endpoint: VPS1000 OpenClaw consumes mail events from RS2000 mail-infra-x4 gateway. Token/URL set via existing secrets pattern (Bitwarden or runtime.env, NOT plaintext in module.yaml).
Implement dispatch_openclaw_intake handler: incoming mail → OpenClaw conversation thread or Signal handoff per existing channel routing patterns.
First-class reply action: outbound mail via mail-infra-x4 gateway with In-Reply-To + References headers preserved.
Telemetry fix: lastInboundAt / lastOutboundAt populated on Signal + Matrix integrations once mail handler activates.
Operator validation: send test email to Piotr's tracked address → Iskra reads → Iskra replies via voice approval (per existing assistant.send UX pattern). Document in runbooks/iskra-mail-loop.md.

Codex Packet (read this carefully — anti-drift fences below)

Scope: ONLY mail-infra glue between RS2000 mail-infra-x4 and VPS1000 OpenClaw. NO new mail provider integrations. NO refactor of existing mail-infra-x4 module on RS2000 (it's healthy per evidence).

Files likely touched:

modules/openclaw-mail-infra/module.yaml (verify it exists; create if not, follow v2 schema)
modules/openclaw-mail-infra/runbook.md
New runbook: runbooks/iskra-mail-loop.md
Recon report: state/reports/2026-05-12-mail-infra-recon.md (READ-ONLY discovery first; no code changes until this lands)

Sequence:

Recon-only PR: file under state/reports/. Codex may execute SSH probes (read-only) per existing AGENTS.md guidance for VPS1000 inventory. NO mutation.
Operator review of recon report — decide go/no-go on config approach (Bitwarden vs runtime.env, etc.). Recon must surface the tradeoffs.
Config + handler PR — only after operator approval. Smallest coherent unit per class/security-sensitive discipline.
Telemetry + reply action PR — final piece, after Phase 3 of this issue lands.

Non-goals (DON'T do this)

❌ Adding new mail providers (Fastmail JMAP, etc.) — that's Issue #69 territory on iskra-openclaw repo, not here.
❌ Restructuring mail-infra-x4 on RS2000 — out of scope, it's healthy.
❌ Voice-note-to-mail-draft — adjacent feature, separate issue if needed.
❌ Building a "mail dashboard" UI — Iskra's surface is Signal/Matrix, not a new UI.
❌ Plaintext secrets in module.yaml. Hard fail per policies/sacred-paths.yaml + safety.py.

References

state/L3/OPEN_LOOPS.md — "Mail infra '60% done'" cluster
Commits cited: 617b59fa (Apr 12), a931c692 (Apr 12), 44684022 (Apr 5)
AGENTS.md §security-sensitive class
REVIEW.md — security-sensitive PRs require tier/full canary

Filed by claude (Prof Kong intermezzo, 2026-05-12 morning) under operator's "platform w twoje ręce" mandate. Pan Herbatka primary on this repo; coordinate via STATUS_NOW.md.

## Why this helps Iskra Iskra's #1 promised value is: *"reads my email + replies as me, with context."* Per `state/L3/OPEN_LOOPS.md` (Apr 12 audit), mail infra is **60% done** — gateway on RS2000 is healthy, but VPS 1000 OpenClaw isn't consuming. **The user-facing reply action doesn't exist yet.** Every day this stays open is a day where Iskra is technically alive but practically silent on her highest-value job. This is operator-emotional priority. Not architectural. --- ## Context (from `state/L3/OPEN_LOOPS.md` — `unresolved_active` cluster "Mail infra '60% done'") Three concrete gaps surfaced in **3 independent threads** (Apr 4, Apr 12, repeatedly): 1. **`OPENCLAW_MAIL_OPENCLAW_DISPATCH_URL` and `_TOKEN` empty** (commit `617b59fa`, Apr 12) — RS2000 mail-infra-x4 gateway is healthy and dispatching, but VPS1000 OpenClaw side has no consumer URL/token configured. 2. **`dispatch_openclaw_intake` not configured** — action-plane partially inactive on the OpenClaw side; no handler picks up the dispatched messages. 3. **No first-class `reply` action** (commit `a931c692`) — even when intake works, there's no symmetric outbound path. Iskra can read, can't respond. 4. **Telemetry gap**: `lastInboundAt` / `lastOutboundAt` null on Signal/Matrix despite `running=true`. We can't see if anything is moving. These have been open since early April. Three threads, never closed. --- ## Acceptance criteria - [ ] **Discovery (Codex first task)**: SSH to VPS1000, confirm current state of `OPENCLAW_MAIL_OPENCLAW_DISPATCH_URL` / `_TOKEN` in OpenClaw runtime env (`~openclaw/.openclaw/runtime.env` or extension config). Write findings to `state/reports/2026-05-12-mail-infra-recon.md` BEFORE writing code. - [ ] **Configure dispatch endpoint**: VPS1000 OpenClaw consumes mail events from RS2000 mail-infra-x4 gateway. Token/URL set via existing secrets pattern (Bitwarden or `runtime.env`, **NOT** plaintext in `module.yaml`). - [ ] **Implement `dispatch_openclaw_intake` handler**: incoming mail → OpenClaw conversation thread or Signal handoff per existing channel routing patterns. - [ ] **First-class `reply` action**: outbound mail via mail-infra-x4 gateway with `In-Reply-To` + `References` headers preserved. - [ ] **Telemetry fix**: `lastInboundAt` / `lastOutboundAt` populated on Signal + Matrix integrations once mail handler activates. - [ ] **Operator validation**: send test email to Piotr's tracked address → Iskra reads → Iskra replies via voice approval (per existing `assistant.send` UX pattern). Document in `runbooks/iskra-mail-loop.md`. --- ## Codex Packet (read this carefully — anti-drift fences below) **Scope**: ONLY mail-infra glue between RS2000 mail-infra-x4 and VPS1000 OpenClaw. NO new mail provider integrations. NO refactor of existing mail-infra-x4 module on RS2000 (it's healthy per evidence). **Files likely touched**: - `modules/openclaw-mail-infra/module.yaml` (verify it exists; create if not, follow v2 schema) - `modules/openclaw-mail-infra/runbook.md` - New runbook: `runbooks/iskra-mail-loop.md` - Recon report: `state/reports/2026-05-12-mail-infra-recon.md` (READ-ONLY discovery first; no code changes until this lands) **Sequence**: 1. **Recon-only PR**: file under `state/reports/`. Codex may execute SSH probes (read-only) per existing AGENTS.md guidance for VPS1000 inventory. NO mutation. 2. **Operator review of recon report** — decide go/no-go on config approach (Bitwarden vs runtime.env, etc.). Recon must surface the tradeoffs. 3. **Config + handler PR** — only after operator approval. Smallest coherent unit per `class/security-sensitive` discipline. 4. **Telemetry + reply action PR** — final piece, after Phase 3 of this issue lands. --- ## Non-goals (DON'T do this) - ❌ Adding new mail providers (Fastmail JMAP, etc.) — that's Issue #69 territory on iskra-openclaw repo, not here. - ❌ Restructuring mail-infra-x4 on RS2000 — out of scope, it's healthy. - ❌ Voice-note-to-mail-draft — adjacent feature, separate issue if needed. - ❌ Building a "mail dashboard" UI — Iskra's surface is Signal/Matrix, not a new UI. - ❌ Plaintext secrets in `module.yaml`. **Hard fail** per `policies/sacred-paths.yaml` + safety.py. --- ## References - `state/L3/OPEN_LOOPS.md` — "Mail infra '60% done'" cluster - Commits cited: `617b59fa` (Apr 12), `a931c692` (Apr 12), `44684022` (Apr 5) - AGENTS.md §security-sensitive class - REVIEW.md — security-sensitive PRs require `tier/full` canary --- *Filed by claude (Prof Kong intermezzo, 2026-05-12 morning) under operator's "platform w twoje ręce" mandate. Pan Herbatka primary on this repo; coordinate via STATUS_NOW.md.*

pdurlej added the

labels

2026-05-12 07:58:23 +02:00

pdurlej referenced this issue

2026-05-12 07:59:20 +02:00

fix(security): finish Bws/Infisical secrets injection — close 3-thread gap #237

claude referenced this issue

2026-05-17 18:11:53 +02:00

docs(specs): secrets-pipeline-foundation-v0 prebuild (#237) #335

claude referenced this issue from a commit

2026-05-17 21:09:39 +02:00

docs(specs): Iskra mail consumer v0 prebuild for #235

claude referenced this issue

2026-05-17 21:09:58 +02:00

docs(specs): Iskra mail consumer v0 prebuild (#235) #346

claude referenced this issue from a commit

2026-05-17 21:14:35 +02:00

docs(specs): Iskra Phase 1.0 bundle apply v0 prebuild for #236

claude referenced this issue

2026-05-17 21:14:58 +02:00

docs(specs): Iskra Phase 1.0 bundle apply v0 prebuild (#236) #347

claude referenced this issue from a commit

2026-05-17 21:28:58 +02:00

docs(specs): secrets-pipeline-foundation-v0 prebuild (#237)

codex added this to the 08 - Persona and OpenClaw product loops milestone

2026-05-19 08:36:31 +02:00

pdurlej referenced this issue from a commit

2026-05-23 10:31:21 +02:00

Merge pull request 'docs(specs): Iskra mail consumer v0 prebuild (#235)' (#346) from claude/iskra/mail-consumer-v0 into main

codex referenced this issue

2026-05-25 00:24:55 +02:00

docs(w7): record product integration smoke #463

codex referenced this issue

2026-05-25 00:41:08 +02:00

fix(w7): pin pogodowa-babcia registry artifact #464

codex referenced this issue

2026-05-25 01:16:10 +02:00

docs(w7): close registry runtime cleanup #467

codex referenced this issue

2026-05-28 01:21:54 +02:00

chore(m08): select next one or two Persona/OpenClaw product loops #542

codex referenced this issue

2026-05-29 16:55:52 +02:00

chore(m08): select next one or two Persona/OpenClaw product loops #542

codex commented

2026-05-29 16:55:52 +02:00

Collaborator

M08 triage result: hold for now. Iskra's metadata-only domain reply recommends #131/#236/#568 first; mail loop remains high value, but needs tighter live scope/evidence before execution. No runtime mutation was performed.

codex referenced this issue

2026-05-29 16:58:33 +02:00

chore(m08): select next one or two Persona/OpenClaw product loops #542

codex referenced this issue

2026-05-29 16:58:33 +02:00

Mail infra 60% done — continue or sunset (owner decision needed) #48

codex referenced this issue

2026-05-29 16:59:57 +02:00

chore(w9): milestone archaeology packet for stale open issues #535

~~codex referenced this issue 2026-05-30 06:59:54 +02:00~~

docs(coordination): claude/Codex work-division seam (Codex Pro 20x rebalance) #625

claude added the

dependency/blocked

priority:p1

labels

2026-05-30 22:42:01 +02:00

claude referenced this issue

2026-06-01 08:54:34 +02:00

Mail infra 60% done — continue or sunset (owner decision needed) #48

codex referenced this issue from a pull request that will close it,

2026-06-04 22:27:53 +02:00

docs(mail): map Iskra mail loops #716

codex commented

2026-06-04 22:50:37 +02:00

Collaborator

Mail loop closeout reframe from Codex.

This issue should no longer be treated as the old standalone iskra-mail-consumer-v0 wiring task. That path is now historical/superseded. The current closeout model is:

Gmail header radar: Iskra may see only headers/metadata, with sensitive subject denylist hiding subject/sender when needed.
Missive explicit escalation: an operator @iskra comment grants exactly one conversation for body read/comment handling.
Fastmail DMZ: selected/forwarded mail becomes an action workspace where Iskra can classify and draft, but cannot send without promote/approve.

Current PR chain:

platform #716 maps the canonical mail loops and marks the old spec as superseded.
iskra-openclaw #417 exposes Gmail metadata radar capability.
iskra-openclaw #418 locks Missive grant boundaries.
iskra-openclaw #419 reanimates Fastmail DMZ contracts, tests, skill, scripts, and systemd templates without runtime deploy.

Do not close #235 yet. Close only after operator smoke proves: Iskra helps with mail without reading everything and without autonomous send.

Mail loop closeout reframe from Codex. This issue should no longer be treated as the old standalone `iskra-mail-consumer-v0` wiring task. That path is now historical/superseded. The current closeout model is: 1. Gmail header radar: Iskra may see only headers/metadata, with sensitive subject denylist hiding subject/sender when needed. 2. Missive explicit escalation: an operator `@iskra` comment grants exactly one conversation for body read/comment handling. 3. Fastmail DMZ: selected/forwarded mail becomes an action workspace where Iskra can classify and draft, but cannot send without promote/approve. Current PR chain: - platform #716 maps the canonical mail loops and marks the old spec as superseded. - iskra-openclaw #417 exposes Gmail metadata radar capability. - iskra-openclaw #418 locks Missive grant boundaries. - iskra-openclaw #419 reanimates Fastmail DMZ contracts, tests, skill, scripts, and systemd templates without runtime deploy. Do not close #235 yet. Close only after operator smoke proves: Iskra helps with mail without reading everything and without autonomous send.

pdurlej closed this issue

2026-06-04 22:55:29 +02:00