Knowledge capability · Local archive

Ship a portable pack.

Build knowledge as a self-contained directory, validate it locally, then upload one immutable archive to E Hub.

Quick start

01

Build the directory

Keep normalized public records under the standard E directories and give every record a stable id.

02

Validate locally

Run the E validator before archiving. It checks references, revisions, and content hashes.

03

Upload once

Choose Local file in the publisher workspace and upload a .tar.gz or .tgz.

Pack structure

A pack is portable because the manifest and records travel together. The manifest identity must use the @publisher/name format.

knowledge-pack/
├── manifest.json
├── sources/
├── documents/
├── chunks/
├── entities/
├── relations/
└── revisions/

Validate and archive

The validator reads the directory before the Hub sees it. Keep archive creation reproducible and do not rewrite record bytes after validation.

# Validate the pack before publishing
npx @vxnus/e-knowledge ./knowledge-pack

# Create an archive without changing record bytes
tar -czf teyvat-1.0.0.tar.gz -C knowledge-pack .

# Check the archive locally
sha256sum teyvat-1.0.0.tar.gz

What the Hub does

01 · InspectChecks the archive type, size, safe paths, manifest, records, references, and revision content hash.
02 · FingerprintCalculates a SHA-256 checksum for the exact uploaded archive.
03 · DistributeStores the archive in R2 and records its public URL, checksum, release, and audit event.

The archive is immutable by package and version. Publish a new version when public content changes.

E-compatible consumption

After publication, any E-compatible AI discovers the archive through the registry and validates it before exposing it to the runtime.

GET https://e.vxnus.xyz/api/packs/acme/teyvat?version=1.0.0

distribution.kind: archive
distribution.url: https://knowledge.e.vxnus.xyz/...
distribution.checksum: sha256:...
Ready to upload?Build a project, then publish from the workspace.
Open publisher workspace ↗