thesis: stage v2.0 reserve-asset spine as Workshop candidates (v0.1.0:72)
Incorporates the signal-engine workstream's v2.0 thesis correction: the spine is bitcoin as the apex NON-DEBASABLE RESERVE ASSET (debasement = forcing function, AI = abundance engine), NOT "infrastructure settles on bitcoin" (the settlement/payments claim — Strike's payments thesis died in backtest). thesis_seed.ensure_thesis_v2_candidate stages the v2.0 root/forcing-function, throughline, the verifiable-vs-contrarian decomposition, and the 3 seams (Energy↔Compute, Debasement↔Bitcoin, AI↔Data-Ownership) as CANDIDATE nodes under the core line (idempotent sentinel; provenance + "unratified, exposure unconfirmed" on the section). Nothing canonical (guardrail #4). docs/thesis-handoff.md gets a SUPERSEDED-spine banner pointing to v2.0. NOT done (gated on partner ratification): the live THROUGHLINE/PILLAR_1 constants and architect_agent.py's system prompt ("scarcity as the connecting idea") still encode the old spine — until ratified+updated, Vary/Revise/outreach regenerate the old framing. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
@@ -36,8 +36,9 @@ export const PACKAGE_TITLE = 'Ten31 Database'
|
||||
// * 0.1.0:68 (Outreach Draft Assistant — tailored LP drafts via thesis + redaction boundary)
|
||||
// * 0.1.0:69 (follow-up radar — deterministic "needs attention" list + one-click draft)
|
||||
// * 0.1.0:70 (outreach voice upgrade — per-user voice from own emails + transparency; active-thread context)
|
||||
// * Current: 0.1.0:71 (voice by-purpose larger sample + Tier-B: create Gmail draft w/ in-thread reply)
|
||||
export const PACKAGE_VERSION = '0.1.0:71'
|
||||
// * 0.1.0:71 (voice by-purpose larger sample + Tier-B: create Gmail draft w/ in-thread reply)
|
||||
// * Current: 0.1.0:72 (stage v2.0 reserve-asset thesis spine as Workshop candidates)
|
||||
export const PACKAGE_VERSION = '0.1.0:72'
|
||||
|
||||
export const DATA_MOUNT_PATH = '/data'
|
||||
export const WEB_PORT = 8080
|
||||
|
||||
Reference in New Issue
Block a user