Cartesian Closed Dialectica Categories

Bodil Biering

    Research output: Journal Article or Conference Article in JournalJournal articleResearchpeer-review

    Abstract

    When Gödel developed his functional interpretation, also known as the Dialectica interpretation, his aim was to prove (relative) consistency of first order arithmetic by reducing it to a quantifier-free theory with finite types. Like other functional interpretations (e.g. Kleene’s realizability interpretation and Kreisel’s modified realizability) Gödel’s Dialectica interpretation gives rise to category theoretic constructions that serve both as new models for logic and semantics and as tools for analysing and understanding various aspects of the Dialectica interpretation itself. Gödel’s Dialectica interpretation gives rise to the Dialectica categories (described by V. de Paiva in [V.C.V. de Paiva, The Dialectica categories, in: Categories in Computer Science and Logic (Boulder, CO, 1987), in: Contemp. Math., vol. 92, Amer. Math. Soc., Providence, RI, 1989, pp. 47–62] and J.M.E. Hyland in [J.M.E. Hyland, Proof theory in the abstract, Ann. Pure Appl. Logic 114 (1–3) (2002) 43–78, Commemorative Symposium Dedicated to Anne S. Troelstra (Noordwijkerhout, 1999)]). These categories are symmetric monoidal closed and have finite products and weak coproducts, but they are not Cartesian closed in general. We give an analysis of how to obtain weakly Cartesian closed and Cartesian closed Dialectica categories, and we also reflect on what the analysis might tell us about the Dialectica interpretation.
    Original languageEnglish
    JournalAnnals of Pure and Applied Logic
    Volume156
    Pages (from-to)290-307
    Number of pages18
    ISSN0168-0072
    DOIs
    Publication statusPublished - 2008

    Keywords

    • Dialectica categories
    • Dialectica interpretation
    • Functional interpretation
    • Realizability

    Fingerprint

    Dive into the research topics of 'Cartesian Closed Dialectica Categories'. Together they form a unique fingerprint.

    Cite this