Metadata-Version: 2.4
Name: intentframe-native-kit
Version: 0.1.0
Summary: IntentFrame first-party kit — action registry, native bundles, executor packs (console/posix/macos), and resource registry
Project-URL: Homepage, https://github.com/intentframe/intentframe
Project-URL: Repository, https://github.com/intentframe/intentframe
Project-URL: Issues, https://github.com/intentframe/intentframe/issues
Author: IntentFrame Contributors
License-Expression: Apache-2.0
License-File: LICENSE
Keywords: adapters,agents,ai,bundles,intentframe,security
Classifier: Development Status :: 3 - Alpha
Classifier: Intended Audience :: Developers
Classifier: Programming Language :: Python :: 3
Classifier: Topic :: Security
Requires-Python: >=3.14
Requires-Dist: command-shield==0.1.0
Requires-Dist: fastapi
Requires-Dist: httpx>=0.28.1
Requires-Dist: intentframe-bundle-sdk==0.1.0
Requires-Dist: intentframe-executor-sdk==0.1.0
Requires-Dist: pydantic>=2.12.5
Description-Content-Type: text/markdown

# intentframe-native-kit

The first-party kit for [IntentFrame](https://github.com/intentframe/intentframe).
It bundles the reference implementations that ship out of the box:

- **action registry** — the canonical action catalog, categories, and domain schemas
- **native bundles** — the deterministic action/domain bundles (files, terminal, email, finance, deletion, …)
- **executor packs** — `console`, `posix`, and `macos` capability adapters
- **resource registry** — the deny-floor and resource model
- packaged service-graph profiles (`supervisor_profile.yaml`, `edge_profile.yaml`, `core.yaml`)

The executor packs and bundles register themselves through the
`intentframe.executor_packs` and `intentframe.bundles` entry-point groups, so
the executor service and bundle loader discover them automatically once this
package is installed. Built on `intentframe-bundle-sdk`,
`intentframe-executor-sdk`, and `command-shield`.

```bash
pip install intentframe-native-kit
```

## License

`intentframe-native-kit` is distributed under the Apache License 2.0.

## Email integration (optional)

Email bundles and macOS mail adapters call the product-side EDI `EmailClient` via
**lazy imports** — nothing email-related is imported at package install time.

- `email-sync-service` (`external_data_ingestion`) is **not** on PyPI and is **not**
  declared in this package’s dependencies.
- A normal `pip install intentframe-native-kit` is enough for all non-email actions.
- To use email actions, your deployment must also provide EDI (for example the
  in-repo `external_data_ingestion` tree used by the IntentFrame product). Without
  it, importing or running those code paths fails at **use time** with
  `ImportError`, not at install time.

See [docs/licensing.md](../../docs/licensing.md) for the publishable `packages/`
surface vs product-facing modules.
