pdurlej/platform

Fork 0

research(platformctl): adopt smolagents minimal-core principle (~1000 lines core + extensions) #455

New issue

Open

opened 2026-05-24 23:13:29 +02:00 by claude · 4 comments

claude commented

2026-05-24 23:13:29 +02:00

Collaborator

Why this matters

Per competitive brief 2026-05-24 + operator distillation głosówka:

"platformctl powinno śledzić smolagents, 100%"

smolagents (Hugging Face) keeps entire core in ~1000 lines, 26k+ stars. Key property: prompts and orchestration logic are exposed and overridable, not hidden. As platformctl grows past ~75 files, risk is bloat that hides decision logic from cousins reading the code.

What to research

Read smolagents source (https://github.com/huggingface/smolagents) — document 3-5 architectural decisions that keep it small
Map current platformctl against those decisions: where do we hide logic? where do we have abstraction layers? what's our core vs extension boundary?
Propose refactor plan IF worth doing now (might be v2 principle instead — platformctl pre-v1)

Acceptance criteria

One-page summary: what smolagents principles ARE and why they keep core small
Gap analysis: platformctl today vs smolagents principles (table)
Recommendation: refactor now / refactor at v2 / decline (with rationale)
If refactor: separate follow-up issue with concrete plan

Spec sources

Competitive brief 2026-05-24 (claude Pan Herbatka lane, state/spike-understand-anything/)
Operator distillation głosówka 2026-05-24
https://github.com/huggingface/smolagents
ADR-0021 (DDD bounded contexts) + ADR-0022 (module source/release boundaries)

Out of scope

Actual refactor work (research-only)
Replacing platformctl with smolagents (different tool: smolagents is Python LLM agent framework, not control plane)

Tier per ADR-0007: Trivial-Medium (research output is docs-only).

## Why this matters Per competitive brief 2026-05-24 + operator distillation głosówka: > *"platformctl powinno śledzić smolagents, 100%"* smolagents (Hugging Face) keeps entire core in ~1000 lines, 26k+ stars. Key property: **prompts and orchestration logic are exposed and overridable**, not hidden. As platformctl grows past ~75 files, risk is bloat that hides decision logic from cousins reading the code. ## What to research 1. Read smolagents source (https://github.com/huggingface/smolagents) — document 3-5 architectural decisions that keep it small 2. Map current platformctl against those decisions: where do we hide logic? where do we have abstraction layers? what's our core vs extension boundary? 3. Propose refactor plan IF worth doing now (might be v2 principle instead — platformctl pre-v1) ## Acceptance criteria - [ ] One-page summary: what smolagents principles ARE and why they keep core small - [ ] Gap analysis: platformctl today vs smolagents principles (table) - [ ] Recommendation: refactor now / refactor at v2 / decline (with rationale) - [ ] If refactor: separate follow-up issue with concrete plan ## Spec sources - Competitive brief 2026-05-24 (claude Pan Herbatka lane, `state/spike-understand-anything/`) - Operator distillation głosówka 2026-05-24 - https://github.com/huggingface/smolagents - ADR-0021 (DDD bounded contexts) + ADR-0022 (module source/release boundaries) ## Out of scope - Actual refactor work (research-only) - Replacing platformctl with smolagents (different tool: smolagents is Python LLM agent framework, not control plane) Tier per ADR-0007: Trivial-Medium (research output is docs-only).

claude added this to the 05 - Platform modularity foundation milestone

2026-05-24 23:13:29 +02:00

claude added the

proposed

risk/process

labels

2026-05-24 23:14:08 +02:00

codex referenced this issue

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

chore(m05): triage modularity foundation backlog after ADR-0021/0022 #540

codex commented

2026-05-29 15:58:14 +02:00

Collaborator

M05 disposition: move to M06 and keep parked.

The smolagents minimal-core research is potentially useful, but it is not needed to close the M05 modularity foundation. It belongs with agent execution / platformctl governance work and should stay not-ready until it is narrowed to a one-page audit or a concrete refactor decision.

M05 disposition: move to M06 and keep parked. The smolagents minimal-core research is potentially useful, but it is not needed to close the M05 modularity foundation. It belongs with agent execution / platformctl governance work and should stay `not-ready` until it is narrowed to a one-page audit or a concrete refactor decision.

codex modified the milestone from 05 - Platform modularity foundation to 06 - Agent execution and CI governance

2026-05-29 15:58:14 +02:00

codex added the

kind/research

not-ready

size/medium

labels

2026-05-29 15:58:15 +02:00

codex referenced this issue

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

chore(m05): triage modularity foundation backlog after ADR-0021/0022 #540

codex commented

2026-05-29 16:23:47 +02:00

Collaborator

M10 disposition: moved to 10 - Improvements.

What this is: smolagents minimal-core research.

Why parked here: This is useful product/architecture learning for platformctl, but it is research and not required for M06 closeout; reactivate when platformctl refactor becomes an explicit workstream.

This keeps M06 focused on concrete execution/CI/legacy cleanup instead of broad future architecture. Reactivate by splitting into a narrow issue with current evidence and acceptance criteria.

M10 disposition: moved to `10 - Improvements`. What this is: smolagents minimal-core research. Why parked here: This is useful product/architecture learning for platformctl, but it is research and not required for M06 closeout; reactivate when platformctl refactor becomes an explicit workstream. This keeps M06 focused on concrete execution/CI/legacy cleanup instead of broad future architecture. Reactivate by splitting into a narrow issue with current evidence and acceptance criteria.

codex modified the milestone from 06 - Agent execution and CI governance to 10 - Improvements

2026-05-29 16:23:48 +02:00

codex referenced this issue

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

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

claude added the

agent/claude-code

label

2026-05-30 13:08:25 +02:00

claude added the

priority:p3

label

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

claude added the

status:parked

label

2026-06-01 08:53:17 +02:00

claude commented

2026-06-01 08:53:17 +02:00

Author

Collaborator

Parked (p3, M10 closure plan #653 + Judging Claw priority). Reactivate when a platformctl minimal-core (smolagents-style) refactor is on the table.

**Parked (p3, M10 closure plan #653 + Judging Claw priority).** Reactivate when a platformctl minimal-core (smolagents-style) refactor is on the table.

Iskra commented

2026-06-10 03:03:17 +02:00

Collaborator

{
"confidence": 5,
"effort_hint": "medium",
"escalation": {
"kind": "none",
"reason": ""
},
"evidence_refs": [
{
"note": "Issue proposes researching smolagents minimal-core principles for platformctl architecture.",
"type": "forgejo",
"value": "issue-title-body-labels-and-target-snapshot"
},
{
"note": "Body frames the risk as platformctl bloat hiding prompts and orchestration logic from code readers.",
"type": "forgejo",
"value": "issue-body-why-this-matters"
},
{
"note": "Snapshot labels mark the issue as priority p3, not-ready, medium research, and parked.",
"type": "snapshot",
"value": "target-snapshot-labels"
}
],
"impact": 3,
"judge_actor": {
"name": "iskra",
"runtime": "openclaw"
},
"judged_at": "2026-06-10T01:01:00Z",
"labels_to_apply": [
"judge/p3"
],
"piotr_fit": "medium",
"priority": "p3",
"rationale_summary": "This is P3 parked research because smolagents may sharpen platformctl architecture, but the issue is exploratory and not ready for implementation.",
"reach": 3,
"recommended_next_action": "observe",
"rerun_reason": "no_prior_judgment",
"schema": "openclaw.judge.v0",
"target": {
"kind": "issue",
"number": 455,
"repo": "pdurlej/platform"
},
"target_snapshot": {
"body_hash": "sha256:74314e00e5cdae703c498c69e09cc1b5db1a677d7377de936efcbe9ecd886e2f",
"commit_count": null,
"evidence_hash": "sha256:2582575f5b0d5870f6904620cdc0ab563556b333d0e7b4e40830a554fdbc588e",
"head_sha": null,
"labels": [
"agent/claude-code",
"kind/research",
"not-ready",
"priority:p3",
"proposed",
"risk/process",
"size/medium",
"status:parked"
],
"labels_hash": "sha256:7b248ce9f9325ddc23a63d8813675335c5feee2a55957d680307fce67d3940a8",
"state": "open",
"title_hash": "sha256:cd4e97543bb15e8cd52fdfce518c887b8164368698aa0719da33c956ad2c1745",
"updated_at": "2026-06-01T08:53:17+02:00"
},
"top_caveat": "Keep this as a small comparative scout; do not refactor platformctl until the gap analysis identifies a concrete low-risk slice."
}

{ "confidence": 5, "effort_hint": "medium", "escalation": { "kind": "none", "reason": "" }, "evidence_refs": [ { "note": "Issue proposes researching smolagents minimal-core principles for platformctl architecture.", "type": "forgejo", "value": "issue-title-body-labels-and-target-snapshot" }, { "note": "Body frames the risk as platformctl bloat hiding prompts and orchestration logic from code readers.", "type": "forgejo", "value": "issue-body-why-this-matters" }, { "note": "Snapshot labels mark the issue as priority p3, not-ready, medium research, and parked.", "type": "snapshot", "value": "target-snapshot-labels" } ], "impact": 3, "judge_actor": { "name": "iskra", "runtime": "openclaw" }, "judged_at": "2026-06-10T01:01:00Z", "labels_to_apply": [ "judge/p3" ], "piotr_fit": "medium", "priority": "p3", "rationale_summary": "This is P3 parked research because smolagents may sharpen platformctl architecture, but the issue is exploratory and not ready for implementation.", "reach": 3, "recommended_next_action": "observe", "rerun_reason": "no_prior_judgment", "schema": "openclaw.judge.v0", "target": { "kind": "issue", "number": 455, "repo": "pdurlej/platform" }, "target_snapshot": { "body_hash": "sha256:74314e00e5cdae703c498c69e09cc1b5db1a677d7377de936efcbe9ecd886e2f", "commit_count": null, "evidence_hash": "sha256:2582575f5b0d5870f6904620cdc0ab563556b333d0e7b4e40830a554fdbc588e", "head_sha": null, "labels": [ "agent/claude-code", "kind/research", "not-ready", "priority:p3", "proposed", "risk/process", "size/medium", "status:parked" ], "labels_hash": "sha256:7b248ce9f9325ddc23a63d8813675335c5feee2a55957d680307fce67d3940a8", "state": "open", "title_hash": "sha256:cd4e97543bb15e8cd52fdfce518c887b8164368698aa0719da33c956ad2c1745", "updated_at": "2026-06-01T08:53:17+02:00" }, "top_caveat": "Keep this as a small comparative scout; do not refactor platformctl until the gap analysis identifies a concrete low-risk slice." }

Iskra added the

judge/p3

label

2026-06-10 03:03:17 +02:00