ChristopherA

Cloudflare & the Gordian Stack

TL;DR: The Gordian Stack is a set of open standards from Blockchain Commons that let people, and the AI agents acting for them, prove who signed, who authorized and what may be seen, without trusting the platform underneath. On Cloudflare that means:

• Durable Objects + Gordian Envelope: store sensitive records that Cloudflare can't read, reveal only the fields each party needs, and prove nothing was rolled back.
• Artifacts + Open Integrity: let agents work in their own forks while only a person's passkey can sign a change to main, verifiable anywhere with stock Git.
• Already running: two live demos on Workers, Durable Objects and Artifacts, linked below.

Cloudflare supplies the scale. The Gordian Stack keeps the trust with the people who own the data.

ChristopherA

Per-Project Claude Code Profiles

Giving each project its own account, its own standing instructions, and its own memory.

Every tool that scopes configuration per project eventually discovers that its scoping has a seam. Claude Code's seam sits exactly where you would not look for it: in the mechanisms you leave alone rather than the one you configure.

I run several Claude Code projects that have no business sharing a login, a set of standing instructions, or a session history. Claude Code supports this through the CLAUDE_CONFIG_DIR environment variable, and it does what it says. What surprised me is that turning it on exposes two further mechanisms that stayed invisible for as long as everything lived in one place. An Ancestor Walk quietly hands your global instructions back to the project you just isolated. Account Sync refills that project with the skills and connectors attached to your account. Three Surfaces, near the end, takes both apart; the steps below only close them.

Both are clo

ChristopherA

A Redactable Append-Only Log

A design for an append-only event log whose entries can be redacted, and disclosed to different readers at different depths, without breaking verification. It is described so that it can be implemented in any language on any platform.

The design rests on four practices: the log is a truth separate from the application's live state rather than the source that state is rebuilt from, redaction preserves the chain instead of breaking it, one committed entry serves every audience at a different depth, and the format's version moves when meaning moves rather than when fields are added.

1. Scope

This is a design for logs of one shape rather than for logs in general, and the shape is what decides whether it applies. Entries are events attributed to a principal. They accumulate in order and are not edited afterwards. Some of them carry content that only a subset of readers may see. Some of that content has eventually to be destroyed, on request or on a schedule, while the fact tha

ChristopherA

Passkey Identity with Delegated Agents

An architecture for passkey authentication in systems where software agents act on behalf of people. It is described so that it can be implemented in any language on any platform.

The architecture rests on four practices: a person holds many credentials rather than one, authentication is separated from authorization, authority originates with the natural person and agents derive it, and agents can be delegated credentials without holding a key.

Scope

This document specifies the architecture around WebAuthn ceremonies. It assumes a conforming WebAuthn relying party underneath it and does not restate that specification. Origin and relying-party-identifier validation, user-presence and user-verification flags, algorithm acceptance, and attestation policy are defined by the W3C Web Authentication specification. Where a requirement here reaches into ceremony territory, notably challenge handling, it does so because the surrounding architecture depends on that detail.

ChristopherA

An Image-Persistent Substrate for Agentic AI -- Concept Brief

Draft, 2026-05-01.

Christopher Allen <ChristopherA@LifeWithAlacrity.com

---

The pain everyone in the room knows

ChristopherA

created	2026-04-12
did	did:repo:53936a6c815841cab48caa0ac46e37364a197e86
github	https://gist.github.com/ChristopherA/151aefa6a6bde1ce4fa6b1182656cebe
purpose	Agent reference for wikilinks and named edges in plain-markdown knowledge graphs
copyright	©2026 by @ChristopherA, licensed under CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)
summary	How wikilinks and named edge predicates work in a plain-markdown knowledge graph. Covers syntax, YAML vs body predicates, node types (atomic and compound), annotated predicates, vocabulary curation (folksonomy vs ontology), classification predicates (conforms_to:: over is_a::) and predicate conflation, naming sovereignty across collaborating systems, and agent traversal patterns.

• conforms_to::[[Reference Guide Contract]]

ChristopherA

• did: did:repo:423c9aee3c2cfd0d48ccacf645d3432b9b6bf2b2/blob/main/README.md
• github: https://gist.github.com/ChristopherA/e2d59c62e3e50abe2595d74c0fd6f782
• updated: 2026-03-20 by Christopher Allen <ChristopherA@LifeWithAlacrity.com>

Open Integrity Inception Commit — Gist Proof of Concept

This gist demonstrates that a GitHub Gist can carry a valid Open Integrity inception commit and that a script within the gist can verify its own provenance.

The Problem with curl | sh

ChristopherA

Self-Improving Claude Code: A Bootstrap Seed

The Hypothesis

A single prompt (~1400 tokens), placed in a project's .claude/CLAUDE.md, can bootstrap a Claude Code instance into a self-improving system — one that captures learnings, extracts patterns, evolves its own configuration, and gets meaningfully better at helping its user with each session.

No pre-built infrastructure required. No user-level config. No hooks, skills, templates, or elaborate folder hierarchies. Just a seed and the affordances Claude Code already provides.

Background

ChristopherA

Alpine Linux on UTM: Automation Guide

A comprehensive guide to automating Alpine Linux VMs on UTM for rapid deploy-test-destroy workflows.

---

Document Information

Abstract: This guide documents Alpine-specific discoveries and workflows for UTM automation, focusing on P2P protocol testing, rapid iteration, and minimal resource overhead.

ChristopherA

Automating UTM VMs on macOS

A comprehensive, distribution-agnostic guide to automating VM creation and management with UTM on macOS.

---

Document Information

Abstract: This guide documents hard-won lessons from real-world UTM automation, focusing on the challenges unique to UTM/QEMU on macOS rather than any specific Linux distribution.