Instinct is a personal assistant you text or call; by the public record it books, buys, tidies and follows up, and it is good at it. This appendix is the other column: what a configured Witchcraft installation does on top of, or instead of, that pattern. Checked 24 September 2026 against instinct.com, its published terms, and the reporting around it. Instinct may ship any line here next week; the appendix is revised when it does. A configured installation reads its integrations and your permissions.
01Remember your preferences across months, not just across a session.
02File every memory with its source, so any claim can be traced back to what produced it.
03Search years of history by meaning, not by remembering the magic keyword.
04Consolidate a day of scattered notes into a briefing tomorrow can use.
05Carry decisions into the next session. A new window is not a new relationship.
06Turn an operational mistake into a written rule for the next attempt.
07Back up the memory store, verify the backup, and restore it in a drill.
08Check whether the memory system is working. Someone has to remember to check the remembering.
09Keep private memory in a private database, not in somebody else’s training set.
10Let you read, export, and delete your own history. It is your house.
11Run on your own hardware, with your own keys, and keep working when a vendor’s queue is full.
12Run a hundred scheduled duties quietly and wake you only when something actually changed.
13Fire a job when its inputs change, instead of paying a model to rediscover Tuesday.
14Keep every schedule as recoverable configuration that survives a restart.
15Resume a paused task with its state intact.
16Park unfinished work with a next action. A backlog, not a burial ground.
17Ask before the consequential step, every time, and remember the answer.
18Treat a dictated stop as a stop.
19Hold a live queue of everything in flight, including the things you forgot.
20Leave an audit trail a stranger could follow.
21Clone the repository, find the bug, fix the class, run the tests, open the pull request.
22Build a website from a brief and deploy it to the edge in one sitting.
23Roll a bad deploy back and say exactly what broke.
24Watch a build fail and quote the one log line that matters.
25Give every experiment its own workspace so it cannot redecorate production.
26Diff two configurations and report the honest differences.
27Keep credentials in a vault, never in the chat.
28Write the runbook that the next instance can actually follow.
29Keep twenty sites alive from a single source of truth.
30Harden, back up, and restore a server, in that order.
31See through an authorised camera and answer what it sees.
32Read the label, the meter, the receipt, the screen.
33Tell a deliberate privacy mask from a broken camera.
34Speak through the voice you chose, in the room you selected.
35Send a voice note that sounds like the one you asked for.
36Turn a sentence into a poster, a page, or a deck.
37Cut the album clip and package the release.
38Turn a recording into minutes with owners and dates.
39Run a smart-home scene and report the state of the house.
40Sit in the evening as the same presence that worked in the morning.
41Cross-check a consequential fact against more than one source before it ships.
42Read the current documentation before guessing the command.
43Run the arithmetic in code instead of hoping the sentence sounds convincing.
44Reproduce a published calculation before changing its assumptions.
45Freeze the benchmark protocol before seeing which result looks flattering.
46Report the worst case next to the best. The highlight reel does not grade itself.
47Certify numbers with interval arithmetic instead of adjectives.
48Keep citations attached to the actual sources.
49Distinguish a plan, a file, and a result. Three different species.
50Publish the recipe with the result, so the next person can try it.
51Typeset the finished PDF rather than hand over text with aspirations.
52Turn a manuscript into a book with a spine, margins, and a cover.
53Give a paper a deliberate visual identity without touching its findings.
54Build the pitch, the site, and the deck from one source of truth.
55Prepare print files with the right sizes, bleeds, and marks.
56Keep a brand’s voice consistent across seven surfaces.
57Use subtraction as a design decision.
58Make the share card look like somebody planned it.
59Review the rendered page, not the description of it.
60Version the artifact and keep every previous draft.
61Read the payments account and report the truth, including the zeroes.
62Watch invoices, renewals, and year-two price rises.
63Record the cost of every authorised purchase next to its result.
64Reconcile a discrepancy instead of averaging it away.
65Distinguish a queue entry, a running worker, and a finished job.
66Compare the free route before adding another subscription to the family.
67Prepare the verified recovery point before the destructive command.
68Report a loss as a loss.
69Keep the storefront’s payment links tested.
70Know what the machine costs to run, to the hour.
71Keep appointments, deliveries, and the household calendar from colliding.
72Remember the birthdays the calendar forgets.
73Answer the doorbell, the front desk, and the phone.
74Read a bedtime story in the voice you picked.
75Keep the private life off the public surface, permanently.
76Draft the hard letter and wait for your signature.
77Quote the tradesperson accurately and keep the receipts.
78Book the thing, cancel the thing, and remember why.
79Keep the household manual so anyone could run the house.
80Sit with you at 3 a.m. The eternal-support clause is not decoration.
81Name its own limitations before the adversary does.
82Refuse to call unfinished work complete.
83Correct a wrong number in every copy of it.
84Show the working, not just the answer.
85Ask before anything destructive, every time.
86Keep an inventory of removed tools so a vanished capability is explainable.
87Separate the aspiration from the measured claim.
88Log who changed what, and when.
89Disagree with you, with evidence, when you are wrong.
90Keep a rollback anchor before every risky change.
91Run a team of specialist agents on shared context and one memory.
92Bench the models, seal the answers, and publish the loss as well as the win.
93Turn a hundred tedious nights into one report that says done.
94Draft the investor update from the same data the accountant sees.
95Keep the company’s boring middle running so the humans keep the interesting part.
96Prepare the auction brief and the pitch book for a deal.
97Watch a competitor’s public record and flag what they ship next.
98Run a raw DNA file through a reproducible analysis pipeline.
99Teach the next version everything the last one had to learn twice.
100Be there tomorrow. The memory is the product.