Experiments Index

ZinxLabs experiments are organized as ongoing inquiries rather than finished projects. Each experiment exists to test a specific claim about how systems behave under constraint.

Experiments are grouped by status, not importance:

  • Active — currently running or under revision

  • Archived — completed, paused, or superseded

  • Failed — explicitly documented breakdowns

Each experiment entry includes:

  • Title and short hypothesis

  • Current status

  • Start date and last revision

  • Primary domain (governance, education, AI, culture, infrastructure)

  • Link to the full experiment record

The index is chronological by default. No ranking or scoring is applied.

Active Experiments

Active experiments represent systems currently under observation. These are live tests, not demonstrations.

Each active experiment page opens with a clear statement of uncertainty:

  • What is being tested

  • Why the test exists

  • What is not yet understood

Active experiments may change without notice. Revisions are logged publicly and timestamped. Incomplete data, open questions, and visible iteration are expected.

Stability is not assumed.

Archived Experiments

Archived experiments are not “successful” by default. They are experiments that have reached a stopping condition.

Common reasons for archiving include:

  • Hypothesis resolved

  • Structural limits reached

  • External constraints encountered

  • Superseded by a revised experiment

Archived experiments remain accessible for reference and comparison. No results are removed, and no conclusions are retroactively edited.

Failed Experiments

Failure is treated as a first‑class research outcome.

Failed experiments are systems that broke in ways that could not be safely revised or meaningfully extended. They are documented explicitly to prevent repetition and to surface hidden assumptions.

Each failed experiment includes:

  • Original hypothesis

  • Conditions under which failure occurred

  • Observed failure modes

  • Why revision was insufficient

  • What the failure revealed

Failures are not buried inside other pages. They are indexed, searchable, and preserved as institutional memory.

Experiment Methodology

ZinxLabs experiments follow a consistent structure to allow comparison across domains.

Each experiment record includes:

  • Hypothesis — the claim being tested

  • Constraints — assumptions, limits, and boundaries

  • Simulation — environment or model used

  • Observation — data, behavior, and anomalies

  • Failure Modes — where and how the system breaks

  • Revision Notes — changes made during testing

  • Outcome — provisional conclusions or open questions

Experiments are designed to surface failure early rather than hide it.

Research Logs

Research logs document thinking in motion. They are not summaries and not conclusions.

Logs may include:

  • Daily or weekly observations

  • Unexpected behavior

  • Rejected assumptions

  • Notes on revision decisions

  • Questions for future testing

Logs are timestamped and immutable once published. Corrections appear as new entries, not edits. This creates a visible trail of reasoning over time.