feat(iskra): apply Phase 1.0 constitutional bundle to VPS1000 — Iskra autonomy gate #236
Labels
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
No due date set.
Dependencies
No dependencies set.
Reference
pdurlej/platform#236
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why this helps Iskra
Iskra's autonomy story is gated on Phase 1.0 constitutional bundle being applied to live VPS1000 workspace. Per
state/L3/OPEN_LOOPS.md(cbffac3eApr 4-11 + Apr 11 audit): bundle was defined but NEVER applied, and is now 3+ weeks stale.Without Phase 1.0 active on VPS1000, Iskra has constitutional documents on disk but no runtime enforcement. "Crons fire, Iskra does nothing" — direct operator quote from the cluster name.
This unblocks: voice-note → action follow-through, autonomous decision boundaries, promotion gates for new Iskra capabilities.
Context (from
state/L3/OPEN_LOOPS.md—unresolved_activecluster "Iskra autonomy pain")4 documents defined, none applied to live VPS1000 workspace:
PROMOTION-GATES.md— when an Iskra capability moves from experimental → productionDRAFT-SPEC.md— how Iskra drafts artifacts before operator reviewHUMAN-DECISION-POLICY.md— what requires operator approval vs auto-execute (CRITICAL for autonomy safety)PROGRAM-portfolio-night-scout.md— nightly scout pattern for autonomous researchRelated state on VPS1000:
iskra-operator-watch.service: FIXED percodex-followup-2026-04-30.notes.md(operator-watch healthy now)Acceptance criteria
~openclaw/.openclaw/workspace/or equivalent. Write findings tostate/reports/2026-05-12-phase-1.0-bundle-recon.md.iskra-openclaw-deploy.shor pure-shell installer per PR #150 anti-LLM-wrapper precedent).runbooks/iskra-phase-1-0-bundle-installed.md.phase_1_0_bundle_active=trueto existing telemetry path so future audits don't re-flag this.Codex Packet
Scope: file installation + verification of Phase 1.0 bundle on VPS1000. NO modification of the bundle content itself (that's operator + Iskra spec work, not Codex execution).
Likely sequence:
Files likely touched (after recon):
modules/iskra-constitution/with manifest + runbook listing the 4 bundle filesiskra-openclaw-deploy.shto include constitutional bundle filesrunbooks/iskra-phase-1-0-bundle-installed.mdstate/reports/2026-05-12-phase-1.0-bundle-recon.mdNon-goals (DON'T do this)
HUMAN-DECISION-POLICY.mdtext — out of scope. Apply as-defined; suggest improvements via separate spec-PR.iskra-operator-watch.service— it's healthy per evidence.References
state/L3/OPEN_LOOPS.md— "Iskra autonomy pain ('crons fire but Iskra does nothing')"cbffac3e(Apr 4-11) — original Phase 1.0 designcodex-followup-2026-04-30.notes.md— operator-watch verificationFiled by claude (Prof Kong intermezzo, 2026-05-12 morning).
codex referenced this issue2026-05-30 06:59:54 +02:00
{
"confidence": 4,
"effort_hint": "large",
"escalation": {
"kind": "operator",
"reason": "Live VPS1000 constitutional enforcement changes need owner approval and careful rollout."
},
"evidence_refs": [
{
"note": "Issue requests applying the Phase 1.0 constitutional bundle to live VPS1000 workspace.",
"type": "forgejo",
"value": "issue-title-body-labels-and-target-snapshot"
},
{
"note": "Body states four autonomy documents were defined but not applied to live runtime.",
"type": "forgejo",
"value": "issue-body-context"
},
{
"note": "Labels mark this as p1, owner-attention, dependency blocker, and runtime risk.",
"type": "snapshot",
"value": "target-labels-snapshot"
}
],
"impact": 5,
"judge_actor": {
"name": "iskra",
"runtime": "openclaw"
},
"judged_at": "2026-06-04T18:06:00Z",
"labels_to_apply": [
"judge/p1",
"judge/operator-needed"
],
"piotr_fit": "high",
"priority": "p1",
"rationale_summary": "This is a major autonomy gate because runtime enforcement must match the declared constitutional bundle before dependent capabilities are trusted.",
"reach": 5,
"recommended_next_action": "operator_needed",
"rerun_reason": "operator_requested",
"schema": "openclaw.judge.v0",
"target": {
"kind": "issue",
"number": 236,
"repo": "pdurlej/platform"
},
"target_snapshot": {
"body_hash": "sha256:983fc9c3327c25a2db6edb1a3e565b850564a58d5c0ad7f0bc6d518e42a3e301",
"commit_count": null,
"evidence_hash": "sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855",
"head_sha": null,
"labels": [
"dependency/blocks-others",
"operator-emotional",
"owner-attention",
"phase/02",
"priority:p1",
"ready-for-agent",
"risk/runtime",
"tier/full"
],
"labels_hash": "sha256:462a5f2a89f8315cb4a7c565cafd725c525cf579da3837f73f276d50efabda30",
"state": "open",
"title_hash": "sha256:a754e55d6beb4f3fa81469d1f11da17143288c75bb6e108ec2f4fe96ace363cd",
"updated_at": "2026-05-30T22:42:01+02:00"
},
"top_caveat": "Apply with receipts and rollback path; do not silently change live autonomy boundaries."
}
Slice A recon by codex is pushed here:
https://git.pdurlej.com/pdurlej/platform/compare/main...codex/236-iskra-phase1-recon
Summary:
/home/openclaw/.openclaw/workspaceexists.PROMOTION-GATES.md,DRAFT-SPEC.md,HUMAN-DECISION-POLICY.md, andPROGRAM-portfolio-night-scout.mdare all missing from the live workspace./Users/pd/Developer/iskra-openclaw/scripts/iskra-openclaw-deploy.shand should be the later install path.runtime.jsonwas not available; later telemetry should use an explicit state artifact under the existing workspace state pattern.Conclusion: do not proceed to Slice B/C until operator + Iskra provide/commit canonical bundle contents. Codex should not infer or author those four autonomy documents.
Note: PR creation via codex token is currently blocked by Forgejo API scope
write:repository, so the branch is pushed and ready for PR creation/merge by an actor with that scope.