Stax Digital Garden

TRC-1010 - The Plain-Text GTD Execution Standard

3 min read

Living Document Notice
Published 2026-09-17. The evolving architecture, revisions, and connected notes for this dispatch live in the Stax Digital Garden.

The Plain-Text GTD Execution Standard

The Plain-Text GTD Execution Standard: Dual-trace Phosphor P20 safety amber and P22R ruby red vector CRT macro showing long-horizon decadal stability grids and sovereign plain-text execution format boundaries

Summary

Productivity applications rise and fall, but commitments and achievements span entire careers. Trice formalizes the plain-text execution standard for sovereign task management, guaranteeing decadal durability, zero cloud lock-in, and full intellectual autonomy.

The Perennial Churn of Productivity Tools

Every three to five years, a new venture-backed productivity tool captures market attention, promising effortless task tracking and algorithmic enlightenment. Within half a decade, the tool is either acquired, pivoted to an enterprise CRM, or shuttered, leaving users with fragmented JSON exports and broken workflows.

Trice is built on a radical alternative hypothesis: The software you use to manage your life’s commitments should be readable by a standard text editor fifty years from now.

The Plain-Text Longevity Continuum:
  2000: Org-mode / Todo.txt
         │ (Plain ASCII, Perfectly Readable in 2026)
         ▼
  2026: Trice Markdown + YAML Frontmatter + Rowan CST
         │ (POSIX Compatible, Zero Daemon Footprint)
         ▼
  2076: Future Computing Terminals
           (No Emulators Required; UTF-8 Invariant)

The Four Tenets of Sovereign Execution

Trice is governed by four immutable engineering principles:

1. The File is the Database

The single source of truth is the UTF-8 Markdown file on disk. Any SQLite index or vector cache is strictly ephemeral and completely rebuildable from disk notes in seconds:

# Rebuild all task indices from scratch
bosun index rebuild --realm trice

2. Zero Network Ports

Task management is inherently local. Trice operates with zero HTTP endpoints, zero listening sockets, and zero cloud sync dependencies. Sync is delegated to encrypted transport layers (Git, Syncthing, SSH).

3. Non-Destructive Mutations

Automated tools must never silently reformat user prose, destroy comments, or discard metadata. All edits use Rowan Concrete Syntax Trees that preserve every byte of human trivia.

4. Open-World Graph Interoperability

Tasks do not exist in isolation. They bind to human beings in Yeoman, architectural decisions in Logbook, and code manifests in Quartermaster using standard URN graph relations.

Architectural Roadmap for Realm 03

As Trice matures within the Bosun PKM ecosystem, development focuses on three strategic milestones:

PhaseMilestoneObjectiveTarget
Phase 1Core Task EngineMarkdown state gates, CST checkbox splicing, stdio RPCActive
Phase 2DAG Dependency EngineTopological sorting, automated unblocking triggersQ4 2026
Phase 3P2P Commitment MeshCross-device CRDT synchronization and delegation2027

The purpose of Trice is not to optimize human beings into automated task-processing engines, but to provide a calm, sovereign sanctuary where commitments are tracked with precision, executed with clarity, and completed with peace of mind.

  • Directus Target: trice
  • Garden Source Reference: MOC - Bosun PKM Tools, MOC - Fleet Operations
  • Garden Source Reference: [TRC-1010 - The Plain-Text GTD Execution Standard](TRC-1010 - The Plain-Text GTD Execution Standard)

Graph View