loom/loom-cli
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
4e7aa1ff1ff590037280e74b7a76ddbcabf99e25
loom-cli/.loom/orientation.md
T
jeffryandClaude Opus 5 da6e8b9b51 loomctl orient: one table of contents, restating no rule 
Generates .loom/orientation.md — what this repository depends on, where each copy
came from, and which facets sit beside it — for whoever arrives next, of any make.

One file rather than two, decided by loom's own rule. Generate what varies, adopt
what does not: the publishing half varies not at all and is already adopted, so
publication.md appears in the index like any other adopted document, in exactly the
repositories that adopted it. A second command would emit a file whose whole content
is a pointer to a file already in the tree, and would revive a noun declined when
published check went.

Restates no rule. The three moves are phrased as operations — what to run, what to
write, where — and every rule stays in the document that owns it. The .usages.md is
pointed at rather than summarised, because what depends on a document is free prose
and anything extracting a claim from prose eventually extracts it wrong. It says
nothing recorded when a document has no usages file, which is a finding rather than
an omission and is currently true of six of nine.

Byte-deterministic, pinned by a test that inserts records out of order and
generates three times. Written to .loom/orientation.md rather than inside
.loom/externals/, where check would report it as an unlocked external in every
repository using the feature.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018UTxuSizozEA8yDitPuris
2026-09-08 09:11:04 -04:00

3.2 KiB
Raw Blame History

What this repository depends on

Copies of other people's documents are kept under .loom/externals/, at a path that says where each came from. They are copies: do not edit them. Anything you want to say about one goes in a file beside it, never into it.

Three moves, and each has a document that owns the rule:

  • A copy is wrong, or you needed something it does not say — write it in <name>.gaps.md beside the copy.
  • What of ours depends on a copy — write it in <name>.usages.md beside it.
  • A source changed — loomctl external check says so and stages the new copy; loomctl external apply takes it. Neither edits anything on its own.

git.hypertheory-labs.dev/jeffry/homelab-cluster/gitea.md

git.hypertheory-labs.dev/loom/annotating/annotating.md

git.hypertheory-labs.dev/loom/bedrock/loom-directory.md

git.hypertheory-labs.dev/loom/bedrock/publication.md

git.hypertheory-labs.dev/loom/bedrock/recording-decisions.md

git.hypertheory-labs.dev/loom/bedrock/sibling-facets.md

git.hypertheory-labs.dev/loom/bedrock/starting.md

git.hypertheory-labs.dev/loom/cart/cart.md

git.hypertheory-labs.dev/loom/externals/externals.md

Reference in New Issue View Git Blame Copy Permalink