Package Exports

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (kytip-pm) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Kytip

+------------------------------------------------------+
|   [ ]   [ ]   [ ]          +--------------------+    |
|     \    |    /            | :::::::::::::::::: |    |
|      \   |   /     ---->   | :::::::::::::::::: |    |
|       \  |  /              +--------------------+    |
|        \ | /                    +----+----+----+     |
|         \|/                     | [] | [] | [] |     |
|          *                      +----+----+----+     |
|         /|\                         \    |    /      |
|        / | \                         \   |   /       |
+------------------------------------------------------+

Transcripts in. Durable project memory out.

Kytip takes noisy meeting input, preserves the flow, extracts operational signal, and reconciles it into one workspace memory surface.

raw transcript batches -> structured meeting packets
packets -> ledgers, streams, project pages, portfolio brief
pm-state/ -> one terminal hub instead of scattered docs

Agent-Oriented, Not Agent-Locked

Kytip is built for agentic workflows, but it is not tied to one provider or one orchestration stack.

works with Codex, Claude, OpenAI, local models, or manual operators
runtime contract is only pm-state/
if you use ACE, pair it with ace-swarm
Kytip itself does not require ACE, Codex, Claude, or provider-specific state

What It Ships

PMing workflow assets and optional adapter packs
a seeded pm-state/ workspace skeleton
a terminal UI for overview, kanban, and note navigation
templates, references, and validation helpers

The shipped package surface is intentionally narrow:

contents come from package.json#files
runtime UI lives at assets/runtime/kytip_ui.js
internal discovery/spec docs and transcript-derived run outputs do not ship

Workflow

Kytip expects a workspace with pm-state/ and a provider or operator that can run this sequence:

meeting-packetizer
pm-ledger-updater
stream-reconciler
portfolio-brief-writer

That produces:

pm-state/meetings/*.md
pm-state/ledgers/*.md
pm-state/projects/*.md
pm-state/STREAMS.md
pm-state/PORTFOLIO_BRIEF.md

Quick Start

From source:

./assets/scripts/bootstrap-workspace.sh /path/to/workspace
cd /path/to/workspace
./kytip

From npm:

npx --package kytip-pm kytip-bootstrap /path/to/workspace
cd /path/to/workspace
./kytip

If the workspace is already bootstrapped:

npx --package kytip-pm kytip --workspace .

Terminal Hub

kytip reads only pm-state/ and gives you one place to inspect:

portfolio summary
blockers and gates
active actions and next steps
meeting and project notes

Controls:

1 2 3 switch tabs
h l move across kanban lanes
j k or arrows move selection
Enter opens the selected source note
PageUp / PageDown scroll note content
r refresh from disk
q quit

Build And Pack

Local validation:

npm run check
npm run pack:dry-run

Optional rebuild if dev dependencies are installed:

npm run build

Published package:

package name: kytip-pm
CLI: kytip
UI alias: kytip-ui
bootstrap helper: kytip-bootstrap

Clean Repo Boundary

These are maintainer-only and not part of the shipped runtime:

agent-state/pming/*.md
repo-local smoke outputs
local caches like .npm-cache/
root-level workspace artifacts such as .kytip/, .agents/, and pm-state/

Collaboration

Reach out at voybio.fundr@gmail.com for collaboration, ideas, or integrations.