Back to Core product mapcurrent-contract / staged

.kungfu portable work format

.kungfu is a portable, verifiable record of real work.

It keeps one bounded piece of work—what happened, the facts and artifacts it produced, and the evidence needed to verify it—together so a fresh person or agent can inspect and continue it without reconstructing the story from a chat.

Why it exists

Keep the work, not just the conversation.

A folder keeps files. A transcript keeps words. Neither reliably tells the next agent what actually happened, which information was trusted, which outputs belong to the work, or how to check them. .kungfu keeps those relationships together.

What happened

An Episode records one bounded occurrence. Facts record the state the work relied on.

What it produced

Artifacts, a Manifest, Receipts and dependencies keep outputs connected to the work that produced them.

Why it can be checked

Content roots let another reader verify the retained material before trusting or acting on it.

A simple handoff

How a fresh agent continues the same work

Work

An agent performs a bounded piece of real work and produces facts, artifacts and evidence.

Retain

.kungfu keeps the Episode and its verification material together instead of leaving context scattered across a chat and a folder.

Continue

A fresh agent can inspect what is known, preserve material it does not yet understand, and act only when the required semantics are compatible.

Safe reader behavior

Not understanding something is different from losing it.

Preserve

Keep unfamiliar but well-formed material as exact bytes without pretending to understand it.

Inspect

Read structure and verification evidence within the reader's declared capability.

Act

Deriving canonical state, admitting it as trusted, or executing it requires complete compatible semantics.

Current boundary

Qualified does not mean stable.

This packaged format authority is qualified but still pre-release. It proves the current contract and retained test corpus; it does not promise stable compatibility or automatic understanding of every future format.

For implementers and auditors Inspect the exact Spec contract, compatibility rules, roots and machine artifacts. This material remains complete, but it does not have to be understood before the product makes sense.

Package-declared surface model

An exact pre-release portable authority bundle, projected without creating a second format truth.

The site binds @kungfu-tech/spec@4.0.0-alpha.1, its normative root, v4 alpha baseline and artifact roots while the owning format, reader, migration, schema and vector contracts retain semantic authority.

Capabilities

Inspect the portable authority overview and exact package pickup coordinate.
Route required-reader profiles, compatibility tuples, migration ownership and the schema registry.
Inspect the qualified retained cross-version vector corpus and every rooted artifact without monorepo reach-through.
Render all eleven integrity-bound human page models directly from the installed package.

Known limits

The standalone portable format is pre-release and is not declared stable.
Package semver is a pickup coordinate, not a format compatibility algorithm.
The historical Spec 0.1 prose is non-normative.

Exact packaged Spec authority

The portable format is the versioned composition of independently owned semantic objects, containers, records, schemas, manifests, and content-root protocols.

Spec pickup: @kungfu-tech/spec@4.0.0-alpha.1
Format namespace: libkungfu:fact-ledger
Authority status: pre-release
Normative root: sha256:1aea26e10e7b142247254513f744b7c7bc5a06e4b65942d90a49ec1a064b9713
Retained corpus: v2 · 16 vectors · sha256:bd03705e65b8df296329e65753a577d5d4aee34a929e5e889ba20c95f9b3463d
Projection policy: exact-byte-copy-from-verified-@kungfu-tech/spec/v1

Composition rule: Compatibility is decided per authority and then composed against an explicit reader profile; no highest, latest, or package version may stand in for all axes.

Not one authority

one-mega-schema

Not one authority

one-global-version-number

Not one authority

one-json-document

Not one authority

one-directory-layout

Not one authority

one-npm-package

Not one authority

one-site-projection

Required-reader behavior

Preservation, structural inspection, and semantic authority are distinct capabilities. Unsupported semantics may remain exact bytes, but they never enter canonical fold, admission, or execution.

preservation

none

Semantic scope: none

Unknown material: preserve-only

Unsupported root: preserve-only

inspection