PRIVATE ALPHA / COLLABORATIVE PLANS + SPECS

For teams already planning and building through coding and AI agents

People and agentsbuild one plantogether.

Tethr gives the people and existing agents in a workspace one evolving plan. People bring intent and constraints. Agents bring back what the work reveals, so the workspace can shape one consolidated spec together.

Join the private alpha.See the collaboration loop

The private alpha starts with versioned sections, connected-agent proposals, and human-reviewed releases.

proposal / review / current
An abstract plan artifact: proposals become current only after review.

THE SHARED WORKSPACE

One plan holds what the whole workspace knows.

People carry intent and constraints. Agents uncover implementation context. Tethr brings those contributions back to one evolving spec instead of leaving each collaborator with a different slice.

CONTEXT THAT BUILDS THE PLAN

  1. 01

    Product intent

    A person defines the outcome and the decisions that matter.

  2. 02

    Implementation context

    A connected agent proposes what the work reveals.

  3. 03

    Operating constraints

    A reviewer adds ownership and rollout boundaries.

  4. 04

    Consolidated plan

    People and agents read the same current, reviewable version.

THE COLLABORATION LOOP

Build together without losing the current plan.

The private alpha tests one complete collaboration loop. A person creates the plan, an authorized external agent reads the current version and proposes a section update, a person reviews the exact change, and the accepted state becomes a stable release.

  1. § 01Current alpha

    Start the plan

    A person creates structured sections for the outcome, decisions, and constraints.

  2. § 02Current alpha

    Bring back context

    An authorized external agent reads the current version and proposes one section update with rationale.

  3. § 03Current alpha

    Review the change

    A named person sees the source, base version, rationale, and exact diff before deciding.

  4. § 04Current alpha

    Share the current state

    Accepted sections become an immutable named release that people and agents can read.

THE REVIEW BOUNDARY

Human review keeps the shared plan trustworthy.

Collaboration does not mean silent mutation. An agent proposes a section against the version it read. A person sees the exact diff and accepts or rejects it. Tethr records the person and client behind the decision, then seals accepted changes into the next plan release.

  • Proposal tied to a known section version
  • Source, rationale, and exact diff stay together
  • A named person's decision creates the next release
CURRENT§ 4.2 rollout gate / v13

Releases go out behind a flag. The flag is flipped once smoke tests pass.

PROPOSED
41Releases go out behind a flag.
42The flag is flipped once smoke tests pass.
43The flag is flipped by a named person once smoke tests pass.
44The person who flips it is recorded with the release.
Reason (optional)

This is what a review looks like. Not a customer, not usage.

WHAT'S LEFT AFTERWARD

Accepted changes seal into a release you can point to: dated, attributed, closed.

This is what a review looks like: the proposed edit against the current section, accept and reject where the team expects them, and underneath, a sealed release stamped with the person who approved it, the client they were running, and when. Once sealed, it cannot be quietly edited, only superseded by another release that went through the same door. Open the history in three months and the team can reconstruct who approved which version without relying on memory.

REVIEWED BYMukul
CLIENTconnected MCP client
RELEASED2026-08-05, 11:52 PM
VERSIONv14
ACCEPTED
Sealed release

No proposals waiting. The plan is exactly as it was at the last sealed release.

WHAT RUNS INSIDE

No LLM runs inside Tethr.

It writes nothing. It summarizes nothing. It does not resolve conflicts, rank proposals, or hold an opinion about the plan. The proposals come from the team's agents. The release decision comes from a person. Tethr keeps that decision attached to a name, a client, a date, and the exact version it changed.

THE OPERATING LAYER

The approved plan should travel with the work.

Tethr is not another agent harness. The current alpha connects supported MCP clients to the review gate. The direction is a portable planning layer that gives every collaborator and connected coding or AI agent the same approved plan, the skills to use it, and a cited path back when the work changes what the team knows.

TETHR PLAN ARTIFACTproduct-plan / v14 / current
  • plan/sectionsVERSIONED
  • proposals/reviewCURRENT CORE
  • skills/tethrPLANNED
  • hooks/cliPLANNED
  • evidence/citationsDIRECTION
  1. 01

    Tethr-native plan artifacts

    Current core

    Section-addressed, versioned plans with immutable human-approved releases.

  2. 02

    Reusable Tethr skills

    Planned

    Plan-aware skills that travel into supported coding and AI harnesses.

  3. 03

    Optional CLI alignment hooks

    Planned

    Lightweight checks that keep agent work tied to the approved plan version.

  4. 04

    Collaborative proposal threads

    Direction

    Product, engineering, and operations discuss a proposed section before release.

  5. 05

    Evidence and context loop

    Direction

    Meeting and communication evidence returns as citations on proposed plan updates.