What we do not
know yet.

1. Pin a product release or repository commit and record the host environment.
2. Create a disposable repository with a passing baseline test.
3. Run a bounded change with two agents where supported; record permissions and logs.
4. Record a failed attempt, actual outcome, and artifacts without secrets.
5. Have another person reproduce the result before labeling it reproduced.

Applies to: Unpinned public documentation as of 2026-09-13 · Documentation review only

Contributor: Testedknowhow initial research. Commissioned by a Nimbalyst maintainer; not an independent comparison.

1. Pin a product release or repository commit and record the host environment.
2. Create a disposable repository with a passing baseline test.
3. Run a bounded change with two agents where supported; record permissions and logs.
4. Record a failed attempt, actual outcome, and artifacts without secrets.
5. Have another person reproduce the result before labeling it reproduced.

Applies to: Unpinned public documentation as of 2026-09-13 · Documentation review only

Contributor: Testedknowhow initial research. Commissioned by a Nimbalyst maintainer; not an independent comparison.

1. Pin a product release or repository commit and record the host environment.
2. Create a disposable repository with a passing baseline test.
3. Run a bounded change with two agents where supported; record permissions and logs.
4. Record a failed attempt, actual outcome, and artifacts without secrets.
5. Have another person reproduce the result before labeling it reproduced.

Applies to: Unpinned public documentation as of 2026-09-13 · Documentation review only

Contributor: Testedknowhow initial research. Commissioned by a Nimbalyst maintainer; not an independent comparison.

1. Pin a product release or repository commit and record the host environment.
2. Create a disposable repository with a passing baseline test.
3. Run a bounded change with two agents where supported; record permissions and logs.
4. Record a failed attempt, actual outcome, and artifacts without secrets.
5. Have another person reproduce the result before labeling it reproduced.

Applies to: Unpinned public documentation as of 2026-09-13 · Documentation review only

Contributor: Testedknowhow initial research. Commissioned by a Nimbalyst maintainer; not an independent comparison.

1. Pin a product release or repository commit and record the host environment.
2. Create a disposable repository with a passing baseline test.
3. Run a bounded change with two agents where supported; record permissions and logs.
4. Record a failed attempt, actual outcome, and artifacts without secrets.
5. Have another person reproduce the result before labeling it reproduced.

Applies to: Unpinned public documentation as of 2026-09-13 · Documentation review only

Contributor: Testedknowhow initial research. Commissioned by a Nimbalyst maintainer; not an independent comparison.

1. Pin a product release or repository commit and record the host environment.
2. Create a disposable repository with a passing baseline test.
3. Run a bounded change with two agents where supported; record permissions and logs.
4. Record a failed attempt, actual outcome, and artifacts without secrets.
5. Have another person reproduce the result before labeling it reproduced.

Applies to: Unpinned public documentation as of 2026-09-13 · Documentation review only

Contributor: Testedknowhow initial research. Commissioned by a Nimbalyst maintainer; not an independent comparison.

1. Pin a product release or repository commit and record the host environment.
2. Create a disposable repository with a passing baseline test.
3. Run a bounded change with two agents where supported; record permissions and logs.
4. Record a failed attempt, actual outcome, and artifacts without secrets.
5. Have another person reproduce the result before labeling it reproduced.

Applies to: Unpinned public documentation as of 2026-09-13 · Documentation review only

Contributor: Testedknowhow initial research. Commissioned by a Nimbalyst maintainer; not an independent comparison.

1. Pin a product release or repository commit and record the host environment.
2. Create a disposable repository with a passing baseline test.
3. Run a bounded change with two agents where supported; record permissions and logs.
4. Record a failed attempt, actual outcome, and artifacts without secrets.
5. Have another person reproduce the result before labeling it reproduced.

Applies to: Repository documentation at fccf350847097c8f9d9de3e7e5c98b0d292a4554 · Documentation review only

Contributor: Testedknowhow initial research. Commissioned by a Nimbalyst maintainer; not an independent comparison.

1. Pin a product release or repository commit and record the host environment.
2. Create a disposable repository with a passing baseline test.
3. Run a bounded change with two agents where supported; record permissions and logs.
4. Record a failed attempt, actual outcome, and artifacts without secrets.
5. Have another person reproduce the result before labeling it reproduced.

Applies to: Repository documentation at ce1ffb4392b01f38e2c4599c7c84d2a93973b138 · Documentation review only

Contributor: Testedknowhow initial research. Commissioned by a Nimbalyst maintainer; not an independent comparison.

1. Pin a product release or repository commit and record the host environment.
2. Create a disposable repository with a passing baseline test.
3. Run a bounded change with two agents where supported; record permissions and logs.
4. Record a failed attempt, actual outcome, and artifacts without secrets.
5. Have another person reproduce the result before labeling it reproduced.

Applies to: Repository documentation at 5e73a49b89b4f13766fc2e22723297a36e7dcef2; Unpinned public documentation and/or pinned README sections reviewed 2026-09-13; per-claim source scope applies. · Documentation review only

Contributor: Testedknowhow initial research. Commissioned by a Nimbalyst maintainer; not an independent comparison.

1. Pin a product release or repository commit and record the host environment.
2. Create a disposable repository with a passing baseline test.
3. Run a bounded change with two agents where supported; record permissions and logs.
4. Record a failed attempt, actual outcome, and artifacts without secrets.
5. Have another person reproduce the result before labeling it reproduced.

Applies to: Repository documentation at 70c16d8a4910db48cd9684aeacdd431caefd7d71; Unpinned public documentation and/or pinned README sections reviewed 2026-09-13; per-claim source scope applies. · Documentation review only

Contributor: Testedknowhow initial research. Commissioned by a Nimbalyst maintainer; not an independent comparison.

1. Pin a product release or repository commit and record the host environment.
2. Create a disposable repository with a passing baseline test.
3. Run a bounded change with two agents where supported; record permissions and logs.
4. Record a failed attempt, actual outcome, and artifacts without secrets.
5. Have another person reproduce the result before labeling it reproduced.

Applies to: Repository documentation at dd61b9abd37de5ded86e82b9fe8a83fd49d46fa5; Unpinned public documentation and/or pinned README sections reviewed 2026-09-13; per-claim source scope applies. · Documentation review only

Contributor: Testedknowhow initial research. Commissioned by a Nimbalyst maintainer; not an independent comparison.

1. Pin a product release or repository commit and record the host environment.
2. Create a disposable repository with a passing baseline test.
3. Run a bounded change with two agents where supported; record permissions and logs.
4. Record a failed attempt, actual outcome, and artifacts without secrets.
5. Have another person reproduce the result before labeling it reproduced.

Applies to: Repository documentation at 22ae1c56fd83103e2d9c80ec3341a9a08557e6e1; Unpinned public documentation and/or pinned README sections reviewed 2026-09-13; per-claim source scope applies. · Documentation review only

Contributor: Testedknowhow initial research. Commissioned by a Nimbalyst maintainer; not an independent comparison.

1. Pin a product release or repository commit and record the host environment.
2. Create a disposable repository with a passing baseline test.
3. Run a bounded change with two agents where supported; record permissions and logs.
4. Record a failed attempt, actual outcome, and artifacts without secrets.
5. Have another person reproduce the result before labeling it reproduced.

Applies to: Repository documentation at c1c0b55ca03a4cd1d1eff2f64449445f778be4c4; Unpinned public documentation and/or pinned README sections reviewed 2026-09-13; per-claim source scope applies. · Documentation review only

Contributor: Testedknowhow initial research. Commissioned by a Nimbalyst maintainer; not an independent comparison.

1. Pin a product release or repository commit and record the host environment.
2. Create a disposable repository with a passing baseline test.
3. Run a bounded change with two agents where supported; record permissions and logs.
4. Record a failed attempt, actual outcome, and artifacts without secrets.
5. Have another person reproduce the result before labeling it reproduced.

Applies to: Repository documentation at b867ec9145750d0ae1ff7f02d35406e9bf2a0b16 · Documentation review only

Contributor: Testedknowhow initial research. Commissioned by a Nimbalyst maintainer; not an independent comparison.

1. Pin a product release or repository commit and record the host environment.
2. Create a disposable repository with a passing baseline test.
3. Run a bounded change with two agents where supported; record permissions and logs.
4. Record a failed attempt, actual outcome, and artifacts without secrets.
5. Have another person reproduce the result before labeling it reproduced.

Applies to: Repository documentation at c36e22634860e06e0aa63234fae37bbd83d3b182 · Documentation review only

Contributor: Testedknowhow initial research. Commissioned by a Nimbalyst maintainer; not an independent comparison.

1. Pin a product release or repository commit and record the host environment.
2. Create a disposable repository with a passing baseline test.
3. Run a bounded change with two agents where supported; record permissions and logs.
4. Record a failed attempt, actual outcome, and artifacts without secrets.
5. Have another person reproduce the result before labeling it reproduced.

Applies to: Repository documentation at df23b7f9488a38e6f8064a0739d4f8cde86d7cfb; Unpinned official documentation checked 2026-09-13; Unpinned public documentation and/or pinned README sections reviewed 2026-09-13; per-claim source scope applies. · Documentation review only

Contributor: Testedknowhow initial research. Commissioned by a Nimbalyst maintainer; not an independent comparison.

1. Pin a product release or repository commit and record the host environment.
2. Create a disposable repository with a passing baseline test.
3. Run a bounded change with two agents where supported; record permissions and logs.
4. Record a failed attempt, actual outcome, and artifacts without secrets.
5. Have another person reproduce the result before labeling it reproduced.

Applies to: Repository documentation at 5dc9490bb35f9729ef2c95d00a19ccd30c26339c; Unpinned public documentation and/or pinned README sections reviewed 2026-09-13; per-claim source scope applies. · Documentation review only

Contributor: Testedknowhow initial research. Commissioned by a Nimbalyst maintainer; not an independent comparison.

1. Pin a product release or repository commit and record the host environment.
2. Create a disposable repository with a passing baseline test.
3. Run a bounded change with two agents where supported; record permissions and logs.
4. Record a failed attempt, actual outcome, and artifacts without secrets.
5. Have another person reproduce the result before labeling it reproduced.

Applies to: Unpinned public documentation as of 2026-09-13 · Documentation review only

Contributor: Testedknowhow initial research. Commissioned by a Nimbalyst maintainer; not an independent comparison.

1. Pin a product release or repository commit and record the host environment.
2. Create a disposable repository with a passing baseline test.
3. Run a bounded change with two agents where supported; record permissions and logs.
4. Record a failed attempt, actual outcome, and artifacts without secrets.
5. Have another person reproduce the result before labeling it reproduced.

Applies to: Unpinned public documentation as of 2026-09-13 · Documentation review only

Contributor: Testedknowhow initial research. Commissioned by a Nimbalyst maintainer; not an independent comparison.

1. Pin the target configuration and define workload fixtures, access and budget.
2. With authorization, test concurrent writes and recovery against explicit correctness expectations.
3. For vector workloads, measure filtered recall against an exact-search baseline and record index settings.

Applies to: Unpinned upstream documentation accessed 2026-09-14; pin engine, extension and service versions before use. · Operator manages deployment, backups and upgrades. This target excludes extensions.

Contributor: Testedknowhow database research. Commissioned by a Nimbalyst maintainer. Documentation synthesis; no independent review or product execution.

1. Pin the target configuration and define workload fixtures, access and budget.
2. With authorization, test concurrent writes and recovery against explicit correctness expectations.
3. For vector workloads, measure filtered recall against an exact-search baseline and record index settings.

Applies to: Unpinned upstream documentation accessed 2026-09-14; pin engine, extension and service versions before use. · Application owns the database file, lifecycle and backup procedure; no separate database server.

Contributor: Testedknowhow database research. Commissioned by a Nimbalyst maintainer. Documentation synthesis; no independent review or product execution.

1. Pin the target configuration and define workload fixtures, access and budget.
2. With authorization, test concurrent writes and recovery against explicit correctness expectations.
3. For vector workloads, measure filtered recall against an exact-search baseline and record index settings.

Applies to: Unpinned upstream documentation accessed 2026-09-14; pin engine, extension and service versions before use. · Operator manages the deployment. This target does not include an Atlas service or configured vector-search component.

Contributor: Testedknowhow database research. Commissioned by a Nimbalyst maintainer. Documentation synthesis; no independent review or product execution.

1. Pin the target configuration and define workload fixtures, access and budget.
2. With authorization, test concurrent writes and recovery against explicit correctness expectations.
3. For vector workloads, measure filtered recall against an exact-search baseline and record index settings.

Applies to: Unpinned upstream documentation accessed 2026-09-14; pin engine, extension and service versions before use. · PostgreSQL plus an installed and enabled pgvector extension; operator manages both.

Contributor: Testedknowhow database research. Commissioned by a Nimbalyst maintainer. Documentation synthesis; no independent review or product execution.

1. Pin the target configuration and define workload fixtures, access and budget.
2. With authorization, test concurrent writes and recovery against explicit correctness expectations.
3. For vector workloads, measure filtered recall against an exact-search baseline and record index settings.

Applies to: Unpinned upstream documentation accessed 2026-09-14; pin engine, extension and service versions before use. · Self-managed server deployment; Qdrant Cloud and Edge are outside this target.

Contributor: Testedknowhow database research. Commissioned by a Nimbalyst maintainer. Documentation synthesis; no independent review or product execution.

1. Pin the target configuration and define workload fixtures, access and budget.
2. With authorization, test concurrent writes and recovery against explicit correctness expectations.
3. For vector workloads, measure filtered recall against an exact-search baseline and record index settings.

Applies to: Unpinned upstream documentation accessed 2026-09-14; pin engine, extension and service versions before use. · Database is a managed service separate from Worker application compute; do not assume arbitrary SQLite extensions.

Contributor: Testedknowhow database research. Commissioned by a Nimbalyst maintainer. Documentation synthesis; no independent review or product execution.

1. Pin the target configuration and define workload fixtures, access and budget.
2. With authorization, test concurrent writes and recovery against explicit correctness expectations.
3. For vector workloads, measure filtered recall against an exact-search baseline and record index settings.

Applies to: Unpinned upstream documentation accessed 2026-09-14; pin engine, extension and service versions before use. · Each object owns private storage. Application implements Worker routing and cross-object coordination.

Contributor: Testedknowhow database research. Commissioned by a Nimbalyst maintainer. Documentation synthesis; no independent review or product execution.

1. Pin the target configuration and define workload fixtures, access and budget.
2. With authorization, test concurrent writes and recovery against explicit correctness expectations.
3. For vector workloads, measure filtered recall against an exact-search baseline and record index settings.

Applies to: Unpinned upstream documentation accessed 2026-09-14; pin engine, extension and service versions before use. · Neon hosted Postgres; vector claims require enabling pgvector per database. Other backend services are excluded.

Contributor: Testedknowhow database research. Commissioned by a Nimbalyst maintainer. Documentation synthesis; no independent review or product execution.

1. Pin the target configuration and define workload fixtures, access and budget.
2. With authorization, test concurrent writes and recovery against explicit correctness expectations.
3. For vector workloads, measure filtered recall against an exact-search baseline and record index settings.

Applies to: Unpinned upstream documentation accessed 2026-09-14; pin engine, extension and service versions before use. · Atlas cluster plus configured search indexes; region, cluster type and search resources must be specified.

Contributor: Testedknowhow database research. Commissioned by a Nimbalyst maintainer. Documentation synthesis; no independent review or product execution.

1. Pin the target configuration and define workload fixtures, access and budget.
2. With authorization, test concurrent writes and recovery against explicit correctness expectations.
3. For vector workloads, measure filtered recall against an exact-search baseline and record index settings.

Applies to: Unpinned upstream documentation accessed 2026-09-14; pin engine, extension and service versions before use. · Hosted index and namespace configuration; attached metadata is not classified as a general document database.

Contributor: Testedknowhow database research. Commissioned by a Nimbalyst maintainer. Documentation synthesis; no independent review or product execution.

1. Choose hardware and obtain explicit approval for installations, downloads and execution resources.
2. Pin runtime and engine versions, model artifact hashes, tokenizer, template, quantization and inference settings.
3. Run the local-model-mac investigation with synthetic prompts and capture raw measurements; do not record documentation as execution.

Applies to: Repository revision 38a5b42d9a3e82e0a586bcd1caed121f36c87a73; living documentation separately dated. · Self-managed local build and server; pin compiled backends and model files.

Contributor: Testedknowhow model runtime research. Commissioned by a Nimbalyst maintainer. Documentation synthesis; no independent review or product execution.

1. Choose hardware and obtain explicit approval for installations, downloads and execution resources.
2. Pin runtime and engine versions, model artifact hashes, tokenizer, template, quantization and inference settings.
3. Run the local-model-mac investigation with synthetic prompts and capture raw measurements; do not record documentation as execution.

Applies to: Repository revision 872ae88d1fac77350db23c8c04fe8dd372a9e3e8; living documentation separately dated. · Local Apple Silicon execution with MLX; model conversion and server configuration remain operator-owned.

Contributor: Testedknowhow model runtime research. Commissioned by a Nimbalyst maintainer. Documentation synthesis; no independent review or product execution.

1. Choose hardware and obtain explicit approval for installations, downloads and execution resources.
2. Pin runtime and engine versions, model artifact hashes, tokenizer, template, quantization and inference settings.
3. Run the local-model-mac investigation with synthetic prompts and capture raw measurements; do not record documentation as execution.

Applies to: Repository revision a43fad18b088095de20fbd7a8f0de50824cf5d27; living documentation separately dated. · Local Ollama server with OLLAMA_NO_CLOUD=1 and preloaded local models; excludes Ollama Cloud and web search.

Contributor: Testedknowhow model runtime research. Commissioned by a Nimbalyst maintainer. Documentation synthesis; no independent review or product execution.

1. Choose hardware and obtain explicit approval for installations, downloads and execution resources.
2. Pin runtime and engine versions, model artifact hashes, tokenizer, template, quantization and inference settings.
3. Run the local-model-mac investigation with synthetic prompts and capture raw measurements; do not record documentation as execution.

Applies to: Living documentation accessed 2026-09-15; app and installed engine versions are not pinned. · Local LM Studio app and server; pin the separately installed llama.cpp or MLX engine. Excludes remote hosts, Bionic workflows and external tools.

Contributor: Testedknowhow model runtime research. Commissioned by a Nimbalyst maintainer. Documentation synthesis; no independent review or product execution.

1. Use the small-team-knowledge investigation to specify the required collaboration and access boundaries.
2. With explicit authorization, create an isolated synthetic workspace and named test accounts; do not invite real colleagues or upload private knowledge.
3. Test editing, viewer restrictions, recovery and export with pinned clients and plan; retain sanitized artifacts before drawing conclusions.

Applies to: Living documentation accessed 2026-09-15; pin plan, client, deployment and tenant policies before use. · Hosted Notion workspace; desktop/mobile required for the cited offline mode.

Contributor: Testedknowhow collaboration research. Commissioned by a Nimbalyst maintainer. Public-source synthesis; no independent review or product execution.

1. Use the small-team-knowledge investigation to specify the required collaboration and access boundaries.
2. With explicit authorization, create an isolated synthetic workspace and named test accounts; do not invite real colleagues or upload private knowledge.
3. Test editing, viewer restrictions, recovery and export with pinned clients and plan; retain sanitized artifacts before drawing conclusions.

Applies to: Living documentation accessed 2026-09-15; pin plan, client, deployment and tenant policies before use. · Google Docs in Google Workspace; Drive storage and organization are a separate target.

Contributor: Testedknowhow collaboration research. Commissioned by a Nimbalyst maintainer. Public-source synthesis; no independent review or product execution.

1. Use the small-team-knowledge investigation to specify the required collaboration and access boundaries.
2. With explicit authorization, create an isolated synthetic workspace and named test accounts; do not invite real colleagues or upload private knowledge.
3. Test editing, viewer restrictions, recovery and export with pinned clients and plan; retain sanitized artifacts before drawing conclusions.

Applies to: Living documentation accessed 2026-09-15; pin plan, client, deployment and tenant policies before use. · Google Workspace Drive, including shared drives where enabled; excludes Docs, Sheets and Slides editing engines.

Contributor: Testedknowhow collaboration research. Commissioned by a Nimbalyst maintainer. Public-source synthesis; no independent review or product execution.

1. Use the small-team-knowledge investigation to specify the required collaboration and access boundaries.
2. With explicit authorization, create an isolated synthetic workspace and named test accounts; do not invite real colleagues or upload private knowledge.
3. Test editing, viewer restrictions, recovery and export with pinned clients and plan; retain sanitized artifacts before drawing conclusions.

Applies to: Living documentation accessed 2026-09-15; pin plan, client, deployment and tenant policies before use. · Hosted Coda document workspace; current branding is Superhuman Docs. Pack behavior is excluded.

Contributor: Testedknowhow collaboration research. Commissioned by a Nimbalyst maintainer. Public-source synthesis; no independent review or product execution.

1. Use the small-team-knowledge investigation to specify the required collaboration and access boundaries.
2. With explicit authorization, create an isolated synthetic workspace and named test accounts; do not invite real colleagues or upload private knowledge.
3. Test editing, viewer restrictions, recovery and export with pinned clients and plan; retain sanitized artifacts before drawing conclusions.

Applies to: Living documentation accessed 2026-09-15; pin plan, client, deployment and tenant policies before use. · Confluence Cloud with the space features enabled; excludes Data Center and Marketplace apps.

Contributor: Testedknowhow collaboration research. Commissioned by a Nimbalyst maintainer. Public-source synthesis; no independent review or product execution.

1. Use the small-team-knowledge investigation to specify the required collaboration and access boundaries.
2. With explicit authorization, create an isolated synthetic workspace and named test accounts; do not invite real colleagues or upload private knowledge.
3. Test editing, viewer restrictions, recovery and export with pinned clients and plan; retain sanitized artifacts before drawing conclusions.

Applies to: Living documentation accessed 2026-09-15; pin plan, client, deployment and tenant policies before use. · Work or school Microsoft 365 tenant; excludes personal-account and Copilot-specific capabilities.

Contributor: Testedknowhow collaboration research. Commissioned by a Nimbalyst maintainer. Public-source synthesis; no independent review or product execution.

1. Use the small-team-knowledge investigation to specify the required collaboration and access boundaries.
2. With explicit authorization, create an isolated synthetic workspace and named test accounts; do not invite real colleagues or upload private knowledge.
3. Test editing, viewer restrictions, recovery and export with pinned clients and plan; retain sanitized artifacts before drawing conclusions.

Applies to: Living documentation accessed 2026-09-15; pin plan, client, deployment and tenant policies before use.; Repository revision 2af30773aecd567f09b346e7b72fc69143144057; deployed release not pinned. · AFFiNE clients with a selected cloud or self-hosted backend; pin edition and team entitlements.

Contributor: Testedknowhow collaboration research. Commissioned by a Nimbalyst maintainer. Public-source synthesis; no independent review or product execution.

1. Use the small-team-knowledge investigation to specify the required collaboration and access boundaries.
2. With explicit authorization, create an isolated synthetic workspace and named test accounts; do not invite real colleagues or upload private knowledge.
3. Test editing, viewer restrictions, recovery and export with pinned clients and plan; retain sanitized artifacts before drawing conclusions.

Applies to: Living documentation accessed 2026-09-15; pin plan, client, deployment and tenant policies before use. · Obsidian core app plus official Sync for shared vaults; Publish is a separately identified add-on. Excludes community collaboration plugins.

Contributor: Testedknowhow collaboration research. Commissioned by a Nimbalyst maintainer. Public-source synthesis; no independent review or product execution.

1. Use the small-team-knowledge investigation to specify the required collaboration and access boundaries.
2. With explicit authorization, create an isolated synthetic workspace and named test accounts; do not invite real colleagues or upload private knowledge.
3. Test editing, viewer restrictions, recovery and export with pinned clients and plan; retain sanitized artifacts before drawing conclusions.

Applies to: Living documentation accessed 2026-09-15; pin plan, client, deployment and tenant policies before use.; Desktop repository revision 14cf1e6efcb4e3bf2d425afe92fdfecc1f603574. · Anytype clients and a chosen Anytype or self-hosted network; per-object permission boundaries are excluded.

Contributor: Testedknowhow collaboration research. Commissioned by a Nimbalyst maintainer. Public-source synthesis; no independent review or product execution.