HomeManifesto

The Tezit Manifesto

A new era of communication where context travels with synthesis.

15 min read
Version 1.0 • January 26, 2026

All Work Is Becoming Vibe Work

Vibe work is knowledge work where you direct AI to accomplish outcomes rather than manually performing each step—you manage context, intention, and quality rather than execution.

We are living through the most significant transformation of knowledge work since the invention of the spreadsheet. AI assistants are fundamentally changing how humans synthesize information, make decisions, and communicate ideas.

The 99% of workers who aren't developers—lawyers, analysts, project managers, executives—are discovering they can load documents into an AI, ask questions, and receive synthesis that would have taken hours to produce manually. This is vibe work: directing AI with intent rather than performing rote information processing.

But there's a problem.

We have new tools for creation, but the same broken tools for transmission.

When a knowledge worker uses AI to synthesize documents, emails, data, and conversations into an insight, they can only share the final output—a PDF, a slide deck, a summary email. The reasoning is lost. The sources are detached. The scaffolding that supported the conclusion is dismantled the moment the artifact is "done."

Recipients must trust the summary or reverse-engineer the work. Phone calls are scheduled to "walk through the thinking." Documents are revised sequentially, with context lost at each iteration. Negotiations become adversarial because parties can't examine each other's evidence.

This is the fundamental bottleneck of modern knowledge work.

The Tezit Vision

Tezit is an open protocol for transmitting knowledge with its scaffolding intact.

A Tez (plural: tezits) is a bundle that carries:

  • The synthesis (the insight, recommendation, or position)
  • The context (the source materials that informed it)
  • The conversation (the AI dialogue that produced it)
  • The parameters (the negotiable assumptions)

When you share a Tez, recipients don't just read your conclusion—they can interrogate it. They can ask the AI the same questions you asked, against the same materials you used. They can reframe the synthesis for their perspective. They can fork it to create a counter-position with their own evidence.

The Tez is the native artifact of AI-augmented knowledge work.

Why Now?

The AI Moment

Large language models have crossed a threshold. They can synthesize multiple documents into coherent narratives, answer questions about complex material accurately, maintain context across extended reasoning chains, and cite sources and explain reasoning.

But every AI platform treats conversations as ephemeral. The synthesis happens, value is created, and then it evaporates into chat history. There's no artifact that captures the work.

The Collaboration Crisis

Knowledge work is increasingly collaborative, but our collaboration tools assume linear documents:

  • Documents: Single-threaded, no reasoning trail
  • Email: Sequential, context lost in forwarding
  • Chat: Real-time but ephemeral
  • Wikis: Append-only, no dialectic

None of these support what knowledge workers actually need: the ability to share reasoning and negotiate evidence.

The Trust Problem

In a world where AI can generate plausible-sounding content instantly, provenance matters more than ever. How do you know a summary accurately represents the source material? How do you verify that a recommendation is grounded in actual data?

Tezit solves this by keeping context attached. Recipients don't have to trust—they can verify.

The Cautionary Tale: Why Interface Matters

This protocol exists because of a specific failure.

A company founder needed to prepare a Statement of Work for deploying an AI platform to a client. Instead of the traditional approach, the founder loaded the actual codebase into an AI assistant—not documentation, but the code itself. Added the client's technical specifications. Added the company's SOW template. The AI could see both sides of the integration and generate accurate estimates based on real complexity.

The result was a git repository containing the contract, the source materials, and the complete AI conversation. The instruction to legal:

"There's a contract in here, and enough information for you to ask any question you like and get a good answer without having to call me."

A Tez existed. The concept worked perfectly. Context was assembled. Synthesis was produced. The bundle was transmitted with scaffolding intact.

But legal had no idea what to do with a git repository.

The paradigm succeeded; the interface failed. This is why Tezit.com exists. The protocol describes what to transmit. The platform solves how non-technical recipients consume it.

The Tezit Protocol

Core Concepts

The Tez

A Tez is a structured bundle with a well-defined format:

{tez-id}/
├── manifest.json      # Bundle metadata and structure
├── tez.md             # The synthesis (human-readable)
├── context/           # Source materials
│   ├── doc-001.pdf
│   ├── email-002.eml
│   └── data-003.json
├── conversation.json  # AI dialogue (optional)
└── params.json        # Negotiable parameters (optional)

The Tezit (verb)

To tezit is to assemble context, synthesize with AI, and bundle for transmission. The tezit process has three phases:

  1. Context Discovery: Gather and scope the relevant materials
  2. AI Synthesis: Develop the position through dialogue
  3. Bundle & Transmit: Package and share

The Interrogation

When you receive a Tez, you can interrogate it—ask questions that the AI answers from the transmitted context, not from its general training. This ensures the recipient can examine the same evidence the sender used.

The Fork

If you disagree with a Tez, you can fork it—creating a new Tez that starts with the original's context but adds your own materials and develops a counter-position. Forks create a tree of reasoning, not a flat document chain.

For the complete technical specification including JSON schemas and examples, see the Protocol Specification.

The Tezit Ecosystem

Tezit.com — The Platform

Tezit.com is to knowledge work what GitHub is to code.

GitHub provides:

  • • Repositories for code
  • • Commits for version history
  • • Pull requests for collaboration
  • • Issues for discussion
  • • Forks for divergent work

Tezit.com provides:

  • • Vaults for Tez storage
  • • Versions for Tez history
  • • Interrogations for AI-powered Q&A
  • • Discussions for context around tezits
  • • Forks for counter-arguments

The Open Protocol

The Tezit protocol is open source and vendor-neutral. Anyone can create tezits in any tool, host tezits on any storage, build Tezit-compatible applications, and contribute to the protocol specification.

Tezit.com is one implementation of the protocol, but not the only one. Organizations can self-host Tezit vaults, integrate Tezit into their own platforms, or use the protocol in ways we haven't imagined.

Use Cases

Business Negotiations

Before Tezit: Parties exchange term sheets. Each side builds their analysis independently. Negotiations happen through calls where people walk through spreadsheets.

With Tezit: Seller creates a Tez with their valuation model, comparable deals, and proposed terms. Buyer interrogates the Tez, identifies weak assumptions, forks with their counter-analysis. Both parties can see exactly where they diverge and why.

Research & Analysis

Before Tezit: Analyst writes report. Reader must trust the summary accurately represents sources. If questions arise, analyst schedules a call.

With Tezit: Analyst creates Tez with synthesis and all source materials. Reader interrogates to understand methodology. The reasoning chain is always visible.

Legal & Compliance

Before Tezit: Lawyer writes memo. Client reads conclusion but can't easily verify it against the actual regulations and precedents cited.

With Tezit: Lawyer creates Tez with legal analysis and all relevant documents. Client (or auditor) interrogates to verify conclusions are supported. Context is immutable and timestamped.

Education & Learning

Before Tezit: Professor publishes paper. Students read conclusion but don't see the analytical process.

With Tezit: Professor creates Tez showing how they developed their thesis. Students interrogate to understand methodology, fork to practice. The reasoning process is the curriculum.

Technical Architecture

Storage

Tezits are self-contained bundles that can be stored anywhere: local filesystem, cloud storage (S3, GCS, Azure Blob), Tezit.com vaults, IPFS for decentralized storage, or Git repositories.

AI Integration

The protocol is AI-model agnostic. Interrogation can use commercial models (Claude, GPT, Gemini), open models (Llama, Mistral), self-hosted models, or organization-specific fine-tuned models.

Security

  • Content Integrity: All context items are hashed (SHA-256)
  • Encryption: AES-256-GCM at rest, TLS 1.3 in transit
  • Access Control: Capability URLs, OAuth/OIDC, fine-grained permissions

Governance

The Tezit Foundation

The Tezit protocol is governed by the Tezit Foundation, a non-profit organization dedicated to maintaining the protocol specification, certifying compatible implementations, funding open-source development, and promoting adoption and best practices.

Protocol Evolution

Protocol changes follow a structured RFC process with community feedback, consensus voting, and migration periods for existing tezits.

Comparison to Existing Approaches

AspectTraditional DocsTezit
SynthesisYesYes
Attached contextNo (links at best)Yes (bundled)
AI interrogationNoYes
ForkingManual copyNative
Reasoning chainLostPreserved

vs. MCP (Model Context Protocol)

MCP and Tezit are complementary: MCP is a protocol for AI-to-tool communication during synthesis. Tezit is a protocol for bundling and transmitting the result. A Tezit implementation might use MCP internally for tool calls during synthesis, then bundle the result as a Tez for transmission.

Roadmap

2026 Q1: Foundation

  • ✓ Protocol specification v1.0
  • ✓ Reference implementation (Python, TypeScript)
  • ○ Tezit.com beta launch
  • ○ CLI tools for Tez creation and validation

2026 Q2: Adoption

  • ○ Integrations (Slack, Teams, email)
  • ○ Enterprise features (SSO, audit, compliance)
  • ○ Mobile apps (iOS, Android)

2026 Q3: Ecosystem

  • ○ Marketplace for Tez templates
  • ○ Public Tez discovery and search
  • ○ API for third-party integrations

Getting Started

Create Your First Tez

Terminal
# Install the Tezit CLI
npm install -g @tezit/cli

# Initialize a new Tez
tezit init "My Analysis"

# Add context
tezit add-context ./documents/report.pdf
tezit add-context ./data/metrics.json

# Synthesize with AI
tezit synthesize --model claude-opus-4

# Export bundle
tezit bundle --output my-analysis.tez

# Share
tezit share --upload tezit.com

Interrogate a Tez

Terminal
# Open a Tez
tezit open https://tezit.com/jane/acme-analysis

# Ask questions
tezit interrogate "What assumptions drive the revenue projection?"

# Fork if you disagree
tezit fork --reason "Different market assumptions"

Join the Movement

The way we work is changing. The way we share knowledge must change too.

Tezit is an open invitation to rethink knowledge transmission for the AI era. We believe:

  • Context should travel with synthesis
  • Recipients should be able to verify, not just trust
  • Collaboration should be dimensional, not sequential
  • AI augments human judgment, it doesn't replace it

If you share these beliefs, join us:

  • Use Tezit: Create and share tezits in your work
  • Build with Tezit: Integrate the protocol into your tools
  • Contribute: Help evolve the protocol specification
  • Spread the word: Share this manifesto
"The Tez is the native artifact of AI-augmented knowledge work."

— The Tezit Foundation

This document is licensed under CC BY 4.0. You are free to share and adapt it with attribution.