> For the complete documentation index, see [llms.txt](https://quantumphp.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://quantumphp.gitbook.io/docs/packages/encryption/architecture.md).

# Architecture

The package uses a simple factory-plus-adapter design.

## Resolution flow

A typical helper call follows this path:

```
crypto_encode()/crypto_decode()
  -> CryptorFactory::get($type)
  -> Di-managed CryptorFactory instance
  -> CryptorFactory::resolve($type)
  -> Cryptor(new <adapter>())
  -> adapter->encrypt() / adapter->decrypt()
```

## `CryptorFactory` lifecycle

`CryptorFactory::get()` uses `Quantum\Di\Di` as its singleton boundary:

1. if `CryptorFactory` is not registered yet, it registers the class
2. it resolves the factory from the container with `Di::get(self::class)`
3. it calls `resolve($type)` on that shared factory instance

Inside the factory, `$instances` memoizes one `Cryptor` per type string.

Practical effect:

* repeated symmetric requests reuse the same symmetric `Cryptor`
* repeated asymmetric requests reuse the same asymmetric `Cryptor`
* both lifetimes are tied to the current DI container

## `Cryptor` wrapper behavior

`Quantum\Encryption\Cryptor` stores exactly one `EncryptionInterface` adapter.

It exposes:

* `getAdapter()` to inspect the concrete adapter
* `isAsymmetric()` as a concrete-type check against `AsymmetricEncryptionAdapter`
* `__call()` to forward runtime method calls to the adapter

`__call()` is guarded with `method_exists(...)`. Calling an unsupported method throws `CryptorException::methodNotSupported($method, <adapter class>)`.

In practice, the intended public methods are still just:

* `encrypt(string $plain): string`
* `decrypt(string $encrypted): string`

## Factory adapter map

`CryptorFactory::ADAPTERS` is a fixed constant map:

* `symmetric` -> `SymmetricEncryptionAdapter`
* `asymmetric` -> `AsymmetricEncryptionAdapter`

There is no extension point in the current package for replacing this map at runtime.

## State model differences

### Symmetric adapter state

The symmetric adapter stores only one piece of state: the resolved application key.

### Asymmetric adapter state

The asymmetric adapter stores a generated public/private key pair in object properties.

Because the keys are generated inside `__construct()`, the object's lifetime is the key lifetime. This is the main architectural constraint of the package.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://quantumphp.gitbook.io/docs/packages/encryption/architecture.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.