Skill output should contain no filler; every line of a run-summary should carry weight.

Entities in the same semantic neighborhood but without a typed relation to this one — candidates for new edges or unrecognized duplicates.

• A skill should do its work and stop, avoiding performative complexity and multi-stage flows when single-pass suffices.claim0.766
• A skill's output length should match task complexity—short tasks produce short reports, long tasks produce structured hierarchical reports.claim0.763
• Parallel sub-tasks within skills and across skill families should produce parallel outputs for legibility.claim0.751
• Skills should interconnect with each other rather than operate independently; output of one feeds another.claim0.742
• Every skill should have one unmistakable thing it does; sprawling skills violate the Strong Centers principle.claim0.739
• Proving that a program meets accomplishment specifications must be based on assumptions about the world, the information it makes available to the program and the effects of the program's actions as well as on facts about the program itself.claim0.735
  Claim about the nature of accomplishment verification.
• Perhaps we will need three levels of specification, internal, input-output and accomplishment.hypothesis0.734
  Speculation about specification hierarchy.
• About Blank's 'About' page should function as a navigable thinker-and-framework graph rather than prose explanation.claim0.732