Tags
Every concept here is filed by what kind of page it is: the directory carries its nature, and the index lists the sections in the order the ideas build. That leaves no room for the other question a reader asks, which is what a page is about, so the subject rides on tags instead. The reasoning is Split orthogonal classification axes across folders and tags.
This page is the other way in. Every tag in use, and every page under it, so a subject that runs across six directories can be read as one thing.
agent-first¶
- Agent-integration layer and multi-vault interaction for an OKF-conformant PKB
- Federated OKF knowledge bases: a workspace-manifest architecture
- Federating my knowledge base as privacy-tiered OKF bundles
- Running this knowledge base on awiki
- Substrate options for an OKF-based agent-first LLM wiki: investigation
agent-knowledge¶
agent-skills¶
- End-to-end test an LLM skill by driving a real agent in a disposable fake HOME
- Wrapping the kb skills in a federation layer
- agent-knowledge (stjbrown)
- caveman (Julius Brussee)
- federated-knowledge-skills (Felix Schindler)
- ponytail (Dietrich Gebert)
- project-wiki (giodra96)
- skills (Vercel Labs)
- skills.sh: repository layout, selective install and telemetry
agent-wiki¶
- Open Knowledge Format (OKF): findings
- Running this knowledge base on awiki
- Security Analysis of Agent Wiki (awiki)
- Substrate options for an OKF-based agent-first LLM wiki: investigation
- agent-wiki (TacoTakumi)
- awiki title extraction breaks on frontmatter-led source files
- awiki tracks backlinks via wikilinks only, not Markdown links
agents¶
- Adopting caveman at lite, without its init block
- Adopting ponytail without its always-on ruleset
- OpenChamber
- Route a rule to the layer that reaches whoever must obey it
- Sharing one user-level AGENTS.md across harnesses
- Teaching my agents to write better
- markitdown
- opencode
ai-agents¶
- Adopting caveman at lite, without its init block
- Adopting ponytail without its always-on ruleset
- Security Analysis of Agent Wiki (awiki)
- Sharing one user-level AGENTS.md across harnesses
- caveman (Julius Brussee)
- ponytail (Dietrich Gebert)
- skills (Vercel Labs)
- skills.sh: repository layout, selective install and telemetry
api¶
arup¶
audio¶
- A Bluetooth headset reconnects in A2DP instead of the saved profile
- Bluetooth A2DP fails with Protocol not available after resume
- Dell Precision 5470
- OpenMove by Shokz
- WirePlumber
authentication¶
- A GitHub token does not authenticate requests to github.com web pages
- Git LFS fails when the remote URL has a trailing slash
- Let CI push to a protected branch with a GitHub App
- linkspector ignores the httpHeaders in its config
benchmarking¶
- A microbenchmark body must not mutate state that outlives one iteration
- nanobench reports no Big-O estimate, or one fitted across unrelated runs
blueprint¶
bluetooth¶
- A Bluetooth headset reconnects in A2DP instead of the saved profile
- Bluetooth A2DP fails with Protocol not available after resume
- Dell Precision 5470
- OpenMove by Shokz
bug¶
- Dependabot declines transitive security updates in uv.lock
- awiki title extraction breaks on frontmatter-led source files
- awiki tracks backlinks via wikilinks only, not Markdown links
- linkspector ignores the httpHeaders in its config
build¶
categorization¶
caveman¶
chromium¶
ci¶
- A test that cannot run must fail loudly, never skip into a green result
- Resolve a repo's own dev tools through an ephemeral runner, not a project virtualenv
ci-cd¶
- Bound every CI job with an explicit timeout
- Cancel superseded CI runs with a concurrency group
- Dependabot
- Dependabot declines transitive security updates in uv.lock
- Grant least-privilege CI permissions at both workflow and job level
- Guard invariants at commit-time, not review-time
- Install from a frozen lockfile in CI
- Keep a linear history: block merge, fixup and squash commits
- Keep transitive dependencies in the regular update cycle
- Let CI push to a protected branch with a GitHub App
- Mirror every local guard in CI
- MkDocs Material PKB publishing stack
- Name every CI step so the run log reads as a narrative
- Run CI steps under a strict shell (errexit, pipefail)
- Split CI jobs for attributable failure and minimal dependencies
- Validate config files against their published schema
- Verify a pre-commit hook's file-type filter actually matches your file
clarity¶
communication¶
config-management¶
- A config symlink makes every omo migration fail on start
- A plugin upgrade renamed a routing category and silently breached provider isolation
- Sharing one user-level AGENTS.md across harnesses
- Test a config layering assumption with a marker key
- neo-tree's hide_hidden does not show dotfiles on Linux
- opencode
- opencode merges a profile over the base config rather than replacing it
- zsh does not expand a tilde in env VAR=~/path, and opencode creates the literal directory
configuration¶
- A declared-but-inert config documents intent, not enforcement
- pymarkdown's fix mode dedents YAML frontmatter
cpp¶
data-privacy¶
- Security Analysis of Agent Wiki (awiki)
- skills.sh: repository layout, selective install and telemetry
decision¶
- Adopting caveman at lite, without its init block
- Adopting ponytail without its always-on ruleset
- Building my visual PKB
- Federating my knowledge base as privacy-tiered OKF bundles
- Teaching my agents to write better
dell¶
dependabot¶
- Batch dependency updates with a cooldown, not a firehose
- Dependabot
- Dependabot declines transitive security updates in uv.lock
dependencies¶
dictation¶
documentation¶
- Date a page whose claim is about a version
- Give a knowledge base a tier that is not asked to earn its place
- Give every cross-cutting concept one definitional home
- Hand the reader one idea at a time
- Name the concrete behaviour, not its abstract label
- Record an abandoned exploration as an exploration, not a superseded decision
- Route a rule to the layer that reaches whoever must obey it
- Structure docs as the reader's task path - lead with action, defer rationale
- Teaching my agents to write better
- Write in a calm, quantified, settled-fact voice - not a promotional one
- linkspector
dx¶
- A declared-but-inert config documents intent, not enforcement
- A sandbox test must use the live working-tree source and rebuild fresh each run
- A test that cannot run must fail loudly, never skip into a green result
- Adopting caveman at lite, without its init block
- Adopting ponytail without its always-on ruleset
- Autofix in the hook, don't just flag
- Declare formatting once, editor-agnostically, via .editorconfig
- Do not make a tool a prerequisite for work it is not needed for
- Document a rationale for every disabled lint rule
- Fail early on a missing tool with a message that names it and points at the fix
- Give every cross-cutting concept one definitional home
- Guard invariants at commit-time, not review-time
- Hand the reader one idea at a time
- Make support-tool config files dotfiles
- Make the build interface a self-documenting Makefile
- Name the concrete behaviour, not its abstract label
- Order auto-fixers so later ones do not re-dirty earlier output
- Resolve a repo's own dev tools through an ephemeral runner, not a project virtualenv
- Route a rule to the layer that reaches whoever must obey it
- Sharing one user-level AGENTS.md across harnesses
- Spell-checking prose in a pre-commit hook: corpus checkers, dictionary checkers, and what each one misses
- Structure docs as the reader's task path - lead with action, defer rationale
- Teaching my agents to write better
- Treat warnings as errors
- Use PEP 723 inline script metadata for zero-install tooling scripts
- Write in a calm, quantified, settled-fact voice - not a promotional one
e2e¶
epub¶
exploration¶
federation¶
- Federated OKF knowledge bases: a workspace-manifest architecture
- Federating my knowledge base as privacy-tiered OKF bundles
- Separate audiences with separate bundles, not with folders or tags
- Wrapping the kb skills in a federation layer
- federated-knowledge-skills (Felix Schindler)
felix¶
finding¶
- A Bluetooth headset reconnects in A2DP instead of the saved profile
- A GitHub token does not authenticate requests to github.com web pages
- A config symlink makes every omo migration fail on start
- A plugin upgrade renamed a routing category and silently breached provider isolation
- Bluetooth A2DP fails with Protocol not available after resume
- Chromium maximises to the wrong size after an undock, and closing every window does not restart it
- Dependabot declines transitive security updates in uv.lock
- Git LFS fails when the remote URL has a trailing slash
- awiki title extraction breaks on frontmatter-led source files
- awiki tracks backlinks via wikilinks only, not Markdown links
- fs.protected_regular Blocks Root Writes in Sticky tmp
- linkspector ignores the httpHeaders in its config
- nanobench reports no Big-O estimate, or one fitted across unrelated runs
- neo-tree's hide_hidden does not show dotfiles on Linux
- opencode merges a profile over the base config rather than replacing it
- opencode writes its session transcripts into the Claude config directory
- pymarkdown's fix mode dedents YAML frontmatter
- zsh does not expand a tilde in env VAR=~/path, and opencode creates the literal directory
foss¶
frontmatter¶
- A markdown autofixer can corrupt YAML frontmatter it treats as content
- awiki title extraction breaks on frontmatter-led source files
- pymarkdown's fix mode dedents YAML frontmatter
git¶
- A declared-but-inert config documents intent, not enforcement
- Enforce LF line endings everywhere
- Enforce a canonical author identity via .mailmap
- Git LFS fails when the remote URL has a trailing slash
- Keep a linear history: block merge, fixup and squash commits
- Resolve a repo's own dev tools through an ephemeral runner, not a project virtualenv
- Track every committed binary type in .gitattributes
git-lfs¶
- Git LFS fails when the remote URL has a trailing slash
- Track every committed binary type in .gitattributes
github¶
- A GitHub token does not authenticate requests to github.com web pages
- Dependabot
- Let CI push to a protected branch with a GitHub App
- linkspector ignores the httpHeaders in its config
github-actions¶
- Bound every CI job with an explicit timeout
- Cancel superseded CI runs with a concurrency group
- Grant least-privilege CI permissions at both workflow and job level
- Keep a linear history: block merge, fixup and squash commits
- Let CI push to a protected branch with a GitHub App
- Mirror every local guard in CI
- Name every CI step so the run log reads as a narrative
- Pin GitHub Actions to full commit SHAs
- Run CI steps under a strict shell (errexit, pipefail)
- Split CI jobs for attributable failure and minimal dependencies
gtd¶
- Automatic session capture is not an inbox
- Keep the GTD inbox inside the private bundle, not beside it
guide¶
hardware¶
inbox¶
- Automatic session capture is not an inbox
- Keep the GTD inbox inside the private bundle, not beside it
information-architecture¶
ingest¶
kde¶
knowledge-management¶
- Agent-integration layer and multi-vault interaction for an OKF-conformant PKB
- Automatic session capture is not an inbox
- Building my visual PKB
- Date a page whose claim is about a version
- Federated OKF knowledge bases: a workspace-manifest architecture
- Federating my knowledge base as privacy-tiered OKF bundles
- Give a knowledge base a tier that is not asked to earn its place
- Keep the GTD inbox inside the private bundle, not beside it
- Layer build-knowledge as a values-to-blueprints derivation pipeline
- Open Knowledge Format (OKF): findings
- Prefer plain-text, tool-agnostic formats
- Record an abandoned exploration as an exploration, not a superseded decision
- Route a rule to the layer that reaches whoever must obey it
- Running this knowledge base on awiki
- Separate audiences with separate bundles, not with folders or tags
- Split orthogonal classification axes across folders and tags
- Substrate options for an OKF-based agent-first LLM wiki: investigation
- Wishes for a personal knowledge base
- Wrapping the kb skills in a federation layer
- agent-knowledge (stjbrown)
- agent-wiki (TacoTakumi)
- awiki tracks backlinks via wikilinks only, not Markdown links
- federated-knowledge-skills (Felix Schindler)
- project-wiki (giodra96)
kwin¶
links¶
- A GitHub token does not authenticate requests to github.com web pages
- linkspector
- linkspector ignores the httpHeaders in its config
linkspector¶
linting¶
- Autofix in the hook, don't just flag
- Document a rationale for every disabled lint rule
- Enforce the intersection of all renderers and consumers
- Spell-checking prose in a pre-commit hook: corpus checkers, dictionary checkers, and what each one misses
- Validate config files against their published schema
- Verify a pre-commit hook's file-type filter actually matches your file
linux¶
- A Bluetooth headset reconnects in A2DP instead of the saved profile
- Bluetooth A2DP fails with Protocol not available after resume
- Chromium maximises to the wrong size after an undock, and closing every window does not restart it
- Dell Precision 5470
- OpenMove by Shokz
- Vocalinux (VocaHQ)
- Voxtype (Peter Jackson)
- WirePlumber
- fs.protected_regular Blocks Root Writes in Sticky tmp
llm¶
llm-wiki¶
- Agent-integration layer and multi-vault interaction for an OKF-conformant PKB
- Federated OKF knowledge bases: a workspace-manifest architecture
- Running this knowledge base on awiki
- Substrate options for an OKF-based agent-first LLM wiki: investigation
- agent-knowledge (stjbrown)
- agent-wiki (TacoTakumi)
- project-wiki (giodra96)
make¶
markdown¶
- A markdown autofixer can corrupt YAML frontmatter it treats as content
- Enforce the intersection of all renderers and consumers
- awiki title extraction breaks on frontmatter-led source files
- awiki tracks backlinks via wikilinks only, not Markdown links
- markitdown
- pymarkdown's fix mode dedents YAML frontmatter
markitdown¶
mkdocs¶
- Agent-integration layer and multi-vault interaction for an OKF-conformant PKB
- Federated OKF knowledge bases: a workspace-manifest architecture
- MkDocs Material PKB publishing stack
model-order-reduction¶
nanobench¶
neo-tree¶
neovim¶
numerical-analysis¶
oh-my-openagent¶
- A config symlink makes every omo migration fail on start
- A plugin upgrade renamed a routing category and silently breached provider isolation
- opencode writes its session transcripts into the Claude config directory
okf¶
- Agent-integration layer and multi-vault interaction for an OKF-conformant PKB
- Federated OKF knowledge bases: a workspace-manifest architecture
- Federating my knowledge base as privacy-tiered OKF bundles
- Open Knowledge Format (OKF): findings
- Substrate options for an OKF-based agent-first LLM wiki: investigation
- Wrapping the kb skills in a federation layer
- agent-knowledge (stjbrown)
- agent-wiki (TacoTakumi)
- federated-knowledge-skills (Felix Schindler)
openchamber¶
opencode¶
- A config symlink makes every omo migration fail on start
- A plugin upgrade renamed a routing category and silently breached provider isolation
- Adopting ponytail without its always-on ruleset
- OpenChamber
- Sharing one user-level AGENTS.md across harnesses
- opencode
- opencode merges a profile over the base config rather than replacing it
- opencode writes its session transcripts into the Claude config directory
- ponytail (Dietrich Gebert)
- zsh does not expand a tilde in env VAR=~/path, and opencode creates the literal directory
packaging¶
people¶
performance¶
- A microbenchmark body must not mutate state that outlives one iteration
- nanobench reports no Big-O estimate, or one fitted across unrelated runs
permissions¶
pipewire¶
- A Bluetooth headset reconnects in A2DP instead of the saved profile
- Bluetooth A2DP fails with Protocol not available after resume
- WirePlumber
pkb¶
- Agent-integration layer and multi-vault interaction for an OKF-conformant PKB
- Building my visual PKB
- Categorize by what content is, not why you made it
- Federated OKF knowledge bases: a workspace-manifest architecture
- Federating my knowledge base as privacy-tiered OKF bundles
- Keep the GTD inbox inside the private bundle, not beside it
- Local-first, but not local-required
- MkDocs Material PKB publishing stack
- Running this knowledge base on awiki
- Security Analysis of Agent Wiki (awiki)
- Separate audiences with separate bundles, not with folders or tags
- Substrate options for an OKF-based agent-first LLM wiki: investigation
- Teaching my agents to write better
- Wishes for a personal knowledge base
- federated-knowledge-skills (Felix Schindler)
plain-text¶
plasma¶
ponytail¶
pre-commit¶
- A markdown autofixer can corrupt YAML frontmatter it treats as content
- Guard invariants at commit-time, not review-time
- Keep declared toolchain versions in sync, and guard it
- Make support-tool config files dotfiles
- Mirror every local guard in CI
- Order auto-fixers so later ones do not re-dirty earlier output
- Pin pre-commit hooks to frozen revisions
- Pin transitive runtime dependencies, not just the tool
- Spell-checking prose in a pre-commit hook: corpus checkers, dictionary checkers, and what each one misses
- Validate config files against their published schema
- Verify a pre-commit hook's file-type filter actually matches your file
- linkspector
- pymarkdown's fix mode dedents YAML frontmatter
principle¶
- A declared-but-inert config documents intent, not enforcement
- A markdown autofixer can corrupt YAML frontmatter it treats as content
- A microbenchmark body must not mutate state that outlives one iteration
- A sandbox test must use the live working-tree source and rebuild fresh each run
- A test that cannot run must fail loudly, never skip into a green result
- Autofix in the hook, don't just flag
- Batch dependency updates with a cooldown, not a firehose
- Bound every CI job with an explicit timeout
- Cancel superseded CI runs with a concurrency group
- Declare formatting once, editor-agnostically, via .editorconfig
- Do not make a tool a prerequisite for work it is not needed for
- Document a rationale for every disabled lint rule
- End-to-end test an LLM skill by driving a real agent in a disposable fake HOME
- Enforce LF line endings everywhere
- Enforce a canonical author identity via .mailmap
- Enforce the intersection of all renderers and consumers
- Fail early on a missing tool with a message that names it and points at the fix
- Give every cross-cutting concept one definitional home
- Grant least-privilege CI permissions at both workflow and job level
- Guard invariants at commit-time, not review-time
- Hand the reader one idea at a time
- Install from a frozen lockfile in CI
- Keep a linear history: block merge, fixup and squash commits
- Keep declared toolchain versions in sync, and guard it
- Keep filenames lowercase with no whitespace
- Keep transitive dependencies in the regular update cycle
- Layer build-knowledge as a values-to-blueprints derivation pipeline
- Make support-tool config files dotfiles
- Make the build interface a self-documenting Makefile
- Mirror every local guard in CI
- Name every CI step so the run log reads as a narrative
- Name the concrete behaviour, not its abstract label
- Order auto-fixers so later ones do not re-dirty earlier output
- Pin GitHub Actions to full commit SHAs
- Pin pre-commit hooks to frozen revisions
- Pin transitive runtime dependencies, not just the tool
- Resolve a repo's own dev tools through an ephemeral runner, not a project virtualenv
- Route a rule to the layer that reaches whoever must obey it
- Run CI steps under a strict shell (errexit, pipefail)
- Split CI jobs for attributable failure and minimal dependencies
- Split orthogonal classification axes across folders and tags
- Structure docs as the reader's task path - lead with action, defer rationale
- Test a config layering assumption with a marker key
- Track every committed binary type in .gitattributes
- Treat warnings as errors
- Use PEP 723 inline script metadata for zero-install tooling scripts
- Validate config files against their published schema
- Verify a pre-commit hook's file-type filter actually matches your file
- Write in a calm, quantified, settled-fact voice - not a promotional one
project-wiki¶
prose¶
provenance¶
pymarkdown¶
python¶
- Keep declared toolchain versions in sync, and guard it
- Use PEP 723 inline script metadata for zero-install tooling scripts
- markitdown
- uv
reading¶
repo-hygiene¶
- A sandbox test must use the live working-tree source and rebuild fresh each run
- Declare formatting once, editor-agnostically, via .editorconfig
- Enforce LF line endings everywhere
- Keep filenames lowercase with no whitespace
- Make support-tool config files dotfiles
- Track every committed binary type in .gitattributes
reproducibility¶
secrets¶
security¶
- Grant least-privilege CI permissions at both workflow and job level
- Pin GitHub Actions to full commit SHAs
- Pin pre-commit hooks to frozen revisions
- Security Analysis of Agent Wiki (awiki)
- fs.protected_regular Blocks Root Writes in Sticky tmp
self-authored¶
self-hosted¶
shokz¶
situational¶
- Enforce a canonical author identity via .mailmap
- Keep filenames lowercase with no whitespace
- Local-first, but not local-required
- Order auto-fixers so later ones do not re-dirty earlier output
skills-sh¶
software¶
- A declared-but-inert config documents intent, not enforcement
- A markdown autofixer can corrupt YAML frontmatter it treats as content
- A microbenchmark body must not mutate state that outlives one iteration
- A sandbox test must use the live working-tree source and rebuild fresh each run
- A test that cannot run must fail loudly, never skip into a green result
- Autofix in the hook, don't just flag
- Batch dependency updates with a cooldown, not a firehose
- Bound every CI job with an explicit timeout
- Building my visual PKB
- Cancel superseded CI runs with a concurrency group
- Declare formatting once, editor-agnostically, via .editorconfig
- Do not make a tool a prerequisite for work it is not needed for
- Document a rationale for every disabled lint rule
- End-to-end test an LLM skill by driving a real agent in a disposable fake HOME
- Enforce LF line endings everywhere
- Enforce a canonical author identity via .mailmap
- Enforce the intersection of all renderers and consumers
- Fail early on a missing tool with a message that names it and points at the fix
- Grant least-privilege CI permissions at both workflow and job level
- Guard invariants at commit-time, not review-time
- Install from a frozen lockfile in CI
- Keep a linear history: block merge, fixup and squash commits
- Keep declared toolchain versions in sync, and guard it
- Keep filenames lowercase with no whitespace
- Keep transitive dependencies in the regular update cycle
- Local-first, but not local-required
- Make support-tool config files dotfiles
- Make the build interface a self-documenting Makefile
- Mirror every local guard in CI
- MkDocs Material PKB publishing stack
- Name every CI step so the run log reads as a narrative
- Order auto-fixers so later ones do not re-dirty earlier output
- Pin GitHub Actions to full commit SHAs
- Pin pre-commit hooks to frozen revisions
- Pin transitive runtime dependencies, not just the tool
- Prefer FOSS software wherever possible
- Prefer plain-text, tool-agnostic formats
- Resolve a repo's own dev tools through an ephemeral runner, not a project virtualenv
- Run CI steps under a strict shell (errexit, pipefail)
- Split CI jobs for attributable failure and minimal dependencies
- Test a config layering assumption with a marker key
- Track every committed binary type in .gitattributes
- Treat warnings as errors
- Use PEP 723 inline script metadata for zero-install tooling scripts
- Validate config files against their published schema
- Verify a pre-commit hook's file-type filter actually matches your file
- Wishes for a personal knowledge base
- Write in a calm, quantified, settled-fact voice - not a promotional one
speech-to-text¶
spelling¶
ssh¶
static-site¶
structure¶
- Give every cross-cutting concept one definitional home
- Structure docs as the reader's task path - lead with action, defer rationale
supply-chain¶
- Batch dependency updates with a cooldown, not a firehose
- Dependabot
- Dependabot declines transitive security updates in uv.lock
- Install from a frozen lockfile in CI
- Keep transitive dependencies in the regular update cycle
- Pin GitHub Actions to full commit SHAs
- Pin pre-commit hooks to frozen revisions
- Pin transitive runtime dependencies, not just the tool
- uv
sysctl¶
systemd¶
taxonomy¶
- Date a page whose claim is about a version
- Give a knowledge base a tier that is not asked to earn its place
- Layer build-knowledge as a values-to-blueprints derivation pipeline
- Record an abandoned exploration as an exploration, not a superseded decision
- Separate audiences with separate bundles, not with folders or tags
- Split orthogonal classification axes across folders and tags
testing¶
- A microbenchmark body must not mutate state that outlives one iteration
- A sandbox test must use the live working-tree source and rebuild fresh each run
- A test that cannot run must fail loudly, never skip into a green result
- End-to-end test an LLM skill by driving a real agent in a disposable fake HOME
tmp¶
tooling¶
- Do not make a tool a prerequisite for work it is not needed for
- Fail early on a missing tool with a message that names it and points at the fix
- Resolve a repo's own dev tools through an ephemeral runner, not a project virtualenv
- Sharing one user-level AGENTS.md across harnesses
- Spell-checking prose in a pre-commit hook: corpus checkers, dictionary checkers, and what each one misses
tools¶
- Dependabot
- Liseur and Liseur-Sync
- OpenChamber
- Vocalinux (VocaHQ)
- Voxtype (Peter Jackson)
- WirePlumber
- agent-knowledge (stjbrown)
- agent-wiki (TacoTakumi)
- caveman (Julius Brussee)
- federated-knowledge-skills (Felix Schindler)
- linkspector
- markitdown
- opencode
- ponytail (Dietrich Gebert)
- project-wiki (giodra96)
- skills (Vercel Labs)
- uv
traceability¶
uv¶
- Dependabot declines transitive security updates in uv.lock
- Keep declared toolchain versions in sync, and guard it
- Use PEP 723 inline script metadata for zero-install tooling scripts
- uv
value¶
vocalinux¶
voxtype¶
wayland¶
wireplumber¶
- A Bluetooth headset reconnects in A2DP instead of the saved profile
- Bluetooth A2DP fails with Protocol not available after resume
- WirePlumber
wish¶
workflow¶
- Automatic session capture is not an inbox
- Keep the GTD inbox inside the private bundle, not beside it
writing¶
- Adopting caveman at lite, without its init block
- Give every cross-cutting concept one definitional home
- Hand the reader one idea at a time
- Name the concrete behaviour, not its abstract label
- Structure docs as the reader's task path - lead with action, defer rationale
- Teaching my agents to write better
- Write in a calm, quantified, settled-fact voice - not a promotional one
- caveman (Julius Brussee)
x11¶
zsh¶
Backlinks¶
The following pages link to this page: