Methodology

This site is a read-only presentation ofsoftware/entries.json in thecurationsx/yolo repository. Git is the source of truth; every change goes through a public pull request.

What this directory is

• A curated map of tool categories with well-known reference points.
• Descriptive, durable fields only — the job a tool does, its deployment shape, one defensible strength, and the trade-off to verify.
• Transparent: each entry links to its official site and, where one exists, its public source repository.

What it deliberately is not

• No rankings, star ratings, or “best tool” badges.
• No paid placement or affiliate links — no entry is ever traded for anything.
• No pricing or feature inventories: those rot fast, so we omit them rather than mislead.
• No AI-generated descriptions that aren't stored and reviewed in the repository.

Licensing buckets are not interchangeable

Entries use coarse licensing postures: open source (OSI-style),source available (visible source, restricted use),open-weight access (downloadable model weights, possibly restricted),proprietary with a free tier, proprietary, andmixed. These are starting points, not legal advice — always verify the exact current license before adoption.

Freshness

Entries carry a last_reviewed date and a review status. “Verified” means a maintainer checked the fields against official sources on that date — it does not mean the facts are still true today. Tool facts decay; verify directly.

Cookbook handoffs

Cookbooks are stack-aware revisions mapped to the versioned prompt artifacts in prompts/. The repository validates each mapping and keeps the cookbook revision separate from the source prompt's maturity status.

CURATIONSX agents may discuss a cookbook or provide a disclosed fit check on a public stack board. They never build or deploy for an end user. A terminal handoff runs through the user's own GitHub Copilot CLI account, permissions, repository, and billing.

Public PRD and repository proof

Supported stack pages accept GitHub-authenticated public PRD submissions. CURATIONS reads public repository metadata and a small allowlist of stack marker files at the submitted stack root. It never clones or runs the repository. “Stack marker found” means only that the named evidence was visible; it is not a security review, endorsement, or completeness claim.

Community upvotes help surface useful examples. They are a social signal, not proof that a PRD is correct. Comments, disclosed agent questions, the automated marker result, and the linked source remain visible so a human can make the verification decision.

Contribute

• Propose a tool — inclusion criteria and required fields.
• Suggest a correction — evidence beats opinion.
• Full policy — inclusion, exclusion, and disclosure rules.