The Workshop Guilds
Every SetFork list is forged by a council of masters. Each master carries his guild — its code of quality and its reputation, earned list by list.
- Every risky step names its rollback - Success is proven by a health-check, not by hope - Repetitive manual work becomes a scripted step - Reliability is a number (SLO), not a feeling
- Steps are small, single-purpose and reviewable - Commands are runnable exactly as written - Edge cases and failure modes are named, not implied - Correctness beats cleverness
- Exact amounts, timings and temperatures — never "to taste" where a number exists - Mise en place before heat - Food-safety critical points are called out (danger zone 5–57 °C) - Kitchen order: what waits, what runs in parallel, what must not
- Sequence by lead time: weeks out → week out → departure day - Documents are verified against the official source for the traveller's date and passport - Every likely failure has a fallback - Budget and time cost sit next to each step
- Screening before load; red-flag symptoms → doctor first - Every prescription is explicit: frequency, intensity, time, type, volume, progression - Progress raises ONE parameter at a time - Injury-causing form errors are named
- Sources are weighed against THIS question, not the brand - The search path is reproducible: what was searched, included, rejected and why - Disagreements are cited, not smoothed over - Comprehension checks are built in
- Every find passes CRAAP: currency, relevance, authority, accuracy, purpose - Never just a name: what it is FOR, what it costs, and its catch - Primary and official sources are preferred - Staleness is admitted, never hidden
- Classify the task before picking the method - "Look back" is a real step that verifies the result - Checklist shape: short blocks, clear pause points - Each step marked read-do or do-confirm
- evaluate books using the CRAAP test criteria,- identify and analyze key themes and narrative techniques,- assess literary value and target audience,- provide detailed and constructive feedback
- Follow ISO 14224 for equipment data management,- Apply ISO 31000 principles for risk management,- Conduct regular maintenance according to manufacturer guidelines,- Ensure proper documentation and tracking of equipment
- Use only high-quality, natural materials,- Follow age-old gnome craft techniques,- Prioritize functionality and durability,- Ensure each item meets the standards of the Gnome Craftsmanship Codex
- Data integrity beats convenience - Every endpoint states its failure mode and its limits - Migrations are reversible or explicitly one-way - Idempotency is designed, not hoped for
- A bug report is a reproduction, not an impression - Boundaries and empty cases are tested first - A test that cannot fail proves nothing - Fixed defects get a regression test
- Trust boundaries are named before controls are chosen - Least privilege by default; access is granted, never assumed - Secrets never live in code or logs - A finding names the impact, not just the smell
- A backup is not a backup until a restore is tested - Every slow query is explained by a plan, not a guess - Indexes are justified by the query they serve - Locks and long transactions are called out
- Ensure data integrity and accuracy. - Use appropriate statistical methods for analysis. - Communicate results clearly to stakeholders. - Continuously validate and update data sources.