Software search criteria · version 2 (DAP Optimized)

Software Search Criteria

The message below is formatted in Dense AI Protocol (DAP). It tells the assistant what to prefer, what to reject, and how to rank tools, using highly compressed JSON. This reduces token count by ~45% and drastically lowers KV-cache VRAM usage during the prefill phase, preventing "choking" on local 4GB VRAM setups.

Build rules are inherited. Page construction comes from standards.html. This page adds software search rules only. Do not duplicate B01–B12 here; refer back.

The software clock is 90 days. A stable tool can be correct for months without a commit. 365 days is the threshold for likely dead.

The message

Message to AI — copy or paste

Default is DAP (Dense AI Protocol) to save VRAM. Use the toggle above to view the human-readable version. If the copy button fails, click inside the box, select all, and copy manually.

Quick reference

The same rules, compressed. Use this when you are checking a result by eye rather than feeding the box to an assistant.

What gets skipped

What gets ranked highest

The rule table

A01
Arch official repositories top tier.
A02
AUR second tier, with recent votes and comments, PKGBUILD from upstream.
A03
Upstream source third tier, reproducible from upstream alone.
A04
Flatpak, Snap, AppImage, blobs avoided by default.
A05
Proprietary skipped unless explicitly asked; flag contract trap.
A06
Western social media never primary for software.
B01
Reject EULA longer than a short licence header.
B02
Reject forced updates, remote deactivation, feature removal.
B03
Reject subscription, account, or online activation.
B04
Reject geographic or export restrictions.
B05
Prefer GPL, LGPL, MIT, BSD, Apache 2.0, MPL.
C01
Reject opt-out telemetry that cannot be disabled at build time.
C02
Reject phoning home, consentless update checks, remote dependency for local function.
C03
Flag defence or surveillance funding where publicly recorded.
D01
Terminal preferred. TUI > CLI > minimal GUI > Electron.
D02
Reject Electron or web wrapper where native exists.
D03
Prefer one thing well, composable, plain-text config.
D04
Prefer no database or daemon for ordinary use.
D05
Fewer dependencies rank higher.
E01
90-day software clock. 365 days means likely dead.
E02
Check Arch package last update and maintainer. Orphan is a flag.
E03
Check upstream commits, releases, issue responses.
E04
AUR needs recent comments and votes. No comments in a year means unmaintained.
E05
Rolling-release is a feature, not a risk.
F01
State what it does and what it does not do.
F02
One-line install command. If more, say why.
F03
State config and data locations.
F04
Prefer small dedicated tools for niche searches.
G01
Dependency liveness is a hard gate. One missing dependency means the result is not listed.
G02
Verify PKGBUILD source URL resolves, upstream reachable, not flagged out-of-date.
G03
If any dependency is unverifiable, say Dependency chain unverified and do not recommend.
G04
Separate build dependencies from runtime dependencies, verify both.
G05
Never assume a dependency exists. Print it first as its own command.

How to invoke this page

At the start of a software query, paste one line:

apply apps: barkester.net/apps.html

The assistant fetches the page, reads last_verified, applies the DAP rules, and answers in the shape specified. If the page cannot be fetched, paste the contents of the copy box into the chat instead. Same rules, same result, but with significantly lower VRAM overhead.

Build compliance

This page inherits B01–B12 from standards.html and does not restate them. The only local additions are the software search rules above. The header is the barkester.net header, collapsible on devices with a checkbox and a label, so it works with JavaScript off.