open-index/open-npm huggingface dataset:
npm package: @manifest-network/manifest-mcp-chain
Description: MCP server for Cosmos SDK chain operations (queries, transactions, module discovery)
Author: Felix C. Morency
Latest version: 0.5.0

# @manifest-network/manifest-mcp-chain

MCP server for generic Cosmos SDK chain operations. Registers 6 tools for queries, transactions, fee estimation, and module discovery.

## Installation

```bash
npm install @manifest-network/manifest-mcp-chain
```

## Tools

| Tool | Description |
|------|-------------|
| `get_account_info` | Get the address of the configured wallet |
| `cosmos_query` | Execute any Cosmos SDK query (bank, staking, gov, etc.) |
| `cosmos_tx` | Sign and broadcast any Cosmos SDK transaction |
| `cosmos_estimate_fee` | Estimate gas and fee for a transaction without broadcasting |
| `list_modules` | List all available query and transaction modules |
| `list_module_subcommands` | List subcommands for a specific module |

## Usage

### As an MCP server (via node package)

See [`packages/node/README.md`](https://github.com/manifest-network/manifest-mcp-mono/blob/main/packages/node/README.md) for CLI usage and MCP client integration.

### As a library

```typescript
import { ChainMCPServer } from '@manifest-network/manifest-mcp-chain';

const server = new ChainMCPServer({
  config,          // ManifestMCPConfig from core
  walletProvider,  // WalletProvider from core
});
```

## Build

```bash
npm run build    # tsdown (platform: neutral)
npm run lint     # tsc --noEmit
npm run test     # vitest
```

## License

MIT
npm package: @manifest-network/manifest-mcp-core
Description: Shared library for Cosmos SDK blockchain logic, tool functions, and server utilities (Manifest Network)
Author: Felix C. Morency
Latest version: 0.5.0

# @manifest-network/manifest-mcp-core

Shared library for Manifest MCP servers. Contains Cosmos SDK logic, on-chain tool functions, server utilities, and the LCD/REST adapter. This package is **not** an MCP server itself -- it provides building blocks that the chain, lease, fred, and cosmwasm packages compose into servers.

## Installation

```bash
npm install @manifest-network/manifest-mcp-core
```

## What's inside

- **CosmosClientManager** (`client.ts`) -- Keyed-instance client lifecycle with rate limiting and lazy init (RPC + LCD)
- **LCD adapter** (`lcd-adapter.ts`) -- Converts LCD/REST responses to the RPC query client shape, making the codebase transport-agnostic
- **Module registry** (`modules.ts`) -- Static maps of Cosmos SDK modules with metadata and handler functions
- **Query/transaction routing** (`cosmos.ts`) -- Routes `(module, subcommand, args)` to per-module handlers
- **On-chain tool functions** (`tools/`) -- `getBalance`, `fundCredits`, `stopApp` (used by the lease package)
- **Server utilities** (`server-utils.ts`) -- `withErrorHandling`, `jsonResponse`, `bigIntReplacer`, `sanitizeForLogging`
- **Wallet providers** (`wallet/`) -- `MnemonicWalletProvider` (BIP-39), `signArbitraryWithAmino` (ADR-036)
- **Logger** (`logger.ts`) -- Leveled logger (stderr output, configurable via `LOG_LEVEL` env var)
- **Retry** (`retry.ts`) -- Exponential backoff with transient/permanent error classification
- **Validation** (`validation.ts`) -- Input validation helpers (`requireString`, `requireUuid`, `parseArgs`, etc.)

## Supported modules

| Module | Query | Transaction |
|--------|:-----:|:-----------:|
| bank | yes | yes |
| staking | yes | yes |
| distribution | yes | yes |
| gov | yes | yes |
| billing | yes | yes |
| sku | yes | yes |
| group | yes | yes |
| wasm | yes | yes |
| auth | yes | -- |
| manifest | -- | yes |

## Usage

```typescript
import {
  CosmosClientManager,
  cosmosQuery,
  cosmosTx,
  createValidatedConfig,
} from '@manifest-network/manifest-mcp-core';

const config = createValidatedConfig({
  chainId: 'manifest-1',
  rpcUrl: 'https://your-rpc-endpoint/',
  gasPrice: '0.01umfx',
  addressPrefix: 'manifest',
});
```

## Build

```bash
npm run build    # tsdown (platform: neutral)
npm run lint     # tsc --noEmit
npm run test     # vitest
```

## License

MIT
npm package: @manifest-network/manifest-mcp-cosmwasm
Description: MCP server for Manifest MFX-to-PWR converter contract operations
Author: Felix C. Morency
Latest version: 0.5.0

# @manifest-network/manifest-mcp-cosmwasm

MCP server for Manifest MFX-to-PWR converter contract operations. Registers 2 tools for querying conversion rates and executing token conversions via the on-chain CosmWasm converter contract.

## Installation

```bash
npm install @manifest-network/manifest-mcp-cosmwasm
```

## Tools

| Tool | Description |
|------|-------------|
| `get_mfx_to_pwr_rate` | Get the current MFX-to-PWR conversion rate and optionally preview a conversion amount |
| `convert_mfx_to_pwr` | Convert MFX tokens to PWR via the on-chain converter contract |

## Usage

### As an MCP server (via node package)

See [`packages/node/README.md`](https://github.com/manifest-network/manifest-mcp-mono/blob/main/packages/node/README.md) for CLI usage and MCP client integration.

Requires the `MANIFEST_CONVERTER_ADDRESS` environment variable set to the CosmWasm converter contract address.

### As a library

```typescript
import { CosmwasmMCPServer } from '@manifest-network/manifest-mcp-cosmwasm';

const server = new CosmwasmMCPServer({
  config,            // ManifestMCPConfig from core
  walletProvider,    // WalletProvider from core
  converterAddress,  // CosmWasm converter contract address
});
```

## Build

```bash
npm run build    # tsdown (platform: neutral)
npm run lint     # tsc --noEmit
npm run test     # vitest
```

## License

MIT
npm package: @manifest-network/manifest-mcp-fred
Description: MCP server for Manifest provider (Fred) operations (deploy, status, logs, restart, update)
Author: Felix C. Morency
Latest version: 0.5.0

# @manifest-network/manifest-mcp-fred

MCP server for Manifest provider (Fred) operations. Registers 8 tools for app deployment, status, logs, restart, update, diagnostics, and releases. Composes on-chain operations with off-chain provider HTTP calls using ADR-036 authentication.

This package also **exports all tool functions and HTTP clients** for use by library consumers without requiring the MCP protocol.

## Installation

```bash
npm install @manifest-network/manifest-mcp-fred
```

## Tools

| Tool | Description |
|------|-------------|
| `browse_catalog` | Browse available providers and service tiers with health checks |
| `deploy_app` | Deploy a new application (create lease + deploy container) |
| `app_status` | Get detailed status for a deployed app by lease UUID |
| `get_logs` | Get logs for a deployed app by lease UUID |
| `restart_app` | Restart a deployed app via the provider |
| `update_app` | Update a deployed app with a new manifest |
| `app_diagnostics` | Get provision diagnostics for a deployed app |
| `app_releases` | Get release/version history for a deployed app |

## Usage

### As an MCP server (via node package)

See [`packages/node/README.md`](https://github.com/manifest-network/manifest-mcp-mono/blob/main/packages/node/README.md) for CLI usage and MCP client integration.

### As a library

```typescript
// Use the MCP server class
import { FredMCPServer } from '@manifest-network/manifest-mcp-fred';

const server = new FredMCPServer({
  config,          // ManifestMCPConfig from core
  walletProvider,  // WalletProvider from core
});

// Or use individual tool functions and HTTP clients directly
import { deployApp, browseCatalog } from '@manifest-network/manifest-mcp-fred';
import { createAuthToken } from '@manifest-network/manifest-mcp-fred';
```

### HTTP clients

The package contains three HTTP client modules:

- **`http/auth.ts`** -- ADR-036 token construction. Pure functions that build sign messages and assemble base64 bearer tokens. No network calls.
- **`http/provider.ts`** -- Provider API client: `uploadLeaseData()`, `getLeaseConnectionInfo()`, `getProviderHealth()`. All provider URLs require HTTPS (localhost HTTP allowed for development).
- **`http/fred.ts`** -- Fred API client: `getLeaseStatus()`, `getLeaseLogs()`, `getLeaseProvision()`, `restartLease()`, `updateLease()`, `getLeaseReleases()`, `getLeaseInfo()`, and `pollLeaseUntilReady()`.

## Build

```bash
npm run build    # tsdown (platform: neutral)
npm run lint     # tsc --noEmit
npm run test     # vitest
```

## License

MIT
npm package: @manifest-network/manifest-mcp-lease
Description: MCP server for Manifest on-chain lease operations (billing, SKU, credits)
Author: Felix C. Morency
Latest version: 0.5.0

# @manifest-network/manifest-mcp-lease

MCP server for Manifest on-chain lease operations. Registers 6 tools for credit management, lease queries, SKUs, and providers. Performs purely on-chain operations -- no off-chain HTTP calls.

## Installation

```bash
npm install @manifest-network/manifest-mcp-lease
```

## Tools

| Tool | Description |
|------|-------------|
| `credit_balance` | Query on-chain credit balance |
| `fund_credit` | Send tokens to the billing account |
| `leases_by_tenant` | List leases for the current account by state |
| `close_lease` | Close a lease on-chain |
| `get_skus` | List available SKUs |
| `get_providers` | List available providers |

## Usage

### As an MCP server (via node package)

See [`packages/node/README.md`](https://github.com/manifest-network/manifest-mcp-mono/blob/main/packages/node/README.md) for CLI usage and MCP client integration.

### As a library

```typescript
import { LeaseMCPServer } from '@manifest-network/manifest-mcp-lease';

const server = new LeaseMCPServer({
  config,          // ManifestMCPConfig from core
  walletProvider,  // WalletProvider from core
});
```

## Build

```bash
npm run build    # tsdown (platform: neutral)
npm run lint     # tsc --noEmit
npm run test     # vitest
```

## License

MIT
npm package: @manifest-ui/primitive-button
Description: **@manifest-ui/primitive-button** is an Accessible `Button` component primitive.
Author: project44
Latest version: 0.0.0

# @manifest-ui/primitive-button

**@manifest-ui/primitive-button** is an Accessible `Button` component primitive.

<p><br /></p>

```sh
# with npm
npm install @manifest-ui/primitive-button

# with yarn
yarn add @manifest-ui/primitive-button
```

<p><br /></p>

```jsx
import { Button } from "@manifest-ui/primitive-button";

export default function App() {
  return (
    <Button>Click me</Button>
  );
}
```

<p><br /></p>

## Documentation

For full documentation, visit [zeroheight](https://zeroheight.com/27d9b4710).

## Contributing

Please follow our [contributing guidelines](./CONTRIBUTING.md).

## Authors

- Brandon Clark ([@yhbrandon](https://twitter.com/yhbrandon)) - [project44](https://project44.com)
- _Could be you!_ DM me on Twitter if you are interested in joining our team 🎉

## License

Licensed under the MIT License, Copyright © 2021-present project44.

See [LICENSE](./LICENSE.md) for more information.

[project44]: https://project44.com
npm package: @manifest-ui/tokens
Description: Design tokens for manifest-ui projects
Author: project44
Latest version: 0.3.0

# @manifest-ui/tokens

Design tokens for manifest-ui projects

## Installation

```sh
yarn add @manifest-ui/tokens
```

## Usage

Use the `getToken` function to return the token value.

```ts
import { getToken } from '@manifest-ui/tokens';

const backgroundColor = getToken('color-background-primary');
```

### Raw Values

You can also access the raw token value, however, this is not recommended as these are subject to
change.

```ts
import { COLOR_BACKGROUND_PRIMARY } from '@manifest-ui/tokens';
```
npm package: @manifest-ui/vessel
Description: Pre-packaged configs for the Babel, ESLint, Jest, Prettier, and TypeScript drivers and developer tools. Inspired by [@beemo/dev](https://github.com/beemojs/dev).
Author: project44
Latest version: 0.3.1

# Vessel - Development configuration module

Pre-packaged configs for the Babel, ESLint, Jest, Prettier, and TypeScript drivers and developer
tools. Inspired by [@beemo/dev](https://github.com/beemojs/dev).

## Installation

```bash
yarn add --dev @manifest-ui/vessel-dev
```

## Setup

Create a `.config/beemo.ts` file in the root of your project that configures
`@manifest-ui/vessel-dev` as the configuration module. Be sure to enable all drivers and any
settings.

```ts
// .config/beemo.ts
export default {
  module: '@manifest-ui/vessel-dev',
  drivers: ['babel', 'eslint', 'jest', 'prettier', 'typescript'],
  settings: {},
};
```

### Settings

The following Beemo `settings` can be defined and will be passed to applicable drivers.

- `node` (`boolean`) - Current project will target Node.js instead of the browser. Defaults to
  `false`.
- `projects` (`boolean | string[]`) - Enable Jest projects. If `true` is passed, will be resolved
  using workspaces, otherwise requires an array of explicit strings. Defaults to `false`.
- `next` (`boolean`) - Enable Next.js for all drivers. Defaults to `false`.
- `react` (`boolean | classic | automatic`) - Enable React and JSX support for all drivers. Defaults
  to `false`.

### Overrides

If you would like to override a driver config, create a `.config/beemo/<driver>.ts` file in the root
of the project.
[View the official Beemo docs for more information](https://beemo.dev/docs/consumer#overriding-configs).

```ts
// .config/beemo/eslint.ts
export default {
  rules: {
    'no-param-reassign': 'off',
  },
};
```

## Drivers

The following drivers are directly supported in this configuration module, and automatically passed
common command line options when being ran.

- Babel
- ESLint
- Jest
- Prettier
- TypeScript

> Please refer to their documentation for more information on how each one is configured.

## Scaffolds

Once your project has been configured to use Beemo, you can scaffold specific files using our
built-in templates.

### project/dotfiles

Will scaffold common dotfiles like `.gitignore`.

```bash
beemo scaffold project dotfiles
```

### project/package

Will append fields to the root `package.json`.

- Adds `scripts` for common actions like linting, testing, etc.

```bash
beemo scaffold project package
```
npm package: @manifest-ui/vessel-config-babel
Description: Babel configuration for beemo.
Author: project44
Latest version: 0.1.0

# Vessel - Babel config

A Project44 Beemo Babel config based on `babel-preset-Vessel`.

## Installation

```bash
yarn install --dev @babel/core @beemo/core @beemo/driver-babel @manifest-ui/vessel-config-babel
```

## Usage

Create a `configs/babel.ts` file in your Beemo configuration module that re-exports this config.

```ts
export { default } from '@manifest-ui/vessel-config-babel';
```

## Settings

The following `settings` can be defined and will be passed to the preset.

- `react` (`boolean | classic | automatic`) - Enable the React plugin and the defined JSX runtime.

```ts
export default {
  module: '<config-module>',
  drivers: ['babel'],
  settings: {
    react: 'automatic',
  },
};
```
npm package: @manifest-ui/vessel-config-eslint
Description: ESLint configuration for beemo.
Author: project44
Latest version: 0.1.0

# Vessel - ESLint config

A Project44 Beemo ESLint config based on `eslint-config-vessel`.

## Installation

```bash
yarn install --dev eslint @beemo/core @beemo/driver-eslint @manifest-ui/vessel-config-eslint
```

## Usage

Create a `configs/eslint.ts` file in your Beemo configuration module that re-exports this config.

```ts
export { default } from '@manifest-ui/vessel-config-eslint';
```

## Settings

The following `settings` can be defined and will be passed to the config.

- `react` (`boolean | classic | automatic`) - Enable React rules. Defaults to `false`.

```ts
export default {
  module: '<config-module>',
  drivers: ['eslint'],
  settings: {
    react: 'automatic',
  },
};
```
npm package: @manifest-ui/vessel-config-jest
Description: Jest configuration for beemo.
Author: project44
Latest version: 0.1.0

# Vessel - Jest config

A Project44 Beemo Jest config based on `jest-preset-vessel`.

## Installation

```bash
yarn install --dev jest @beemo/core @beemo/driver-jest @manifest-ui/vessel-config-jest
```

## Usage

Create a `configs/jest.ts` file in your Beemo configuration module that re-exports this config.

```ts
export { default } from '@manifest-ui/vessel-config-jest';
```

## Settings

The following `settings` can be defined to customize Jest even further.

- `projects` (`boolean | string[]`) - Enable Jest projects. If `true` is passed, will be resolved
  using workspaces, otherwise requires an array of explicit strings. Defaults to `false`.
- `react` (`boolean | classic | automatic`) - Set the testing environment to `jsdom` to support
  React. Defaults to `false`.

```ts
export default {
  module: '<config-module>',
  drivers: ['jest'],
  settings: {
    react: true,
  },
};
```
npm package: @manifest-ui/vessel-config-prettier
Description: Prettier configuration for beemo.
Author: project44
Latest version: 0.1.0

# Vessel - Prettier config

A Project44 Beemo Prettier config based on `prettier-config-vessel`.

## Installation

```bash
yarn install --dev prettier @beemo/core @beemo/driver-prettier @manifest-ui/vessel-config-prettier
```

## Usage

Create a `configs/prettier.ts` file in your Beemo configuration module that re-exports this config.

```ts
export { default } from '@manifest-ui/vessel-config-prettier';
```
npm package: @manifest-ui/vessel-config-typescript
Description: TypeScript configuration for beemo.
Author: project44
Latest version: 0.1.0

# Vessel - TypeScript config

A Project44 Beemo TypeScript config based on `tsconfig-vessel`.

## Installation

```bash
yarn install --dev typescript @beemo/core @beemo/driver-typescript @manifest-ui/vessel-config-typescript
```

> Config will automatically assume project references are being used if a project is using
> workspaces.

## Usage

Create a `configs/typescript.ts` file in your Beemo configuration module that re-exports this config
with your own `include`, `exclude`, etc.

```ts
import config from '@manifest-ui/vessel-config-typescript';

export default {
  ...config,
  include: ['src/**/*'],
};
```

## Settings

The following `settings` can be defined and will be enable compiler options.

- `react` (`boolean | classic | automatic`) - Enable React (or React Native) syntax with the defined
  JSX runtime. Defaults to `false`.

```ts
export default {
  module: '<config-module>',
  drivers: ['typescript'],
  settings: {
    react: 'automatic',
  },
};
```
npm package: @manifest-ui/vessel-dev
Description: CLI for JavaScript and Typescript projects
Author: project44
Latest version: 0.2.0

# Vessel - Development configuration module

Pre-packaged configs for the Babel, ESLint, Jest, Prettier, and TypeScript drivers and developer
tools. Inspired by [@beemo/dev](https://github.com/beemojs/dev).

## Installation

```bash
yarn add --dev @manifest-ui/vessel-dev
```

## Setup

Create a `.config/beemo.ts` file in the root of your project that configures
`@manifest-ui/vessel-dev` as the configuration module. Be sure to enable all drivers and any
settings.

```ts
// .config/beemo.ts
export default {
  module: '@manifest-ui/vessel-dev',
  drivers: ['babel', 'eslint', 'jest', 'prettier', 'typescript'],
  settings: {},
};
```

### Settings

The following Beemo `settings` can be defined and will be passed to applicable drivers.

- `node` (`boolean`) - Current project will target Node.js instead of the browser. Defaults to
  `false`.
- `projects` (`boolean | string[]`) - Enable Jest projects. If `true` is passed, will be resolved
  using workspaces, otherwise requires an array of explicit strings. Defaults to `false`.
- `next` (`boolean`) - Enable Next.js for all drivers. Defaults to `false`.
- `react` (`boolean | classic | automatic`) - Enable React and JSX support for all drivers. Defaults
  to `false`.

### Overrides

If you would like to override a driver config, create a `.config/beemo/<driver>.ts` file in the root
of the project.
[View the official Beemo docs for more information](https://beemo.dev/docs/consumer#overriding-configs).

```ts
// .config/beemo/eslint.ts
export default {
  rules: {
    'no-param-reassign': 'off',
  },
};
```

## Drivers

The following drivers are directly supported in this configuration module, and automatically passed
common command line options when being ran.

- Babel
- ESLint
- Jest
- Prettier
- TypeScript

> Please refer to their documentation for more information on how each one is configured.

## Scaffolds

Once your project has been configured to use Beemo, you can scaffold specific files using our
built-in templates.

### project/dotfiles

Will scaffold common dotfiles like `.gitignore`.

```bash
beemo scaffold project dotfiles
```

### project/package

Will append fields to the root `package.json`.

- Adds `scripts` for common actions like linting, testing, etc.

```bash
beemo scaffold project package
```
npm package: @manifesto-ai/app
Description: Manifesto App - Facade and orchestration layer over the Manifesto protocol stack
Author: eggplantiny
Latest version: 2.6.0
Deprecated: Deprecated compatibility package. Use @manifesto-ai/sdk as canonical public entrypoint. See https://docs.manifesto-ai.dev/guides/migrate-app-to-sdk

ERROR: No README data found!
npm package: @manifesto-ai/engine
Description: Core DSL engine - expression evaluator, dependency tracker, schema loader
Author: eggp
Latest version: 0.0.1

# @manifesto-ai/engine

The Manifesto engine provides a framework-agnostic runtime that executes Manifesto schemas. It combines expression evaluation, dependency tracking, form/list runtimes, schema loading, and legacy system adaptation into one package.

## Contents
- **Expression Evaluator**: Safe Mapbox-style expression runner with operator registry, depth/timeout guards, and debug logging.
- **Reactive Dependency Tracker**: DAG-based tracker that recomputes only the fields affected by a change.
- **Form Runtime**: Manages form state, coercion/validation against Entity schemas, reactions, and side effects (navigation, API-driven options, emits).
- **List Runtime**: Handles list views with pagination, sorting, filtering, and expression-driven column metadata.
- **Schema Loader**: Fetches and validates schemas with caching and TTL control.
- **Legacy Adapter**: Anti-corruption layer that transforms requests/responses via pipelines for SOAP/XML/legacy APIs.

## Quickstart
```ts
import { createFormRuntime } from '@manifesto-ai/engine'
import { productView, productEntity } from './schemas'

const runtime = createFormRuntime(productView, {
  entitySchema: productEntity,
  initialValues: { name: 'Sample', price: 100 },
  context: { user: { id: 'u1' } },
})

const initResult = runtime.initialize()
if (initResult._tag === 'Ok') {
  runtime.dispatch({ type: 'FIELD_CHANGE', fieldId: 'price', value: 120 })
  console.log(runtime.getState())
}
```

For detailed APIs, see `docs/api-reference/engine.md`.
npm package: @manifesto-ai/governance
Description: Manifesto Governance - decorator runtime for legitimacy, approval, and governed execution
Author: eggplantiny
Latest version: 3.7.0

# @manifesto-ai/governance

> Decorator runtime for legitimacy, approval, and governed execution.

`@manifesto-ai/governance` is the package that turns a composable manifesto into a governed world. Its canonical public entry is `withGovernance(manifesto, config)`.

> **Current Contract Note:** The current package contract is [docs/governance-SPEC.md](docs/governance-SPEC.md). The v2.0.0 governance spec remains as the historical service-first baseline.

## Canonical Runtime Path

```ts
import { createManifesto } from "@manifesto-ai/sdk";
import { createInMemoryLineageStore, withLineage } from "@manifesto-ai/lineage";
import { withGovernance } from "@manifesto-ai/governance";

const governed = withGovernance(
  withLineage(createManifesto<CounterDomain>(schema, effects), {
    store: createInMemoryLineageStore(),
  }),
  {
    bindings,
    execution: {
      projectionId: "counter",
      deriveActor(intent) {
        return { actorId: "agent:demo", kind: "agent" };
      },
      deriveSource(intent) {
        return { kind: "agent", eventId: intent.intentId };
      },
    },
  },
).activate();

const proposal = await governed.proposeAsync(
  governed.createIntent(governed.MEL.actions.increment),
);
```

## What This Package Owns

- `withGovernance()` and the activated `GovernanceInstance`
- proposal lifecycle and authority evaluation
- pending human/tribunal resolution through `approve()` / `reject()`
- governance decision records and post-commit governance events
- lineage-preserving query access such as `getWorldSnapshot()`, `getLatestHead()`, and `getBranches()`
- low-level governance stores, services, authority handlers, and intent-instance helpers via `@manifesto-ai/governance/provider`

## What Changes After Governance Activation

- direct `dispatchAsync` and `commitAsync` no longer exist
- the canonical state-change path becomes `proposeAsync() -> approve()/reject()`
- lineage must be composed before governance activation
- visible snapshots publish only after approved execution seals successfully
- `getWorldSnapshot(worldId)` remains the stored sealed canonical snapshot lookup; `restore(worldId)` remains the normalized resume path inherited from lineage

## Low-Level Surface Still Available

The provider entry point remains public for lower-level tooling and protocol tests:

- `@manifesto-ai/governance/provider`
- `createGovernanceService()`
- `createGovernanceEventDispatcher()`
- `createAuthorityEvaluator()`
- authority handlers and lifecycle types

`createInMemoryGovernanceStore()` also remains available from the root package as a consumer-safe bootstrap helper.

Those are no longer the canonical application entry story.

## Docs

- [Docs Landing](docs/README.md)
- [Governance Guide](docs/GUIDE.md)
- [Governance Specification](docs/governance-SPEC.md)
- [Historical v2 Baseline](docs/governance-SPEC-2.0.0v.md)
- [Historical v1 Baseline](docs/governance-SPEC-1.0.0v.md)
- [VERSION-INDEX](docs/VERSION-INDEX.md)
npm package: @manifesto-ai/lineage
Description: Manifesto Lineage - decorator runtime for seal-aware continuity, history, and restore
Author: eggplantiny
Latest version: 3.7.0

# @manifesto-ai/lineage

> Seal-aware continuity for the ADR-017 decorator runtime.

`@manifesto-ai/lineage` is the package that adds time, history, and restore to a composable manifesto.

> **Current Contract Note:** The current package contract is [docs/lineage-SPEC.md](docs/lineage-SPEC.md). The v2 lineage spec remains as the historical service-first baseline.

## What This Package Owns

- `withLineage(createManifesto(...), config).activate()`
- lineage-aware `commitAsync` that seals before publication
- restore, head, branch, and world queries on the activated runtime
- `getWorldSnapshot(worldId)` for stored sealed canonical snapshot lookup
- `getLineage()` for DAG inspection on the activated runtime
- sealing substrate and the provider surface
- deterministic world identity, branch semantics, and restore normalization

## Canonical Path

```ts
import { createManifesto } from "@manifesto-ai/sdk";
import { withLineage, createInMemoryLineageStore } from "@manifesto-ai/lineage";

const manifesto = createManifesto<CounterDomain>(schema, effects);
const lineage = withLineage(manifesto, {
  store: createInMemoryLineageStore(),
}).activate();

await lineage.commitAsync(
  lineage.createIntent(lineage.MEL.actions.increment),
);

const head = await lineage.getLatestHead();
if (head) {
  await lineage.restore(head.worldId);
}
```

## Low-Level Usage

Use `@manifesto-ai/lineage/provider` when you need `LineageService`, `LineageStore`, prepared commits, or custom persistence without the activated runtime wrapper.

## Docs

- [Docs Landing](docs/README.md)
- [Lineage Guide](docs/GUIDE.md)
- [Lineage Specification](docs/lineage-SPEC.md)
- [Historical v2 Service-First SPEC](docs/lineage-SPEC-2.0.0v.md)
- [VERSION-INDEX](docs/VERSION-INDEX.md)
npm package: @manifesto-ai/runtime
Description: Manifesto Runtime - Internal execution orchestration engine
Author: eggplantiny
Latest version: 0.1.3

# @manifesto-ai/runtime

> **Runtime** is the internal orchestration engine for the Manifesto protocol stack.

> **Internal Package:** This package is not intended for direct consumption. Use `@manifesto-ai/sdk`.

---

## Overview

Runtime sits between SDK and protocol layers and executes the action lifecycle.

```text
SDK (public API)
    |
    v
Runtime (orchestration)
    |
    +--> Core (compute)
    +--> Host (execute)
    +--> World (govern)
```

---

## Responsibilities

- 5-stage action pipeline: prepare → authorize → execute → persist → finalize
- Shared type and error definitions
- Policy routing and scope validation
- Memory hub integration and context freezing
- Branch and world-store orchestration
- System runtime handling (`system.*` actions)

---

## Non-Responsibilities

- Public API contract design (SDK responsibility)
- Pure semantic computation (Core responsibility)
- Effect IO execution semantics (Host responsibility)
- Governance decisions and lineage policy (World responsibility)

---

## Installation

Runtime is consumed transitively by SDK.

```bash
pnpm add @manifesto-ai/sdk
```

---

## Relationship with Other Packages

| Relationship | Package | How |
|--------------|---------|-----|
| Consumed by | `@manifesto-ai/sdk` | SDK delegates orchestration to Runtime |
| Depends on | `@manifesto-ai/core` | Pure computation |
| Depends on | `@manifesto-ai/host` | Effect execution |
| Depends on | `@manifesto-ai/world` | Governance and lineage |
| Depends on | `@manifesto-ai/compiler` | MEL compilation |

---

## Documentation

- [runtime-SPEC-v0.1.0.md](docs/runtime-SPEC-v0.1.0.md)
- [VERSION-INDEX.md](docs/VERSION-INDEX.md)
- [ADR-008](../../docs/internals/adr/008-sdk-first-transition-and-app-retirement.md)

---

## License

[MIT](../../LICENSE)
npm package: @manifesto-ai/sdk
Description: Manifesto SDK - Activation-first public API for the base runtime
Author: eggplantiny
Latest version: 3.8.0

# @manifesto-ai/sdk

> Activation-first entry point for Manifesto applications.

`@manifesto-ai/sdk` is the default package for applications that start with `createManifesto()`.

> **Current Contract Note:** The current SDK contract is the living v3.6.0 activation-first model documented in [docs/sdk-SPEC.md](docs/sdk-SPEC.md). It includes typed `createIntent()` object binding, intent explanation reads, `@manifesto-ai/sdk/extensions`, and `createSimulationSession(instance)`.

## When to Use It

Use the SDK when you want:

- the shortest path to a running base runtime
- typed intent creation through `MEL.actions.*`
- `dispatchAsync`, subscriptions, legality queries, explanation reads, dry-run simulation, and snapshot reads in one package
- projected Snapshot reads by default, with canonical inspection available explicitly
- safe post-activation arbitrary-snapshot tooling through `@manifesto-ai/sdk/extensions`

## Smallest Example

```typescript
import { createManifesto } from "@manifesto-ai/sdk";

const manifesto = createManifesto<CounterDomain>(counterSchema, {});
const instance = manifesto.activate();

const intent = instance.createIntent(instance.MEL.actions.increment);
await instance.dispatchAsync(intent);
console.log(instance.getSnapshot().data.count);
```

Base runtime reads cover availability, dispatchability, intent explanation, dry-run simulation, subscriptions, events, and both projected and canonical snapshot access.

If you need review, approval, or sealed history later, compose `@manifesto-ai/lineage` and `@manifesto-ai/governance` before `activate()`. If you need arbitrary-snapshot tooling after activation, use `@manifesto-ai/sdk/extensions`.

## Docs

- [Public API Reference](../../docs/api/sdk.md)
- [SDK Guide](docs/GUIDE.md)
- [SDK Specification](docs/sdk-SPEC.md)
- [VERSION-INDEX](docs/VERSION-INDEX.md)