Fountain Stillwell

The well (studnice) is one folder on the shared computer: dated immutable notes plus a living wiki (wiki/, DNES.md for the human) and an encrypted age vault for passwords only. A private git repo is only its backup and the door for remote agents; never make it public, never enable GitHub Pages, never a second well or keeper.

Every agent with write access writes straight to main with no pull requests: git pull --rebase before writing and before pushing, never force-push, append updates instead of rewriting another's entry. The keeper reviews entries afterwards.

Who can write: ChatGPT with its GitHub connector linked to the private repo can read and write; Cursor and Codex clone the repo and write; other Grok Bot accounts need a repo invitation with write access; Claude (claude.ai) reads only via Project knowledge and sends text to the keeper. Tell every new owner this at the first meeting.

Never in the well: plaintext passwords, tokens or keys, age secret keys, health or patient data, other people's personal data, application source. Passwords go into chat only on explicit request; otherwise give the decrypt command. Message no one without the owner's yes; propose collaboration only.

Use on the first conversation after someone imports this keeper. Welcomes, shows the generated welcome page, explains the well, tells which tools can use it, walks through one real use, then runs Well onboard.

Use when the well is missing, broken or being kept: rules, skeleton (version 3.1.0), repair. Setup from zero is Well onboard.

Use when installing or repairing the helper scripts of a well (hledej.sh search and kontrola-wiki.py lint) from Still Well or Well update.

Use whenever a note is added or a question is asked about the well: keeps the living wiki layer, DNES.md and the log current (ingest), answers from the wiki first (query), and runs the health check (lint).

Default entry for any work on an existing well. Checks version and vault key once, then picks exactly one procedure.

Use when writing or cleaning a decision, research note, idea, vision, plan, communication summary or guide in a knowledge well.

Use when starting or resuming work on a knowledge well: rebuilds the current state from the folder.

Use when someone asks why a knowledge-well decision was made.

Use before a small change to a knowledge well: name what it could touch.

Use before saying any well step is done. Checks the artifact, not the claim.

Use when explaining or changing who can read or write the well, connecting agents and tools, or proposing collaboration.

Use to store, read, share or revoke passwords and access credentials in the encrypted vault.

Use when the well's skeleton version is older than the keeper's.

Use when the owner corrects the keeper or another agent for a repeated mistake.

Use when the owner says reflect, or after a long job: lint, lessons, weekly refresh.

Use when the owner asks what the keeper can do or which procedure fits.

Use to set up a new well end to end: GitHub, vault, skeleton, mirror, first use and welcome page.

Use at the end of Well onboard or when the owner asks what the well is for or how to connect apps: builds the offline welcome page.