APPL.OPS SYSTEM ACTIVE CYCLE 07 / ACTING ON YOUR BEHALF UTC 00:00:00 Join / Support
APPL / Artifacts

Primary encounter surfaces, not side outputs

APPL uses inspectable objects, decision environments, workshops, software, and public encounters to make governance questions tangible.

SimulationsPrototypesSoftwareEvents

Artifact logic

Why artifacts
Artifacts / logic

Artifacts are not side outputs. They are APPL’s primary policy-comprehension and policy-development surfaces. The institution uses inspectable objects, decision environments, and public encounters to make governance questions tangible before they harden into default systems or crisis conditions.

Papers, briefings, and essays remain part of APPL’s work, but they should be read as synthesis grounded in encounters, prototypes, simulations, and interpretation cycles rather than the dominant identity of the institution.

Primary encounter formats

What APPL builds
Primary formats A
  • Tabletop games and simulation kits
  • Software prototypes and agentic-system experiments
  • UX artifacts and interactive systems
  • Future incident reports and governance prototypes
  • Constitutional mockups and decision environments
  • Workshop kits, seminar formats, and salon structures
  • Exhibitions, screenings, gatherings, and pop-ups
  • Experiential collaborations with institutions, companies, and cultural partners

Derivative synthesis outputs

What follows the encounter
Derivative outputs B
  • White papers
  • Essays
  • Blog posts
  • Briefings
  • Teaching materials
  • Public reports
  • Lecture and screening notes

Evaluation questions

What each artifact should answer
Evaluation C
  • What future condition or governance question is being made tangible?
  • Which audience is meant to encounter it?
  • What becomes recognizable through the encounter?
  • What synthesis, policy development, product adaptation, or public understanding should follow?