johnandersen777.bsky.social/atlibs-identlink
ident.link agent-of walk with grants over CAR-verified sync.getRecord: Rust crate identlink, wasm, JS
Working here
Pins
The atlibs crates this repository pins by git rev (atlibs-host, atlibs-iroh, atlibs-kube, atlibs-ssh, identlink),
the module pins in an atlibs.lock.json and a versions.env commit follow one tested set, atlibs pins.json. Before a
push, at the root:
curl -sSf https://knotless.dev/johnandersen777.bsky.social/atlibs/raw/main/pins.sh | sh -s -- check
Behind: catch up (rewrites the revs, cargo update --workspace, cargo check), then commit and push.
curl -sSf https://knotless.dev/johnandersen777.bsky.social/atlibs/raw/main/pins.sh | sh -s -- sync
.knotless/workflows/pins.yml checks each push to main and syncs nightly, pushing the bump; it runs once a knotless
runner serves this repository (none yet) and grants it PINS_PASSWORD.
README
Every block runs from a fresh clone: node docs/readme-check.mjs README.md (DOCS_ACCOUNT=bob|aliceoa adds run=account blocks).
Landing changes
Agents never push to the base branch (main; runner-atlibs-composition in the knotless fork): it is protected with
--queue, and the merge queue lands a change once its checks pass. Push a branch, open a pull and queue it:
U=knotless://<owner>/<repo>
git push origin HEAD:refs/heads/<branch>
knotless pull create $U <base> $U <branch> "<title>" -m "<why>"
knotless pull merge $U <pull> --queue
knotless queue list $U
knotless pull show $U <pull> says where it is; a pull whose checks fail is ejected from the queue (fix the branch, queue it
again).
Security controls: propose, never implement
Never add a security control unless the owner explicitly approved that exact control. That includes:
- caps and size limits;
- refusals and validation that rejects input;
- allowlists and denylists;
- scope or permission checks;
- sandbox rules;
- timeouts added "for safety".
If you think one is needed, add it to docs/security/proposed-controls.md and tell the owner. Do not implement it.
## <short name>
- What: <the check, one line>
- Where: <file:line or component>
- Threat: <who does what, and what this stops>
Found an existing control the owner never approved? List it there under "Existing, not owner-approved". Do not remove or extend it on your own.
Plan document before work
Every change executes a plan in docs/plans/NNNN-<slug>.md. No plan covers the issue? Write one first, land it through the merge queue, then execute it.
# NNNN - <title>
Status: plan | approved by the owner <date> | done
## Why
<one or two lines>
## Steps
1. …
## Order
1. …
- Plans hold the facts: numbers, names, decisions. Keep them current in the plan, not in chat.
- Brief subagents with the plan's path.