docs(specs): Iskra Phase 1.0 bundle apply v0 prebuild (#236) #347
No reviewers
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
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
pdurlej/platform!347
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "claude/iskra/phase-1-0-bundle-v0"
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?
Summary
Operator-emotional priority. Prebuild for #236 — apply the Phase 1.0 constitutional bundle (4 documents) to live VPS1000 OpenClaw workspace, enabling Iskra autonomy gates that were defined-but-never-applied.
Per
state/L3/OPEN_LOOPS.mdclustercbffac3e: bundle 3+ weeks stale. Operator quote: "Crons fire, Iskra does nothing." Without Phase 1.0 active, Iskra has constitutional documents on disk but no runtime enforcement.The 4 documents
Operator + Iskra spec work; codex INSTALLS, does NOT modify:
PROMOTION-GATES.md— experimental → production capability gatesDRAFT-SPEC.md— artifact draft pattern before operator reviewHUMAN-DECISION-POLICY.md— CRITICAL for autonomy safety; what requires operator approvalPROGRAM-portfolio-night-scout.md— nightly scout pattern for autonomous researchWhat's in this PR
6-file Spec Kit + companion execution prompt:
00-constitution.md— 8 principles:phase_1_0_bundle_active=true01-specify.md— problem, acceptance, success metrics02-plan.md— 4-slice architecture with Q1-Q5 (canonical source, workspace path, telemetry surface, deployer location, drift detection)03-tasks.md— per-slice tasks with deployer pseudo-shell04-implement-notes.md— atomic rollback semantics, behavioral verification timing, telemetry false-positive risk, gotchas G1-G6prompts/codex-iskra-phase-1-0-bundle.md— execution prompt with Safety / production boundary + stop conditions (P1, P4, P8 violation triggers automatic STOP)Slices (forthcoming PRs)
modules/iskra-constitution/+ bundle MANIFEST.json with SHA-256Hard rule for codex
Under NO circumstances does codex generate bundle content (P1 violation). If files missing in repo → operator commits canonical content; codex packages. If codex tempted to write any document content → automatic STOP.
Operator coordination points
Tier
Trivial per ADR-0007 (docs-only prebuild).
Operator action
Draft for review. After merge: paste
prompts/codex-iskra-phase-1-0-bundle.mdto fresh codex session to begin Slice (a) recon.Refs #236 (related: #235 mail consumer aligns reply approval with HUMAN-DECISION-POLICY; #135 OpenClaw scheduler obs PR #325 same sacred surface; #76 Agent Access Plane v0.1 ACL composition; PR #150 anti-LLM-wrapper precedent)