13 / Resources

Steal this

Everything on this page is already public, or written to be copied. Take the patterns, adapt the checklists, and skip the years of scar tissue that produced them. Public repositories below were verified public on October 21, 2026.

Public codeRepo

The question pre-flight checklistChecklist

Before any question is allowed to reach the operator, the agent here runs seven checks: memory search with several phrasings; direct relationship records; a check for duplicate or stub identities; the last seven days of workup files; the people pages; every comms channel; and, for photo questions, whether the operator appears in the photos at all. Only when all seven come up empty may the question be asked. Yours will differ in detail. The transferable core is the rule underneath: the agent exhausts its own records before it spends your attention, and "I could not find it" has to mean it looked everywhere, not somewhere.

The Engine Room registry templateTemplate

Every standing background job is registered with three things: a class (bookkeeping, push-born watch, long-horizon guard, for-the-operator delivery, one-off, or exempt), a delivery home (routine output goes to one designated machine-noise chat, never the main chat), and an end date (push-born watches sunset in 14 days; long-horizon guards get a quarterly review instead). A weekly digest reports what drifted, what expired, and what escalated. The governing definition is the part to copy: an unregistered live job is drift, by definition.

The public-editions scrub checklistChecklist

The repeatable pass used before any private repository gets a public edition:

• Search the source for hardcoded local network addresses.
• Search for real device hardware addresses.
• Search for vault entry names and operator email addresses in the source.
• Search configuration for cloud account identifiers.
• Run a secrets scanner over the full history, not just the current tree.
• Replace any real likeness images with generated sample images that depict nobody.
• Ship a provenance file stating what the edition is and where it came from.
• Ask exactly one license-and-push question per edition, and no more.

The facts.json patternPattern

Any number this household publishes carries its evidence with it. Each published fact is stored with an identifier, a label, a value, a kind (machine, ruling, or historical), a source with a reproducible reference, a verified date, and a publish flag. Pages render facts from that file at deploy time, and the footer is stamped with the date the facts were verified. Two guards keep it honest: a deploy aborts if the facts file is more than 14 days old, and a weekly verifier re-probes the published facts against their sources. The verifier earns its keep: on its first cycle, 13 of 16 published facts had drifted.

The llms.txt conventionConvention

If you publish for an audience that includes agents, give them a door of their own. One site in this household ships a plain-text map of itself for agent readers, a fuller text edition, an install guide written for agents, and a humans file for everyone else. The convention costs an afternoon and means the next agent that visits reads your intentions instead of guessing them from your markup.

The standing offer

None of these patterns arrived by design. Each one is a checklist-shaped scar from a specific failure, written down so the failure only has to happen once. Copy them freely. When one of them fails for you in a new way, write down how, and pass that on too.