Field notes from the Valley.

Field note 01 · October 2026

Why We Replaced Bloated CMS Builds with Version-Controlled Static Infrastructure

A lot of organization websites in this Valley, and a lot of conference sites we get asked to look at, are a theme, a page builder, a form plugin, a security plugin, a backup plugin, and a hosting invoice that nobody can explain without opening four tabs. The site is slow. The person who knew the admin password left. The domain registrar is a different login from the host, and neither login is in the organization’s name.

That is the problem we keep getting hired to end. The CMS is not the villain in the abstract. The villain is a production site nobody can diff, on a stack that costs real money to keep from falling over, for a set of pages that are mostly documents.

The replacement we ship is deliberately plain. The pages live in a repository. A change is a commit. Someone reads it. Then it builds and sits on Cloudflare’s edge as static files, with the headers written down: HTTPS, HSTS, a content type that does not sniff, a referrer policy, and a content security policy we have loaded in a browser. Mail records stay where mail records were. We do not “modernize” an MX record by accident.

Version control is the part clients feel after the launch, not during the demo. Six months later someone needs the sponsor logo from March, or needs to know who changed a ticket price. The history is in the repository. It is not in a freelancer’s memory and not in a hosting snapshot named final-final.

This is the shape of the ongoing work for the Altshuller Institute for TRIZ Studies and for TRIZCON 2026: a conference that has to speak English and Spanish, take registrations into a CRM, and sell through a storefront, on infrastructure the organization can actually hold. The same pattern fits a Mahoning Valley business that needs a fast site and a domain it owns. The domain ownership checklist is the public version of the first week of that job.

If the monthly stack for a brochure or an event site is wandering through the $150–$300 range in themes, plugins, and managed hosting, write the line items down before you buy another plugin to fix the plugin. Then decide what a repository and an edge host would replace. We do that accounting with people. It is not a coupon.

Bring the current URL if you want it rebuilt that way.

Field note 02 · October 2026

Human-in-the-Loop AI: Why Every Automation Needs a Review Gate

AI is useful in this shop. It drafts, it summarizes a long thread, it compares two versions of a page, it helps turn a messy checklist into a cleaner one. Used that way, it gives a small team its mornings back. Used as the thing that emails a registrant or merges a change to the live site, it is a way to be wrong in public at a speed you cannot outrun.

So the rule here is short enough to remember. The model may research, draft, and audit. A person signs every external send and every code merge. The sign-off is a review gate. The note of who signed, and when, is the audit log. We run our own multi-agent operations on that rule. Drafts move between steps. Nothing leaves the building, and nothing lands on the main branch, until a human has looked.

The gate has to be able to say no. A workflow that auto-approves because the queue is long is just a faster way to skip reading. We would rather a briefing sit until morning than a bad paragraph reach a conference attendee or a customer. The person who clicked approve owns the result. That is uncomfortable on purpose. It keeps the tool in the role of staff and the human in the role of principal.

Small teams do not need a platform announcement to start. They need one workflow. The registration exceptions. The page that changes every time a price does. The Monday briefing that currently takes an hour of tab-hopping. Put the model on that job. Write the sentence that says what it will not send. Put the pull request, or the “ready to send” button, in front of a named person.

Keep secrets and full customer files out of the prompt. Keep the decision in the CRM or the repository after the chat is closed. A transcript is not an operating record. The playbook is the checklist form of this note. If you want the gate built into a workflow you already hate doing by hand, that is a project we take.

Field note 03 · October 2026

Reindustrializing from the Ground Up: Starting with Real Software & Real Introductions in the Mahoning Valley

People in Youngstown have heard a lot of speeches about the comeback. Some of them were sincere. The test we use on ourselves is plainer than a speech: what can a person hire this quarter, and who can we introduce them to?

Societas Technologies operates from 1658 Roberts Ln NE, Warren, OH 44483. The photographs on this website are Youngstown because Youngstown is the city we are building for, along with Warren and the rest of the Valley. The mill at Mill Creek and the houses on Sheridan Road are the place.

What we sell is software and operations. Fast sites on infrastructure the owner can hold. Migrations off stacks that have gotten heavy. Bilingual conference sites, registration, and storefronts, including the work underway with the Altshuller Institute and TRIZCON 2026. Practical AI with a human at the gate. Audits and internal tools when a spreadsheet has quietly become the business. Local businesses and regional causes get that work without a costume.

The other half of reindustrializing, the half a website cannot do, is a person. Y Networker is our introduction desk: find the person, not the feed. Someone in the Valley names one concrete need. We broker one introduction. The Founding Valley Cohort is being assembled now, which means we will not pretend a directory is already full. The door is open. The feed is not the product. The introduction is.

That is the ground floor. Organizations here that run on systems they own, and people here who can find each other without leaving for a coastal network to do it. If the next thing you need is a site, start with the services. If the next thing you need is a person, start with the desk.