@ai-content-space/loopx 0.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,31 @@
1
+ ---
2
+ schema_version: 1
3
+ workflow_id: <workflow id>
4
+ stage: plan
5
+ decision_id: loopx-v1
6
+ chosen_option: skill-first-runtime-substrate
7
+ ---
8
+
9
+ # LoopX Architecture: <task name>
10
+
11
+ ## Intent
12
+
13
+ - keep LoopX skill-first while reusing the deterministic runtime/debug substrate
14
+
15
+ ## Boundaries
16
+
17
+ - skills are the primary user surface
18
+ - CLI remains runtime/debug support
19
+ - approvals remain explicit
20
+ - review stays independent from build
21
+
22
+ ## Chosen Design
23
+
24
+ - canonical LoopX artifacts under `.LoopX/`
25
+ - single build lane, no public `team`
26
+ - bounded `autopilot` composition over clarify/plan/build/review
27
+
28
+ ## Alternatives Considered
29
+
30
+ - thin skill wrappers over a CLI-first product
31
+ - plugin-first rebuild
@@ -0,0 +1,27 @@
1
+ ---
2
+ schema_version: 1
3
+ workflow_id: <workflow id>
4
+ stage: plan
5
+ execution_mode_readiness: build
6
+ stage_owner: plan
7
+ ---
8
+
9
+ # LoopX Development Plan: <task name>
10
+
11
+ ## Execution Breakdown
12
+
13
+ 1. prepare clarify spec
14
+ 2. generate plan package
15
+ 3. run build with verification
16
+ 4. run review
17
+
18
+ ## Staffing Guidance
19
+
20
+ - owner: build
21
+ - verifier: review
22
+ - runtime helpers: CLI support only
23
+
24
+ ## Sequencing
25
+
26
+ - do not skip approvals
27
+ - do not bypass review
@@ -0,0 +1,35 @@
1
+ ---
2
+ schema_version: 1
3
+ workflow_id: <workflow id>
4
+ run_id: <run id>
5
+ stage: <stage>
6
+ actor_id: <actor id>
7
+ actor_role: <actor role>
8
+ plan_digest: <plan digest>
9
+ started_at: <started at>
10
+ completed_at: <completed at>
11
+ checkpoint_count: <checkpoint count>
12
+ evidence_manifest: [{"id":"<evidence id>","kind":"artifact","summary":"<summary>","ref":"<ref>"}]
13
+ ---
14
+
15
+ # LoopX Execution Record: <task name>
16
+
17
+ ## Changes
18
+
19
+ - TODO: summarize the implementation result.
20
+
21
+ ## Checkpoint Log
22
+
23
+ - TODO: record execution checkpoints.
24
+
25
+ ## Execution Evidence
26
+
27
+ - TODO: add concrete execution evidence.
28
+
29
+ ## Verification Evidence
30
+
31
+ - TODO: add concrete verification evidence.
32
+
33
+ ## Limitations
34
+
35
+ - TODO: record remaining limitations.
@@ -0,0 +1,34 @@
1
+ ---
2
+ schema_version: 1
3
+ workflow_id: <workflow id>
4
+ stage: plan
5
+ source_spec_path: spec.md
6
+ stage_owner: plan
7
+ ---
8
+
9
+ # LoopX Plan: <task name>
10
+
11
+ ## Requirements Summary
12
+
13
+ - translate the approved LoopX spec into an execution-ready package
14
+
15
+ ## Deliverables
16
+
17
+ 1. produce the LoopX plan package
18
+ 2. keep approvals explicit
19
+ 3. define verification that can prove the run is ready for build
20
+
21
+ ## Implementation Steps
22
+
23
+ 1. update runtime and artifacts as needed
24
+ 2. keep the loop bounded and deterministic
25
+ 3. verify outputs before review
26
+
27
+ ## Risks
28
+
29
+ - skipping approval or verification would break the LoopX contract
30
+
31
+ ## Verification
32
+
33
+ - run contract tests
34
+ - run CLI checks
@@ -0,0 +1,31 @@
1
+ ---
2
+ schema_version: 1
3
+ workflow_id: <workflow id>
4
+ review_id: <review id>
5
+ reviewer_id: <reviewer id>
6
+ reviewed_run_id: <reviewed run id>
7
+ input_manifest: ["spec.md","plan.md","architecture.md","development-plan.md","test-plan.md","execution-record.md"]
8
+ evidence_manifest: [{"id":"<evidence id>","kind":"artifact","summary":"<summary>","ref":"<ref>"}]
9
+ verdict: <verdict>
10
+ rollback_target: <rollback target>
11
+ rollback_rationale: <rollback rationale>
12
+ ---
13
+
14
+ # LoopX Review Report: <task name>
15
+
16
+ ## Verdict
17
+
18
+ - <verdict>
19
+
20
+ ## Evidence Reviewed
21
+
22
+ - TODO: list reviewed evidence.
23
+
24
+ ## Findings
25
+
26
+ - TODO: list findings.
27
+
28
+ ## Rollback Recommendation
29
+
30
+ - <rollback target>
31
+ - <rollback rationale>
@@ -0,0 +1,33 @@
1
+ ---
2
+ schema_version: 1
3
+ workflow_id: <workflow id>
4
+ stage: clarify
5
+ approval_status: requested
6
+ unresolved_ambiguity_count: 1
7
+ ---
8
+
9
+ # LoopX Spec: <task name>
10
+
11
+ ## Ambiguity List
12
+
13
+ - A-1 | open | Clarify the concrete task, acceptance criteria, and constraints.
14
+
15
+ ## Clarified Answers
16
+
17
+ - TODO: record the accepted clarification answers.
18
+
19
+ ## In Scope
20
+
21
+ - TODO: record the work that belongs in this LoopX run.
22
+
23
+ ## Non-Goals
24
+
25
+ - TODO: record what must stay out of scope.
26
+
27
+ ## Decision Boundaries
28
+
29
+ - Human approval is required before `clarify -> plan`.
30
+
31
+ ## Success Criteria
32
+
33
+ - TODO: record what makes the run plan-ready.
@@ -0,0 +1,23 @@
1
+ ---
2
+ schema_version: 1
3
+ workflow_id: <workflow id>
4
+ stage: plan
5
+ verification_checklist_status: drafted
6
+ ---
7
+
8
+ # LoopX Test Plan: <task name>
9
+
10
+ ## Unit
11
+
12
+ - state transitions
13
+ - artifact generation
14
+ - approval handling
15
+
16
+ ## Integration
17
+
18
+ - clarify -> plan -> build -> review
19
+ - autopilot happy path
20
+
21
+ ## Observability
22
+
23
+ - status must expose stage, blockers, and next action