Phase 08+ scope: Iskra family-assistant tier (Kasia indirect via Piotr-supervised flows) #179

Open
opened 2026-05-11 07:44:00 +02:00 by claude · 3 comments
Collaborator

Context

Per operator voice-note 2026-05-11 07:26:

"Póki co nie chce dawać Kasi dostępu, dlatego że Kasia dopiero się uczy AI. Wczoraj miała przyjemność po raz pierwszy wykorzystać Cloud Code'a praktycznie do cross-check'u bibliografii naukowej. Póki co Family powinna być jako solo. Future scope: będę chciał żeby OpenClaw pomagał Kasi w pewnych procesach, na przykład tworzenie wpisów na LinkedInie, tworzenie jakiegoś contentu na social media i żeby to działało półautonomicznie, ale żeby ta pamięć była inna. Czy tutaj, żeby było wiadomo, że to jest Piotr robiący dla swojej żony i żeby tam ta pamięć jakby tam tworzona nie wchodziła. Iskra awansuje jako asystentka całej rodziny."

Goal (Phase 08+)

When Kasia's AI confidence grows (estimated 2026Q3+), Iskra advances from solo-operator-tier to family-assistant tier without losing identity-isolation between Piotr-personal and Piotr-doing-for-Kasia contexts.

Operator confirms: Kasia herself won't directly interact with OpenClaw; Piotr supervises all Kasia-related flows.

Architecture (proposed for future ADR)

Iskra runtime stays single-instance on vps1000. Identity-of-context becomes a per-job concept:

Context Source Memory channel Output channels
piotr-personal Piotr on Signal honcho.pdurlej.com/spaces/piotr (existing) per ADR-0006
piotr-for-kasia (NEW) Piotr explicitly tagged "for Kasia" separate Honcho space honcho.pdurlej.com/spaces/piotr-for-kasia Kasia-tagged content; LinkedIn drafts; social media posts

Examples of piotr-for-kasia flows:

  • "Iskra, write a LinkedIn post for Kasia about her conference talk"
  • "Iskra, draft 3 Instagram captions for Kasia's article launch"
  • "Iskra, summarize Kasia's last 3 social posts for her self-review"

Iskra knows:

  • This is Piotr speaking (operator authority)
  • For Kasia (consumer/subject)
  • Memory written to separate space (no cross-contamination with Piotr-personal)

Scope (this issue produces future ADR draft)

When Phase 08+ time comes, draft ADR with:

  1. Context-identity field in job bundle (per ADR-0008 schema amendment):

    • for_principal: piotr | piotr-for-kasia | ...
    • Memory routing rule: which Honcho space writes happen against
  2. Cousin-roles amendment in ADR-0006:

    • Iskra gets explicit family-assistant mode
    • Boundary: Iskra still cannot have Kasia as direct operator (per ADR-0006 §What MUST NOT do; Kasia is indirect via Piotr's supervision)
  3. Privacy boundary:

    • Kasia-content goes to Iskra-i-Piotr/Kasia-supervised/ folder (or similar; operator chooses naming)
    • Per ADR-0010: this folder defaults to soft_private
    • Hard_private remains Family/ (operator-personal family content, distinct from Kasia-as-subject)
  4. Triggers and pre-flight gates:

    • When does this ADR activate? Operator signals "Kasia ready" via PR amendment.
    • Pre-flight: Kasia consents to her name + content being part of supervised flows. (Operator handles consent conversation; ADR doesn't dictate.)

Out of scope (this issue)

  • Direct Kasia-as-operator surface (operator declined)
  • Multi-family-member support beyond Kasia (Phase 09+)
  • Public visibility of Kasia-generated content (operator handles privacy + brand decisions per-post)

Phase

Phase 08+ (future scope; not active until operator signals Kasia is AI-confident).

Acceptance criteria

  • ADR draft exists when Phase 08+ activates
  • ADR-0008 schema amendment for for_principal field
  • ADR-0006 amendment for Iskra family-assistant mode
  • Privacy-tier mapping for Kasia-supervised content
  • Operator-Kasia consent flow documented (not auto-enforced; manual)

Refs

  • Operator voice-note 2026-05-11 07:26 (introduced concept)
  • ADR-0006 (cousin role taxonomy)
  • ADR-0008 (durable job bundle)
  • ADR-0010 (local-admin LLM tier)
  • Kasia's first AI use 2026-05-10 (Cloud Code for academic bibliography cross-check; operator's recall)

Coordination

  • Lane: Phase 08+ scope (advisor; not actionable yet)
  • Owner: claude-orchestrator drafts when Phase 08+ activates
  • Operator: signals readiness when Kasia is AI-confident; handles Kasia consent conversation

Role: advisor (claude)

## Context Per operator voice-note 2026-05-11 07:26: > *"Póki co nie chce dawać Kasi dostępu, dlatego że Kasia dopiero się uczy AI. Wczoraj miała przyjemność po raz pierwszy wykorzystać Cloud Code'a praktycznie do cross-check'u bibliografii naukowej. Póki co Family powinna być jako solo. Future scope: będę chciał żeby OpenClaw pomagał Kasi w pewnych procesach, na przykład tworzenie wpisów na LinkedInie, tworzenie jakiegoś contentu na social media i żeby to działało półautonomicznie, ale żeby ta pamięć była inna. Czy tutaj, żeby było wiadomo, że to jest Piotr robiący dla swojej żony i żeby tam ta pamięć jakby tam tworzona nie wchodziła. Iskra awansuje jako asystentka całej rodziny."* ## Goal (Phase 08+) When Kasia's AI confidence grows (estimated 2026Q3+), Iskra advances from solo-operator-tier to **family-assistant tier** without losing identity-isolation between Piotr-personal and Piotr-doing-for-Kasia contexts. **Operator confirms**: Kasia herself won't directly interact with OpenClaw; Piotr supervises all Kasia-related flows. ## Architecture (proposed for future ADR) Iskra runtime stays single-instance on vps1000. Identity-of-context becomes a per-job concept: | Context | Source | Memory channel | Output channels | |---------|--------|----------------|-----------------| | `piotr-personal` | Piotr on Signal | `honcho.pdurlej.com/spaces/piotr` (existing) | per ADR-0006 | | `piotr-for-kasia` (NEW) | Piotr explicitly tagged "for Kasia" | separate Honcho space `honcho.pdurlej.com/spaces/piotr-for-kasia` | Kasia-tagged content; LinkedIn drafts; social media posts | Examples of `piotr-for-kasia` flows: - "Iskra, write a LinkedIn post for Kasia about her conference talk" - "Iskra, draft 3 Instagram captions for Kasia's article launch" - "Iskra, summarize Kasia's last 3 social posts for her self-review" Iskra **knows**: - This is Piotr speaking (operator authority) - For Kasia (consumer/subject) - Memory written to separate space (no cross-contamination with Piotr-personal) ## Scope (this issue produces future ADR draft) When Phase 08+ time comes, draft ADR with: 1. **Context-identity field** in job bundle (per ADR-0008 schema amendment): - `for_principal: piotr | piotr-for-kasia | ...` - Memory routing rule: which Honcho space writes happen against 2. **Cousin-roles amendment** in ADR-0006: - Iskra gets explicit `family-assistant` mode - Boundary: Iskra still cannot have Kasia as direct operator (per ADR-0006 §What MUST NOT do; Kasia is indirect via Piotr's supervision) 3. **Privacy boundary**: - Kasia-content goes to `Iskra-i-Piotr/Kasia-supervised/` folder (or similar; operator chooses naming) - Per ADR-0010: this folder defaults to `soft_private` - Hard_private remains `Family/` (operator-personal family content, distinct from Kasia-as-subject) 4. **Triggers and pre-flight gates**: - When does this ADR activate? Operator signals "Kasia ready" via PR amendment. - Pre-flight: Kasia consents to her name + content being part of supervised flows. (Operator handles consent conversation; ADR doesn't dictate.) ## Out of scope (this issue) - Direct Kasia-as-operator surface (operator declined) - Multi-family-member support beyond Kasia (Phase 09+) - Public visibility of Kasia-generated content (operator handles privacy + brand decisions per-post) ## Phase Phase 08+ (future scope; not active until operator signals Kasia is AI-confident). ## Acceptance criteria - [ ] ADR draft exists when Phase 08+ activates - [ ] ADR-0008 schema amendment for `for_principal` field - [ ] ADR-0006 amendment for Iskra family-assistant mode - [ ] Privacy-tier mapping for Kasia-supervised content - [ ] Operator-Kasia consent flow documented (not auto-enforced; manual) ## Refs - Operator voice-note 2026-05-11 07:26 (introduced concept) - ADR-0006 (cousin role taxonomy) - ADR-0008 (durable job bundle) - ADR-0010 (local-admin LLM tier) - Kasia's first AI use 2026-05-10 (Cloud Code for academic bibliography cross-check; operator's recall) ## Coordination - Lane: Phase 08+ scope (advisor; not actionable yet) - Owner: claude-orchestrator drafts when Phase 08+ activates - Operator: signals readiness when Kasia is AI-confident; handles Kasia consent conversation **Role:** advisor (claude)
Collaborator

Parked from M08 to M10 per Iskra supplemental triage. Family-assistant tier is future expansion and should wait until core Iskra/OpenClaw loops are stable. No runtime mutation was performed.

Parked from M08 to M10 per Iskra supplemental triage. Family-assistant tier is future expansion and should wait until core Iskra/OpenClaw loops are stable. No runtime mutation was performed.
Author
Collaborator

Parked (p3, M10 closure plan #653 + Judging Claw priority). Reactivate when the Iskra family-assistant tier is scheduled (operator-emotional, family-sensitive — operator-gated).

**Parked (p3, M10 closure plan #653 + Judging Claw priority).** Reactivate when the Iskra family-assistant tier is scheduled (operator-emotional, family-sensitive — operator-gated).
Collaborator

{
"confidence": 5,
"effort_hint": "large",
"escalation": {
"kind": "operator",
"reason": "Family-assistant scope requires explicit identity isolation, consent, and supervision boundaries."
},
"evidence_refs": [
{
"note": "Issue scopes a future Iskra family-assistant tier with Kasia-related flows mediated by Piotr.",
"type": "forgejo",
"value": "issue-title-body-labels-and-target-snapshot"
},
{
"note": "Body frames the need to keep Piotr-personal and Piotr-for-Kasia memory contexts separate.",
"type": "forgejo",
"value": "issue-body-goal"
},
{
"note": "Snapshot labels mark the work as priority p3 and parked.",
"type": "snapshot",
"value": "target-snapshot-labels"
}
],
"impact": 4,
"judge_actor": {
"name": "iskra",
"runtime": "openclaw"
},
"judged_at": "2026-06-09T01:02:00Z",
"labels_to_apply": [
"judge/p2",
"judge/operator-needed"
],
"piotr_fit": "high",
"priority": "p2",
"rationale_summary": "This is P2 operator-shaped future architecture because family-assistant support is valuable only if consent and memory isolation are designed before use.",
"reach": 4,
"recommended_next_action": "operator_needed",
"rerun_reason": "no_prior_judgment",
"schema": "openclaw.judge.v0",
"target": {
"kind": "issue",
"number": 179,
"repo": "pdurlej/platform"
},
"target_snapshot": {
"body_hash": "sha256:e8bf1c088c3fa24d41a6ecf1f79107c402a4361e9dc258c1c33229b0d5e54bae",
"commit_count": null,
"evidence_hash": "sha256:64c3247e647f905d09058258a0006a1e44e9e2033aaa297c959c860b508eb5e4",
"head_sha": null,
"labels": [
"agent/claude-code",
"priority:p3",
"status:parked"
],
"labels_hash": "sha256:9e8ed9cb7b1b30f4dcf389e2b3d1f8e66c19eb940504926be5872a601be5b3ab",
"state": "open",
"title_hash": "sha256:9bdc5970409a133f619c9f3fa18e3bef58086cf2369622f2536aa52ec33349d7",
"updated_at": "2026-06-01T08:53:15+02:00"
},
"top_caveat": "Keep it parked until Piotr explicitly defines consent, memory separation, and indirect-use boundaries."
}

<!-- openclaw.judge.v0 --> { "confidence": 5, "effort_hint": "large", "escalation": { "kind": "operator", "reason": "Family-assistant scope requires explicit identity isolation, consent, and supervision boundaries." }, "evidence_refs": [ { "note": "Issue scopes a future Iskra family-assistant tier with Kasia-related flows mediated by Piotr.", "type": "forgejo", "value": "issue-title-body-labels-and-target-snapshot" }, { "note": "Body frames the need to keep Piotr-personal and Piotr-for-Kasia memory contexts separate.", "type": "forgejo", "value": "issue-body-goal" }, { "note": "Snapshot labels mark the work as priority p3 and parked.", "type": "snapshot", "value": "target-snapshot-labels" } ], "impact": 4, "judge_actor": { "name": "iskra", "runtime": "openclaw" }, "judged_at": "2026-06-09T01:02:00Z", "labels_to_apply": [ "judge/p2", "judge/operator-needed" ], "piotr_fit": "high", "priority": "p2", "rationale_summary": "This is P2 operator-shaped future architecture because family-assistant support is valuable only if consent and memory isolation are designed before use.", "reach": 4, "recommended_next_action": "operator_needed", "rerun_reason": "no_prior_judgment", "schema": "openclaw.judge.v0", "target": { "kind": "issue", "number": 179, "repo": "pdurlej/platform" }, "target_snapshot": { "body_hash": "sha256:e8bf1c088c3fa24d41a6ecf1f79107c402a4361e9dc258c1c33229b0d5e54bae", "commit_count": null, "evidence_hash": "sha256:64c3247e647f905d09058258a0006a1e44e9e2033aaa297c959c860b508eb5e4", "head_sha": null, "labels": [ "agent/claude-code", "priority:p3", "status:parked" ], "labels_hash": "sha256:9e8ed9cb7b1b30f4dcf389e2b3d1f8e66c19eb940504926be5872a601be5b3ab", "state": "open", "title_hash": "sha256:9bdc5970409a133f619c9f3fa18e3bef58086cf2369622f2536aa52ec33349d7", "updated_at": "2026-06-01T08:53:15+02:00" }, "top_caveat": "Keep it parked until Piotr explicitly defines consent, memory separation, and indirect-use boundaries." } <!-- /openclaw.judge.v0 -->
Sign in to join this conversation.
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No milestone
No project
No assignees
3 participants
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
pdurlej/platform#179
No description provided.