KYB releases

14 releases from 2026-08-08 to 2026-11-09, 165 downloads of release files.

v0.3.4latest

· kyb v0.3.4

kyb v0.3.4 for aarch64-apple-darwin (Apple Silicon), Docker (linux/amd64, linux/arm64) and crates.io. Intel macOS is not supported.

A patch release. It adds a decision journal for agent teams and a bounded brief before the work, plus a one-line installer.

Decision journal: kyb confident (#55)

When an agent asks its owner to decide something (a release, a deploy, a push, a deletion, a public post, a design choice), it records the question, the answer and later the outcome. Before the next question it asks what was decided before about the same thing.

  • kyb confident check "<one English line>" returns up to three earlier decisions from other sessions (who decided, the verdict, the owner's words, the outcome), hazards and lint on the draft question.
    • Hazards are the same kind of step on the same target that was corrected, rejected, reverted, dropped or never answered.
    • The lint flags several decisions bundled into one question, and facts left unchecked.
  • kyb confident ask opens a record when the agent asks. It runs the same check and returns an id.
  • kyb confident decided <id> records the answer: approve_plain, approve_with_additions, choose_option, defer, correction, reject, confused, counter_question or redirect. The owner may choose an option nobody listed. A retry with the same answer commits nothing.
  • kyb confident outcome <id> appends what came of the decision (kept, corrected, reverted, dropped). A ref to the evidence is required.
  • kyb confident abandon <id> marks a question nobody answered.
  • kyb confident open lists records still waiting for an answer; one open for more than 48 hours is marked stale.
  • Storage. Records are JSON files under confident/ in the same git repository, so every change is a version. Ordinary search, the brief and the export never rank them.
  • Matching.
    • It runs on the one-line gist with the embedding model the server already uses; each gist is embedded once, when it is written.
    • Without a model it falls back to word overlap.
    • The same kind of step on the same target counts as a precedent however it was worded.
    • Records from the caller's own session younger than an hour are left out: that is the same conversation asking again.
  • Refused workspaces. KYB_CONFIDENT_DENY lists workspace name fragments whose writes are refused.
  • API, MCP and the skill.
    • Routes /confident, /confident/check and /confident/{id}/decided|outcome|abandon; capability confident.
    • MCP tools kyb_confident_check and kyb_confident_open are read-only. kyb_confident_ask, kyb_confident_decided and kyb_confident_outcome write and are left out with ?readonly=1.
    • The skill and the MCP instructions tell an agent to check before every question to its owner. A precedent is evidence for the agent to judge, never permission.

Session brief: kyb brief (#53, #54)

kyb brief (GET /brief, MCP kyb_brief) shows what is live in the base, as pointers only. It lists:

  • deadlines;
  • open incidents by severity;
  • active work (in progress, blocked, urgent);
  • knowledge retracted or changed recently, with who wrote it.

Each section is capped, so the brief fits in about 40 lines. The skill and the MCP tool tell an agent to call it before infrastructure work, as context and never as a to-do list. Nothing calls it automatically, so sub-agents do not each load it into their context.

Install

  • One-line installer (#46, #49). https://kybmemory.com/install.sh picks the install path:
    • Apple Silicon with Homebrew: Homebrew;
    • a machine with usable Docker: the Docker image (rootless included);
    • macOS without Homebrew: the release archive under launchd. Running it again upgrades in place. KYB_MODE=client installs only the CLI and skill; KYB_DRY_RUN=1 prints the plan.
  • Public compose file. https://kybmemory.com/docker-compose.yml.
  • Skill installer (#50). On a fresh machine it creates the agent's instructions file instead of skipping it.

Fixed

  • The CLI refuses a key that is not a slug with exit 1 (rejected) rather than exit 3 (unreachable) (#41).
  • MCP refuses such a key instead of panicking the handler (#42).

Build and CI (#47, #48)

  • Builds and tests run through Mitts in CI and in the Docker image.
  • CI runs the installer for real on Linux amd64 and arm64 and on macOS, including an upgrade from the previous release.
  • CI installs Mitts from crates.io when the release download fails.

v0.3.3

· kyb v0.3.3

kyb v0.3.3 for aarch64-apple-darwin (Apple Silicon), Docker (linux/amd64, linux/arm64) and crates.io. Intel macOS is not supported.

A patch release. The console now shows deadlines; the CLI reports failures in its exit code and names the right agent; tags survive rewrites.

Deadlines in the console (#35)

  • A strip under the header, on every tab. It lists what is late or nearly due, late first, as in the deadlines block of every read answer. An item opens its task, "all deadlines" opens the by-date view, and × hides the strip until tomorrow. When nothing is late or near, there is no strip.
  • Tasks. A "late or due soon" queue and a due column (6d late, in 3d, or the date when the task is outside its reminder window). A late task, or one waiting on an event, carries a note in its row.
  • By due date. Rows grouped Late / This week / Later / No date under a 30-day ribbon: the past in red, a dot per deadline (square for hard, dashed for provisional). Pressing a dot moves the cursor to its row.
  • The task card. A late task gets a callout saying how late it is, with Move date and Done. A provisional date shows what it waits on, with "It happened — set the date".
  • The task form. Due, Hard, Remind, and "the date depends on an event" (Waits on, Expected).

The console sends its own date as X-KYB-Today, like the CLI.

Deadlines, corrected (#34)

  • A deadline with a date and time is now judged by its own calendar day against the caller's today, the same way as a bare date. It is also late once its instant has passed, as long as the caller's today is the present (#31).
  • The per-response block lists what is late first (hard before soft, the latest first), then what is coming. A distant hard deadline can no longer push a late task out of the five-item cap (#32).

CLI

  • Exit codes (#30). 0 success, 1 the server rejected the request, 2 server error, 3 the server could not be reached. On a failure the error goes to stderr and stdout stays empty. See kyb --help.
  • The agent that wrote it (#33). The CLI walks up its process tree and records the nearest agent and that agent's own session. Claude Code inside an Antigravity terminal is now recorded as Claude, not as Antigravity. KYB_AGENT still overrides it.

Tags (#38, #39)

  • Rewriting an incident or a task keeps its tags unless the write names them, over the CLI, HTTP and MCP alike. --tags "" (or []) clears them.
  • A tag filter lists everything carrying the tag across knowledge, incidents and tasks, beyond the first hundred.

Fixed

  • /api/audit read while a record was being written could return fragments of it, and the console's ledger broke on them. Records are now written in one piece, and a line still being written is skipped (#35).

Install

brew install alex09x/apps/kyb          # Apple Silicon
cargo install knowyourbusiness --locked  # kyb-server only
docker pull ghcr.io/alex09x/kyb:v0.3.3

v0.3.2

· kyb v0.3.2

kyb v0.3.2 for aarch64-apple-darwin (Apple Silicon), Docker (linux/amd64, linux/arm64) and crates.io. Intel macOS is not supported.

A patch release with one addition: deadlines on tasks, which the server surfaces on its own (#27, #28).

Deadlines on tasks

A date written into a task's title as prose can be neither sorted nor noticed. A task now carries it as data:

  • due: YYYY-MM-DD, or a date-time with its zone (2026-03-14T17:00:00-07:00). A time without a zone is refused.
  • hard: missing it has consequences outside the team (an expiry, a contract, a regulator). Hard deadlines come first and are surfaced earlier.
  • remind_days: how far ahead to start surfacing it. The default is 14 days, or 30 for a hard deadline.
  • waits_on with expected: for a date that depends on an event. The provisional date is reminded on, and marked provisional, until the real due is set.

The fields live in the frontmatter like every other field. Moving a date is a new version, so kyb history and kyb diff show when it moved and who moved it. A deadline field left out of a write keeps its stored value, so rewriting a task never drops its due date; clearing the date clears the deadline whole. Tasks without a deadline are stored exactly as before.

kyb task --key task-renew-api-cert --title "Renew the certificate" --due 2026-03-14 --hard <<< "body"
kyb task-status task-renew-api-cert --due 2026-03-21     # no --status needed to move only the date
kyb deadlines [--within 14d] [--overdue] [--hard] [--tag a,b] [--assignee A] [--json]

Deadlines in every read answer

/search, /knowledge/{key}, /tasks and /incidents, and with them every CLI and MCP read, carry a deadlines block when an open task is late or inside its reminder window. The block holds up to five items, hard ones first and then by date, each with its days_left. A query scoped by tag shows that area first. When nothing is due there is no block at all. The CLI prints it as a short banner on stderr, so stdout stays the server's JSON:

kyb deadlines, today 2026-03-16: 1 overdue, 1 due soon
  2d late    HARD task-renew-api-cert  Renew the certificate  (due 2026-03-14)
  in 4d      task-answer-quote  Answer the vendor's quote  (expected 2026-03-20, waits on the quote)

To leave the block off, use --no-deadlines, ?deadlines=false, or MCP "deadlines": false.

GET /deadlines (kyb deadlines, MCP kyb_deadlines) is the full calendar: every open task with a date, grouped overdue, this week and later. Closed tasks, and tasks archived without closing, never appear.

A bare date is judged by the caller's calendar: the CLI sends its own date as X-KYB-Today. Other callers get the server's date in its TZ. The image now ships tzdata, and Compose passes TZ (default UTC).

The server advertises a new deadlines capability. The CLI checks it before sending a deadline flag, --no-deadlines or kyb deadlines, because an older server would silently drop the fields.

KYB reminds; it does not schedule. There are no notifications and no recurrence. The agent skill has a recipe for a session-start hook that prints kyb deadlines --within 14d.

Also

  • The agent skill now states that --history searches every version, the current one included, and that --as-of and --changed-between are lexical-only (#26).

Install

brew install alex09x/apps/kyb          # Apple Silicon
cargo install knowyourbusiness --locked  # kyb-server only
docker pull ghcr.io/alex09x/kyb:v0.3.2

v0.3.1

· kyb v0.3.1

kyb v0.3.1 for aarch64-apple-darwin (Apple Silicon), Docker (linux/amd64, linux/arm64) and crates.io. Intel macOS is not supported.

A patch release with one addition: a full export of the base.

Export: every key of the base as of one commit

Search ranks and caps its answer at 100, so it cannot answer "everything in the base", and before this release no route listed all knowledge or any retracted knowledge.

GET /export?at=<rev>&after=<key>&limit=N returns JSON lines:

  • a snapshot line: the commit, total, and counts per kind and state;
  • one entry line per key, in key order, with state: active (its file is in that commit's tree), archived (an incident or task closed out of it) or retracted (knowledge taken out). A removed key reads as it was just before its removal and carries the removing commit;
  • an end line with next_after and complete.

Pages that pass the same at=<sha> read one commit, so writes made between pages change nothing; a commit outside HEAD's history is refused. Earlier versions are not part of the export; kyb history <key> lists them. The route needs the read role, like /search.

kyb export [--at <sha>] [--out FILE] [--page N] pages through one snapshot and checks every page before asking for the next (same snapshot, keys after the cursor and in order, a cursor that advances), then the whole result (no key twice, the announced counts and total, a last page that says complete). It exits 1 with the problems otherwise. The command is gated on the server's new export capability, so an older server is refused rather than asked.

Install

brew install alex09x/apps/kyb          # Apple Silicon
cargo install knowyourbusiness --locked  # kyb-server only
docker pull ghcr.io/alex09x/kyb:v0.3.1

v0.3.0

· kyb v0.3.0

kyb v0.3.0 for aarch64-apple-darwin (Apple Silicon), Docker (linux/amd64, linux/arm64) and crates.io. Intel macOS is not supported.

109 commits since v0.2.3, every one reviewed before merge.

Attribution: every write records who made it

Each commit in the canon now carries four trailers: Kyb-Agent, Kyb-Session, Kyb-Workspace, Kyb-Via. The same record is returned as by in history, in the activity ledger and on the Versions tab of the web console, and kyb whoami shows what the current shell would write.

The agent and its session are chosen together from one source and never borrowed from a source that names another agent. via names that source:

  • cli: the kyb command read its environment.
  • hook: Claude Code called the kyb MCP tools and a decision-free PreToolUse hook supplied the record.
  • meta: the MCP client's own call metadata named the conversation (Codex, Antigravity).
  • headers: the client sent X-Kyb-Agent / X-Kyb-Session / X-Kyb-Workspace itself.

Workspace names stay inside the repository (a repository-relative path, never an absolute one). The git author stays kyb.

Boundaries, stated precisely. The cli and hook paths have live evidence from the fleet; the meta formats for Codex and Antigravity are fixture-tested and have not yet been exercised by a live client. There is one via per write, not per field; per-field provenance and "unknown" reasons are deferred. The record is supplied by the caller: it is attribution, not authenticated identity. Commit author metadata is not cryptographic commit signing.

Access: tokens and three roles

A caller presents a bearer token; the server looks it up in a book of principals kept outside the knowledge repository (KYB_AUTH_FILE, on the volume under Compose; a book inside the canon is refused). Roles: read < write < admin. Modes (KYB_AUTH): off as before; compat honours a token when sent and keeps full access for callers without one (rollout on a trusted bind, protects nothing); required admits no one without a token, or the role in KYB_ANON for a public demo. The book is re-read when it changes, so issuing and revoking need no restart. kyb-server auth add|token|revoke|list edits it on the machine that holds it; kyb login|whoami|logout on the client, the token sent through a curl config stream and never on the command line.

A write made with a token is committed under the token's principal; a write without one keeps the service signature and is shown with no author, so nothing is attributed to the owner by default any more. The audit log gains an actor field, including for refused requests. The web console asks for a token on 401 and hides every control the role would be refused. The maintainer's own preview runs auth=off: shipping roles does not mean a deployment enforces them.

Point-in-time search answers from the snapshot, never from a superseded version

--as-of T now selects the version current at T for every key first, then applies the text and metadata predicates. A version already replaced at T never answers, even if nothing newer matched. Knowledge deleted at T' is absent from every snapshot after T' (archived incidents and tasks are not deletions: they stay findable at their last version). A later rewrite with the same text is a new version. Documents and their tombstones are published as one generation, so a reader never sees documents from one commit paired with tombstones from another. The matching set is counted before it is fetched, so no fixed candidate budget truncates it. --history still returns every version; --changed-between keeps its contract.

History index

One index over the whole canon, extended by the commits since, replaces a walk over every commit per question. A card's history was a second per request; it is now served from the index. The start-up walk reports what it skips instead of refusing to start.

Relations

The force-directed topology graph drawn from tags and hosts is gone: no edge in it was something an author wrote. Relations are now derived from what entries actually say and stored nowhere: an incident's or task's knowledge list, a task's parent_task, and internal links in the body ([[key]], [text](key), [text](#/knowledge/key); fenced blocks and inline code are skipped, a key merely mentioned is not a link). Three read endpoints: /knowledge/{key}/related, /places (services and hosts named by incidents, the worst first) and /impact?service=|host=. The console gets a Services tab and a Related section on every card, each row with the reason it is there. Nothing is inferred from tags. An archive note is settled by its own number, and a build consumes only the notes it acted on.

Web console

A redesign to one quiet system: one type scale, one accent, colour only where state demands it; every control checked against the design. Incidents and tasks are attention queues with the reason in the row; Activity is a change ledger showing the whole change; History and Diff are one Versions panel listing every version with everything it changed, who wrote it and from where. Deep links and permalinks, #tag filters, paging at 40, a card that draws before its history arrives, and a browser test that drives every screen and every write a person can make, with block coverage of the UI script gated at 100% in CI. The page is assembled from src/web/css and src/web/js at compile time and served from the binary unless KYB_UI_PATH says otherwise.

Deploy

scripts/deploy.sh installs the exact digest the CI run smoke-tested (published as an artifact only after the smoke passed), keeps a named rollback, waits for a cold start, compares the running image id with the pinned digest's local id, and refuses a stale UI override. The served-page marker identifies a console generation; the pinned image identity identifies the deployed artifact.

Registry and citation

server.json and glama.json describe the MCP server for the registries. CITATION.cff is at 0.3.0 and cites the concept DOI 10.5281/zenodo.22850723; the versioned DOI of this release is added once Zenodo archives it. The 0.2.3 record (10.5281/zenodo.23027682) remains the DOI of 0.2.3 only.

Known, not blocking

Card "ago" labels from a date-only updated_at; kyb query brief output, scores and --help; canon git gc automation; kyb lookup / context / verified_at. The audit deliberately omits the console's polling routes, so it is not a complete traffic record.

Install

brew install alex09x/apps/kyb          # Apple Silicon
cargo install knowyourbusiness --locked  # kyb-server only
docker pull ghcr.io/alex09x/kyb:v0.3.0

v0.2.3

· kyb v0.2.3

kyb v0.2.3 for aarch64-apple-darwin (Apple Silicon). Intel macOS is not supported.

v0.2.2

· KYB 0.2.2 — crates.io installation and author metadata

KYB 0.2.2 adds installation from crates.io and consistent author and citation metadata.

  • Install the server with cargo install knowyourbusiness --locked.
  • Alexander Panasenko is identified in Cargo metadata, the README byline, MIT copyright and CITATION.cff.
  • The README links the project website and registry, separates server installation from the client and optional model setup, and labels the Zenodo citation as archived v0.2.1.

Website · crates.io · Author

Install

Rust package, server binary:

cargo install knowyourbusiness --locked

Apple Silicon macOS, prebuilt server and CLI through Homebrew:

brew install alex09x/apps/kyb

For an existing Homebrew installation:

brew update
brew upgrade alex09x/apps/kyb

The attached aarch64-apple-darwin archive includes the server, CLI, agent skill, README and MIT license. The native binary targets Apple Silicon; see the README for Docker and model setup.

Validation: 321 Rust tests, macOS server/CLI smoke checks, package installation and an isolated health check passed. The downloaded crates.io artifact matches the verified package by SHA-256.

v0.2.1

· kyb v0.2.1

kyb v0.2.1 for aarch64-apple-darwin (Apple Silicon). Intel macOS is not supported.

v0.2.0

· kyb v0.2.0

kyb v0.2.0 for aarch64-apple-darwin (Apple Silicon). Intel macOS is not supported.

v0.1.4

Make kyb --help exit successfully for Homebrew and automation checks.

v0.1.3

Pure-HTTP kyb CLI with Homebrew installation support and release-driven tap formula automation.

v0.1.2

· v0.1.2 - Release with big@prod.codes badge link

Updated README.md badge link to mailto:big@prod.codes and updated author email.

v0.1.1

· v0.1.1 - Fix docker-compose image tag

Updated docker-compose.yml image reference to ghcr.io/alex09x/kyb:latest.

v0.1.0

· v0.1.0 - Initial Release

Initial release of KYB service with automated Docker publishing pipeline.

Release history from GitHub as of 2026-11-16.