Files
ZIPs/ZIPs/zip-0510-species-protection-monitoring.md
zeekay 29a22c6239 One source of truth for a ZIP's status, and a status each ZIP earns
The same fact lived in five hand-kept places and they all disagreed. The ZIP
frontmatter held 156 rows; README's table held 18; INDEX.md held 144;
docs/zip-index.json and docs/site/zip-index.json held 16 each. Both generators
were last run when the corpus had 16 ZIPs and went on reporting success against
156, because neither could tell a truncated read from a small repo.

scripts/index.py replaces both. It reads the frontmatter, writes README's table,
and refuses when a ZIP has no frontmatter, carries a status outside the
vocabulary, disagrees with its own filename, shares a number, requires a ZIP
that does not exist, or when the corpus has shrunk below a recorded floor. CI
runs it with --check. INDEX.md, both zip-index.json files, docs/site/ and the
root index.html that redirected into it are gone; the site already reads
ZIPs/*.md directly through docs/lib/source.ts.

Eight status values collapse to three. Draft: proposed, no implementation, or an
experiment — an ordinary resting place for a research network. Final: the thing
exists in code. Living: never finalises. Active on a registry became Living;
Active on a completed adoption became Final.

Status now follows the code. 22 are Final because a repository holds the work:
the chain (0015), KMS (0014), teleport (0802), replication (0803), PQ (0005),
genesis (0002), brand adoption (0031), and the AI surfaces that exist —
chat, memory, aci, jin, search, mcp, operative, bitdelta, distillation, and the
published Zen VL/Live/Guard/Translator/Coder models. 113 are Draft, and that is
the honest number: 19 of 28 repository: fields named repos that do not exist,
and the conservation-DeFi, NFT, gaming and DeSci families have Lean proofs and
papers but no contracts or services behind them.

Deleted, with reasons:
  0001, 0003  HLLM and Eco-1/z-JEPA. ZIP-0010 supersedes both and ZIP-0418
              already carries HLLM in full.
  0009        restates ZIP-0427 with no new mechanism.
  0013        asserts Zoo is chain 122, Lux 120, Hanzo 121. They are 200200,
              96369 and 36963. Correcting the map leaves nothing, and its
              supersedes: ZIP-2, ZIP-5 pointed at unrelated proposals.
  0038, 0039  a BSC token-history record and the re-mint migration it feeds.
              A migration path is not a specification of what Zoo is.
  0200        a second ZRC-721 beside ZIP-0701. One standard, one number; 0701
              keeps its place beside ZRC-20 and ZRC-1155.
  0407        calls itself the precursor to Zoo Gym, which is ZIP-0434.
  0433        a summary of ZIP-0011, which is the specification.
  0900        a version chronology, and the only file with no frontmatter.

The 120/121/122 chain-id map appeared in ZIPs 0007 through 0014 and is now the
real one everywhere. requires: had four spellings and now holds ZIP numbers
only; HIP and LP references moved to related-hips and related-lps.

The site builds 148 pages. @hanzo/design moves 0.5.21 to 0.5.25: the older
package shipped files named Zen-Variable.woff2 whose name table said Geist,
vendor VRCL, so the page asked for Zen and painted Geist. The faces the build
now emits name themselves Zen and carry both copyright lines.

pages.yml is removed. GitHub Pages is disabled on this repository, so every run
since May either failed at configure-pages or hung until cancelled. The
Dockerfile served the repository verbatim and relied on the docs/site/ explorer
that is now gone; it builds and serves docs/out instead.
2026-08-28 18:22:02 -07:00

8.4 KiB

zip, title, tags, description, author, discussions-to, status, type, originated, traces-from, follow-on, created, requires
zip title tags description author discussions-to status type originated traces-from follow-on created requires
510 Species Protection & Monitoring
conservation
species
monitoring
technology
Framework for species protection initiatives and monitoring programs. Zoo Labs Foundation (@zoolabs) https://github.com/zoolabs/zips/discussions Living Meta 2021-10 Whitepaper section 03 (Sustainability)
zoo-wildlife-tracking
2025-12-17
500
501

ZIP-510: Species Protection & Monitoring

Abstract

This ZIP establishes the framework for Zoo Labs Foundation's species protection and monitoring initiatives. It defines priority-setting criteria, monitoring methodologies, technology deployment standards, and success metrics for species-focused conservation work.

Species Prioritization

Priority Criteria

Criterion Weight Description
Conservation status 30% IUCN Red List category
Uniqueness 20% Evolutionary distinctiveness
Feasibility 20% Likelihood of success
Opportunity 15% Partner/site availability
Technology fit 15% AI/tech applicability

Conservation Status Scoring

IUCN Category Score
Critically Endangered (CR) 5
Endangered (EN) 4
Vulnerable (VU) 3
Near Threatened (NT) 2
Data Deficient (DD) 3 (high uncertainty value)
Least Concern (LC) 1

Priority Species Categories

Category Definition Examples
Flagship High-profile, ecosystem representatives Great apes, elephants
Keystone Disproportionate ecological role Apex predators, pollinators
Indicator Health of ecosystem Amphibians, corals
Umbrella Protection benefits many species Wide-ranging species
Edge Evolutionarily distinct EDGE species

Monitoring Methodologies

Survey Methods

Direct Observation

Method Application Technology
Line transects Population density GPS, data apps
Point counts Species presence Audio recording
Focal follows Behavior, health Video recording
Mark-recapture Population size Individual ID

Remote Sensing

Method Application Technology
Camera traps Presence, occupancy AI species ID
Acoustic monitoring Vocal species Bioacoustic AI
Satellite tracking Movement, range GPS/Argos tags
Drone surveys Population counts, habitat AI image analysis

Genetic Methods

Method Application Technology
eDNA Aquatic species presence Metabarcoding
Non-invasive sampling Population genetics DNA analysis
Tissue banking Conservation genetics Biobanking

Monitoring Protocol Standards

Protocol Requirements

Element Requirement
Objectives Clear, measurable goals
Design Statistically robust sampling
Methods Standardized, repeatable
Analysis Pre-specified approach
Reporting Consistent format

Data Collection Standards

Standard Implementation
Species ID Verified by expert or AI confidence >95%
Location GPS coordinates (appropriate precision)
Date/time Standardized format
Observer Recorded for all observations
Effort Systematic effort tracking

AI-Assisted Monitoring

Species Recognition Models

Model Type Application Performance Standard
Image classification Camera trap ID >95% top-1 accuracy
Object detection Wildlife in imagery >90% mAP
Individual ID Re-identification >85% accuracy
Sound classification Bioacoustic ID >90% accuracy

Deployment Standards

Standard Requirement
Validation Local validation dataset
Human review QA on sample of outputs
Continuous improvement Retrain with local data
Uncertainty flagging Flag low-confidence detections

Protection Programs

Anti-Poaching Technology

Detection Systems

Technology Application Integration
Camera networks Intrusion detection Real-time alerts
Acoustic sensors Gunshot, chainsaw detection Rapid response
Satellite monitoring Large-area surveillance Change detection
Drone patrol Active monitoring AI-guided routes

Response Integration

Component Implementation
Alert system Real-time notification to rangers
Response coordination GPS-guided dispatch
Incident logging Automated record keeping
Analysis Pattern recognition for prevention

Health Monitoring

Wildlife Health Surveillance

Component Implementation
Routine health checks Protocol-based assessments
Disease detection AI-assisted diagnostics
Outbreak response Early warning systems
One Health integration Human-wildlife-ecosystem health

Welfare Standards

For captive/managed populations:

Standard Requirement
Five Domains Nutrition, environment, health, behavior, mental
Assessment frequency Regular welfare scoring
Intervention thresholds Defined action triggers

Data Management

Species Data Standards

Data Type Standard
Taxonomy IUCN/ITIS standard names
Location WGS84 coordinates
Observation Darwin Core standard
Genetic GenBank/BOLD submission

Data Sharing

Data Category Sharing Approach
Occurrence data GBIF contribution
Population data Species-specific databases
Genetic data GenBank, BOLD
Sensitive data Restricted access (poaching risk)

Sensitive Species Protection

Protection Measure Implementation
Location fuzzing Reduce coordinate precision
Access control Restricted to authorized users
Need-to-know Only share when necessary
Legal protection Comply with species protections

Partnerships

Partner Types

Partner Role
Government agencies Policy, enforcement, permits
Protected area managers Site access, coordination
Research institutions Science, expertise
Local NGOs Community links, implementation
Indigenous communities Traditional knowledge, stewardship

Partnership Standards

Standard Requirement
Data agreements Clear ownership and use terms
Co-authorship Appropriate credit
Benefit sharing Equitable benefits
Capacity building Knowledge transfer

Success Metrics

Species-Level Metrics

Metric Target
Status improvement Downlisting on IUCN Red List
Population stability Stable or increasing trend
Range maintenance No range contraction
Genetic health Maintained diversity

Program-Level Metrics

Metric Target
Species monitored 100 priority species
Detection accuracy >90% for target species
Response time <30 min for poaching alerts
Partner satisfaction >80% positive rating

Technology Metrics

Metric Target
Deployment uptime >95% operational
Data quality <5% error rate
Model accuracy >90% for deployed models
User adoption >80% of trained users active
  • ZIP-500: ESG Principles for Conservation Impact
  • ZIP-501: Conservation Impact Measurement
  • ZIP-520: Habitat Conservation
  • ZIP-530: Community Partnerships & FPIC
  • ZIP-540: Research Ethics & Data Governance

Changelog

Version Date Changes
1.0 2025-12-17 Initial draft

Copyright and related rights waived via CC0.