⏾ Concept Map

Record of filler definitions

|↑| Records | Record of filler definitions | Record of filler definitions query | Record of filler definitions sleuth

Everything that enters the map is assumed to need an explanation, at least. One of the standard maintenance queries checks each concept for lack of an incoming |1st| entry and sounds out if it finds any matches.

There are two ways to defuse this:

  1. If the concept has the symbol of a predefined set, or is a non-forked mutant version of a predefined set, it gets forgiven. These display This page intentionally left blank. The reasoning is that they’re mainly used for navigation, so they get created/deleted too quickly to keep up defining each one, and that their predictable names and relationships render a definition superfluous anyway.
  2. If padded with a filler entry, the concept then naturally passes the check.

This page tracks those cases where I decided it would be better to pad the page than to strive for a definition. It’s usually such that these are sets which are merely names for grouping their members. It’s always such that the idea behind the name is easily understood from the surrounding context. (When I don’t have a definition on hand but recognize that the idea still needs one, it gets a placeholder instead.)

Pile

Uncharacterized

Thing-words: Software and the command, etc, which summons it. Can be understood by comparison with the software. Cannot share the software’s definition, because they’re not quite exactly the same thing. Sometimes documentation is available to define the command (etc), but often not.

Phantoms

SUMMARY

Number of bullets: 39

Compare to number reported by Record of filler definitions query