Kytip

+-----------------------------------------------------------------------+
| [kytip] [bootstrap] [kanban] [notes] [streams] [portfolio]            |
|-----------------------------------------------------------------------|
|   | /    \ /    ---    ---    |~~\                                   |
|   |/      Y      |      |      |__/     K Y T I P                     |
|   |\      |      |      |      |                                      |
|   | \     |      |     ---     |                                      |
|                                                                       |
|   transcript batches -> packets -> ledgers -> streams -> terminal hub |
+-----------------------------------------------------------------------+

Kytip turns messy transcript drops into durable project memory inside the current workspace.

It gives you a repeatable local shape:

• meeting packets you can actually revisit
• ledgers for blockers, gates, decisions, actions, and next steps
• project and stream pages that survive chat-window loss
• a terminal hub over pm-state/, instead of forcing you to click through docs

Bootstrap Into A Workspace

Run this from inside the directory you want Kytip to materialize into:

mkdir my-workspace && cd my-workspace
npm exec --yes --package kytip-pm@latest -- kytip bootstrap
./kytip

Kytip writes into . and creates:

• ./.kytip/
• ./.agents/PMing/
• ./.agents/skills/...
• ./templates/
• ./references/
• ./tasks/
• ./pm-state/
• ./kytip

The portable skill contracts live under ./.agents/skills/. Deprecated PMing instruction overlays are not installed into the workspace.

Bootstrap is cautious:

• existing files are skipped by default
• pass --force only when you intentionally want to overwrite
• files under pm-state/ are operator state and are seeded only when missing; pm-state/CONTEXT.md is never overwritten by bootstrap

npm exec --yes --package kytip-pm@latest -- kytip bootstrap --force

Install Modes

If you want it pinned in a project:

npm i kytip-pm
npx kytip bootstrap
./kytip

If you want the command available everywhere:

npm i -g kytip-pm
kytip bootstrap
./kytip

If you are working from source:

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

What Kytip Actually Is

Kytip is agent-oriented, but not agent-locked.

• it works with Codex, Claude, OpenAI workflows, local models, or manual operators
• its runtime contract is just pm-state/
• if you are running ACE, pair it with ace-swarm
• it does not require ACE-specific runtime state to function

The default PMing passes are:

1. meeting-packetizer
2. pm-ledger-updater
3. stream-reconciler
4. portfolio-brief-writer

Those materialize:

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

Agent-Native Staging

kytip packetize batch.md
kytip status

kytip packetize stages prepared transcripts under pm-state/ingest/prepared/. kytip status shows what is still waiting for an ambient agent to run the meeting-packetizer skill and how many meeting packets already exist.

Prepared transcripts point the agent at pm-state/CONTEXT.md when present. That file is the operator-facing place for team rosters, project aliases, glossary terms, known mishearings, and corrections. Treat it as a disambiguation hint layer: it can guide packetization, but it must not override transcript evidence or silently become durable packet truth.

If the input contains base64-heavy payloads, Kytip elides the blob in prepared transcripts and writes compact sidecar records under pm-state/ingest/base64_sidecars/. Packet docs should carry only elision markers and sidecar references, never long base64 blocks.

PM-Lite Promotion Boundary

The standalone pm-lite skill is a lightweight note-cleanup mode. PMing can ship a packaged pm-lite helper, but root-level pm-lite/ is not modified by PMing bootstrap.

If you want to promote pm-lite output into full PMing state:

1. Review the notes as draft-only.
2. Route them through meeting-packetizer or kytip promote-raw.
3. Preserve source fingerprint/context references.
4. Never overwrite an existing packet; create an amendment sibling instead.
5. Validate the final packet before ledgers or briefs consume it.

The Terminal Hub

./kytip reads pm-state/ and brings the run together in one terminal surface:

• overview and portfolio pressure
• blockers and gates in one place
• active actions and next steps
• notes you can move through without leaving the TUI

Controls:

• 1 2 3 switch views
• h l move across kanban lanes
• j k or arrows move selection
• Enter jumps to the source note for the selected card
• PageUp / PageDown scroll note content
• r refresh from disk
• q quit

Package Surface

Published package:

• package name: kytip-pm
• primary CLI: kytip
• UI alias: kytip-ui
• bootstrap alias: kytip-bootstrap

What ships:

• files whitelisted in package.json#files
• runtime under assets/runtime/
• workspace bootstrap scripts and PMing assets
• agent, skill, and instruction contracts under .agents/

What does not ship:

• transcript-derived smoke outputs
• repo-local caches and throwaway run state
• internal sidecar/spec history that is not required at runtime
• workspace-root instruction spillover

Build

npm test
npm run pack:dry-run

If dev dependencies are installed, you can also rebuild the JS runtime:

npm run build

License

Kytip ships under the custom LICENSE.

Allowed without separate permission:

• personal use
• academic use
• research use
• evaluation use
• internal non-commercial use

Commercial use is not automatically granted. If you want to use Kytip in a paid product, service, internal commercial workflow, or partnership context, contact voybio.fundr@gmail.com.

Collaboration

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