Package Reference

Use these pages when you need to choose or integrate one part of Kehto. Each page is grounded in the package manifest and source barrel for the current repository state.

Alpha status: Kehto is an early runtime implementation for a draft NIP-5D protocol. NAP contracts and package APIs are not final; use these package pages as current implementation guidance, not as a stability guarantee.

Package	Page	Role
@kehto/acl	ACL	Pure capability state and enforcement primitives.
@kehto/cli	CLI	Top-level kehto command namespace, including kehto paja.
@kehto/paja	Paja	Single-window local authoring workshop for loading a target app URL in a Kehto iframe.
@kehto/firewall	Firewall	Pure behavioral abuse-detection engine (temporal complement to ACL).
@kehto/runtime	Runtime	Browser-agnostic NIP-5D protocol engine.
@kehto/shell	Shell	Browser shell adapter over the runtime.
@kehto/services	Services	Reference service handlers for runtime domains.
@kehto/nip	NIP utilities	Unique Nostr NIP utilities, including NIP-5A/5D napplet artifact verification and Cache Storage reuse.
@kehto/wm	Window Management	Structural window-management contracts.
@kehto/playground	Playground	9-napplet demo and verification target.

Reading Order

1. Start with @kehto/runtime if you are building a host.
2. Add @kehto/shell when you need browser iframe/session integration.
3. Add @kehto/services for reference implementations of runtime services.
4. Use @kehto/acl directly when you need capability-state persistence or policy tests, and @kehto/firewall for behavioral rate-limiting and abuse detection over time.
5. Use @kehto/nip and @kehto/wm as optional utilities.
6. Use @kehto/cli for package scripts such as kehto paja.
7. Use @kehto/paja directly when embedding or extending the Paja implementation API.
8. Use the playground page to reproduce integrated behavior locally.

Generated API reference lives under docs/api/. Package pages link to generated module pages for the public packages included in TypeDoc.