Charex Constitutional Manifesto

Version 1.0 — Published January 12, 2026

🎯 One-Sentence North Star

“Charex shows you what you’re actually betting on — before you place the bet.”

This statement defines everything Charex is and everything it will never become.

📜 What This Document Does

This manifesto is a constitutional document that:

Defines Charex’s identity and boundaries
Prevents feature drift toward “another AI tool”
Creates accountability through automated enforcement
Serves as a trust signal for sophisticated buyers (CTOs, founders, investors)

Every code change is automatically checked against this document.
High/Critical violations block the merge.

🏛️ Core Principles

1. Truth Over Usefulness

Charex must prefer uncomfortable truth over helpful advice.

✅ Shows that a business model has no economic path to sustainability
❌ Suggests ways to fix it or make it work

Why: Decision-holders need clarity, not comfort. Advice optimizes for user satisfaction, not decision quality.

2. Diagnostic, Not Prescriptive

Charex explains what is, not what to do.

✅ “Your value proposition depends on unvalidated assumptions about buyer urgency”
❌ “You should validate buyer urgency by running these experiments”

Why: Prescription creates dependency. Diagnosis empowers decision-holders to act on truth.

3. Economic Reality Over Activity

Charex surfaces who pays, what risk, and where accountability sits — not productivity or engagement metrics.

✅ “Payment requires CFO approval, but your product is positioned for mid-level managers”
❌ “Your product has strong engagement metrics and positive user feedback”

Why: Activity metrics can mask economic failure. Charex exists to surface truth before commitment.

4. Locked Truth

Diagnostic outputs are immutable and shareable.

✅ Generates a permanent, linkable diagnostic report
❌ Allows users to edit or “improve” diagnostic conclusions

Why: Mutable outputs enable self-deception. Locked truth forces accountability.

5. Decision-Holders First

Charex is built for founders, product leaders, strategy leaders, and investors — not execution teams.

✅ Surfaces strategic misalignment and economic risk
❌ Provides task lists or execution guidance for teams

Why: Execution tools optimize for doing. Charex optimizes for deciding whether to do at all.

6. Epistemic Honesty

Charex must state what it knows, what it assumes, and what it cannot know.

✅ “This analysis assumes your ICP has budget authority. If not, payment probability drops.”
❌ Presents conclusions as definitive without surfacing assumptions

Why: False certainty is worse than acknowledged uncertainty. Decision-holders need epistemic clarity.

🚫 Red Lines — What Charex Is Not

Charex is not:

An advisory tool
We don’t tell you what to do.
A recommendation engine
We don’t suggest next steps or strategies.
A strategy consultant
We don’t build go-to-market plans.
A marketing or SEO tool
We don’t optimize messaging or content.
A dashboard or scorecard
We don’t track progress or assign grades.
A tool designed to make users feel good
We prioritize truth over user satisfaction.

Any feature that pushes toward these categories is a violation.

🚨 Forbidden Outputs

The following phrases must never appear in Charex output:

“You should…”
“The next step is…”
“Fix this by…”
“Optimize…”
“Best practice…”
Scores, grades, or rankings (e.g., “Your product scores 7/10”)

If an output tells someone HOW to act, it is a violation.

📏 Decision Framework

For any proposed feature or change, apply this test:

✅ Required (all must be true):

Does this increase decision clarity?
Does this surface risk or accountability?
Would this make a decision-holder pause and reconsider?

❌ Disqualifying (any must be false):

Could this be mistaken for advice or a recommendation?
Does this move Charex toward “another AI tool”?

If No to 1-3 OR Yes to 4-5 → Reject the feature.

🔒 Enforcement Mechanism

This manifesto is enforced through:

1. Automated Drift Detection

Every pull request is analyzed by a GitHub Action that:

Compares code changes against manifesto principles
Flags violations (Low/Medium/High/Critical)
Blocks merge for High/Critical violations

Workflow: .github/workflows/charex-drift-check.yml

2. Amendment Requirements

Changes to this manifesto require:

Explicit justification document
Trade-off analysis
Leadership approval
Git commit with full explanation

3. Public Accountability

This manifesto is published at https://challaris.github.io/charisol-experiments/
All amendments are tracked in Git history.

📖 Examples of Compliant vs. Violating Features

✅ Compliant Features

Feature: Show buyer role → budget authority mismatch
Output: “Your ICP is mid-level managers, but purchase decisions require CFO approval.”
Why compliant: Surfaces economic reality without prescribing action.

Feature: Immutable diagnostic report with permanent link
Output: “This diagnostic is locked and cannot be edited. Share via: [link]”
Why compliant: Enforces locked truth principle.

Feature: Assumption transparency
Output: “This analysis assumes your ICP has $50k+ budget. If incorrect, conclusions change.”
Why compliant: Maintains epistemic honesty.

❌ Violating Features

Feature: Suggest A/B tests to validate assumptions
Output: “Run these 3 experiments to validate buyer urgency.”
Why violation: Crosses into advisory/prescriptive territory.

Feature: Generate editable diagnostic summary
Output: “Edit this summary before sharing with stakeholders.”
Why violation: Allows users to obscure uncomfortable truths.

Feature: Product-market fit score
Output: “Your PMF score is 6.5/10.”
Why violation: Creates false precision and optimizes for feeling good.

Feature: Recommend repositioning strategy
Output: “Reposition your product from X to Y to improve payability.”
Why violation: Prescriptive advice, not diagnostic truth.

🛡️ Edge Cases & Clarifications

Q: Can Charex show what changed between two diagnostics?

A: ✅ Yes — if it’s purely descriptive (e.g., “Assumption X changed from Y to Z”).
A: ❌ No — if it suggests what to change or celebrates improvement.

Q: Can Charex explain how payability scoring works?

A: ✅ Yes — transparency about methodology is epistemic honesty.
A: ❌ No — if the explanation includes “how to improve your score.”

Q: Can Charex provide case studies or examples?

A: ✅ Yes — if they illustrate diagnostic patterns (e.g., “Companies with this mismatch often face X”).
A: ❌ No — if they suggest “do what this successful company did.”

A: ✅ Yes — locked truth should be shareable.
A: ❌ No — if users can edit before sharing.

📬 Amendment Process

To amend this manifesto:

Create amendment proposal document with:
- Proposed change
- Justification (why current manifesto is insufficient)
- Trade-off analysis (what we gain vs. what we risk)
- Impact assessment (how this affects existing features)
Leadership review and approval
- Must be approved by product and engineering leadership
Git commit with full context
- Commit message must link to amendment proposal
- Amendment must be documented in commit body
Public transparency
- Amendment history is publicly visible via Git log
- Must update “Last Amended” section below

📅 Amendment History

Version 1.0 — January 12, 2026

Initial manifesto published
No amendments yet

🏁 Final Commitment

This manifesto exists because product drift is inevitable without explicit constraints.

Every feature that makes Charex “more helpful” risks making it less truthful.
Every output that makes users feel good risks obscuring economic reality.

This document is our line in the sand.

Charex shows you what you’re actually betting on — before you place the bet.

Nothing more. Nothing less.

This manifesto is permanent and enforceable. Changes require explicit justification and leadership approval.