custom
code
sovereign-compute
File size: 10,137 Bytes
ef6eb55
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
# PAX-Coder Pricing & Provisioning

**Last Updated:** 2026-08-18  
**All prices in USD**

---

## Overview

PAX-Coder is a commercial product. Production authorization requires contact, approval, and a commercial agreement.

**All production access requires approval and commercial terms.** Contact for access request at [CONTACT.md](CONTACT.md).

---

## Tiers

### 1. Individual / Node Key β€” Production Authorization Credential

**$250–$500 per node key (one-time)**

**Audience:** Independent developers and small labs

**What this tier grants:**

A provisioned Sovereign Node Key that authorizes your workstation for production operations.

- βœ… One production-authorized node (one workstation)
- βœ… Ed25519 cryptographic identity + operator-signed authorization
- βœ… Authority to sign official releases
- βœ… Authority to deploy production kernels
- βœ… Local production execution rights
- βœ… Provisioning is permanent (non-revocable unless terms violated)

**What this tier does NOT include:**
- ❌ Commercial licensing (BSL-1.1 applies; separate commercial agreement required)
- ❌ Commercial redistribution rights
- ❌ Enterprise support SLA
- ❌ Multiple nodes (additional nodes: purchase additional keys at same price)
- ❌ Custom Lean 4 proof development
- ❌ Legal claims or warranties

**Important distinction:**
- **Payment** enables provisioning review
- **Approval** grants the right to provision
- **Provisioning** creates the Sovereign Node Key
- **Authorization** is operator-signed (cannot be self-created)
- **Protected operations** require valid authorization

**Provisioning Flow:**
1. Submit provisioning request (CONTACT.md form)
2. PAX-Coder reviews request (1–3 business days)
3. Request approved or denied
4. Payment processing (if approved)
5. Node credential generated (node.json, node_pk.pem, .node_sk)
6. Operator-signs authorization record (authorization.json)
7. Node activated (authorization status = ACTIVE)

---

### 2. Commercial Team β€” Production Authorization + Commercial Licensing

**$12,000–$25,000 per year**

**Audience:** AI startups, HFT shops, cloud GPU laboratories

**What this tier grants:**

Unlimited production-authorized nodes within your organization, plus commercial licensing rights.

- βœ… Unlimited internal Sovereign Node keys (all provisioned and operator-authorized)
- βœ… Full commercial licensing
- βœ… Hardware target support (sm_86, sm_90)
- βœ… Multiple provisioned nodes
- βœ… Team deployment rights
- βœ… Release signing capability
- βœ… Priority email support
- βœ… Annual renewal

**What's NOT included:**
- ❌ Custom Lean 4 proof development
- ❌ Formal kernel audits
- ❌ SLA-backed support
- ❌ White-label embedding

**Process:**
1. Submit provisioning request
2. Commercial review
3. Agreement negotiation
4. Payment processing
5. Team provisioning setup

---

### 3. Enterprise Verification

**$50,000–$150,000+ per year**

**Audience:** Mission-critical, defense, and FinTech deployments

**What's included:**
- βœ… Unlimited Sovereign Node keys
- βœ… Custom Lean 4 proof modeling for your kernels
- βœ… Formal kernel audits and sign-off
- βœ… Direct SLA (response time guarantees)
- βœ… White-label embedding rights
- βœ… Enterprise commercial licensing
- βœ… Custom hardware target support
- βœ… Direct technical contact
- βœ… Annual renewal

**Custom packages available:**
- Multi-year contracts
- Exclusive deployments
- Custom feature development
- Governance involvement

**Process:**
1. Executive engagement
2. Detailed requirements gathering
3. Custom quote
4. Legal/procurement
5. Deployment and provisioning

---

### 4. Proof Audit & Sign-Off

**$10,000+ per custom kernel**

**What's included:**
- βœ… Formal verification of custom CUDA kernel
- βœ… Lean 4 proof verification outside standard axiom basis (PO_1–PO_8)
- βœ… Cryptographic sign-off with Sovereign Node key
- βœ… Detailed audit report
- βœ… Proof artifact

**Process:**
1. Submit kernel and specifications
2. Audit engagement
3. Verification and proof development
4. Sign-off and delivery

---

## Provisioning & Node Credentials

### What is a Sovereign Node?

A Sovereign Node is:
- βœ… A cryptographic identity (Ed25519 public/private keypair)
- βœ… A provisioned authorization record
- βœ… Eligible for signed authorization capabilities
- βœ… Bound to commercial agreement terms

A Sovereign Node is NOT:
- ❌ Something generated locally by running a script
- ❌ Something from cloning the repository
- ❌ A self-signed or self-authorized credential
- ❌ Automatically available to anyone

### Node Provisioning States

```

UNPROVISIONED

    (no request)

         ↓

REQUESTED

    (user submitted request)

         ↓

REVIEWING

    (PAX-Coder authority review)

         ↓

  APPROVED ← or ← REJECTED

         ↓

PROVISIONING

    (credential issuance)

         ↓

ACTIVE

    (node is authorized)

         ↓

REVOKED (if terms violated)

```

### How to Get a Node

**Step 1: Select Tier**

Choose the appropriate plan above (Individual, Commercial Team, or Enterprise).

**Step 2: Request Provisioning**

Fill out the provisioning form at:

```

https://snapkittywest.com/pax-coder/request

```

or email:

```

jessica@collectivekitty.com

```

Include:
- Your name / organization
- Intended use case
- Requested tier
- Deployment requirements
- Contact email

**Step 3: Review & Approval**

- Individual tier: 1–3 business day review
- Commercial/Enterprise: Formal review process

**Step 4: Commercial Agreement & Payment**

- Individual: Secure payment link (one-time)
- Commercial/Enterprise: Formal commercial agreement

**Step 5: Provisioning**

- Node credential created
- Authentication material provided
- Activation in your environment

**Step 6: Active Node**

Use your provisioned credential for:
- Signing releases
- Protected kernel operations
- Production deployment

---

## FAQ

### Q: Can I access the repository?

**A:** Repository access is free for verification/testing. Production authorization requires contact, approval, and the applicable commercial tier. See [CONTACT.md](CONTACT.md).

### Q: Do I get a Sovereign Node automatically?

**A:** No. Approval is required for access. To perform protected operations (signing releases, production deployment), you need a provisioned node through the appropriate tier after approval and payment.

### Q: How much does a Sovereign Node cost?

**A:** It depends on your usage:
- **Individual:** $250–$500 (one-time, one workstation)
- **Commercial Team:** Included with $12,000–$25,000/year plan
- **Enterprise:** Included with $50,000–$150,000+/year plan

### Q: Can I generate a node key locally?

**A:** You can generate a local cryptographic keypair, which creates a node IDENTITY. However, this is NOT a provisioned node. It is UNREGISTERED and UNAUTHORIZED for production use. Only provisioned nodes (obtained through purchase/provisioning) are authorized for protected operations.

### Q: What's the difference between node IDENTITY and node AUTHORIZATION?

**A:** 
- **Identity:** A cryptographic public key + metadata. Anyone can generate one locally. Not sufficient for authorization.
- **Authorization:** A provisioned credential from PAX-Coder authority, issued only after provisioning. Required for protected operations.

### Q: Can I use an Individual node on multiple machines?

**A:** The Individual tier includes one provisioned node for one workstation. Additional machines require additional node keys (additional $250–$500 each). Commercial Team and Enterprise tiers support multiple nodes.

### Q: What happens if I don't renew my subscription?

**A:** 
- **Individual:** One-time purchase; no renewal required. Your node remains active indefinitely (unless revoked for terms violation).
- **Commercial/Enterprise:** Upon renewal deadline, the subscription ends. Existing nodes become inactive; new authorization capabilities are not issued. Contact for reactivation.

### Q: Can I transfer my node to another person/organization?

**A:** No. Nodes are provisioned to the named organization/individual. Transfer requires a new provisioning request and agreement.

### Q: What if I violate the commercial terms?

**A:** Terms violations may result in:
- Provisioning revocation
- Capability expiration
- Node deactivation
- Legal action (depending on violation severity)

Contact support if you believe a violation has occurred.

### Q: How do I request an Enterprise contract?

**A:** Email:

```

jessica@collectivekitty.com

```

Include:
- Organization name
- Executive/technical contact
- Deployment requirements
- Estimated kernel volume
- Custom requirements

Enterprise team will respond within 2 business days.

---

## Commercial Licensing

PAX-Coder is dual-licensed:

- **BSL-1.1:** For commercial usage under provisioning agreement
- **AGPL-3.0:** For source code review and non-commercial use

Provisioning establishes the commercial usage rights appropriate to your tier.

See [LICENSE.md](LICENSE.md) for full details.

---

## Support

### Individual Tier

- Email support: individual-jessica@collectivekitty.com
- Response time: 2–5 business days
- Included: Technical questions about provisioning and kernel generation

### Commercial/Enterprise Tier

- Dedicated Slack channel
- Priority email support
- Phone support (Enterprise only)
- Response time: 1 business day (Commercial), 4 hours (Enterprise)

---

## Contact

**General inquiries:**
```

jessica@collectivekitty.com

```

**Provisioning requests:**
```

https://snapkittywest.com/pax-coder/request

```

**Enterprise:**
```

jessica@collectivekitty.com

```

**Support issues:**
```

jessica@collectivekitty.com

```

---

**PAX-Coder is developed by SnapKitty.**  
**Β© 2026 SnapKitty. All rights reserved.**