Tools, systems, and experiments built by following a question far enough to make something you can inspect and use.
Explore the interactive catalogue · Browse the complete directory
Every project receives the same space in the catalogue. Search by a job, filter by an interest, or follow a project's worked example into its source. Libraries, tools, workbenches, experiments, and a design method appear together; those forms describe what is available, not a ranking.
Families and history connects documented parent systems, focused extractions, public continuations, and related adapters. Dates identify particular source experiments where recorded. Snapshot and continuation labels describe the published material, not a claim that development is active or abandoned. Project pages show the repository name alongside the display title.
catalogue.json is the single public data source. Each entry identifies a visitor job, a concrete example, implementation links, scope, and reuse terms. No private source conversations or release-workspace records belong in it.
The optional lineage fields hold an origin summary, public adaptations, scoped dates, and typed relationships with public source links. families defines only documented source or integration groups. Keep thematic interests separate: a shared topic does not establish code ancestry. Missing history stays missing until a specific source or a current decision documents it. lineage.py renders these fields without reading private records.
python build.py --release
python check.pyOpen docs/index.html directly. The generated site works offline, with no external scripts, fonts, accounts, or telemetry. JavaScript adds local search, filters, and theme selection; project pages and the full directory remain readable without it. GitHub Pages serves docs/ from the main branch.
A project earns an independent entry when someone can get useful value from it without adopting its parent. The package must supply the needed code or method, example material, instructions, and an explanation of its limits. A component's origin alone neither requires nor forbids a separate repository.
The full parent implementation remains available. Shared code is preserved where needed for each usable edition; ancestry is explained where it helps someone inspect or maintain the code. Synchronization between editions is a maintenance decision, not an automatic promise that every copy evolves together.
An experiment may offer a controlled comparison or an executable recipe instead of a complete application. The public description says which. Internal release plans and superseded profile drafts are not additional products in the catalogue.
MIT for this catalogue's own code and design. Each listed project carries its own license and third-party notices.