Skip to main content

Posts

Power User's Guide to Large Language Models

Power User's Guide to Large Language Models Analysis · Methodology · Cognitive Systems Power User's Guide to Large Language Models Beyond Prompt Engineering, Automation, and One-Shot Outputs This guide describes how to use large language models as reasoning environments, cognitive instruments, and components inside a long-term knowledge system. It is not about prompt tricks or generic productivity advice. Core Principle Prompts control outputs. Systems control thinking. Power users design workflows, not isolated prompts. § 01 Two Fundamental Modes of Work Almost all misuse comes from confusing these modes. Exploration Mode (High Entropy) The goal is to discover structure not yet fully articulated. Ideas are rough, ambiguity is allowed, contradictions are tolerated, and editorial friction is kept as low as possible. Input methods that work well: voice dictation, stream-of-consciousness...
Recent posts

Field Manual: Psychedelic Safety (The Savannah Protocol)

The Savannah Protocol · Red‑Flag Framework (corrected footnotes) THE SAVANNAH PROTOCOL Absolute Red‑Flag Framework for Psychedelic Safety ⛔ ABSOLUTE RED FLAG — NON‑NEGOTIABLE — ABORT IMMEDIATELY (NON‑CLINICAL CONTEXT) If anyone agrees to sit for you while you are in an active major crisis, ABORT. No exceptions (outside a licensed, medically supervised program designed for acute care). This rule overrides: trust · reputation · warmth · experience · spiritual framing · your own desire for relief. A psychedelic session increases psychological permeability. A crisis already means reduced stability. Combining the two creates unbounded risk—especially without clinical screening, monitoring, and emergency capacity. Contemporary clinical protocols rely heavily on screening, preparation, monitoring, and exclusion criteria to reduce predictable harms. [1] ...

Field Manual: How to Backup Global Civilization

Fieldmanual: Dual-Core Civilizational Backup Architecture Fieldmanual: Dual-Core Civilizational Backup Architecture Public Reconstruction Substrate + Separate Machine Training Substrate. Offline-first Privacy Absolute Strict Infrastructure Separation TL;DR CC: Public, human-readable, ~2–4 TB. LTC: Separate, machine-optimized, capped at ~10 TB (v0.5). Rule 0: Never share distribution infrastructure. Rule 1: Ship CC first. Team: ~10 people, ~12 months, frozen scope. Final Directives Ship Civilizational Core first. Enforce absolute privacy filtering in both layers. Maintain strict infrastructure separation between CC and LTC. Freeze scope for Version 1.0. Mission Build a decentralized, verifiable knowledge substrate capable of surviving institutional failure or systemic disruption. Architectural Overview Property...

How to Make Citizens Safer and Reduce Drug-War Harm Without Changing Any Laws

Trust infrastructure as public safety infrastructure Debates about drug policy usually focus on laws. Change the statutes. Elect different officials. Argue that criminalization causes harm. Sometimes this works. Often it doesn’t. Because many of the harms associated with the “war on drugs” are not primarily legal. They are structural. They arise from a simpler condition: Illegal markets lack trust infrastructure. And when trust is missing, violence substitutes. If people cannot rely on contracts, courts, or reputation, they rely on intimidation and retaliation. That substitution is mechanical, not cultural. Any market behaves this way under those constraints. If the goal is safer neighborhoods, the first problem to solve is not legislation. It is trust. Why illegal markets are disproportionately violent Legal markets use: contracts arbitration licensing credit history reputation systems Disputes get resolved economically: someone loses access, not bl...

Field Manual: Minimal Federated Trust-Bound Social Infrastructure

Minimal Federated Trust-Bound Social Infrastructure (Ur-Protocol) Complete Specification and Field Manual v0.5 Part I: Specification 0. Scope Ur-Protocol defines a portable identity + small-group coordination substrate. It is not: a platform a company service a monolithic app a global social graph It is: a protocol that allows many independent servers and many independent clients to coordinate small human groups safely and cheaply The protocol guarantees: identity continuity social proof admission/recovery group ordering/consistency server replaceability client replaceability Everything else (UX, features, aesthetics) is out of scope. 0.1 Notational Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. 0.5 Fo...