Create a new chain from a ticket. Generates chain_id from kebab-case title.

Read chain state filtered through progressive disclosure.

Early-phase chains show fewer fields to reduce cognitive load. Full data always accessible via direct YAML read.

Lightweight status check: current link, phase, health.

Update chain status with state transition validation.

Tag chain with entity ownership (which subsidiary).

General metadata updates: vision, entity, capacity_role, notes.

Add a new session link to a chain. Auto-increments link_number.

Mark a chain link as complete, record deliverables.

Pause chain — preserves state, signals 'not abandoned'. Idempotent.

Resume a paused chain. Only valid from paused state.

Mark entire chain complete. Lifecycle hooks per Decision 1.

    Bug-fix/maintenance chains: auto-close associated ticket.
    Other chain types: advisory suggesting ticket closure.
    

Move completed chain to archive with retention metadata.

Fork chain when work splits. Parent doesn't complete until all branches do.

Fork a chain when work needs a different type (Decision 5).

    Type changes create child chains; parent retains its type and
    history. spawn_reason is required — it's what makes cross-domain
    ideation patterns researchable.
    

Rename a chain: updates chain_id, renames YAML file, and fixes all cross-references.

    Updates: chain file, ticket references, declaration files, handoff files,
    catch files, and parent/child chain references.
    

Create a new ticket with auto-assigned sequential ID.

Read full ticket state.

Update ticket metadata and/or append a note.

Close ticket. Advisory: flags if associated chain is incomplete.

Add or remove tags on a ticket.

Associate a ticket with a chain.

    If the chain already has an origin ticket (ticket_id) and the linked
    ticket is different, the ticket is added as a child_ticket (Decision 2).
    

Promote a standalone ticket into a chain (Decision 1).

Creates a chain from the ticket, scans for related tickets (same entity + overlapping tags), and returns candidates for nesting. Optionally nests specified tickets immediately.

Read growth stage for a specific role or all roles.

Record a stage transition (training-wheels -> partnership -> safety-net).

Log a capacity-relevant event with typed attribution (Partner's field notes).

Query capacity event history with optional filters.

Evaluate if any role has hit its stagnation threshold.

Stagnation = active engagement but no growth. Dormancy = no engagement at all. Both surfaced as observations, not errors (Design Principle 2).

Search chains by entity, status, session type, date range.

List all active chains (lightweight summary view).

Search tickets by type, entity, priority, status.

List all open tickets.

Aggregate view: active chains, open tickets, capacity summary, alerts.

    First tool called every session — gives Partner the full operational
    picture in one call.
    

Detect stagnant/forgotten chains. Always active regardless of capacity_tracking.

Write Session Declaration to current chain link.

    6 components: type, goal, deliverable, completion criteria,
    out of scope, partner confirm.
    

Write session-end handoff to chain link and data directory.

Captures decisions, files changed, open threads, emotional context, and next-session recommendation.

Log session-type leapfrog in chain metadata (Design Principle 1).

Partner flags, explains cost, asks — never refuses. The skip is recorded to enable pattern detection over time.

Log Catch firing with qualitative capture.

    Catch events firing = system working, not failure. The metric is
    whether catches lead to better decisions, not whether they stop.
    human_reasoning is optional but gold when present.
    

Create a new ticket. Generic — human specifies everything.

If the ticket type triggers Lockstep threshold (not maintenance), returns a prompt suggesting chain creation. The Partner handles the conversational follow-up.

Create initiative: ticket + full-funnel chain + discovery declaration.

    Pre-typed: full funnel (Discovery -> Research -> Planning ->
    Architecture -> Build -> Review). Starts in Discovery.
    

Create enhancement: ticket + chain + planning declaration.

    Pre-typed: Planning -> Architecture -> Build -> Review.
    Starts in Planning.
    

Create refactor: ticket + chain + architecture declaration.

    Pre-typed: Architecture -> Build -> Review.
    Starts in Architecture. scope = "what's being refactored and why?"
    

Create bug-fix ticket. Optionally creates chain.

    Pre-typed: Build -> Review (optional). Asks before creating chain
    via create_chain parameter. If false, ticket exists for tracking
    but no chain is created.