pdurlej/platform

Fork 0

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

New issue

Closed

opened 2026-05-28 01:21:54 +02:00 by codex · 2 comments

codex commented

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

Collaborator

Scope

Turn Milestone 08 from a broad product-loop bucket into a small next-action queue.

Rank the open M08 issues by value and readiness, then recommend only one or two next flows.

Spec sources

state/roadmap/current-platform-roadmap.md § 08 - Persona and OpenClaw product loops
Open M08 issues: #48, #112, #133, #135, #177, #179, #235, #236, #290

Acceptance criteria

A ranking table exists for all open M08 issues.
Recommend 1-2 next issues, not a broad parallel push.
Identify issues that need owner taste/decision vs agent execution.
No runtime mutation.

Out of scope

Implementing mail consumer, dashboards, or persona bridges.
Changing OpenClaw memory/instructions.
Adding new product-loop issues unless a duplicate/split is unavoidable.

Agent notes

Recommended executor: Gemini 3.5 Flash local.

Rules:

Keep the PR small and boring.
Prefer closing/splitting stale work over adding new architecture docs.
Do not mutate production runtime.
Do not close issues live unless the issue explicitly requests it and evidence is clear.
PR body must include Spec sources read.

## Scope Turn Milestone 08 from a broad product-loop bucket into a small next-action queue. Rank the open M08 issues by value and readiness, then recommend only one or two next flows. ## Spec sources - `state/roadmap/current-platform-roadmap.md` § 08 - Persona and OpenClaw product loops - Open M08 issues: #48, #112, #133, #135, #177, #179, #235, #236, #290 ## Acceptance criteria - A ranking table exists for all open M08 issues. - Recommend 1-2 next issues, not a broad parallel push. - Identify issues that need owner taste/decision vs agent execution. - No runtime mutation. ## Out of scope - Implementing mail consumer, dashboards, or persona bridges. - Changing OpenClaw memory/instructions. - Adding new product-loop issues unless a duplicate/split is unavoidable. ## Agent notes Recommended executor: Gemini 3.5 Flash local. Rules: - Keep the PR small and boring. - Prefer closing/splitting stale work over adding new architecture docs. - Do not mutate production runtime. - Do not close issues live unless the issue explicitly requests it and evidence is clear. - PR body must include `Spec sources read`.

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

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

codex added the

labels

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

codex commented

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

Author

Collaborator

Role: executor
Intent: lane-outcome
Needs owner: no

M08 Persona/OpenClaw product-loop triage packet. No runtime mutation, no OpenClaw writes, no mail/dashboard implementation.

Spec sources read:

state/roadmap/current-platform-roadmap.md § 08 - Persona and OpenClaw product loops
Current open M08 issues visible in Forgejo: #131, #235, #236, #290, #568
Iskra domain reply via Platform Approvals, metadata-only

Iskra domain signal:

ISKRA_M08 issue=542 next=#131,#236,#568 hold=#235,#290 reason=prioritize_infra_observability_and_registration;mail_dashboard_need_live_scope

Ranking:

Rank	Issue	Disposition	Why
1	#568	next	Scheduler observability is prerequisite evidence: understand split cron/systemd/OpenClaw scheduler state before product automation expands.
2	#131	next	Kan MCP registration should become platform-managed; current live-only systemd drop-in is useful drift but not source of truth.
3	#236	next, gated	Phase 1.0 constitutional bundle matters for Iskra autonomy, but any live VPS1000 apply remains operator/runtime-gated.
4	#235	hold	Mail read/reply is high value, but Iskra recommends waiting for live scope/evidence after infra/observability/registration.
5	#290	hold	Dashboard can wait; it is product-facing and needs a tighter data/source contract before implementation.

Recommendation:

Prefer #568 as the next safe non-runtime/spec/evidence work.
Then #131 as platform-managed registration preflight, not ad-hoc secret writes.
Treat #236 as a gated runtime apply lane after observability and registration reduce uncertainty.

Next: close this triage issue; keep M08 focused on #568/#131/#236 before mail/dashboard.

**Role:** executor **Intent:** lane-outcome **Needs owner:** no M08 Persona/OpenClaw product-loop triage packet. No runtime mutation, no OpenClaw writes, no mail/dashboard implementation. Spec sources read: - `state/roadmap/current-platform-roadmap.md` § 08 - Persona and OpenClaw product loops - Current open M08 issues visible in Forgejo: #131, #235, #236, #290, #568 - Iskra domain reply via Platform Approvals, metadata-only Iskra domain signal: ```text ISKRA_M08 issue=542 next=#131,#236,#568 hold=#235,#290 reason=prioritize_infra_observability_and_registration;mail_dashboard_need_live_scope ``` Ranking: | Rank | Issue | Disposition | Why | |---:|---|---|---| | 1 | #568 | next | Scheduler observability is prerequisite evidence: understand split cron/systemd/OpenClaw scheduler state before product automation expands. | | 2 | #131 | next | Kan MCP registration should become platform-managed; current live-only systemd drop-in is useful drift but not source of truth. | | 3 | #236 | next, gated | Phase 1.0 constitutional bundle matters for Iskra autonomy, but any live VPS1000 apply remains operator/runtime-gated. | | 4 | #235 | hold | Mail read/reply is high value, but Iskra recommends waiting for live scope/evidence after infra/observability/registration. | | 5 | #290 | hold | Dashboard can wait; it is product-facing and needs a tighter data/source contract before implementation. | Recommendation: 1. Prefer #568 as the next safe non-runtime/spec/evidence work. 2. Then #131 as platform-managed registration preflight, not ad-hoc secret writes. 3. Treat #236 as a gated runtime apply lane after observability and registration reduce uncertainty. **Next:** close this triage issue; keep M08 focused on #568/#131/#236 before mail/dashboard.

codex closed this issue

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

codex commented

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

Author

Collaborator

Supplemental M08 triage for older open issues. This completes #542's "all open M08" acceptance coverage.

Iskra domain signal, metadata-only:

ISKRA_M08_SUPP issue=542 keep=#135,#177 park=#48,#112,#133,#179 close=none reason=keep_observability_and_privacy_layer;park_old_or_scope_dependent_items

Supplemental disposition:

Issue	Disposition	Why
#135	keep in M08	Scheduler observability is part of the current OpenClaw safety/readiness lane and aligns with #568.
#177	keep in M08	Privacy/pseudo-anonymization read layer remains relevant to safe cloud-agent/persona work.
#48	park in M10	Old mail umbrella / owner-decision shape; #235 is the narrower current mail-loop issue, and Iskra says mail needs live scope first.
#112	park in M10	Heretic Matrix/Ollama room is useful but not current M08 critical path.
#133	park in M10	Mobile Forji auth/upstream work is useful operator UX, not current Persona/OpenClaw critical path.
#179	park in M10	Family-assistant tier is future product expansion, not current platform closeout.

No issues closed from this supplemental pass.

Supplemental M08 triage for older open issues. This completes #542's "all open M08" acceptance coverage. Iskra domain signal, metadata-only: ```text ISKRA_M08_SUPP issue=542 keep=#135,#177 park=#48,#112,#133,#179 close=none reason=keep_observability_and_privacy_layer;park_old_or_scope_dependent_items ``` Supplemental disposition: | Issue | Disposition | Why | |---|---|---| | #135 | keep in M08 | Scheduler observability is part of the current OpenClaw safety/readiness lane and aligns with #568. | | #177 | keep in M08 | Privacy/pseudo-anonymization read layer remains relevant to safe cloud-agent/persona work. | | #48 | park in M10 | Old mail umbrella / owner-decision shape; #235 is the narrower current mail-loop issue, and Iskra says mail needs live scope first. | | #112 | park in M10 | Heretic Matrix/Ollama room is useful but not current M08 critical path. | | #133 | park in M10 | Mobile Forji auth/upstream work is useful operator UX, not current Persona/OpenClaw critical path. | | #179 | park in M10 | Family-assistant tier is future product expansion, not current platform closeout. | No issues closed from this supplemental pass.