PulseExploreJournal ClubDebatesTrendingResearchersJournals
Instagram
HomeExploreJournal ClubTrending
Synapse
⌘+K
Synapse
March 3, 20260 citationsOpen Access

Design as Event — The Ontological Incompatibility with Computational Design: A Discipline-Level Demarcation

View Full Paper
TKTheodoros G. kostas

Key Points

  • The aim is to delineate the computational design paradigm using a strict ontological framework.
  • Introduces a divergence matrix to categorize design errors.
  • Defines categories of computation, systems thinking, and UX within design.
  • Analyzes the state-space presupposition and constitution criteria.
  • Establishes forbidden category errors within design.
  • Identifies admissible secondary roles for computation and related paradigms.

Abstract

This paper performs an external institutional demarcation of the computational design paradigm against the discipline-level definition established in the Design as Event corpus. It introduces a strict ontological criterion: state-space presupposition versus state-space constitution. The paper establishes a Divergence Matrix specifying forbidden category errors and admissible secondary roles of computation, systems thinking, UX, and method-centrism. This document forms part of the canonical Design as Event research corpus and functions as an external positioning artifact.

Ask AI
Helpful
Bookmark
Share
View Full Paper

Cite This Study

Theodoros G. kostas (2026) studied this question.

synapsesocial.com/papers/69a67eebf353c071a6f0a8adhttps://doi.org/10.5281/zenodo.18826145
Ask AI
Helpful
Bookmark
Share
View Full Paper

Also Consider

Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context:

  1. 1Design as Event: The Ontological Cut — Why Process, Representation, and Computation Misread Design2026
  2. 2Design as Event — Discipline-Level Definition2026
  3. 3Design as Event: Temporal Articulation and Morphogenetic Reorganization in Computational Design2026
  4. 4Design as Event: Admissibility, Reconfiguration, and Morphogenetic Necessity2026
  5. 5Design as Event — Technical Note: Duration and Framewise Control (v1.0)2026