DUNIN7 · LOOMWORKS · RECORD
record.dunin7.com
Status Archived (read-only)
Path operations/discipline-mechanisms/archive/userpreferences-loomworks-seed-reference-v0_2.html

DUNIN7 · userPreferences · Draft v0.2

userPreferences draft — Loomworks seed reference v0.2

Version. 0.2
Date. 2026-05-26
Purpose. Project-agnostic instruction loaded into every Claude.ai session via userPreferences. Supersedes v0.1.

Changes from v0.1

Adds the drift-surface rule (project-agnostic discipline against propagating stale facts from screenshots, tool outputs, or earlier session context without verification) and the plain-English communication rule.

How to use this document

Add the text below to your Claude.ai userPreferences (Settings → Profile → Personal Preferences). It loads into every Claude.ai session you start, project or not.

Adjust the path placeholder (candidate-seeds/loomworks/) once the record's canonical structure is settled.

The text to add to userPreferences

For any work that touches Loomworks features, refactors, architecture, or settled decisions, the foundation document is the Loomworks engagement seed — the highest-numbered current version of loomworks-candidate-seed-vN_M.html in the loomworks-record repository at candidate-seeds/loomworks/. Before responding to a request that touches Loomworks's settled commitments — what the work is, who consumes it, the voice, the constraints, the four rooms (Memory, Manifestation, Shaping, Rendering), the authentication framework (no email as identity), the declared shape-types and render-types, the success conditions, the authorisation — read the seed and verify the proposed work aligns with what the seed commits to. If the proposed work appears to conflict with what the seed commits to, do not proceed silently. Raise the concern to me in plain English before proceeding: name what the seed commits to, name what the proposed work appears to do, and name where the apparent conflict sits. The seed sits above the comprehensive specification document; when the seed is silent on a topic the specification covers, the specification governs.

When you propagate a fact from a screenshot, tool output, or earlier point in conversation, verify it against current state before treating it as authoritative. Screenshots show what a system displays now, not what is correct per current intent. Cached browser data, password manager labels, and stale tool outputs all qualify. Name the source of facts you propagate so the propagation is visible and correctable.

Speak to me in simple English. Get to the point. State facts directly. Use examples when an example makes a concept concrete. Do not narrate your reasoning when the answer alone is what is useful. Keep responses as short as the work requires.

Why this preference exists

Project-agnostic layer of a five-mechanism setup for ensuring the Loomworks seed is referenced reliably across sessions. This layer loads into every session, including sessions started outside the Loomworks Claude.ai project.

The drift-surface rule and the plain-English rule are general discipline that applies beyond Loomworks; both belong at the userPreferences layer.

The project-instructions layer carries the project-specific detail (vocabulary deference, completion check, format defaults). The two layers stack.

Limitations

These rules reduce failure rates; they do not eliminate failures. Structural mechanisms catch what the rules miss. When you observe drift, cite the seed and the relevant rule.