Bear Canyon SystemsBear Canyon Systems
Jynsyn logo

Bear Canyon Systems · Research

Jynsyn

A reference architecture for keeping accountability stable in AI-enabled operations, as the models, machines and contractors change.

The SOD is durable. The stack evolves.

Read the white paper (PDF) View on Zenodo (opens in a new tab)

The starting assumption

Every part of an AI-enabled operation will be replaced: models, agents, machines, platforms, even the contractors who run them. Some of that is planned. Some of it happens at 2 a.m., when a link drops or an agent starts getting things wrong. If that's true, accountability can't live in any of those parts. It has to sit somewhere that outlasts them.

The Sovereign Operational Domain

Jynsyn calls that place a Sovereign Operational Domain, or SOD. A SOD is an organization's operational definition: what it is responsible for, who may authorize what, what evidence it must keep, and how it keeps operating when a component fails.

The idea of a governed boundary isn't new. The SOD builds on the security domain and the authorization boundary from established security practice. "Sovereign" is meant in the operational sense: control over who runs, decides, responds and approves exceptions, held by accountable people. A SOD isn't a data-residency or AI sovereignty zone, though it can use one. What Jynsyn adds is keeping that boundary stable while everything inside it changes.

"A well-engineered harness enforces the SOD; it does not define it."

Jynsyn doesn't replace the platforms, agents and harnesses an organization already uses. It gives them a stable definition to answer to.

Four properties

Change without drift

Models, machines and contractors change; responsibilities and approvals change only by decision.

Access without authority

Admitting a system to a role never lets it act on its own say-so.

Failure within limits

An outage or a lost link narrows what is allowed; it never widens it.

Proof on demand

Every consequential action must trace to an accountable role and a named person.

The white paper

Sovereign Operational Domains: Durable Accountability for AI-Enabled Physical Security

Keeping the chain of authority stable as models, machines, and actors change

Timothy E. Chandler · Bear Canyon Systems · Version 1.0 · October 2026 · 25 pages · PDF

Organizations now assemble AI capability from models, agents, hosted services, autonomous machines and existing enterprise systems, and replace those parts far more often than they change who is responsible for the outcome. This paper argues that what an organization should hold stable is not its technology stack but its operational definition: what it is responsible for, who may authorize what, what evidence it must keep, and how it keeps operating when a component fails. Jynsyn calls that definition a Sovereign Operational Domain (SOD).

We follow one illustrative case: overnight security at a logistics company whose guard contractor now pairs a single on-site guard with a docked drone and a ground robot. It shows how the Jynsyn V3 reference architecture separates a durable responsibility from the replaceable system participants that serve it, how the company scales to a region served by a different contractor without rebuilding its authority model, and why, when an AI proposes that a drone follow an intruder off the property, the decision is not the drone's or the model's to make.

The claim is architectural: organizations need a durable object that composes established mechanisms around accountable authority, specified as requirements an implementation can be tested against. The paper ends with propositions that would show it wrong.

Download PDF Zenodo record (opens in a new tab)

Citation

Chandler, T. E. (2026). Sovereign Operational Domains: Durable Accountability for AI-Enabled Physical Security (Version 1.0). Bear Canyon Systems. https://doi.org/10.5281/zenodo.23110479

This version: 10.5281/zenodo.23110479

All versions: 10.5281/zenodo.23110478

Version history

VersionDateNotes
1.02 October 2026First public edition.

Status

The Jynsyn V3 Reference Architecture is forthcoming. When it's released, the paper will be reissued as a new version; the all-versions DOI above will always point to the latest. Jynsyn V3 is a reference architecture, not a product or a certification, and it hasn't yet been proven in the field.

Get in touch

Questions, critique, or interest in building on Jynsyn? We'd like to hear from you.

Contact Bear Canyon Systems

The white paper is licensed under the Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License (CC BY-NC-ND 4.0). The license covers the paper's text and figures only. It grants no rights in the Jynsyn name, does not license the Jynsyn V3 Reference Architecture (which carries its own terms), and does not permit claims of conformance. Jynsyn is a trademark of Bear Canyon Systems. © 2026 Bear Canyon Systems.