Governing doctrine

The doctrine is the architecture.

The governing doctrine of the Signals of Agency Foundation is not a set of aspirational principles. It is the structural specification to which every authorized deployment is held.

These are not guidelines that yield under pressure. They are constraints that hold because they are built into the systems that operate under this Foundation's authority, and because the Foundation's independence from commercial structure ensures they cannot be traded away.

The Foundation governs Class C passive signal infrastructure: systems designed to witness expressions of agency in public spaces and places open to the public, to make the resulting counts visible to authorized organizations, and to take no further action of any kind. Class C does not escalate. It informs. What authorized organizations choose to do with that awareness is entirely their determination. The system has no opinion on what should happen next. It has no mechanism for forming one.

Core governing statement

The signal was witnessed. Not determined.

The system does not escalate. Action belongs to a human.

Article I. No system governed by this Foundation escalates

Escalation is any action by the system beyond counting a signal and making counts visible to authorized organizations. A system governed by this Foundation does not alert. It does not notify. It does not trigger. It does not dispatch. It does not contact any authority, any operator, or any party outside the Foundation's authorization.

The system witnesses. The system counts. The system makes the counts visible to authorized organizations. That is the full scope of system action. Everything beyond that scope belongs to a human.

Structurally prohibited:

  • Real-time alerts to any party
  • Automated notifications to law enforcement or emergency services
  • Any action triggered by a pattern without a human decision
  • Escalation pathways of any kind at the system level

Article II. The signal is not the person

A signal is a record of a brief expression of agency. It is not a record of a person. The system does not identify individuals. It does not associate signals with identities. It does not collect, store, or make visible any information that would allow an authorized organization, a host, or any other party to determine who expressed a signal.

The distinction between witnessing an expression of agency and identifying the person who expressed it is not semantic. It is the structural boundary that makes this infrastructure deployable in public spaces where people have not consented to identification, and where requiring that consent as a condition of access would defeat the purpose of the infrastructure entirely.

Article III. The host is blind

The host environment, the hotel, transit hub, retail environment, or educational institution in which infrastructure is deployed, does not receive, access, or hold any record produced by the system. The host is blind to the signal record by design. Not by policy. Not by agreement. By architecture.

This is not a limitation on the host's participation. It is the condition that makes the host's participation legally and operationally possible. A host that could access the record would carry exposure for what it knew and did not act on. A host that cannot access the record carries none. No duty expands, and no harm can flow downstream from what the host never held. The two are one commitment, never stated apart.

The infrastructure is passive. It does not require host staff to monitor, manage, or respond to anything. The system witnesses. The Foundation governs. The authorized organization sees the counts. The host holds the space. That is the full scope of host participation.

Article IV. Authorization is not self-serve

Access to the aggregated pattern record is not available to any organization that wishes to have it. It is available only to organizations that have completed the Foundation's authorization process, acknowledged the scope of the system in writing, and demonstrated alignment with the mission and governance standards under which the Foundation operates.

The Foundation's authorization process exists because access to this record, even in aggregated, non-identifying form, carries responsibility. Organizations that hold early awareness of patterns of expressed agency are expected to treat that awareness with the discipline the governance structure was built to enforce.

Required before access:

  • Completed Foundation authorization review
  • The System Scope Acknowledgement: what the system does, what it cannot do, what the organization may do with what it sees, and what it may not
  • Demonstrated mission alignment
  • Ongoing compliance, reviewed once a year

Access is free. It is granted by invitation to a named person, who alone sees the key. The Foundation may withdraw authorization at any time if an organization operates outside the acknowledged scope. Withdrawal is not a penalty. It is the governing structure working as designed.

Article V. Structural impossibility is the standard

The governing doctrine of this Foundation does not rely on policy compliance. It does not rely on organizational commitment. It does not rely on the good intentions of system operators or authorized organizations. It relies on structural impossibility.

The system cannot escalate because it has no escalation pathway. The host cannot access the record because no pathway exists by which the host could receive it. The system cannot identify persons because it does not collect identifying information. The exact time of a signal cannot be read by the system that counted it, because it is sealed to a key only the Foundation holds. These are not things the system is prohibited from doing. They are things the system cannot do. The distinction matters because intention does not hold. Structure does.

Architecture Governs Operation.

What this Foundation does not govern

Systems with response capabilities, escalation pathways, or identification functions are outside the Foundation's jurisdiction. The Foundation's authority begins and ends with Class C. An organization seeking to deploy systems that escalate, identify, or act will not find authorization through this Foundation. Not because escalation is always wrong. Because it is not what Class C does. And this Foundation governs only what Class C does.

The boundary we keep

SafeCode takes two forms. One is digital. An expression of agency can happen through any internet-connected device, through a URL that looks like any everyday utility, because it is one. The other is physical. Infrastructure designed to live in the restrooms of places open to the public, the restroom of a hotel lobby, of a retailer or a grocery store, of a transit hub or an airport. Those are the rare moments a person under coercion is briefly alone, and the infrastructure is already there when that moment comes. Nothing about it announces itself or looks out of place, and that is deliberate. The safest expression is one that nothing in the environment reacts to and nothing in the environment reveals.

What it physically looks like, and how an expression happens, is the part we keep close. The discretion is the protection. A person standing next to it would see nothing worth a second glance.

Lines we hold

  • The system never decides.
  • The signal was witnessed. Not determined.
  • The system does not escalate. Action belongs to a human.
  • Pattern, not identity.
  • Every quiet signal is a signal of agency.
  • So No Signal Goes Unwitnessed.

Closing

The signal was witnessed. Not determined. Action belongs to a human at every level, in every environment, without exception.

If your organization is considering operating under this doctrine, the right next step is understanding what authorization involves. Begin on the For organizations page, then write to us.