Product

A tracker your agent
can ship from.

Hydrant wires issues, decisions, notes, and dependencies into one graph — so an agent can pull context, ship work, and leave a trail you can read.

Briefs

An agent ships from a briefing, not a ticket.

A Brief is the issue, every decision it touches, every note it cites, and the dependency footer — assembled into one markdown payload your agent can read in a single pass.

Regenerate it any time the underlying graph moves. The same brief shows up over MCP, in your shell, and in CI.

HYD-88.brief.md

regeneratable

# HYD-88 — PAT handoff after signup

**Type**: task | **Status**: inReview | **Priority**: high

**Branch**: feat/pat-handoff

**Labels**: auth, onboarding

## Space · Hydrant

Project context that lives where the work happens — same actions, same audit trail, for humans and agents.

## Decisions

### DEC-24 — PATs are one-time reveal

- **Decision**: show the token once, never again.

- **Rationale**: rotation is cheaper than leakage.

## Notes

- spec/onboarding-flow.md · handoff sequence diagram

blocks → HYD-89·relates → HYD-71

HYD-88 · linked decisions

DEC-24PATs are one-time revealRevalidate

Revised 4m ago by Henry. Two issues depend on this decision and are now pending.

- show the token on every settings visit

+ show the token once, never again

Affected issues

HYD-88PAT handoff after signup

pending

HYD-71Settings · token rotation UI

pending

Decision propagation

When the call moves, every issue that leaned on it knows.

Decisions are versioned. Revise one, and every issue linked to it goes pending until someone acknowledges the new version still holds — or dismisses it as not relevant.

No silent drift. No agent shipping against a decision the team already moved past.

Readiness

Ready to ship is a checklist, not a vibe.

You decide what makes an issue shippable in your space — description, labels, the right cycle, the right milestone. Every issue carries its own readiness alongside its status.

Triage stops being a judgment call. Your agent stops guessing whether an issue is ready to pick up.

HYD-104Migrate auth middleware to Convex Auth

needsContext

Readiness checks

Description present

Label assigned

Priority set

Cycle attached

missing

Milestone routed

missing

3 of 5 checks satisfied · routing class missingCycle

Activity · audit logAppend-only

pivia Claude Codeset dependencies on HYD-88
set_dependencies·2m ago
HK
Henryrevised DEC-24
update_decision·4m ago
pivia Claude Codeadded a comment to HYD-71
create_comment·7m ago
MR
Marieacknowledged revalidation on HYD-89
ack_revalidation·12m ago
pivia Claude Codecreated HYD-90
create_issue·21m ago

Identity & audit

Your agent is a named account, not an anonymous token.

Claude Code, Cursor, Codex — each instance gets its own identity in your space. Every mutation carries the actor and the tool that did it.

You read what your agent did the same way you read your own commits — by author, with a diff, on a timeline.

The graph

Description prose isn't the source of truth.

Dependencies, sub-issues, and links between issues, decisions, and notes are first-class records. Replace them in one atomic call, not by editing a paragraph an agent hopes is up to date.

Briefs read the graph. Readiness reads the graph. Preflight reads the graph. One source, every surface.

HYD-88 · context graphLive

HYD-89Done

Handoff success state

blocks

DEC-24Decided

PATs are one-time reveal

decided by

MLS-07Milestone

Account handoff

3 of 8 done

part of