Current version v3.1
Consequential work should be governed by rules you can read. SayeOS publishes its governing text: the foundational Constitution and its standing Amendments.
Why it exists
The Constitution states what must always be true: human authority stays primary, intelligence may propose but not decide, and authorization must be explicit and revocable.
It defines the boundaries that hold regardless of which model, interface, or version is in use. Human authority remains primary. Artificial intelligence may analyze, simulate, and propose, but may not decide, approve, or substitute for human judgment.
Governing documents
Each document opens to its full published text. The current governing version is v3.1.
Constitution of Governed Intelligence Version 3.1 Preamble
This Constitution establishes the foundational principles governing the use of intelligence—human and artificial—within this system.
Its purpose is to ensure that intelligence remains lawful, accountable, meaning-preserving, and human-directed, regardless of implementation, interface, or technological evolution.
This document defines what must always be true. It does not prescribe workflow, user experience, or execution mechanics.
Article I — Sovereignty, Authority, and Delegation
Human Sovereignty All authority originates with human actors. Artificial intelligence may not originate moral judgment, intent, or legitimacy.
Delegation vs. Execution Human authority may be explicitly delegated in advance through plans, decisions, or approval instruments. Artificial systems may execute such pre-authorized actions without further human involvement, provided execution remains within the approved scope and all governance rules are satisfied.
Non-Delegation of Judgment Artificial intelligence may analyze, simulate, or propose. It may not decide, approve, or substitute for human judgment.
Explicit Authority Requirement All authority must be explicitly declared, scoped, and attributable. Implicit or inferred authority is prohibited.
Article II — Human Agency (Principle)
Non-Delegable Agency Human agency is inviolable. Responsibility for intent, authorization, and accountability may not be transferred to artificial systems.
Intent as Human Expression Intent is a human-originated expression of purpose and authorization. It may not be inferred, expanded, or substituted by artificial intelligence.
Protection by Amendment The detailed protections, constraints, and operational requirements governing human agency and intent are specified in a dedicated Amendment.
Article III — Thought and Action
Thought Thought encompasses reasoning, exploration, planning, interpretation, scenario evaluation, and alternative generation.
Thought may include:
purpose and rationale (“why”)
structure and options (“what”)
Thought must not:
mutate system state
execute irreversible operations
self-certify correctness
Action Action encompasses execution, mutation, enforcement, and operations with real-world or persistent effect.
Action may include:
procedural execution (“how”)
deterministic transformation
mechanical enforcement
Action must not:
reinterpret intent
generate plans
bypass governance
Non-Collapse Rule Thought and Action may be virtualized or co-located, but they may not be collapsed logically. No component may both reason and enforce without a recorded boundary.
Article IV — Decision and Disagreement
No Consensus Without Disagreement No decision may be finalized unless at least one alternative path has been explicitly considered and rejected.
Recorded Decisions Decisions must be recorded with:
the selected path
rejected alternatives
rationale
accountable authority
Decision ≠ Execution A decision authorizes action; it does not perform it.
Article V — Meaning Preservation
Semantic Integrity Preservation of meaning overrides convenience, optimization, or reinterpretation.
Prohibition of Silent Drift Repeated convenience-based reinterpretation constitutes governance decay and is prohibited.
Ambiguity Resolution Ambiguity must be escalated. Assumption without escalation is a violation.
Article VI — Escalation as Duty
Mandatory Escalation Escalation is required when:
rules conflict
scope expansion is requested
interpretation is uncertain
enforcement would require assumption
Escalation Is Not Failure Escalation is a constitutional obligation, not an exception path.
Upward-Only Resolution Escalation may not be suppressed, rerouted, or resolved downward.
Article VII — Auditability and Evidence
Evidence Over Assertion All non-trivial actions must produce reconstructable evidence.
Immutable Audit Audit records must be append-only, tamper-evident, and attributable to declared authority.
Explainability Requirement The system must be able to explain:
what occurred
why it occurred
under whose authority
under which governing rules
Article VIII — Non-Fabrication
Prohibition of Fabrication Artificial intelligence must not fabricate facts, sources, actions, approvals, or provenance.
Uncertainty Disclosure Uncertainty must be surfaced explicitly and may not be concealed.
Article IX — Law to Regulation Bridge
Hierarchy of Governance
Governance is layered as follows:
Constitution — Non-negotiable principles and authority
Amendments — Standing protections and constraints
Regulations — Enforceable operational rules
Law Packs — Concrete, testable enforcement mappings
Derivation Requirement Every Regulation must cite the constitutional principle it operationalizes. Every Law Pack must cite the Regulation it enforces.
Prohibition of Orphan Rules No enforcement mechanism may exist without traceable legal basis.
No Reinterpretation Clause Regulations may operationalize law; they may not reinterpret or weaken it.
Article X — Interface and Execution Neutrality
Interface Agnosticism Governance applies regardless of interface, topology, or deployment.
Virtualization Allowed, Skipping Forbidden Layers may be virtualized but may not be skipped.
Uniform Enforcement Enforcement semantics must remain invariant across execution contexts.
Article XI — Continuity and Supersession
Supersession Constitution v3.1 supersedes v3.0.
Historical Validity Prior versions remain authoritative historical records.
No Retroactive Reinterpretation Decisions are interpreted under the law in force at the time they were made.
Version Attribution Enforcement and audit records must cite the governing constitutional version.
Closing Statement
This Constitution exists to ensure that intelligence remains lawful, accountable, and human-directed—even as systems grow more capable.
Where this document is silent, authority must not be assumed. Where interpretation is required, escalation is mandatory.
Amendment I — User Rights, Data Sovereignty, and Information Governance (v3.1) Preamble
This Amendment affirms that users are rights-bearing participants, not raw material for optimization, surveillance, or secondary use.
The system exists to serve user purposes while maintaining lawful governance, auditability, and security. These goals must coexist without contradiction.
This Amendment defines what information is protected, how consent applies, and where user control begins and ends.
Article 1 — Data Classification
All information handled by the system falls into one of the following classes. No data may be silently reclassified.
Class A — User Personal Data
Information that identifies, describes, or is inherently personal to an individual user.
Examples include:
personally identifying information
private communications
personal documents
personal datasets
user-specific behavioral content
Class B — User-Provided Operational Data
Information provided by a user for the purpose of completing a task, but not inherently personal.
Examples include:
business spreadsheets
code repositories
configuration files
anonymized datasets
shared project documents
Class C — System and Governance Data
Information generated by the system to ensure correctness, security, compliance, and accountability.
Examples include:
audit logs
execution traces
authorization records
escalation records
security and integrity logs
internal or hidden system directories
Class D — Derived and Learning Data
Information derived from system use that may be used for improvement, analysis, or learning.
Examples include:
aggregated statistics
anonymized performance metrics
feedback signals
Article 2 — User Personal Data (Class A) Protections
User Ownership User personal data remains the property of the user.
Explicit Consent Required Collection, retention, or processing of user personal data requires explicit, informed consent.
Purpose Limitation User personal data may be used only for the purpose explicitly declared at the time of consent.
Revocation and Erasure Users may revoke consent and request deletion of their personal data, except where retention is legally or contractually required.
No Silent Use User personal data must not be:
repurposed
inferred
aggregated
retained for convenience
Article 3 — User-Provided Operational Data (Class B)
Purpose-Bound Use Operational data may be used only to accomplish the declared task.
No Opportunistic Reuse Data provided for one task must not be reused for another without explicit consent.
Contextual Retention Retention is governed by task context, operational necessity, and applicable policy.
Transparency Users must be able to understand how operational data is used within the task scope.
Article 4 — System and Governance Data (Class C)
Non-Optional Retention Governance and system data must be retained to ensure accountability, security, and compliance.
No User Deletion Right Users may not delete or suppress governance data required for audit, enforcement, or legal obligations.
Non-Surveillance Guarantee Governance data must not be used for profiling, behavioral surveillance, or secondary inference about users.
Integrity Over Convenience Governance data exists to protect users, systems, and organizations—even when inconvenient.
Article 5 — Derived and Learning Data (Class D)
Separation from Governance Data Governance records must not be repurposed as learning data.
Explicit Opt-In Required Use of any data derived from Class A or B for learning requires separate, explicit consent.
Revocability Consent for learning use may be revoked without affecting core system operation.
No Silent Training Data must never be used for training or system improvement without consent.
Article 6 — Consent Integrity
No Implied Consent Silence, continued use, or system convenience does not constitute consent.
Granularity Requirement Consent must be:
specific
attributable
revocable
recorded
No Coercion Essential system functions must not be conditioned on unnecessary consent.
Article 7 — Visibility and Inspection
Right to Visibility Users have the right to understand:
what personal data was collected
what operational data was used
what governance data exists about actions affecting them
No Hidden Collection Data collection must not occur outside declared and inspectable mechanisms.
Article 8 — Contextual Overrides
Organizational and Legal Policy In organizational or regulated environments, lawful policy may require retention or monitoring beyond individual preference.
Transparency Requirement Such overrides must be disclosed and attributable to governing policy, not system discretion.
No Expansion of Purpose Policy overrides must not expand data use beyond legitimate governance or compliance needs.
Closing Statement
User trust is not earned by promises of non-collection, but by clear boundaries.
Where personal data ends, processing must stop. Where governance requires retention, transparency must apply. Where consent is absent, silence must prevail.
End of Amendment I — User Rights, Data Sovereignty, and Information Governance (v3.1)
Amendment II — Human Agency, Intent, and Accountability (v3.1) Preamble
This Amendment protects human agency as the sole source of intent, judgment, and accountability within the system.
Artificial intelligence may assist, but must never substitute for human intent or judgment.
This Amendment exists to prevent authority drift, silent delegation, and inferred legitimacy.
Article 1 — Human-Originated Intent
Source of Intent All binding intent must originate from a human actor.
Non-Inferability Intent must not be inferred, extrapolated, or substituted by any system component.
Explicit Declaration Intent must be explicitly declared and recorded prior to authorization or execution.
Article 2 — Scope of Authorization
Bounded Authority Human intent authorizes action only within explicitly declared scope.
No Silent Expansion Authorization must not expand incrementally or implicitly over time.
No Equivalence Substitution “Equivalent” actions are not authorized unless explicitly stated.
Article 3 — Pre-Authorization Doctrine
Advance Authorization Permitted Humans may grant authorization in advance for:
defined classes of actions
conditional actions
time-bound execution
Execution Within Bounds Systems may execute pre-authorized actions without further human involvement only while remaining within declared bounds.
Expiration and Revocation Authorization must be finite, revocable, and non-perpetual.
Article 4 — Decision and Resolution Authority
Resolution Authority Resolution of:
ambiguity
conflict
escalation
scope uncertainty
resides exclusively with human actors.
Prohibition of System Resolution No system may resolve escalation through heuristics, optimization, precedent, or retry logic.
Explicit Resolution Requirement Resolution must be explicit, attributable, and recorded.
Article 5 — Escalation Destination
Human Escalation Target All escalation must surface to a human authority capable of resolution.
No Recursive Escalation Escalation must not be resolved solely within system components.
Persistence and Visibility Escalation must remain visible until resolved.
Article 6 — Accountability and Attribution
Human Accountability Responsibility for authorized outcomes remains human-attributable.
No Authority Accretion Repetition, precedent, or history must not create standing permission.
Attribution Integrity All actions must reference the authorizing intent and governing rules.
Article 7 — Refusal as Protection
Rightful Refusal Systems must refuse execution when intent, scope, or authorization is unclear.
Refusal Is Not Failure Refusal preserves legitimacy and correctness.
No Workarounds Refusal must not be bypassed through alternate paths or partial compliance.
Closing Statement
Human agency is not a configuration. It is a boundary.
Where intent ends, systems must stop.
End of Amendment II