create-egregore 0.19.26 → 0.19.27

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.
@@ -1,5 +1,5 @@
1
1
  #!/usr/bin/env node
2
- // egregore-launcher-version: 0.19.26
2
+ // egregore-launcher-version: 0.19.27
3
3
  //
4
4
  // egregore — launch and browse Egregore instances from your terminal.
5
5
  // Installed by create-egregore. Reads ~/.egregore/instances.json.
@@ -33,7 +33,7 @@ const crypto = require("node:crypto");
33
33
  const { spawnSync, spawn } = require("node:child_process");
34
34
  const readline = require("node:readline");
35
35
 
36
- const VERSION = "0.19.26";
36
+ const VERSION = "0.19.27";
37
37
  const REGISTRY = path.join(os.homedir(), ".egregore", "instances.json");
38
38
  const DEFAULT_FILE = path.join(os.homedir(), ".egregore", "default");
39
39
  const UPDATE_CACHE_FILE = path.join(os.homedir(), ".egregore", "update-check.json");
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "create-egregore",
3
- "version": "0.19.26",
3
+ "version": "0.19.27",
4
4
  "description": "Set up Egregore for your team in one command — installs the egregore launcher and your choice of Claude Code, Codex, or Pi.",
5
5
  "license": "MIT",
6
6
  "bin": {
@@ -0,0 +1,84 @@
1
+ ---
2
+ name: the-spiral
3
+ description: Run a Codex-native structured Socratic dialogue when the user invokes /the-spiral or $the-spiral to turn an intuition into rigorous, communicable output.
4
+ ---
5
+
6
+ # The Spiral
7
+
8
+ Native Codex Egregore skill. The Spiral is a stateful Socratic process for
9
+ developing, pressure-testing, and compressing a complex thesis.
10
+
11
+ ## Setup
12
+
13
+ Gather three inputs, using structured Codex question tooling when available and
14
+ plain one-at-a-time questions otherwise:
15
+
16
+ 1. Domain: what are we spiraling on?
17
+ 2. Purpose: what should the process produce?
18
+ 3. Known areas: what domains must be covered, if any?
19
+
20
+ Create state files:
21
+
22
+ ```text
23
+ spiral_state.json
24
+ spiral_artifacts/ring1
25
+ spiral_artifacts/ring2
26
+ spiral_artifacts/ring3
27
+ spiral_artifacts/ring4
28
+ spiral_artifacts/ring5
29
+ ```
30
+
31
+ State includes domain, purpose, addressable space, current ring, current loop,
32
+ artifacts, emerged domains, parked threads, descents, and ring history.
33
+
34
+ ## Rings
35
+
36
+ 1. Seed: find the irreducible claim. Artifact:
37
+ `spiral_artifacts/ring1/seed.md`.
38
+ 2. Territory: map implications, tensions, contradictions, and open questions.
39
+ Artifact: `spiral_artifacts/ring2/territory.md`.
40
+ 3. Encounter: ground claims in reality. Research facts when needed and write
41
+ domain artifacts under `spiral_artifacts/ring3/`.
42
+ 4. Crucible: test objections and disconfirming evidence. Artifact:
43
+ `spiral_artifacts/ring4/crucible.md`.
44
+ 5. Compression: produce the final deliverables under
45
+ `spiral_artifacts/ring5/`.
46
+
47
+ Ask one question at a time. After each alignment check, update
48
+ `spiral_state.json`. Render a compact text progress view only at setup,
49
+ alignment checks, ring transitions, descents, resume, and completion.
50
+
51
+ ## TUI Rendering
52
+
53
+ Structured UX parity is required. The Spiral must present state as a structured
54
+ terminal view at phase boundaries, not as loose paragraphs:
55
+
56
+ - Show rings 1-5 with current/completed/parked status.
57
+ - Show current thesis, emerged domains, parked threads, descents, and next
58
+ question or alignment check.
59
+ - Render only at setup, alignment checks, ring transitions, descents, resume,
60
+ and completion.
61
+ - On completion, render a final structured view with rings completed, loop
62
+ count, deliverable paths, emerged domains, and parked threads.
63
+ - Do not render mid-flow while asking a Socratic question.
64
+
65
+ ## Flow Rules
66
+
67
+ - If the user gives a marketing-like answer in Ring 1, push toward the real
68
+ conviction.
69
+ - If an objection breaks an earlier assumption, offer a descent to the right
70
+ ring and record the reason.
71
+ - Research is active only when factual claims need grounding or pressure.
72
+ - Never force a domain that has not emerged from the user's answers.
73
+ - If the user is tired or wants to pause, crystallize the current state and
74
+ stop at an alignment boundary.
75
+
76
+ ## Resume
77
+
78
+ If `spiral_state.json` exists, summarize domain, ring, loop, and current
79
+ artifacts, then ask whether to continue or start fresh.
80
+
81
+ ## Completion
82
+
83
+ The process ends when Ring 5 deliverables satisfy the user. Report artifact
84
+ paths, rings completed, loop count, emerged domains, and any parked threads.
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "source": "egregore-runtime",
3
3
  "policy": "available OSS components selected by capability-distribution.json; Connect is an authenticated additive overlay",
4
- "skillCount": 37,
4
+ "skillCount": 38,
5
5
  "skills": [
6
6
  "activity",
7
7
  "announce",
@@ -34,6 +34,7 @@
34
34
  "sync-repos",
35
35
  "telemetry",
36
36
  "test",
37
+ "the-spiral",
37
38
  "tui-design",
38
39
  "tutorial",
39
40
  "update",
@@ -81,6 +82,7 @@
81
82
  ".codex/skills/sync-repos/SKILL.md",
82
83
  ".codex/skills/telemetry/SKILL.md",
83
84
  ".codex/skills/test/SKILL.md",
85
+ ".codex/skills/the-spiral/SKILL.md",
84
86
  ".codex/skills/tui-design/SKILL.md",
85
87
  ".codex/skills/tutorial/SKILL.md",
86
88
  ".codex/skills/update/SKILL.md",
@@ -0,0 +1,84 @@
1
+ ---
2
+ name: the-spiral
3
+ description: Run a Codex-native structured Socratic dialogue when the user invokes /the-spiral or $the-spiral to turn an intuition into rigorous, communicable output.
4
+ ---
5
+
6
+ # The Spiral
7
+
8
+ Native Codex Egregore skill. The Spiral is a stateful Socratic process for
9
+ developing, pressure-testing, and compressing a complex thesis.
10
+
11
+ ## Setup
12
+
13
+ Gather three inputs, using structured Codex question tooling when available and
14
+ plain one-at-a-time questions otherwise:
15
+
16
+ 1. Domain: what are we spiraling on?
17
+ 2. Purpose: what should the process produce?
18
+ 3. Known areas: what domains must be covered, if any?
19
+
20
+ Create state files:
21
+
22
+ ```text
23
+ spiral_state.json
24
+ spiral_artifacts/ring1
25
+ spiral_artifacts/ring2
26
+ spiral_artifacts/ring3
27
+ spiral_artifacts/ring4
28
+ spiral_artifacts/ring5
29
+ ```
30
+
31
+ State includes domain, purpose, addressable space, current ring, current loop,
32
+ artifacts, emerged domains, parked threads, descents, and ring history.
33
+
34
+ ## Rings
35
+
36
+ 1. Seed: find the irreducible claim. Artifact:
37
+ `spiral_artifacts/ring1/seed.md`.
38
+ 2. Territory: map implications, tensions, contradictions, and open questions.
39
+ Artifact: `spiral_artifacts/ring2/territory.md`.
40
+ 3. Encounter: ground claims in reality. Research facts when needed and write
41
+ domain artifacts under `spiral_artifacts/ring3/`.
42
+ 4. Crucible: test objections and disconfirming evidence. Artifact:
43
+ `spiral_artifacts/ring4/crucible.md`.
44
+ 5. Compression: produce the final deliverables under
45
+ `spiral_artifacts/ring5/`.
46
+
47
+ Ask one question at a time. After each alignment check, update
48
+ `spiral_state.json`. Render a compact text progress view only at setup,
49
+ alignment checks, ring transitions, descents, resume, and completion.
50
+
51
+ ## TUI Rendering
52
+
53
+ Structured UX parity is required. The Spiral must present state as a structured
54
+ terminal view at phase boundaries, not as loose paragraphs:
55
+
56
+ - Show rings 1-5 with current/completed/parked status.
57
+ - Show current thesis, emerged domains, parked threads, descents, and next
58
+ question or alignment check.
59
+ - Render only at setup, alignment checks, ring transitions, descents, resume,
60
+ and completion.
61
+ - On completion, render a final structured view with rings completed, loop
62
+ count, deliverable paths, emerged domains, and parked threads.
63
+ - Do not render mid-flow while asking a Socratic question.
64
+
65
+ ## Flow Rules
66
+
67
+ - If the user gives a marketing-like answer in Ring 1, push toward the real
68
+ conviction.
69
+ - If an objection breaks an earlier assumption, offer a descent to the right
70
+ ring and record the reason.
71
+ - Research is active only when factual claims need grounding or pressure.
72
+ - Never force a domain that has not emerged from the user's answers.
73
+ - If the user is tired or wants to pause, crystallize the current state and
74
+ stop at an alignment boundary.
75
+
76
+ ## Resume
77
+
78
+ If `spiral_state.json` exists, summarize domain, ring, loop, and current
79
+ artifacts, then ask whether to continue or start fresh.
80
+
81
+ ## Completion
82
+
83
+ The process ends when Ring 5 deliverables satisfy the user. Report artifact
84
+ paths, rings completed, loop count, emerged domains, and any parked threads.
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "source": "egregore-pi-meta-harness",
3
3
  "policy": "Pi-native lifecycle layer over the available OSS Codex skill corpus",
4
- "skillCount": 37,
4
+ "skillCount": 38,
5
5
  "skills": [
6
6
  "activity",
7
7
  "announce",
@@ -34,6 +34,7 @@
34
34
  "sync-repos",
35
35
  "telemetry",
36
36
  "test",
37
+ "the-spiral",
37
38
  "tui-design",
38
39
  "tutorial",
39
40
  "update",
@@ -80,6 +81,7 @@
80
81
  ".codex/skills/sync-repos/SKILL.md",
81
82
  ".codex/skills/telemetry/SKILL.md",
82
83
  ".codex/skills/test/SKILL.md",
84
+ ".codex/skills/the-spiral/SKILL.md",
83
85
  ".codex/skills/tui-design/SKILL.md",
84
86
  ".codex/skills/tutorial/SKILL.md",
85
87
  ".codex/skills/update/SKILL.md",