gm-plugkit 2.0.1848 → 2.0.1849

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.
@@ -43,7 +43,7 @@ Use **especially** for:
43
43
  - Research questions (turning ideas into research kernels)
44
44
  - Engineering failures (root cause analysis, repair paths)
45
45
  - Product/positioning work (audience, launch strategy)
46
- - High-strangeness problems (mixing themes into research)
46
+ - Mixed-theme problems (combining unrelated ideas into research)
47
47
 
48
48
  ## How to Use
49
49
 
@@ -53,16 +53,6 @@ Use **especially** for:
53
53
  shoot + [your problem]
54
54
  ```
55
55
 
56
- Examples:
57
-
58
- ```
59
- shoot + Seven Millennium Problems
60
- shoot + should I quit my job
61
- shoot + Death + AI
62
- shoot + P vs NP
63
- shoot + How to fix my broken deployment pipeline
64
- ```
65
-
66
56
  ### The Engine Returns
67
57
 
68
58
  A structured route containing:
@@ -113,51 +103,25 @@ You get:
113
103
 
114
104
  Use the engine for *depth*, WFGY-Method for *direction*.
115
105
 
116
- ## Modes and Use Cases
106
+ ## Modes
117
107
 
118
- ### Seven Millennium Problems
108
+ ### Theorem and Formal Work
119
109
 
120
- Shoot the flagship: all seven famous unsolved mathematics problems simultaneously using the same underlying engine logic.
121
-
122
- ```
123
- shoot + Seven Millennium Problems
124
- ```
110
+ Shoot a theorem or formal problem; the engine returns a proof-route structure that can be checked against a formal verification standard.
125
111
 
126
- See `references/seven-millennium-problems.md` for the flagship claim and what it does and does not assert.
112
+ ### Mixing Themes
127
113
 
128
- ### Baseline-50 + Frontier-50
129
-
130
- - **Baseline-50**: Known-truth math problems (check engine accuracy)
131
- - **Frontier-50**: Unknown century-level problems (explore frontier)
132
-
133
- ### High-Strangeness Math Lab
134
-
135
- Mix two unrelated themes and let the engine find the mathematical skeleton:
114
+ Give the engine two unrelated themes and let it find the mathematical skeleton underneath them:
136
115
 
137
116
  ```
138
117
  shoot + [theme 1] + [theme 2]
139
118
  ```
140
119
 
141
- Examples:
142
- - Death + AI -> digital exit operators, hell-state boundaries
143
- - Dream + Physics -> dream-observer collapse, reality drift
144
- - Love + Source Poisoning -> attachment trust graph, false-closure lemmas
120
+ See `references/research-kernel-extraction.md` for how mixed themes become research kernels.
145
121
 
146
- See `references/research-kernel-extraction.md` for how strange themes become research kernels.
122
+ ### Everyday Problems
147
123
 
148
- ### Everyday Shoot Modes
149
-
150
- The same engine works on everyday problems:
151
-
152
- | Mode | Use For |
153
- |---|---|
154
- | Life Decision Shoot | Quitting, moving, major choices |
155
- | Relationship Shoot | Conversations, behavior, hidden tension |
156
- | Work / Career Shoot | Bottlenecks, career drift, stuck loops |
157
- | Product / Startup Shoot | Positioning, audience, launch route |
158
- | Research / Learning Shoot | Turning ideas into research kernels |
159
- | Engineering / Debugging Shoot | Root cause, system debt, repair paths |
160
- | Meme / Absurd Shoot | Small, weird, funny targets made structured |
124
+ The same engine works on ordinary decisions, work problems, product questions, and engineering failures — any well-specified target benefits from being shot into a route rather than answered directly.
161
125
 
162
126
  ## Verification
163
127
 
@@ -178,7 +142,6 @@ This skill does not:
178
142
 
179
143
  See `references/` directory for:
180
144
  - `route-structure.md` — what a route is and how it is structured
181
- - `seven-millennium-problems.md` — the flagship demonstration
182
145
  - `research-kernel-extraction.md` — turning ideas into research kernels
183
146
  - `route-inspection-guide.md` — how to verify and attack a route
184
147
  - `skills/polaris-protocol/SKILL.md` — the Polaris Protocol tree root and state machine
@@ -63,7 +63,7 @@ CLOSED --next atom------------------------------------> COMPILED
63
63
  ## Canonical syntax (pro-rata — use exactly this)
64
64
 
65
65
  - **Compile first. Execute one active atom. Verify before unlock. Claim only what is supported.** (Goal Compiler)
66
- - **shoot + [your problem]** — the Fifth-Dimension Engine interface. Examples: `shoot + Seven Millennium Problems`, `shoot + Death + AI`, `shoot + should I quit my job`.
66
+ - **shoot + [your problem]** — the Fifth-Dimension Engine interface.
67
67
  - **ΔS = 1 − cos(I, G)** — drift between current state (I) and goal (G). Without a real embedding call, ΔS is a qualitative label ("ΔS looks high here"), never a computed decimal — unless a real `similarity` verb is available (see WFGY-Method).
68
68
 
69
69
  "Compile first. Then shoot." is the spine of the whole protocol.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "gm-plugkit",
3
- "version": "2.0.1848",
3
+ "version": "2.0.1849",
4
4
  "description": "Bootstrap and daemon-spawn tool for gm plugkit binary. Downloads the correct platform binary, verifies SHA256, and starts the spool watcher daemon. Includes plugkit-wasm-wrapper for WASM-based spool watching.",
5
5
  "main": "index.js",
6
6
  "bin": {