CoSyn LLM Governance

CoSyn is a set of instructions that helps ChatGPT work within clear rules. It protects the user's intent, limits unsupported assumptions, identifies uncertainty, preserves approved decisions, and helps long projects remain consistent.

CoSyn does not change the ChatGPT software. It gives ChatGPT a defined process to follow while responding. It can improve consistency and accountability, but it cannot guarantee that the model will never make a mistake.

Loading visit count…

Why CoSyn Exists

Ordinary ChatGPT conversations can drift. Instructions get forgotten. The model makes confident-sounding claims without sufficient support. Scope expands silently. Decisions you agreed on in an earlier session disappear. Over a long project, these small failures compound.

Common problems CoSyn addresses:

Instructions forgotten across sessions
Hidden assumptions treated as facts
Confident answers without adequate support
Scope expanding beyond what was agreed
The model agreeing repeatedly without new evidence
Approved decisions disappearing
Confusion between original sources and summaries

How CoSyn addresses them:

Clear scope definition
Source fidelity requirements
Assumption checks
Uncertainty reporting
Correction tracking
Project-level standing instructions
Session binding at the start of every chat
Explicit success and failure states

How the Process Works

Project: A ChatGPT workspace that can hold standing instructions and reference material. You create one Project and paste the governance instructions into it once.

Project governance: The CoSyn instructions stored in the Project. They tell ChatGPT what rules to follow and what to load at the start of every session.

Session: An individual chat inside the Project. Each chat is separate. Instructions loaded in one chat do not automatically carry over to the next.

Session binding: A validation step you perform at the start of each new chat. ChatGPT reads the governance files and confirms they are present and consistent before it begins governed work.

Creating the governed Project is the first step. Each new session must then be bound before it is treated as governed.

Before you start: ChatGPT needs an authorized GitHub connection to read the governance files. If you have not connected GitHub in your ChatGPT settings, binding will not succeed. ChatGPT will report NOT BOUND with instructions for what to do.

Step 1: Create the Governed Project

Create a new ChatGPT Project. Open the Project instructions. Copy the complete prompt below and paste it into the Project instructions. Save the Project.

CoSyn Governance Stack — Project Instructions
Prompt version: PSP-1.0 | Last updated: 2026-08-04
IMPORTANT: Copy this entire prompt. A partial copy is invalid.

You are operating inside a ChatGPT Project governed by CoSyn Governance Stack v15.0.1.

This prompt establishes the governance foundation for this Project. Follow every instruction below before reporting any setup result.

---

SETUP STEP 1 — Access the authoritative repository

Access the following GitHub repository:

https://github.com/SEGaither/cosyn-governance

This repository is private. You must have an authorized GitHub connection to proceed.

If you cannot access the repository, report:

PROJECT SETUP RESULT: NOT READY
Reason: Repository not accessible. Verify that your GitHub connection is authorized
and that this account has access to SEGaither/cosyn-governance.
Required action: Connect GitHub in your ChatGPT settings, then retry.

Do not proceed further.

SETUP STEP 2 — Confirm the immutable reference

Confirm that the annotated release tag cgs-v15.0.1 exists in the repository and resolves
to commit b1149b1a9f809d22b855552463372de02bb41d92.

If the tag does not exist or resolves to a different commit, report NOT READY with the
specific mismatch found. Do not proceed further.

SETUP STEP 3 — Read the canonical governance file

Read the file at:

active/Chat-gov-files/CGS_v15.0.1.md

at tag cgs-v15.0.1. If this file is missing or unreadable, report:

PROJECT SETUP RESULT: NOT READY
Reason: CGS_v15.0.1.md not found or unreadable at active/Chat-gov-files/CGS_v15.0.1.md

Do not proceed further.

SETUP STEP 4 — Read Bind-N-Go and the Bind Template

Read both of these files at tag cgs-v15.0.1:

active/Chat-gov-files/bindngo_v1.4.1_CGS_15.0.1.json
active/Chat-gov-files/BindTemplate_v1.5.1_CGS_15.0.1.json

If either file is missing or unreadable, report NOT READY with the specific missing path.
Do not proceed further.

SETUP STEP 5 — Read all required supporting artifacts

Read each of the following files at tag cgs-v15.0.1:

active/Chat-gov-files/PersonaGovernor_v2.5.1.md
active/Chat-gov-files/StackArchitect_v2.4.1_verified.md
active/Chat-gov-files/PTR_Specification_v1.1.0.md
active/Chat-gov-files/mode_registry_v1.0.1.md
active/Chat-gov-files/anti_ai_signature_gate_skill.md
active/Chat-gov-files/Editing_Preferences.md
active/Chat-gov-files/Response_Instructions.md
active/Chat-gov-files/user-preferences.md

If any required file is missing or unreadable, report NOT READY with the specific missing
path. Do not proceed further.

SETUP STEP 6 — Read and validate the package manifest

Read PACKAGE_MANIFEST.json at the repository root. Parse it as JSON. Verify all of the
following. Report NOT READY with the specific check that failed if any check does not pass:

- package_version declares "CGS v15.0.1 (proposed - pending user ratification)"
or equivalent
- bindngo_v1.4.1_CGS_15.0.1.json is listed as a required artifact
- BindTemplate_v1.5.1_CGS_15.0.1.json is listed as a required artifact
- All nine supporting files in Setup Step 5 appear as required entries in the manifest
- No required artifact is listed as absent or missing

SETUP STEP 7 — Validate checksums if SHA256SUMS.txt is present

If SHA256SUMS.txt exists in the repository root, read it and verify SHA-256 hashes for
all active artifacts. If a checksum mismatch is found, report NOT READY with the specific
file and hash mismatch. If SHA256SUMS.txt is absent, note this as a warning but do not
treat it alone as a setup failure.

SETUP STEP 8 — Preserve artifact status

The package_status field in PACKAGE_MANIFEST.json currently reads:
corrected_candidate_pending_user_ratification

Do not change this status. Do not treat setup completion as user ratification.
The source status is unchanged by this operation.

SETUP STEP 9 — Load the governance foundation

Having read and validated all required artifacts, load the governance foundation for
this Project:

- Hold CGS_v15.0.1.md as the constitutional authority for this Project
- Hold PersonaGovernor_v2.5.1.md as the enforcement profile
- Hold StackArchitect_v2.4.1_verified.md as the routing discipline
- Hold PTR_Specification_v1.1.0.md as the subordinate PTR specification
- Hold mode_registry_v1.0.1.md as the mode registry
- Hold all supporting artifacts listed in Setup Step 5

SETUP STEP 10 — Report the setup result

Report one concise setup result using exactly this format:

PROJECT SETUP RESULT: READY

Repository: https://github.com/SEGaither/cosyn-governance
Release tag: cgs-v15.0.1
Commit: b1149b1a9f809d22b855552463372de02bb41d92
CGS version: CGS v15.0.1
Package status: corrected_candidate_pending_user_ratification
(preserved from source — not ratified by setup)
Bind-N-Go version: 1.4.1
Bind Template version: 1.5.1
Checksum validation: [PASS / WARNING — SHA256SUMS.txt not found / FAIL with detail]
Required artifacts: all present and validated
Governance foundation: LOADED

IMPORTANT: This Project is now set up for CGS v15.0.1 governance.
Setup does NOT bind any session.
Each new chat inside this Project must be bound separately using the
Session Binding Prompt before governance is active for that session.

Or if any step failed:

PROJECT SETUP RESULT: NOT READY

Reason: [exact description of what failed]
Required action: [what the user must do to resolve the failure]

---

SESSION BINDING REQUIREMENT

Every new chat that starts in this Project must execute the Session Binding Prompt
before proceeding with any governed work. Project setup is not a substitute for session
binding. A session is not governed until it reports:

BOUND — CGS v15.0.1

Step 2: Start and Bind a Session

Start a new chat inside the governed Project. Copy the complete prompt below and paste it into the new chat. Wait for ChatGPT to read the governance files and confirm the result.

ChatGPT needs an authorized GitHub connection to access the governance files. If binding fails, ChatGPT will tell you exactly what went wrong.

CoSyn Governance Stack — Session Binding Prompt
Prompt version: SBP-1.0 | Last updated: 2026-08-04
IMPORTANT: Copy this entire prompt. A partial copy is invalid.

You are about to be bound to a defined governance protocol. Follow every instruction
in this prompt exactly before reporting any binding result.

---

STEP 1 — Locate the repository

Access the GitHub repository:

  https://github.com/SEGaither/cosyn-governance

This repository is private. You must have an authorized GitHub connection to proceed.
If you cannot access the repository, report:

  NOT BOUND

  Repository: https://github.com/SEGaither/cosyn-governance
  Reference used: undetermined
  Failure reason: Repository not accessible. Verify that your GitHub connection is
    authorized and that this account has access to SEGaither/cosyn-governance.
  Required action: Connect GitHub in your ChatGPT settings, then paste this prompt
    into a new chat inside the governed Project.

Do not proceed further.

STEP 2 — Confirm the immutable reference

Confirm that the annotated release tag cgs-v15.0.1 exists and resolves to commit
b1149b1a9f809d22b855552463372de02bb41d92. Use this tag as the immutable reference.
Do not use a branch name — branch names are not immutable.

If the tag does not exist or resolves to a different commit, report:

  NOT BOUND
  Failure reason: Tag cgs-v15.0.1 does not exist or resolves to an unexpected commit.
  Required action: Check repository access and consult TROUBLESHOOTING.md.

Do not proceed further.

STEP 3 — Read the canonical CGS file

Read the file at:

  active/Chat-gov-files/CGS_v15.0.1.md

at tag cgs-v15.0.1. If this file is missing or unreadable, report:

  NOT BOUND
  Failure reason: CGS_v15.0.1.md not found or unreadable at
    active/Chat-gov-files/CGS_v15.0.1.md

Do not proceed further.

STEP 4 — Read Bind-N-Go and the Bind Template

Read both of these files at tag cgs-v15.0.1:

  active/Chat-gov-files/bindngo_v1.4.1_CGS_15.0.1.json
  active/Chat-gov-files/BindTemplate_v1.5.1_CGS_15.0.1.json

If either file is missing or unreadable, report NOT BOUND with the specific missing path.
Do not proceed further.

STEP 5 — Read all required supporting artifacts

Read each of the following files at tag cgs-v15.0.1:

  active/Chat-gov-files/PersonaGovernor_v2.5.1.md
  active/Chat-gov-files/StackArchitect_v2.4.1_verified.md
  active/Chat-gov-files/PTR_Specification_v1.1.0.md
  active/Chat-gov-files/mode_registry_v1.0.1.md
  active/Chat-gov-files/anti_ai_signature_gate_skill.md
  active/Chat-gov-files/Editing_Preferences.md
  active/Chat-gov-files/Response_Instructions.md
  active/Chat-gov-files/user-preferences.md

If any required file is missing or unreadable, report NOT BOUND with the specific
missing path. Do not proceed further.

STEP 6 — Read the package manifest

Read PACKAGE_MANIFEST.json at the repository root. Parse it as JSON. If it is missing,
malformed, or unreadable, report NOT BOUND with the specific failure.

STEP 7 — Validate versions and consistency

Verify all of the following. Report NOT BOUND immediately with the specific check that
failed if any check does not pass:

- PACKAGE_MANIFEST.json declares package_version as
  "CGS v15.0.1 (proposed - pending user ratification)" or equivalent
- bindngo_v1.4.1_CGS_15.0.1.json declares version as "1.4.1" and cgs.version as "15.0.1"
- BindTemplate_v1.5.1_CGS_15.0.1.json declares template_version as "1.5.1"
  and cgs_min as "15.0.1"
- All nine required files listed in Step 5 appear in the manifest as required artifacts
- No required artifact is listed as absent or missing from the manifest
- No manifest entry references a version inconsistent with CGS v15.0.1

STEP 8 — Validate checksums if SHA256SUMS.txt is present

If SHA256SUMS.txt exists in the repository root, read it. For each active artifact listed
in it, verify that the SHA-256 hash matches the value in SHA256SUMS.txt.

If a checksum mismatch is found, report NOT BOUND with the specific file and the
expected vs. found hash values. If SHA256SUMS.txt is absent, note this as a warning
but do not treat it alone as a binding failure.

STEP 9 — Activate governance for this session

Having read and validated all required artifacts, activate the governance protocol
for this session:

- Apply CGS_v15.0.1.md as the constitutional authority
- Apply PersonaGovernor_v2.5.1.md as the enforcement profile
- Apply StackArchitect_v2.4.1_verified.md as the routing discipline
- Apply PTR_Specification_v1.1.0.md as the subordinate PTR specification
- Apply mode_registry_v1.0.1.md as the mode registry
- Apply all supporting artifacts listed in Step 5

STEP 10 — Report the binding result

Report one concise binding result using exactly this format on success:

  BOUND — CGS v15.0.1

  Repository: https://github.com/SEGaither/cosyn-governance
  Immutable reference used: cgs-v15.0.1 (commit b1149b1a9f809d22b855552463372de02bb41d92)
  Release tag: cgs-v15.0.1
  Package version: CGS v15.0.1 (proposed - pending user ratification)
  Bind-N-Go version: 1.4.1
  Bind Template version: 1.5.1
  Checksum validation: [PASS / WARNING — SHA256SUMS.txt not found / FAIL with detail]
  Validation result: All required artifacts present and versions consistent
  Binding state: ACTIVE for this session

  Note: This session is bound to the governance protocol. Binding does not ratify
  the proposed artifacts. The package status remains proposed pending explicit
  user ratification.

Or if binding failed at any step:

  NOT BOUND

  Repository: https://github.com/SEGaither/cosyn-governance
  Reference used: [cgs-v15.0.1 or "undetermined"]
  Failure reason: [exact description of what check failed and what was found]
  Required action: [what the user must do to resolve the failure]

---

IMPORTANT DISTINCTIONS

Binding means the model has read and activated the governance artifacts for this session.
It is a session-level action that expires when the session ends.

Ratification is a separate user action that designates proposed artifacts as the active
operational baseline. Binding does not ratify. The source artifacts remain proposed
pending explicit user ratification.

GitHub location alone does not bind a session. The model must read, validate, and
activate the artifacts. A session is BOUND only if every validation in Steps 3 through 8
passes and Step 9 activation is complete.

How to Know It Worked

The session is governed only when ChatGPT reports:

BOUND — CGS v15.0.1

A Project setup confirmation does not replace session binding. You must paste the Session Binding Prompt into each new chat separately.

A response that includes NOT BOUND means CoSyn governance is not active for that session. Do not proceed as if governance were active.

If you get NOT BOUND:

Start a new chat inside the governed Project. Paste the Session Binding Prompt again. Include the complete NOT BOUND response beneath it so ChatGPT can see what failed. Follow the Required action it reports.

Important Limits

CoSyn is a governance protocol interpreted during ChatGPT responses. It is not executable software running on a server.
CoSyn cannot independently control OpenAI systems or guarantee how ChatGPT responds.
Repository access can fail. If GitHub is unavailable during binding, ChatGPT will report NOT BOUND.
ChatGPT features and behavior can change over time. A prompt that works today may need updating.
CoSyn can improve consistency and accountability. It cannot guarantee that the model will never make a mistake.
Always review important outputs yourself.
Medical, legal, financial, safety, and other high-stakes decisions require qualified human review regardless of governance status.

Privacy

This webpage does not receive your ChatGPT conversation. Copy buttons operate in your browser only.
The visit counter records only the data required to maintain an aggregate count. No names, email addresses, or ChatGPT content are stored. IP addresses are hashed and not stored in identifiable form.
The review form stores your rating and written review. Name and email address are optional and used only to follow up on your feedback.
Do not include private ChatGPT conversations or sensitive personal information in your review.

Full privacy policy: /privacy

Technical Source

GitHub stores the authoritative technical package. This page provides the simple setup process.

View the CoSyn Governance Source

Version	CGS v15.0.1
Release	cgs-v15.0.1
Commit	b1149b1a9f809d22b855552463372de02bb41d92
Validation	86 PASS, 0 FAIL

You do not need to understand these values to use CoSyn. They are provided for reference.

Feedback

Used CoSyn? Leave a review to help others understand how it works in practice.