Surface
Question: What is visible?
Output: A short observation note, photo point, and named concern.
Knowledgeability is re-evaluated here as depth plus scope: what is visible, what functions, what relationships are affected, how the system behaves over time, and whether it can be responsibly held in public trust or regional collaboration.
A design is not mature just because it works once. It becomes trustworthy when it is observed across weather, seasons, maintenance cycles, legal constraints, habitat effects, and community responsibilities.
Question: What is visible?
Output: A short observation note, photo point, and named concern.
Question: What does it do?
Output: Inputs, outputs, dependencies, maintenance, and failure modes.
Question: Who or what is affected?
Output: Neighbor, wildlife, water, soil, governance, and equity impacts.
Question: How does it behave over time?
Output: Seasonal, storm, drought, heat, night, migration, and succession review.
Question: Can it be responsibly held?
Output: Documentation, budgets, permissions, public benefit, and adaptation plan.
Bench prototypes can be forgiving; underground rooms, parcels, regional nonprofit allocations, and land trust decisions need heavier documentation, stewardship reserves, and qualified review.
Risk lens: Low cost, quick learning; still needs fire, water, and mold safeguards.
Risk lens: Requires air quality, emergency exit, drainage, and trip-safety checks.
Risk lens: Requires utility locating, permits, soil stability, neighbor effects, and maintenance reserves.
Risk lens: Requires governance, public benefit clarity, data sharing, and conflict repair.
Risk lens: Requires legal, tax, accounting, insurance, ecological, and board review.
Each facet is written as a practical knowledge unit: a focus, health signals, and elementary actions that can be recorded in the regional network before larger commitments are made.
Health signals
Elementary actions
Health signals
Elementary actions
Health signals
Elementary actions
Health signals
Elementary actions
Health signals
Elementary actions
Health signals
Elementary actions
Health signals
Elementary actions
Health signals
Elementary actions
If a system has only been seen once, keep it at prototype scale. If it has passed seasonal, safety, community, maintenance, and documentation review, then consider parcel, regional, or land-trust scale.
Apply this to systems