Kungfu UNGFU™Developer Platform

Back to Core homeruntime / complete mechanism

Core runtime mechanism

Inspect the complete journal, observation, durability, semantic, qualification, and source-contract path.

libkungfu runtime substrate

Append once, observe live, and recover from the same retained evidence path.

The mmap journal, typed storage services, Fact and Episode operations, projections and explicit durability frontiers form the native runtime mechanism.

One journal, four local views
Agent worker Appends action, lifecycle and telemetry frames once.
Append-only mmap Episode journal One published frame stream is retained evidence and the local reader bus. single writer · many local readers
action
tool I/O
tokens
telemetry
Hub live tail Observe published frames without a second event pipeline. integration pattern
Supervisor Read heartbeat and progress without interrupting the worker. integration pattern
Rewind and replay Reopen retained evidence at a qualified frontier. implemented in qualified slices
Local readers Fan out one published stream to co-located consumers. implemented substrate

Claim boundary: Visibility is not durability; strong durability candidates are separately admitted and not the default universal claim. Replication, high availability, arbitrary side-effect recovery and battle-tested external adoption are not claimed.

Why mmap matters to an Agent Hub

The evidence path is already the observation path.

Storage is the bus

The journal is not copied into a second transport just to become observable. Retained frames are the local read surface.

Observation stays off the writer path

Readers attach to published mmap pages, so each observer does not require a new writer-side copy or broker hop.

Recovery starts from retained truth

After failure, resume from the last qualified published or durable frontier and classify any unacknowledged tail explicitly.

Runtime evidence × KFD semantics

Frames record what happened. Policy decides what it means.

The journal carries ordered evidence. KFD and each Hub's local policy define authority, admission, completion and what may safely happen next.

Read the KFD boundary

One stream, explicit frontiers

Visibility is not durability.

implemented

visible

A complete frame is published and available to declared live readers.

candidate-qualified

durable_group

A frame is at or below a selected batch durable watermark. Production durable ingest remains disabled by default.

candidate-qualified

durable_sync

Required data and metadata cross a named local durability barrier. Production durable ingest remains disabled by default.

future

replicated

A separate replication policy acknowledges the frame; this is not a current implementation target.

Evidence boundary

Qualified runtime boundary

Pinned product bundle

The runtime page is rendered from the exact @kungfu-tech/site package consumed by this deployment.

Package
@kungfu-tech/site@4.0.0-alpha.1
Source repository
https://github.com/kungfu-systems/kungfu
Pinned evidence ref
74198a765f8c7d0f69f7e2c848bca935e1f40646
Spec fixture
kungfu.site-bundle/v1
docs_url
https://core.libkungfu.dev/site-bundle.json

.kungfu format and workspace contract

Inspect the pre-release portable authority, required-reader behavior, version matrix, schema registry, retained vectors, workspace layout and preservation rules. Maturity: staged.

libkungfu

Embed the local truth-source loop, Episode lifecycle, query, verification, export and recovery. Maturity: qualified.

Python, npm and Cargo SDKs

Use the same native semantics through one idiomatic language ecosystem. Maturity: staged.

Standalone CLI and TUI

Discover, record, query, verify, maintain and export headlessly. Maturity: staged.

GUI

Run complete supported visual workflows over public lower contracts. Maturity: qualified.

Assembled Kungfu App

Install compatible official layers as one convenience product. Maturity: coming-soon.

Machine fields expected from upstream