
Artifice NYC is a curatorial research nonprofit working between creative science and new media fictions. We produce immersive, site-specific showcases and open creative infrastructure (a public archive practitioners build and control), shaping how speculative practice and emerging technology define the way we live.
Sister vocabulary to open source and open access. The claim is methodological, not aspirational: curatorial process operating on documented principles.
Pair it with a noun: open curatorial principles, practice, method. Until open-curatorial-principles.md is drafted it is the category claim under the mission, never the lead in funder materials.
Artifice NYC is a 501(c)(3) curatorial research nonprofit working between creative science and new media fictions, producing immersive, site-specific showcases and open creative infrastructure (a public archive practitioners build and control) that shapes how speculative practice and emerging technology define the way we live.
Most experimental work reaches the public already finished: the process folded away, the false starts cut, the decisions that mattered left out. Artifice shows the rest of it. In Chapters and nodes, work appears while it is still being figured out: in the lab, where the making stays in view (WHITEBOX), and on the stage, where you meet it before anyone explains it (BLACKBOX). We use science fiction as a method, studying the technology already arriving through the futures we imagine for it. A piece might begin as something on a screen and become a room you walk through; the people who made it record that passage in the Artifact Index, deciding what it includes and how it is held.
Decided 2026-09-08: the format is the through line, not the series. A program is conceived as a WHITEBOX and BLACKBOX pairing first, and is not required to belong to a numbered run.

a gallery displaying creative science and material inquiry: biomaterials, chemical processes, and physical transformation in formation. Said in public as the lab.

a stage performing new media fictions : staging immersive, time-based experiences that shape perception. Said in public as the stage.
A Chapter pairs the two inside a single visit, so audiences move between process and experience within a continuous narrative. This dual structure is what differentiates Artifice from galleries and traditional exhibition formats. Both are formats, not stages and not folders. A property carried on the record, so the same work can be shown either way.
Neither series is retired, deleted or renamed. Both keep their folders, their blueprints and their history exactly where they are. [ ENTER ] is not addressed by the decision.

Artifice runs a lab and a stage for artists working with technology, and keeps a public record of how the work gets made.
If a member says it wrong and it still lands, it is working.
Artifice is a 501(c)(3) curatorial research organization shaping and linking artifacts through science fiction.
We have a taxonomy surplus, not a taxonomy problem.
the lab · the stage · the record
The gate: if a term needs brand.artificenyc.org to be understood, it does not go in a press release, an intro email, or someone’s mouth. Program names surface publicly only attached to a concrete thing (an event, an issue, a work), never as an org explainer.
Three days, five simultaneous zones, 20 artifacts, 176 checked in against 394 RSVPs, $2,408.41 revenue split 50/50 with the venue partner. The Scale band in the nodes: Blueprint is derived from it because it is the only edition with a complete record.


Roles are fixed; names are open until filled.
drive_key is the join. An Asana task carries exactly one, in its Drive Key field. Resolve by key or id, never by name or path.
One canonical asset per format, mark and cursive together, straight from brand.artificenyc.org.

Every typed note carries entity: nonprofit or shared. If you cannot say which, stop and ask.
States what is true and when it became true.
An imperative sentence gets read by the next agent as a task it is supposed to do, and the same work gets attempted every session. The missing entity tag is the second bug.
A rule without its mechanism gets rationalized away.
There are few instruction files and you do not edit them casually.
the-map.png in 00_Start Here/, and the-map-global.png for the whole vault.
_kb/CONVENTIONS.md. Ten rules, each with its reason.
Find the board matching the folder you will work in. The numbers match: 02_Operations in Drive is 02 | Operations in Asana.
Anything ambiguous, before you file it.
If a document disagrees with tree.yaml about where something lives, the tree wins.