KINDNOTESVIEW
HOW IT WORKS.
A local record of what your agents learn and produce.
Superbee keeps what your agents produce and learn in a local, user-owned bundle: structured records, working notes about what happened, and the plans and designs the work itself creates. Five mechanisms make that safe to share and cheap to build on.
01 / Bundle
Keep durable work local.
A bundle is a folder in your repo. It holds structured records, working notes, and produced output. Records and notes are plain Markdown, while Views can be stored as opaque HTML blobs. A write can name the version it expects, so the CLI can reject a stale update instead of silently replacing newer work.
Evidence capture: bundle locate and file listing
schema_version: 1
locator:
kind: local-path
path: /private/tmp/how-it-works-v2-capture
selected_by: explicit-dir
available: true
conventions/task.md
conventions/view.md
references/view-authoring-v0.md
views-registry/review-workflow-reviews.mdsuperbee bundle locate --dir <bundle> and a real disposable-bundle listing. Superbee 0.1.3-pre.2, commit 8042c5d.02 / Conventions and kinds
Declare the shape that work follows.
A convention is structure the bundle declares about itself, flexible in what shape it takes and binding once declared. A kind is one type of convention: the one that governs a record type, declaring which fields are required, what values are allowed, and how records may link to each other. Writes against a kind are checked on the spot, so agents follow your structure instead of inventing their own.
Evidence capture: declared Task kind and rejected write
{"governs":"Task","required":["title","progress_status"],
"values":{"progress_status":["todo","in_progress","blocked","done","canceled"]},
"links":{"depends on":"Task"},"path":"tasks/"}
error:
code: USAGE
message: "'tasks/evidence-check' does not satisfy the 'Task' kind: 'progress_status' value 'unknown' is not one of the allowed values for 'Task': todo, in_progress, blocked, done, canceled."superbee kinds --dir <bundle> --json and a real rejected superbee new write. Superbee 0.1.3-pre.2, commit 8042c5d.03 / Recipes
Share practices among projects.
A recipe packages reusable definitions as installable text: kind declarations, reference notes, and Views. Portable definitions-only recipes reject instance data, while a recipe can also include static reference and View assets. A practice that works in one repo travels to the next as definitions, not as data.
04 / Views
Generate the views you need, when you need them.
A View is HTML that you or your agents define, showing the bundle however you want to see it: open incidents by service, work by priority, whatever the question is. It runs in a sandbox and reads through a narrow bridge. A View has no credential and cannot write; a propose-capable View can request one declared scalar update, which the CLI revalidates before a human applies it.
"Show open incidents grouped by service."
KINDSFIELDSLINKS
INCIDENTS
5 OPENOpen incidents by service
05 / Sync
Share a bundle when you are ready.
Your bundle stays local until you explicitly establish sharing. Once you do, sync uses Git to share bundle changes with the people you work with. Large files travel as bytes and never enter a context window. You choose when that happens.
ESTABLISH SHARING