# Foraging
Foraging covers the practical knowledge, vocabulary, decisions, and field judgment needed to recognize, collect, prepare, and preserve wild foods without turning uncertainty into a medical emergency. It includes plants, fungi, seaweeds, and other locally gathered foods, while recognizing that each group has different identification and contamination hazards. This page defines the topic broadly so the wiki can accept future manuals, diagrams, checklists, regional guides, and local examples without narrowing the subject around a single document.
At this level of the library, the subject should be understandable to non-specialists and usable in difficult conditions. At A0, the subject must be usable under stress with little infrastructure, little time, and uneven training.
Food topics connect survival, health, labor, ecology, storage, and community planning. A useful food page must help readers think across seasons, not only recipes or crops. Foraging can add diversity and micronutrients, but it is rarely a reliable substitute for known stores, cultivated food, or a tested ration plan.
For InfoPreserver, foraging should be treated as a working capability rather than a label. A reader should be able to understand what problem the topic solves, what conditions make it harder, what signs or measurements matter, what mistakes are common, and when the issue belongs in a more specialized folder.
Foraging requires positive identification, local seasonal knowledge, and strict avoidance of look-alike species. A photograph, a folk name, a smell, an animal eating the plant, or a claim that a plant is "usually safe" is not enough. Use several independent features: growth form, leaves, stem, flowers or fruit, underside, habitat, season, and a current regional reference. Record the scientific name when possible because common names change from place to place.
When identification is uncertain, do not taste-test the specimen. Set it aside, preserve a labeled sample or photograph if that can be done safely, and ask a trained local botanist, mycologist, extension specialist, poison center, or other qualified authority. An emergency food plan should assume that an unfamiliar specimen is unavailable.
Mushrooms deserve a separate warning because edible and poisonous species can look alike, common names are unreliable, and serious poisoning can occur from a small serving. Do not use the old rule that a mushroom is safe if animals eat it, if it peels, if it changes color, or if it passes a home "test." There is no universal kitchen test that makes an unknown mushroom safe.
Use a regional mushroom course, supervised field training, and several current references before collecting for food. Treat historical mushroom books as identification history and vocabulary, not as current medical or culinary authority. Do not rely on a guide from another continent or climate. If poisoning is suspected, preserve the specimen or meal if safe, contact emergency services or the local poison center immediately, and do not wait for symptoms to become severe.
Fungi also have non-food value. Some are decomposers, some form mycorrhizal relationships, and some provide tinder, dyes, or other materials. A mushroom can be useful to study without being a food candidate.
Plants may be edible in one part, at one growth stage, or after a particular preparation while another part or stage is harmful. Shellfish and seaweeds add water-quality, tide, algal-bloom, and local closure hazards. Insects and other animal foods require separate attention to allergens, parasites, contamination, and lawful collection. Keep these categories distinct in training and records rather than treating "wild food" as one method.
Avoid roadsides, industrial sites, sprayed land, mine tailings, flood deposits, sewage-affected water, and any location with an unknown contamination history. Rinse or process known foods according to a trusted regional method, but remember that cleaning does not remove every heavy metal, pesticide, biotoxin, or systemic plant toxin.
Get permission where required and respect protected species, sacred places, seasonal closures, and local harvesting rules. Take only what can be used, leave healthy parent plants and reproductive structures, avoid trampling surrounding habitat, and rotate collection areas. For roots, bark, bulbs, and whole plants, the population may be damaged even when the visible harvest looks small. For mushrooms, use the local rule for cutting or lifting and never rake habitat unless the governing authority explicitly permits it.
The aim is a repeatable food source, not a one-time extraction. Record abundance and return visits so the community can see whether collection is reducing the resource.
Treat gathered foods as perishable unless a tested preservation method says otherwise. Use clean water and utensils, keep raw and prepared foods separate, cool or dry promptly, and label the species, date, place, and preparation. Do not create a new preservation method during an emergency by guessing at acidity, heat, drying time, or storage life.
Historical sources often describe useful observation, seasonal timing, and low-infrastructure preparation. They may also contain obsolete taxonomy, incomplete toxin knowledge, or advice that is unsafe under current standards. Compare them with current food-safety and poison-control guidance before teaching or eating from them.
Future additions should explain foraging in a way that a reader can evaluate, teach, and adapt. Good candidates include regional plant and mushroom field guides, ethnobotanical references, checklists, illustrated procedures, training notes, poison-safety guidance, tables of warning signs, preservation references, and public-domain or open-license manuals.
Avoid narrow documents that only mention the topic in passing. If a future PDF belongs partly here and partly somewhere else, keep one primary copy and add cross-links from the related pages. When a source is technical, add a short orientation note explaining prerequisite skills and the A-level where it becomes fully usable.
This page is currently placed in A0 Survival Baseline. If later documents prove that the topic needs simpler emergency treatment or a more advanced technical treatment, it can be split into lower- and higher-level pages without losing this broad orientation.
Path: 10_A0_Survival_Baseline/Core_Survival/Foraging
Page type: Detailed topic guide
Current direct documents: 6 documents
Documents in this branch: 6 documents
Child folders: 0 folders
Navigation: Parent