Rules for enforcing import boundaries between architectural layers and packages
Built-in rules for detecting connascence of meaning — shared string and numeric literals across package boundaries
[](https://www.npmjs.com/package/@aws-sdk/middleware-sdk-s3) [](https://www.npmjs.com/package/@
Core functions & classes shared by multiple AWS SDK clients.
Types for the AWS SDK
Utilities to help with endpoint resolution
[](https://www.npmjs.com/package/@aws-sdk/middleware-logger) [](https://www.npmjs.com/package/@
[](https://www.npmjs.com/package/@aws-sdk/middleware-host-header) [](https://www.npmj
AWS credential provider that sources credentials from known environment variables
AWS credential provider that exchanges a resolved SSO login token file for temporary AWS credentials
AWS credential provider that sources credential_process from ~/.aws/credentials and ~/.aws/config
AWS credential provider for containers and HTTP sources
[](https://www.npmjs.com/package/@aws-sdk/middleware-user-agent) [](https://www.npmjs.c
[](https://www.npmjs.com/package/@aws-sdk/middleware-expect-continue) [](http
AWS credential provider that sources credentials from ~/.aws/credentials and ~/.aws/config
[](https://www.npmjs.com/package/@aws-sdk/middleware-flexible-checksums) [](https://www.npmjs.com/package/@aws-sdk/signature-v4-multi-region) [](https:/
[](https://www.npmjs.com/package/@aws-sdk/util-user-agent-node) [](https://www.npmjs.com/
AWS credential provider that calls STS assumeRole for temporary AWS credentials
[](https://www.npmjs.com/package/@aws-sdk/region-config-resolver) [](https://www.npmj
No description provided.
[](https://www.npmjs.com/package/@aws-sdk/middleware-location-constraint) [](https://www.npmjs.com/package/@aws-sdk/middleware-ssec) [](https://www.npmjs.com/package/@aws-sd
[](https://www.npmjs.com/package/@aws-sdk/middleware-recursion-detection) [![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/middleware-recursion-detectio
Core SDK for the MAAT engine — behavioural traits, events, entity store, typed IDs, testing utilities.
Proc-macro derive for maat-sdk entities — generates `Entity` impls from annotated structs.
Network wire protocol for the MAAT engine — postcard frame definitions for client/server communication. Capability-agnostic; capability-specific frames live in their respective capability crates.
Unified façade crate for the MAAT virtual-tabletop engine — the single entry point for plugin and capability authors. Depends on every Layer-2 sub-crate and re-exports a curated prelude.
WASM-side runtime shim for MAAT plugins targeting wasm32-unknown-unknown — host-import declarations + SetupContext/GameContext implementors that forward to the host via postcard-encoded calls.
Game session engine for MAAT — pipeline, session state, fixtures, spatial index, hot-reload registry.
Test harness for MAAT plugin authors — TestHarness, fixture builders, BDD assertion helpers. Plugin authors depend on this only as a [dev-dependency].
Core type vocabulary for the MAAT engine — newtypes, events, traits-as-data, blueprints. Layer 2 of the architecture: a leaf crate with no maat-* dependencies.