<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>CultureOS — Updates &amp; Research</title>
    <link>https://cultureos.dev</link>
    <description>An AI-native practice for cultural institutions, smaller museums, artist foundations, and archives.</description>
    <language>en-us</language>
    <lastBuildDate>Mon, 05 Oct 2026 18:47:17 GMT</lastBuildDate>
    <atom:link href="https://cultureos.dev/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CultureOS: An AI-native practice for cultural institutions</title>
      <link>https://cultureos.dev</link>
      <guid isPermaLink="true">https://cultureos.dev</guid>
      <pubDate>Mon, 05 Oct 2026 18:47:17 GMT</pubDate>
      <description>Grow your capacity before you grow your staff.  We help smaller museums, artist foundations, and archives modernize, from the website to the server to the catalogue raisonné, at a fraction of the traditional cost.</description>
    </item>
    <item>
      <title>What we do: Not for the day something fails. For all the years after.</title>
      <link>https://cultureos.dev/what-we-do</link>
      <guid isPermaLink="true">https://cultureos.dev/what-we-do</guid>
      <pubDate>Mon, 05 Oct 2026 18:47:17 GMT</pubDate>
      <description>You know something has to change. We know what first. Nobody calls us in an emergency. They call because the institution should work better than it does, and no one has had time to see the whole of it. We see it first. Then we bring what you already have up to date and make it work as one, so nothing depends on one person remembering.</description>
    </item>
    <item>
      <title>Digital transformation: The systems people touch every day.</title>
      <link>https://cultureos.dev/what-we-do/digital-transformation</link>
      <guid isPermaLink="true">https://cultureos.dev/what-we-do/digital-transformation</guid>
      <pubDate>Mon, 05 Oct 2026 18:47:17 GMT</pubDate>
      <description>Website, CMS, newsletter, donor records, volunteers, social tools. In most small institutions they were bought one at a time, by different people, for different reasons, and none of them talk. We rebuild them so they do, and so one person can run them.</description>
    </item>
    <item>
      <title>Infrastructure upgrade: The systems nobody sees until they fail.</title>
      <link>https://cultureos.dev/what-we-do/infrastructure</link>
      <guid isPermaLink="true">https://cultureos.dev/what-we-do/infrastructure</guid>
      <pubDate>Mon, 05 Oct 2026 18:47:17 GMT</pubDate>
      <description>Servers, cloud, backups, accounts, security. Many institutions run critical operations on systems nobody fully documents anymore. We move them to current ground, secure them, write them down, and prove they survived the move.</description>
    </item>
    <item>
      <title>Infrastructure upgrade: The systems nobody sees until they fail.</title>
      <link>https://cultureos.dev/what-we-do/infrastructure-upgrade</link>
      <guid isPermaLink="true">https://cultureos.dev/what-we-do/infrastructure-upgrade</guid>
      <pubDate>Mon, 05 Oct 2026 18:47:17 GMT</pubDate>
      <description>Servers, cloud, backups, accounts, security. Many institutions run critical operations on systems nobody fully documents anymore. We move them to current ground, secure them, write them down, and prove they survived the move.</description>
    </item>
    <item>
      <title>Diagnostic: You don’t know where to start. We do.</title>
      <link>https://cultureos.dev/what-we-do/diagnostic</link>
      <guid isPermaLink="true">https://cultureos.dev/what-we-do/diagnostic</guid>
      <pubDate>Mon, 05 Oct 2026 18:47:17 GMT</pubDate>
      <description>We watch how the work actually moves: where time goes, what systems exist, where knowledge is trapped, what should change first. It ends in a written plan and an order of work that you can carry out with or without us.</description>
    </item>
    <item>
      <title>How we work: Four steps. The fourth is optional.</title>
      <link>https://cultureos.dev/what-we-do/how-we-work</link>
      <guid isPermaLink="true">https://cultureos.dev/what-we-do/how-we-work</guid>
      <pubDate>Mon, 05 Oct 2026 18:47:17 GMT</pubDate>
      <description>Every engagement begins with a diagnostic. Most continue into a pilot and a build. Some ask us to stay a while. None are locked in.</description>
    </item>
    <item>
      <title>In practice: One institution. Front to back, and a laboratory.</title>
      <link>https://cultureos.dev/work/tom-of-finland-foundation</link>
      <guid isPermaLink="true">https://cultureos.dev/work/tom-of-finland-foundation</guid>
      <pubDate>Mon, 05 Oct 2026 18:47:17 GMT</pubDate>
      <description>An artist-endowed foundation in Los Angeles with a small staff, a large archive, and systems that had grown one purchase at a time. The practice modernized how the institution runs. The Labs are using its archive to build a catalogue raisonné methodology.</description>
    </item>
    <item>
      <title>For artist foundations &amp; estates: The archive is the estate.</title>
      <link>https://cultureos.dev/institutions/artist-foundations</link>
      <guid isPermaLink="true">https://cultureos.dev/institutions/artist-foundations</guid>
      <pubDate>Mon, 05 Oct 2026 18:47:17 GMT</pubDate>
      <description>Most artist-endowed foundations run on a board, a trustee, and one or two people who know where everything is. The oeuvre is large, the records are paper, and the catalogue raisonné everyone agrees is needed has always cost too much. We begin where you actually are, which is often before any system exists.</description>
    </item>
    <item>
      <title>For smaller museums: Enterprise complexity. A lean staff.</title>
      <link>https://cultureos.dev/institutions/museums</link>
      <guid isPermaLink="true">https://cultureos.dev/institutions/museums</guid>
      <pubDate>Mon, 05 Oct 2026 18:47:17 GMT</pubDate>
      <description>Most smaller art museums run with twenty-five people or fewer, and few have anyone on the leadership team whose job is digital. The collections system, the donor database, and the image archive were bought in different decades and have never spoken to each other. Nothing needs replacing. Everything needs connecting.</description>
    </item>
    <item>
      <title>For smaller museums: Enterprise complexity. A lean staff.</title>
      <link>https://cultureos.dev/institutions/smaller-museums</link>
      <guid isPermaLink="true">https://cultureos.dev/institutions/smaller-museums</guid>
      <pubDate>Mon, 05 Oct 2026 18:47:17 GMT</pubDate>
      <description>Most smaller art museums run with twenty-five people or fewer, and few have anyone on the leadership team whose job is digital. The collections system, the donor database, and the image archive were bought in different decades and have never spoken to each other. Nothing needs replacing. Everything needs connecting.</description>
    </item>
    <item>
      <title>For archives, special collections &amp; libraries: Half a million files. Two people who can read them.</title>
      <link>https://cultureos.dev/institutions/archives</link>
      <guid isPermaLink="true">https://cultureos.dev/institutions/archives</guid>
      <pubDate>Mon, 05 Oct 2026 18:47:17 GMT</pubDate>
      <description>Special collections are where institutional memory is kept, and where the processing backlog is measured in years. You already have systems. What is missing is the workflow that connects them to how the work is actually done. And before any of that, we should talk about control.</description>
    </item>
    <item>
      <title>For universities &amp; research collections · research: Method, evaluation, and open standards, built with the Labs.</title>
      <link>https://cultureos.dev/institutions/universities</link>
      <guid isPermaLink="true">https://cultureos.dev/institutions/universities</guid>
      <pubDate>Mon, 05 Oct 2026 18:47:17 GMT</pubDate>
      <description>A university collection answers to a provost, not a board. Its budget moves with the university’s, and directors expect both university and public support to fall. The work does not fall with it. We build research capacity inside the budget line that exists, publish how we measure it, and leave the standards open.</description>
    </item>
    <item>
      <title>For institutions: Built for every kind of cultural institution.</title>
      <link>https://cultureos.dev/institutions</link>
      <guid isPermaLink="true">https://cultureos.dev/institutions</guid>
      <pubDate>Mon, 05 Oct 2026 18:47:17 GMT</pubDate>
      <description>We work with institutions whose knowledge, systems, and obligations have outgrown what a small staff can manage by hand. We give them the capacity of a much larger organization, at a fraction of the cost.</description>
    </item>
    <item>
      <title>Cultureos labs: A catalogue raisonné without waiting ten years.</title>
      <link>https://cultureos.dev/labs</link>
      <guid isPermaLink="true">https://cultureos.dev/labs</guid>
      <pubDate>Mon, 05 Oct 2026 18:47:17 GMT</pubDate>
      <description>The research arm of the practice. We are building a methodology for the most expensive kind of cultural scholarship, so that smaller institutions can afford it.</description>
    </item>
    <item>
      <title>Labs · research pilot: Tom of Finland Foundation: the pilot.</title>
      <link>https://cultureos.dev/labs/pilot</link>
      <guid isPermaLink="true">https://cultureos.dev/labs/pilot</guid>
      <pubDate>Mon, 05 Oct 2026 18:47:17 GMT</pubDate>
      <description>The founding laboratory. An archive large enough to test the methodology, a scholarly authority that stays final, and an institution whose systems the practice had already rebuilt.</description>
    </item>
    <item>
      <title>Labs · in development: Open Cultural Evidence Framework.</title>
      <link>https://cultureos.dev/labs/open-framework</link>
      <guid isPermaLink="true">https://cultureos.dev/labs/open-framework</guid>
      <pubDate>Mon, 05 Oct 2026 18:47:17 GMT</pubDate>
      <description>A shared way to move from objects, archives, and documents to assertions, evidence, uncertainty, contradictions, and human review.</description>
    </item>
    <item>
      <title>Perspective: Notes from the work.</title>
      <link>https://cultureos.dev/perspective</link>
      <guid isPermaLink="true">https://cultureos.dev/perspective</guid>
      <pubDate>Mon, 05 Oct 2026 18:47:17 GMT</pubDate>
      <description>Writing from the practice and the Labs, as methods and measurements are ready.</description>
    </item>
    <item>
      <title>About: A practice that gives time back to the people who run cultural institutions.</title>
      <link>https://cultureos.dev/about</link>
      <guid isPermaLink="true">https://cultureos.dev/about</guid>
      <pubDate>Mon, 05 Oct 2026 18:47:17 GMT</pubDate>
      <description>CultureOS is an AI-native practice for smaller museums, artist foundations, and archives in the United States. CultureOS Labs is its research arm.</description>
    </item>
    <item>
      <title>How we hold ourselves: Eight commitments.</title>
      <link>https://cultureos.dev/about/how-we-hold-ourselves</link>
      <guid isPermaLink="true">https://cultureos.dev/about/how-we-hold-ourselves</guid>
      <pubDate>Mon, 05 Oct 2026 18:47:17 GMT</pubDate>
      <description>Not policies adopted after the work. Constraints the work is built to satisfy.</description>
    </item>
    <item>
      <title>Privacy: Data belongs with the institution that holds it.</title>
      <link>https://cultureos.dev/privacy</link>
      <guid isPermaLink="true">https://cultureos.dev/privacy</guid>
      <pubDate>Mon, 05 Oct 2026 18:47:17 GMT</pubDate>
      <description>Restricted material stays restricted. Project-specific privacy terms are established in the governing agreement.</description>
    </item>
    <item>
      <title>Colophon: Built the way we build for clients.</title>
      <link>https://cultureos.dev/colophon</link>
      <guid isPermaLink="true">https://cultureos.dev/colophon</guid>
      <pubDate>Mon, 05 Oct 2026 18:47:17 GMT</pubDate>
      <description>A modular content model, release controls, accessible motion, current and well-supported infrastructure, and a visual language drawn from archives rather than generic AI imagery.</description>
    </item>
  </channel>
</rss>