History

Intervention timeline synthesized from every guide in KNOWLEDGE_GUIDES. Each row is one guide's first action, with the guide itself as the verification artifact. No historical-state recordings exist yet — when they're added, they'll appear below without disturbing the existing rows.

Filter

Pillar (family) Status

Default view shows every entry. Filters are client-only — the full list is in the rendered HTML so search engines and offline readers see it.

Compute Donation Page

Consent-first Web Worker compute for BOINC/Cocoon-style workloads.

AI & Compute hybrid

Best first action

Hover to read the consent explanation, then choose Low or Medium intensity before starting.

When to use

When plugged into power
When the user explicitly consents
When tab visibility and battery are safe
When demonstrating ethical browser compute

Before

Pre-intervention baseline not yet recorded. The guide's source-of-truth row is the baseline artifact.

Verification (after)

Never auto-start compute.
Stop when battery is low or the user leaves.
Expose live stats.
Use workers, never main-thread loops.

Common mistakes to avoid (3)

Starting compute without consent.
Running high intensity on battery.
Claiming BOINC/Cocoon integration is live before real project backends are wired.

Local AI Advisor

wllama local inference with explicit dictionary fallback.

AI & Compute real

Best first action

If bandwidth and power allow, load the smallest model first. Otherwise use dictionary mode knowingly.

When to use

When interpreting tasks
When generating field instructions
When converting recommendations into tasks
When offline and no human expert is available

Before

Pre-intervention baseline not yet recorded. The guide's source-of-truth row is the baseline artifact.

Verification (after)

Prefer operational mode for direct action.
Use Socratic mode for teaching.
Use JSON mode for future automation handoff.
Never treat AI advice as field verification.

Common mistakes to avoid (3)

Loading a 1GB model on weak battery.
Copying AI output into field work without checking maps/sensors.
Assuming dictionary fallback is a live model.

Community, Mutual Aid, and Local Economy

Mastodon, Nostr, Actual Budget, legal aid, TON, BOINC, and Cocoon.

Community & Federation hybrid

Best first action

Use Core Relational first: identify offers, needs, and budget constraints before using token or compute tooling.

When to use

When matching surplus to need
When coordinating volunteers
When tracking time credits
When activating Telegram/TON/BOINC/Cocoon concepts

Before

Pre-intervention baseline not yet recorded. The guide's source-of-truth row is the baseline artifact.

Verification (after)

Keep mutual aid legible before financializing it.
Use Actual Budget for reality checks.
Use Nostr/Mastodon for reach, not private sensitive data.
Treat TON/Cocoon/BOINC panels as setup concepts until real integrations are wired.

Common mistakes to avoid (3)

Confusing UI toggles for real wallet or compute connections.
Putting sensitive legal or personal data on public feeds.
Optimizing token flow before food/water/labor basics.

Federation Mesh: IPFS, BitTorrent, LoRa, ActivityPub

Building resilient communication and data transfer without cloud dependency.

Community & Federation hybrid

Best first action

Map your node\

When to use

When planning data transfer between nodes
When setting up mesh communication for remote sites
When choosing which protocol to use for different data types
When establishing new node connections

Before

Pre-intervention baseline not yet recorded. The guide's source-of-truth row is the baseline artifact.

Verification (after)

Use LoRa for alerts and text only (28km range, low bandwidth).
Use Nostr for signed event broadcasts and small data.
Use BitTorrent for bundles over 10MB.
Use IPFS for permanent, verifiable document storage.
Use ActivityPub for social coordination and mutual aid broadcasts.
Always pin critical IPFS objects on at least 3 nodes.

Common mistakes to avoid (4)

Trying to send large bundles over LoRa.
Assuming one relay publish equals durable storage.
Not verifying checksums on imported bundles.
Using public relays for sensitive operational data.

Legal Aid Templates and Anti-Patent Commons

Offline, do-it-yourself legal infrastructure for sovereign communities.

Community & Federation hybrid

Best first action

Start with the tenant rights template if housing security is at risk — it is the most immediately actionable and has the highest success rate.

When to use

When facing eviction or habitability issues
When asserting riparian water rights
When appealing agricultural zoning decisions
When establishing a community land trust
When filing anti-patent protection for open designs

Before

Pre-intervention baseline not yet recorded. The guide's source-of-truth row is the baseline artifact.

Verification (after)

Customize templates for your jurisdiction before use.
File anti-patents to IPFS before any public disclosure.
Store signed copies locally and on at least two peer nodes.
Consult with a licensed attorney before filing in court.
Document all community designs with date stamps before sharing.

Common mistakes to avoid (4)

Using out-of-jurisdiction templates without local adaptation.
Filing anti-patents after someone else has already filed a patent.
Not keeping local copies of all filed documents.
Assuming templates replace legal counsel in contested matters.

Network Transport and Global Alliances

Nostr relay, IPFS, BitTorrent, LoRa mesh, ActivityPub, and allied organizations.

Community & Federation hybrid

Best first action

Open Federated Swarm, inspect active recovery missions, then review Transport Layer before pledging resources.

When to use

When a peer node needs aid
When choosing a sync transport
When researching allied organizations
When checking federation readiness

Before

Pre-intervention baseline not yet recorded. The guide's source-of-truth row is the baseline artifact.

Verification (after)

Use Nostr for small signed event broadcasts.
Use IPFS/BitTorrent for larger bundles.
Use LoRa for low-bandwidth alerts only.
Verify external alliance links before adopting practices locally.

Common mistakes to avoid (3)

Using one transport for every payload size.
Assuming a relay equals trust.
Broadcasting sensitive personal information.

Drone Swarm Operations

Autonomous seed dispersal, NDVI scanning, and terrain mapping.

Land & Ecology hybrid

Best first action

Verify ArduPilot waypoint file against current Land view GeoJSON. Check battery, GPS lock, and wind before launch.

When to use

When seeding large or inaccessible zones
When plant health assessment requires aerial perspective
Before earthwork construction for baseline mapping
After major interventions for progress verification

Before

Pre-intervention baseline not yet recorded. The guide's source-of-truth row is the baseline artifact.

Verification (after)

Map flight routes before any launch.
Carry manual RTH (Return To Home) override.
Fly NDVI missions at consistent sun angle for comparable data.
Store all flight logs in History with photo attachments.
Use lowest effective altitude to maximize image resolution.

Common mistakes to avoid (3)

Flying seed-bomb routes without verifying drop interval matches seed density targets.
Comparing NDVI images taken at different sun angles without correction.
Neglecting to verify GPS lock before autonomous waypoints.

Land Intelligence: GeoJSON/QGIS

Spatial planning from map features rather than static graphics.

Land & Ecology hybrid

Best first action

Click the feature you intend to work on and read its metadata before opening or completing any related task.

When to use

Before digging or planting
When selecting task zones
When replacing demo data with QGIS exports
When briefing a field crew

Before

Pre-intervention baseline not yet recorded. The guide's source-of-truth row is the baseline artifact.

Verification (after)

Replace the demo GeoJSON with a QGIS export before real earthworks.
Use contour and hydrology layers, not guesswork.
Keep fallback SVG available for degraded environments.
Name every feature with stable IDs so tasks can reference them.

Common mistakes to avoid (3)

Treating the demo GeoJSON as a surveyed field map.
Digging without contour verification.
Using map labels without walking the site.

Mycorrhizae and Seed Bomb Protocol

Biological networking and direct seeding for rapid ecological succession.

Land & Ecology hybrid

Best first action

Inoculate biochar with mycorrhizal spores at 1:100 ratio before field application. Prepare seed bombs at least 24 hours ahead to allow clay binding.

When to use

When recovering bare or degraded soil
After swale construction for immediate berm seeding
When establishing food forest guilds
When bridging gaps between established plant communities

Before

Pre-intervention baseline not yet recorded. The guide's source-of-truth row is the baseline artifact.

Verification (after)

Use Rhizophagus irregularis as primary inoculant — generalist, pairs with 80% of plants.
Add Trichoderma spp. for disease suppression in succession zone 2.
Seed bomb recipe: 40% crimson clover, 20% daikon radish, 15% buckwheat, 15% phacelia, 10% R. irregularis bound in clay.
Map mycorrhizal coverage every 20m grid with soil cores.
Pre-charge biochar with compost tea before myco inoculation.

Common mistakes to avoid (3)

Applying raw (uninoculated) biochar — it will steal nitrogen for 6 months.
Using mycorrhizae in sterile potting mixes where native fungi are absent.
Seed bombing before rain — seeds need moisture within 48 hours of application.

Swales, Chinampas, Terra Preta

Water capture, wetland farming, and carbon-rich soil building.

Land & Ecology hybrid

Best first action

Start with the smallest reversible pilot: one verified contour swale segment or one pilot chinampa bed.

When to use

When flood capture is the bottleneck
After contour verification
When a seasonal pond is stable long enough for chinampa beds
When biomass waste can become biochar

Before

Pre-intervention baseline not yet recorded. The guide's source-of-truth row is the baseline artifact.

Verification (after)

Never build swales off-contour.
Use spillways before extreme rain.
Inoculate biochar before adding to soil.
Document material inputs and labor hours.

Common mistakes to avoid (3)

Raw biochar application that temporarily steals nitrogen.
Oversized earthworks without overflow planning.
Chinampa beds too wide to maintain from the canal edge.

Water Systems: Measurement, Storage, and Quality

Monitoring dissolved O₂, pH, turbidity, rainfall, storage volume, and groundwater.

Land & Ecology hybrid

Best first action

Establish baseline measurements for all 8 water metrics before any intervention. Record location, date, weather conditions, and measurement method.

When to use

Before and after earthwork construction
When establishing baseline water quality
When investigating pollution or contamination
When planning storage infrastructure

Before

Pre-intervention baseline not yet recorded. The guide's source-of-truth row is the baseline artifact.

Verification (after)

Measure dissolved O₂ at multiple depths and times of day.
Target pH 6.5–8.0 for most aquatic ecosystems.
Keep turbidity below 5 NTU — higher values indicate erosion.
Rainfall measurement should be in a standardized gauge away from obstructions.
Track stored volume vs. annual rainfall capture ratio.
Maintain riparian buffer of at least 15m along waterways.

Common mistakes to avoid (4)

Measuring only surface water and ignoring groundwater depth.
Not recording measurement conditions (weather, time, location).
Ignoring seasonal variation when comparing measurements.
Treating single measurements as trends without longitudinal data.

Offline Education: Khan, OpenStax, Wikipedia, Kiwix

Full educational infrastructure that works without any internet connection.

Learning & Fabrication real

Best first action

Set up learner accounts and assign a learning path based on role: Steward → community finance + watershed basics, Field → soil science + ecology, Fabricator → math + physics + CAD basics.

When to use

When teaching new node operators
When schools in the area are disrupted
When learners need self-paced instruction
When the AI tutor needs grounding context for explanations

Before

Pre-intervention baseline not yet recorded. The guide's source-of-truth row is the baseline artifact.

Verification (after)

Use Kiwix for offline content management.
Assign Khan Academy courses that align with task board learning needs.
Use Wikipedia as the first reference before asking Bonsai.
Track active learners and adjust paths based on progress.
Bundle education content with CRK exports for new nodes.

Common mistakes to avoid (3)

Downloading all content at once instead of prioritizing critical subjects first.
Not tracking learner progress or adjusting paths.
Relying solely on AI tutoring without grounding in verified educational content.

OSE GVCS Open Source Fabrication

Build civilization-scale tools at 50–90% below commercial cost.

Learning & Fabrication hybrid

Best first action

Start with the Compressed Earth Brick (CEB) Press — $4,000 vs $52,500 commercial, 92% savings, immediate return on investment through brick production.

When to use

When a critical tool is needed but commercially unavailable or unaffordable
When building local fabrication capacity is a priority
When teaching fabrication skills to community members
When replacing cloud-dependent supply chains with local production

Before

Pre-intervention baseline not yet recorded. The guide's source-of-truth row is the baseline artifact.

Verification (after)

Verify FreeCAD files are the latest version before cutting metal.
Organize community build days — 50 machines require 50 teams.
Document every modification to share back to OSE community.
Build jigs and fixtures before the machines — they multiply accuracy.
Start with hand tools + welder before CNC table.

Common mistakes to avoid (4)

Skipping CEB Press for LifeTrac — CEB generates materials for all other builds first.
Modifying designs without testing load ratings.
Not budgeting 2–3× longer than estimated for first build of any machine.
Treating OSE docs as finished products — they are living documents requiring local adaptation.

R Statistical Analysis Notebooks

Local data science for soil, water, biodiversity, and economy.

Learning & Fabrication hybrid

Best first action

Open soil_carbon_tracker notebook, import your core sample CSV, run the SOM (soil organic matter) regression to establish baseline before any amendment.

When to use

After collecting soil cores or water samples
After drone NDVI flights
Before and after major interventions for comparison
When generating reports for peer nodes or allied organizations

Before

Pre-intervention baseline not yet recorded. The guide's source-of-truth row is the baseline artifact.

Verification (after)

Version control all notebooks with Git.
Keep raw data separate from processed data.
Generate before/after comparison plots for every intervention.
Share notebook outputs as PDF bundles with CRK exports.
Use local R installation — no cloud dependency.

Common mistakes to avoid (3)

Running analysis without establishing baseline measurements first.
Treating statistical significance as ecological significance — always ground-truth.
Not sharing notebook source code with the community — reproducibility requires shared methods.

BioMetriX BWWI Scoring

A deterministic score for watershed wealth and resilience.

Operations Core hybrid

Best first action

Click the weakest metric row to read its definition, target range, and improvement guidance.

When to use

When deciding what task matters most
After completing a field intervention
When comparing this node to peer nodes
When explaining node health to new members

Before

Pre-intervention baseline not yet recorded. The guide's source-of-truth row is the baseline artifact.

Verification (after)

Use the bottleneck pillar to prioritize work.
Treat confidence/provenance badges as part of the score.
Re-measure after interventions rather than assuming improvement.
Keep BWWI reproducible: metric state should define score.

Common mistakes to avoid (3)

Optimizing easy metrics instead of the limiting factor.
Trusting low-confidence or stale measurements without field verification.
Comparing nodes across different bioregions without context.

Home Command Center

The first 10-second read of node health and urgency.

Operations Core real

Best first action

Check the bottleneck pillar and open the highest-impact task before browsing lower-priority panels.

When to use

At the start of every work session
Before assigning labor
When a crisis alert appears
When switching operator roles

Before

Pre-intervention baseline not yet recorded. The guide's source-of-truth row is the baseline artifact.

Verification (after)

Use the Operative Lens selector first: Steward, Field Team, or Fabricator.
Treat the emergency banner as a mission queue, not decoration.
Use BWWI trend as a health signal, not a moral score.
Open History after major actions to confirm the intervention was logged.

Common mistakes to avoid (3)

Chasing high-looking metrics while the bottleneck remains unresolved.
Ignoring role lens context and overloading one user with all priorities.
Treating simulated metrics as sensor-certified field truth.

Intervention History

The node memory and audit trail.

Operations Core hybrid

Best first action

Filter to completed tasks and review the pillar shift chart for the last successful intervention.

When to use

After every completed task
Before repeating a previous intervention
When exporting playbooks
When proving impact to a peer node

Before

Pre-intervention baseline not yet recorded. The guide's source-of-truth row is the baseline artifact.

Verification (after)

Attach verification photos or CIDs when possible.
Use notes to preserve local knowledge.
Do not edit history; append corrections instead.
Export history with CRK bundles for peer learning.

Common mistakes to avoid (3)

Treating history as clutter instead of institutional memory.
Failing to attach evidence.
Deleting logs that explain why a design changed.

Self-Improving Task Board

The execution layer that turns data into field work.

Operations Core real

Best first action

Sort by impact, open the top critical task drawer, read steps/tools, then claim only if you can finish or hand it off clearly.

When to use

When starting a work day
When assigning volunteers
When a bottleneck is identified
When converting AI guidance into action

Before

Pre-intervention baseline not yet recorded. The guide's source-of-truth row is the baseline artifact.

Verification (after)

Use the detail drawer before acting.
Capture evidence notes before marking complete.
Bundle nearby tasks into field routes.
Avoid claiming too many tasks at once.

Common mistakes to avoid (3)

Clicking complete without field evidence.
Claiming tasks to collect credits but not doing the work.
Ignoring dependencies like tools, weather, or labor availability.

CRK, Bundles, Checksums, and Sync Queue

Portable node replication and tamper-evident offline transfer.

Security & Reboot real

Best first action

Export a bundle after a meaningful work session, then verify the checksum on import at the receiving node.

When to use

Before moving data by USB
After completing major interventions
When flushing queued Nostr sync events
When cloning or teaching another node

Before

Pre-intervention baseline not yet recorded. The guide's source-of-truth row is the baseline artifact.

Verification (after)

Do not import bundles with failed checksums.
Keep Nostr disabled until you intend to publish.
Use owned keys in production, not ephemeral localStorage keys.
Record receipts in History.

Common mistakes to avoid (3)

Assuming export equals backup if the file is never copied off-device.
Clearing the sync queue before confirming receipt.
Treating one relay publish as durable federation.